From: Florian Vaussard <florian.vaussard@epfl.ch>
To: Sricharan R <r.sricharan@ti.com>
Cc: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
tony@atomide.com, rnayak@ti.com, b-cousson@ti.com,
Roger Quadros <rogerq@ti.com>
Subject: Re: [PATCH 2/4] ARM: dts: omap5-uevm: Add USB Host support
Date: Wed, 05 Jun 2013 14:15:36 +0200 [thread overview]
Message-ID: <51AF2BE8.1010402@epfl.ch> (raw)
In-Reply-To: <51AF00F4.3010105@ti.com>
On 06/05/2013 11:12 AM, Sricharan R wrote:
> Hi,
> On Wednesday 05 June 2013 01:29 PM, Florian Vaussard wrote:
>> Hello,
>>
>> Some very minor comments.
>>
>> On 06/05/2013 08:46 AM, Sricharan R wrote:
>>> From: Roger Quadros <rogerq@ti.com>
>>>
>>> Provide the RESET regulators for the USB PHYs, the USB Host
>>> port modes and the PHY devices.
>>>
>>> Also provide pin multiplexer information for the USB host
>>> pins.
>>>
>>> Cc: Roger Quadros <rogerq@ti.com>
>>> Signed-off-by: Roger Quadros <rogerq@ti.com>
>>> [Sricharan R <r.sricharan@ti.com>: Replaced constants with preprocessor macros]
>>> Signed-off-by: Sricharan R <r.sricharan@ti.com>
>>> ---
>>> arch/arm/boot/dts/omap5-uevm.dts | 77 ++++++++++++++++++++++++++++++++++++++
>>> arch/arm/boot/dts/omap5.dtsi | 30 +++++++++++++++
>>> 2 files changed, 107 insertions(+)
>>>
>>> diff --git a/arch/arm/boot/dts/omap5-uevm.dts b/arch/arm/boot/dts/omap5-uevm.dts
>>> index 843a001..cf862df 100644
>>> --- a/arch/arm/boot/dts/omap5-uevm.dts
>>> +++ b/arch/arm/boot/dts/omap5-uevm.dts
>>> @@ -25,6 +25,47 @@
>>> regulator-max-microvolt = <3000000>;
>>> };
>>>
>>> + /* HS USB Port 2 RESET */
>>> + hsusb2_reset: hsusb2_reset_reg {
>>> + compatible = "regulator-fixed";
>>> + regulator-name = "hsusb2_reset";
>>> + regulator-min-microvolt = <3300000>;
>>> + regulator-max-microvolt = <3300000>;
>>> + gpio = <&gpio3 16 GPIO_ACTIVE_HIGH>; /* gpio3_80 HUB_NRESET */
>>> + startup-delay-us = <70000>;
>>> + enable-active-high;
>>> + };
>>> +
>>> + /* HS USB Host PHY on PORT 2 */
>>> + hsusb2_phy: hsusb2_phy {
>>> + compatible = "usb-nop-xceiv";
>>> + reset-supply = <&hsusb2_reset>;
>>> + };
>>> +
>>> + /* HS USB Port 3 RESET */
>>> + hsusb3_reset: hsusb3_reset_reg {
>>> + compatible = "regulator-fixed";
>>> + regulator-name = "hsusb3_reset";
>>> + regulator-min-microvolt = <3300000>;
>>> + regulator-max-microvolt = <3300000>;
>>> + gpio = <&gpio3 15 GPIO_ACTIVE_HIGH>; /* gpio3_79 ETH_NRESET */
>>> + startup-delay-us = <70000>;
>>> + enable-active-high;
>>> + };
>>> +
>>> + /* HS USB Host PHY on PORT 3 */
>>> + hsusb3_phy: hsusb3_phy {
>>> + compatible = "usb-nop-xceiv";
>>> + reset-supply = <&hsusb3_reset>;
>>> + };
>>> +
>>> + /* hsusb2_phy is clocked by FREF_CLK1 i.e. auxclk1 */
>>> + clock_alias {
>>> + clock-name = "auxclk1_ck";
>>> + clock-alias = "main_clk";
>>> + device = <&hsusb2_phy>;
>>> + clock-frequency = <19200000>; /* 19.2 MHz */
>>> + };
>>> };
>>>
>>> &omap5_pmx_core {
>>> @@ -35,6 +76,7 @@
>>> &dmic_pins
>>> &mcbsp1_pins
>>> &mcbsp2_pins
>>> + &usbhost_pins
>>> >;
>>>
>>> twl6040_pins: pinmux_twl6040_pins {
>>> @@ -120,6 +162,32 @@
>>> 0x16c (PIN_INPUT | MUX_MODE1) /* mcspi2_cs */
>>> >;
>>> };
>>> +
>>> + usbhost_pins: pinmux_usbhost_pins {
>>> + pinctrl-single,pins = <
>>> + 0x84 (PIN_INPUT | MUX_MODE0) /* usbb2_hsic_strobe INPUT | MODE 0 */
>>> + 0x86 (PIN_INPUT | MUX_MODE0) /* usbb2_hsic_data INPUT | MODE 0 */
>>
>> Comments are redundant with the constants, so maybe you can leave this part out.
>> Same for a few others below.
>>
> Ok, I agree here for attributes like pulls, i/o etc, comments are now not required.
> But comment is still good to describe just the mux mode functionality ?
> One module will use different pins, like data, clk, gpios, etc. Just MUX_MODEX does not
> complete it..
Yes, the 'usbb2_hsic_strobe' part must stay, only 'INPUT | MODE 0'
should be removed
from comments.
>>> +
>>> + 0x19e (PIN_INPUT | MUX_MODE0) /* usbb3_hsic_strobe INPUT | MODE 0 */
>>> + 0x1a0 (PIN_INPUT | MUX_MODE0) /* usbb3_hsic_data INPUT | MODE 0 */
>>> +
>>> + 0x70 (PIN_OUTPUT | MUX_MODE6) /* gpio3_80 OUTPUT | MODE 6 HUB_NRESET */
>>> + 0x6e (PIN_OUTPUT | MUX_MODE6) /* gpio3_79 OUTPUT | MODE 6 ETH_NRESET */
>>> + >;
>>> + };
>>> +};
>>> +
>>> +&omap5_pmx_wkup {
>>> + pinctrl-names = "default";
>>> + pinctrl-0 = <
>>> + &usbhost_wkup_pins
>>> + >;
>>> +
>>> + usbhost_wkup_pins: pinmux_usbhost_wkup_pins {
>>> + pinctrl-single,pins = <
>>> + 0x1A (PIN_OUTPUT | MUX_MODE0) /* fref_clk1_out OUTPUT | MODE 7 for USB hub clk */
>>
>> Mismatch between constants and comments, which mode should it be?
>>
> MODE 0. I see safe mode for 7. Comment should be corrected.
s/corrected/removed/. This will avoid this kind of inconsistency.
Regards,
Florian
WARNING: multiple messages have this Message-ID (diff)
From: florian.vaussard@epfl.ch (Florian Vaussard)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/4] ARM: dts: omap5-uevm: Add USB Host support
Date: Wed, 05 Jun 2013 14:15:36 +0200 [thread overview]
Message-ID: <51AF2BE8.1010402@epfl.ch> (raw)
In-Reply-To: <51AF00F4.3010105@ti.com>
On 06/05/2013 11:12 AM, Sricharan R wrote:
> Hi,
> On Wednesday 05 June 2013 01:29 PM, Florian Vaussard wrote:
>> Hello,
>>
>> Some very minor comments.
>>
>> On 06/05/2013 08:46 AM, Sricharan R wrote:
>>> From: Roger Quadros <rogerq@ti.com>
>>>
>>> Provide the RESET regulators for the USB PHYs, the USB Host
>>> port modes and the PHY devices.
>>>
>>> Also provide pin multiplexer information for the USB host
>>> pins.
>>>
>>> Cc: Roger Quadros <rogerq@ti.com>
>>> Signed-off-by: Roger Quadros <rogerq@ti.com>
>>> [Sricharan R <r.sricharan@ti.com>: Replaced constants with preprocessor macros]
>>> Signed-off-by: Sricharan R <r.sricharan@ti.com>
>>> ---
>>> arch/arm/boot/dts/omap5-uevm.dts | 77 ++++++++++++++++++++++++++++++++++++++
>>> arch/arm/boot/dts/omap5.dtsi | 30 +++++++++++++++
>>> 2 files changed, 107 insertions(+)
>>>
>>> diff --git a/arch/arm/boot/dts/omap5-uevm.dts b/arch/arm/boot/dts/omap5-uevm.dts
>>> index 843a001..cf862df 100644
>>> --- a/arch/arm/boot/dts/omap5-uevm.dts
>>> +++ b/arch/arm/boot/dts/omap5-uevm.dts
>>> @@ -25,6 +25,47 @@
>>> regulator-max-microvolt = <3000000>;
>>> };
>>>
>>> + /* HS USB Port 2 RESET */
>>> + hsusb2_reset: hsusb2_reset_reg {
>>> + compatible = "regulator-fixed";
>>> + regulator-name = "hsusb2_reset";
>>> + regulator-min-microvolt = <3300000>;
>>> + regulator-max-microvolt = <3300000>;
>>> + gpio = <&gpio3 16 GPIO_ACTIVE_HIGH>; /* gpio3_80 HUB_NRESET */
>>> + startup-delay-us = <70000>;
>>> + enable-active-high;
>>> + };
>>> +
>>> + /* HS USB Host PHY on PORT 2 */
>>> + hsusb2_phy: hsusb2_phy {
>>> + compatible = "usb-nop-xceiv";
>>> + reset-supply = <&hsusb2_reset>;
>>> + };
>>> +
>>> + /* HS USB Port 3 RESET */
>>> + hsusb3_reset: hsusb3_reset_reg {
>>> + compatible = "regulator-fixed";
>>> + regulator-name = "hsusb3_reset";
>>> + regulator-min-microvolt = <3300000>;
>>> + regulator-max-microvolt = <3300000>;
>>> + gpio = <&gpio3 15 GPIO_ACTIVE_HIGH>; /* gpio3_79 ETH_NRESET */
>>> + startup-delay-us = <70000>;
>>> + enable-active-high;
>>> + };
>>> +
>>> + /* HS USB Host PHY on PORT 3 */
>>> + hsusb3_phy: hsusb3_phy {
>>> + compatible = "usb-nop-xceiv";
>>> + reset-supply = <&hsusb3_reset>;
>>> + };
>>> +
>>> + /* hsusb2_phy is clocked by FREF_CLK1 i.e. auxclk1 */
>>> + clock_alias {
>>> + clock-name = "auxclk1_ck";
>>> + clock-alias = "main_clk";
>>> + device = <&hsusb2_phy>;
>>> + clock-frequency = <19200000>; /* 19.2 MHz */
>>> + };
>>> };
>>>
>>> &omap5_pmx_core {
>>> @@ -35,6 +76,7 @@
>>> &dmic_pins
>>> &mcbsp1_pins
>>> &mcbsp2_pins
>>> + &usbhost_pins
>>> >;
>>>
>>> twl6040_pins: pinmux_twl6040_pins {
>>> @@ -120,6 +162,32 @@
>>> 0x16c (PIN_INPUT | MUX_MODE1) /* mcspi2_cs */
>>> >;
>>> };
>>> +
>>> + usbhost_pins: pinmux_usbhost_pins {
>>> + pinctrl-single,pins = <
>>> + 0x84 (PIN_INPUT | MUX_MODE0) /* usbb2_hsic_strobe INPUT | MODE 0 */
>>> + 0x86 (PIN_INPUT | MUX_MODE0) /* usbb2_hsic_data INPUT | MODE 0 */
>>
>> Comments are redundant with the constants, so maybe you can leave this part out.
>> Same for a few others below.
>>
> Ok, I agree here for attributes like pulls, i/o etc, comments are now not required.
> But comment is still good to describe just the mux mode functionality ?
> One module will use different pins, like data, clk, gpios, etc. Just MUX_MODEX does not
> complete it..
Yes, the 'usbb2_hsic_strobe' part must stay, only 'INPUT | MODE 0'
should be removed
from comments.
>>> +
>>> + 0x19e (PIN_INPUT | MUX_MODE0) /* usbb3_hsic_strobe INPUT | MODE 0 */
>>> + 0x1a0 (PIN_INPUT | MUX_MODE0) /* usbb3_hsic_data INPUT | MODE 0 */
>>> +
>>> + 0x70 (PIN_OUTPUT | MUX_MODE6) /* gpio3_80 OUTPUT | MODE 6 HUB_NRESET */
>>> + 0x6e (PIN_OUTPUT | MUX_MODE6) /* gpio3_79 OUTPUT | MODE 6 ETH_NRESET */
>>> + >;
>>> + };
>>> +};
>>> +
>>> +&omap5_pmx_wkup {
>>> + pinctrl-names = "default";
>>> + pinctrl-0 = <
>>> + &usbhost_wkup_pins
>>> + >;
>>> +
>>> + usbhost_wkup_pins: pinmux_usbhost_wkup_pins {
>>> + pinctrl-single,pins = <
>>> + 0x1A (PIN_OUTPUT | MUX_MODE0) /* fref_clk1_out OUTPUT | MODE 7 for USB hub clk */
>>
>> Mismatch between constants and comments, which mode should it be?
>>
> MODE 0. I see safe mode for 7. Comment should be corrected.
s/corrected/removed/. This will avoid this kind of inconsistency.
Regards,
Florian
next prev parent reply other threads:[~2013-06-05 12:15 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-05 6:46 [PATCH 0/4] ARM: dts: omap5: Cleanup and updates for DT files Sricharan R
2013-06-05 6:46 ` Sricharan R
2013-06-05 6:46 ` [PATCH 1/4] ARM: dts: omap5: Rename omap5-evm to omap5-uevm Sricharan R
2013-06-05 6:46 ` Sricharan R
2013-06-05 6:50 ` Sricharan R
2013-06-05 6:50 ` Sricharan R
2013-06-05 6:46 ` [PATCH 2/4] ARM: dts: omap5-uevm: Add USB Host support Sricharan R
2013-06-05 6:46 ` Sricharan R
2013-06-05 7:59 ` Florian Vaussard
2013-06-05 7:59 ` Florian Vaussard
2013-06-05 9:12 ` Sricharan R
2013-06-05 9:12 ` Sricharan R
2013-06-05 12:15 ` Florian Vaussard [this message]
2013-06-05 12:15 ` Florian Vaussard
2013-06-05 10:32 ` Roger Quadros
2013-06-05 10:32 ` Roger Quadros
2013-06-05 11:50 ` Sricharan R
2013-06-05 11:50 ` Sricharan R
2013-06-05 13:57 ` Nishanth Menon
2013-06-05 13:57 ` Nishanth Menon
2013-06-06 17:51 ` Sricharan R
2013-06-06 17:51 ` Sricharan R
2013-06-06 18:46 ` Nishanth Menon
2013-06-06 18:46 ` Nishanth Menon
2013-06-07 6:08 ` Sricharan R
2013-06-07 6:08 ` Sricharan R
2013-06-05 6:46 ` [PATCH 3/4] ARM: dts: omap5-uevm: Add LED support for uEVM blue LED Sricharan R
2013-06-05 6:46 ` Sricharan R
2013-06-05 17:04 ` Dan Murphy
2013-06-05 17:04 ` Dan Murphy
2013-06-06 17:52 ` Sricharan R
2013-06-06 17:52 ` Sricharan R
2013-06-05 6:46 ` [PATCH 4/4] ARM: dts: omap5-uevm: Add uart pinctrl data Sricharan R
2013-06-05 6:46 ` Sricharan R
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=51AF2BE8.1010402@epfl.ch \
--to=florian.vaussard@epfl.ch \
--cc=b-cousson@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=r.sricharan@ti.com \
--cc=rnayak@ti.com \
--cc=rogerq@ti.com \
--cc=tony@atomide.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.