From: tomasz.figa@gmail.com (Tomasz Figa)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 0/2] ohci and ehci-platform clks, phy and dt support
Date: Sun, 12 Jan 2014 14:04:26 +0100 [thread overview]
Message-ID: <52D292DA.8010709@gmail.com> (raw)
In-Reply-To: <52D2064B.3010103@prisktech.co.nz>
Hi,
[Cc'ing DT maintainers directly]
On 12.01.2014 04:04, Tony Prisk wrote:
> On 12/01/14 11:30, Alan Stern wrote:
>> On Fri, 10 Jan 2014, Hans de Goede wrote:
>>
>>> Hi,
>>>
>>> On 01/11/2014 12:50 AM, Sergei Shtylyov wrote:
>>>> Hello.
>>>>
>>>> On 01/11/2014 01:46 AM, Hans de Goede wrote:
>>>>
>>>>> 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 and and one point in
>>> time we
>>> need to make a decision and move forward.
>> If this isn't beating a dead horse... Maybe everyone can agree on a
>> name like ohci-generic or generic-ohci. That seems like a pretty good
>> description of the hardware that the platform driver can handle.
>>
>> Alan Stern
> I prefer the -generic option, although generic- is equally fine - Having
> said that, I don't really care if it's called mmio either (although this
> does seem less 'descriptive').
Grepping over existing dts files, I can find several occurrences of
"usb-ehci" compatible string:
at91sam9g45.dtsi: compatible =
"atmel,at91sam9g45-ehci", "usb-ehci";
at91sam9x5.dtsi: compatible =
"atmel,at91sam9g45-ehci", "usb-ehci";
omap3.dtsi: compatible = "ti,ehci-omap",
"usb-ehci";
omap4.dtsi: compatible = "ti,ehci-omap",
"usb-ehci";
omap5.dtsi: compatible = "ti,ehci-omap",
"usb-ehci";
sama5d3.dtsi: compatible = "atmel,at91sam9g45-ehci",
"usb-ehci";
spear13xx.dtsi: compatible = "st,spear600-ehci", "usb-ehci";
spear13xx.dtsi: compatible = "st,spear600-ehci", "usb-ehci";
spear3xx.dtsi: compatible = "st,spear600-ehci", "usb-ehci";
spear600.dtsi: compatible = "st,spear600-ehci", "usb-ehci";
spear600.dtsi: compatible = "st,spear600-ehci", "usb-ehci";
tegra114.dtsi: compatible = "nvidia,tegra30-ehci", "usb-ehci";
tegra114.dtsi: compatible = "nvidia,tegra30-ehci", "usb-ehci";
tegra20.dtsi: compatible = "nvidia,tegra20-ehci", "usb-ehci";
tegra20.dtsi: compatible = "nvidia,tegra20-ehci", "usb-ehci";
tegra20.dtsi: compatible = "nvidia,tegra20-ehci", "usb-ehci";
tegra30.dtsi: compatible = "nvidia,tegra30-ehci", "usb-ehci";
tegra30.dtsi: compatible = "nvidia,tegra30-ehci", "usb-ehci";
tegra30.dtsi: compatible = "nvidia,tegra30-ehci", "usb-ehci";
Same for "usb-ohci":
arch/arm/boot/dts/at91rm9200.dtsi: compatible =
"atmel,at91rm9200-ohci", "usb-ohci";
arch/arm/boot/dts/at91sam9260.dtsi: compatible =
"atmel,at91rm9200-ohci", "usb-ohci";
arch/arm/boot/dts/at91sam9263.dtsi: compatible =
"atmel,at91rm9200-ohci", "usb-ohci";
arch/arm/boot/dts/at91sam9g45.dtsi: compatible =
"atmel,at91rm9200-ohci", "usb-ohci";
arch/arm/boot/dts/at91sam9n12.dtsi: compatible =
"atmel,at91rm9200-ohci", "usb-ohci";
arch/arm/boot/dts/at91sam9x5.dtsi: compatible =
"atmel,at91rm9200-ohci", "usb-ohci";
arch/arm/boot/dts/lpc32xx.dtsi: compatible =
"nxp,ohci-nxp", "usb-ohci";
arch/arm/boot/dts/omap3.dtsi: compatible =
"ti,ohci-omap3", "usb-ohci";
arch/arm/boot/dts/omap4.dtsi: compatible =
"ti,ohci-omap3", "usb-ohci";
arch/arm/boot/dts/omap5.dtsi: compatible =
"ti,ohci-omap3", "usb-ohci";
arch/arm/boot/dts/sama5d3.dtsi: compatible =
"atmel,at91rm9200-ohci", "usb-ohci";
arch/arm/boot/dts/spear13xx.dtsi: compatible =
"st,spear600-ohci", "usb-ohci";
arch/arm/boot/dts/spear13xx.dtsi: compatible =
"st,spear600-ohci", "usb-ohci";
arch/arm/boot/dts/spear3xx.dtsi: compatible =
"st,spear600-ohci", "usb-ohci";
arch/arm/boot/dts/spear3xx.dtsi: compatible =
"st,spear600-ohci", "usb-ohci";
arch/arm/boot/dts/spear600.dtsi: compatible =
"st,spear600-ohci", "usb-ohci";
arch/arm/boot/dts/spear600.dtsi: compatible =
"st,spear600-ohci", "usb-ohci";
For "usb-ehci" there is even a documentation file [1], while "usb-ohci"
seems to be undocumented.
[1] Documentation/devicetree/bindings/usb/usb-ehci.txt
Aren't they both something that should be accounted for in this series?
Best regards,
Tomasz
next prev parent reply other threads:[~2014-01-12 13:04 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-10 22:46 [PATCH v4 0/2] ohci and ehci-platform clks, phy and dt support Hans de Goede
2014-01-10 22:46 ` [PATCH v4 1/2] ohci-platform: Add support for devicetree instantiation Hans de Goede
2014-01-11 8:37 ` Tony Prisk
2014-01-12 9:17 ` Hans de Goede
2014-01-10 22:46 ` [PATCH v4 2/2] ehci-platform: Add support for clks and phy passed through devicetree Hans de Goede
2014-01-10 23:50 ` [PATCH v4 0/2] ohci and ehci-platform clks, phy and dt support Sergei Shtylyov
2014-01-10 22:52 ` Hans de Goede
2014-01-10 23:08 ` Bjørn Mork
2014-01-11 0:19 ` Sergei Shtylyov
2014-01-10 23:45 ` Bjørn Mork
2014-01-11 0:10 ` Sergei Shtylyov
2014-01-10 23:24 ` Hans de Goede
2014-01-11 1:03 ` Sergei Shtylyov
2014-01-11 22:30 ` Alan Stern
2014-01-12 3:04 ` Tony Prisk
2014-01-12 13:04 ` Tomasz Figa [this message]
2014-01-13 15:54 ` Hans de Goede
2014-01-13 16:06 ` Alan Stern
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52D292DA.8010709@gmail.com \
--to=tomasz.figa@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).