<karlp>
you probably have better sources than me...
<stdint>
yes it does
<stdint>
Oh, it is Chapter 17 MACPHY
<stdint>
a very strange design I think
<stdint>
having a internal PHY and GMAC interface
<stdint>
I often see there are too similar interface in a chip
<stdint>
I found a EHCI controller, DWC2 EHCI controller and HSIC controller for the USB at rk3288
<stdint>
I often wonder what the a design house doing that
paulk-collins has joined #linux-rockchip
jaocb has joined #linux-rockchip
<afaerber>
mmind00: is it still worth pointing out the typo in the subject? ;)
paulk-collins has quit [Remote host closed the connection]
jaocb has quit [Ping timeout: 264 seconds]
<mmind00>
afaerber: where? ... and yes :-)
<afaerber>
mmind00: I'm not seeing the patch on the mailing list... :/
<karlp>
stdint: not taht uncommon, it's fairly similar in micros to have usb HS support, but only have a FS phy built in, need an exteranl ULPI phy for HS
<mmind00>
afaerber: which patch? The PX? ones ... it seems Andy missed including linux-rockchip and only has devicetree + linux-arm-kernel
<afaerber>
ah...
<afaerber>
mmind00: found it, replying with some more comments
<mmind00>
afaerber: ok :-)
<mmind00>
afaerber: trying to dissect the naming here, before we end up with a big mail trail :-) ... as far as I understand it, the px-something are based on their regular counterpart ... i.e. the px2 is a rk3066a with some industrial foo applied (reliability or whatever)
<mmind00>
afaerber: same for px3 = rk3188+industrial-foo (and px5 as well)
<mmind00>
but from the IP core side they are the same it seems
<afaerber>
mmind00: that may well be, it's just done differently elsewhere
<mmind00>
afaerber: no sure I understand you fully ... this was meant with regards to your suggestion for a rk3188-px3.dtsi ... which would essentially be empty, except for maybe a compatible string, which would get overwritten by the board anway
jkstrick_ has joined #linux-rockchip
jkstrick has quit [Ping timeout: 244 seconds]
jkstrick_ has quit [Remote host closed the connection]
jkstrick has joined #linux-rockchip
<afaerber>
mmind00: yes, it would be rather empty currently but provide the right level of abstraction - could be done as follow-up, but I have no PX3 so Rockchip should do it themselves
<mmind00>
afaerber: I asked the "parental units" for advice as well ;-) ... as I'm still prefering the rk3188-px3-evb style and wanted to make sure I'm making dumb decisions: "<arnd> mmind00: I don't think it's important, just pick one or the other. I'd probably go for the more verbose rk3188-px3-evb naming if I had to make the decision"
<mmind00>
"not" making dumb decisions ;-)
<afaerber>
choose whatever you feel is right, I just feel it breaks the scheme in that rk3368-px5-evb.dtb is not an RK3368 based board, even if it borrows IP
paulk-veyron-min has joined #linux-rockchip
<afaerber>
note we're having similar discussions for Amlogic currently
<mmind00>
afaerber: contrary to the apq vs msm thingy, the px5 really is just a rk3368
<afaerber>
about whether we need to duplicate amlogic,meson-gxl-s905x if we already have a second amlogic,s905x string to represent that
<afaerber>
err amlogic,meson-gxl obviously
<afaerber>
mmind00: what's different with msm then?
<mmind00>
afaerber: msm .. with modem, apq without modem
<afaerber>
mmind00: and you said px3 is with industrial, rk3188 without ... same thing, no?
<mmind00>
afaerber: industrial yes, but the soc internals are identical ... you probably only get lifespan guarantees or something
<afaerber>
oh, I thought there was additional IP or something left out
* afaerber
afk
cnxsoft has quit [Quit: cnxsoft]
afaerber has quit [Quit: Ex-Chat]
paulk-veyron-min has quit [Read error: Connection reset by peer]
JohnDoe_71Rus has joined #linux-rockchip
jkstrick has quit [Remote host closed the connection]
jkstrick has joined #linux-rockchip
pulser has quit [Remote host closed the connection]
pulser has joined #linux-rockchip
vetkat has quit [Ping timeout: 265 seconds]
vetkat has joined #linux-rockchip
vetkat has joined #linux-rockchip
jkstrick has quit [Remote host closed the connection]
jkstrick has joined #linux-rockchip
afaerber has joined #linux-rockchip
vagrantc has joined #linux-rockchip
jkstrick has quit [Remote host closed the connection]
jkstrick has joined #linux-rockchip
jkstrick has quit [Remote host closed the connection]
jkstrick has joined #linux-rockchip
matthias_bgg has quit [Quit: Leaving]
jkstrick has quit [Remote host closed the connection]
jkstrick has joined #linux-rockchip
paulk-collins has joined #linux-rockchip
jkstrick has quit [Remote host closed the connection]
afaerber has quit [Quit: Ex-Chat]
jkstrick has joined #linux-rockchip
jkstrick has quit [Remote host closed the connection]
jkstrick has joined #linux-rockchip
jkstrick has quit [Read error: Connection reset by peer]
jkstrick_ has joined #linux-rockchip
jkstrick_ has quit [Remote host closed the connection]
afaerber has joined #linux-rockchip
jkstrick has joined #linux-rockchip
mrueg has quit [Remote host closed the connection]