ohci and ehci-platform clks, phy and dt support
Get series with b4
b4 am [email protected]Versions newest first · linked by author and title
- v4 Latest posting 2/20 of 2 patches 0 repliesNew
- v4 posting 1/20 of 2 patches 0 repliesSuperseded
Patches in v4 posting 2/2 No applies recorded yet
None of the 2 patches the cover letter announces are in this archive.
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v4 yet.
Cover letter [PATCH v4 0/2] ohci and ehci-platform clks, phy and dt support
Hello.
Quoted 9 lines · Hans de Goede
Quoted 8 lines
Quoted 8 lines
Quoted 4 lines
Quoted 2 lines
Here is v4 of my ohci and ehci-platform clks, phy and dt support patch-set, this version should be 100% ready for merging upstream.
I see you've decided to completely ignore my opinion. NAK, FWIW.
I'm sorry but the whole prefix thing has become a thing of
-ETOOMUCHBIKESHEDDING,
everyone except you seems to be fine with mmio
Quoted 6 lines
Quoted 2 lines
Everyone being couple of people reading this thread? Of which only one
being familiar with the real [EO]HCI hardware? :-)You are aware that I've worked on qemu's USB emulation for 3 years full-time, including things like making the ehci emulation Windows XP compatible and many other hcd emulation fixes?
Then you should have known that all [EO]HCI controllers use MMIO, and it's
pointless to call them "MMIO [EO]HCI controller" in your title and in your "compatible" prop. Because you plainly create an impression that there's some other kind of [EO]HCI controllers out there, e.g. I/O mapped (for which a separate binding would be needed?).
Quoted 1 line
And Alan Stern's credentials speak for themselves.
Yes, I meant Alan by [EO]HCI expert. He's not DT expert, unfortunately, AFAIK.
Quoted 1 line
Comments like this do not really help to get your own comments taken serious.
Well, if nothing else helps... :-(
Quoted 5 lines
Quoted 1 line
The name is just plain stupid if you want to know my real opinion.
Your opinion has been noted, but so far your entire objection seems to be you not liking the name and now calling it stupid, while there have been actually *technical* arguments against the other prefixes.
I didn't hear your reply to my last mail which laid out some plan of
dealing with ehci-ppc-of.c. Your "technical" argument against using "usb-ehci" didn't really make much sense to me and I told you why and what to do to get things right. You chose to not even reply to this and instead post "100% fready for merge" patchset.
Sigh, it's a pity Alistair Popple's patches [1], [2] didn't get merged. He
simply disappeared somewhere.
Quoted 11 lines
Quoted 8 lines
And you've posted v3 with this name used first only what, 1.5 days ago?
Quoted 2 lines
and and one point in time we
need to make a decision and move forward.I see the first version of your patches posted on January 6th, today is
11th (just starting here). You must be in a very big hurry to get this merged, I see. :-)This is not about being in a hurry, this is about not wanting to waste time on what is quickly turning into pure bike-shedding.
Do you think calling other people's opinions "pure bike-shedding" helps
the discussion?
Quoted 6 lines
Quoted 2 lines
Serious changes like this are not really done at such pace. Only the
stuff that someone else has to painfully fix up later... :-(If you're suggestion that the mmio- prefix will cause breakage later now is your time to actually make an actual technical argument. "just plain stupid" does not help to get your comments taken serious.
The worst thing is once the bindings get merged, they're "set in stone"
and it won't be easy to fix, if at all possible... :-(
Quoted 3 lines
Regards,
Hans
[1] http://marc.info/?l=linux-usb&m=138508645219604
[2] http://marc.info/?l=linuxppc-embedded&m=138508628409947