All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rajendra Nayak <rnayak@ti.com>
To: Kishon Vijay Abraham I <kishon@ti.com>
Cc: b-cousson@ti.com, tony@atomide.com, linux@arm.linux.org.uk,
	rob.herring@calxeda.com, rob@landley.net, balbi@ti.com,
	linux-usb@vger.kernel.org, linux-omap@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	devicetree-discuss@lists.ozlabs.org, gregkh@linuxfoundation.org
Subject: Re: [PATCH 3/8] ARM: dts: omap: Add usb_otg and glue data
Date: Thu, 7 Feb 2013 11:51:28 +0530	[thread overview]
Message-ID: <511347E8.2030604@ti.com> (raw)
In-Reply-To: <1360162604-14320-4-git-send-email-kishon@ti.com>

[]...

>
> diff --git a/Documentation/devicetree/bindings/usb/omap-usb.txt b/Documentation/devicetree/bindings/usb/omap-usb.txt
> index 29a043e..4688265 100644
> --- a/Documentation/devicetree/bindings/usb/omap-usb.txt
> +++ b/Documentation/devicetree/bindings/usb/omap-usb.txt
> @@ -15,6 +15,7 @@ OMAP MUSB GLUE
>      represents PERIPHERAL.
>    - power : Should be "50". This signifies the controller can supply upto
>      100mA when operating in host mode.
> + - usb-phy : the phandle for the PHY device
>
>   SOC specific device node entry
>   usb_otg_hs: usb_otg_hs@4a0ab000 {
> diff --git a/arch/arm/boot/dts/omap3-beagle-xm.dts b/arch/arm/boot/dts/omap3-beagle-xm.dts
> index 3705a81..cb07583 100644
> --- a/arch/arm/boot/dts/omap3-beagle-xm.dts
> +++ b/arch/arm/boot/dts/omap3-beagle-xm.dts
> @@ -107,3 +107,9 @@
>   	 */
>   	ti,pulldowns = <0x03a1c4>;
>   };
> +
> +&usb_otg_hs {
> +	interface_type = <0>;
> +	mode = <3>;
> +	power = <50>;
> +};
> diff --git a/arch/arm/boot/dts/omap3-evm.dts b/arch/arm/boot/dts/omap3-evm.dts
> index e8ba1c2..afb9ba9 100644
> --- a/arch/arm/boot/dts/omap3-evm.dts
> +++ b/arch/arm/boot/dts/omap3-evm.dts
> @@ -59,3 +59,9 @@
>   &twl_gpio {
>   	ti,use-leds;
>   };
> +
> +&usb_otg_hs {
> +	interface_type = <0>;
> +	mode = <3>;
> +	power = <50>;
> +};
> diff --git a/arch/arm/boot/dts/omap3-overo.dtsi b/arch/arm/boot/dts/omap3-overo.dtsi
> index 89808ce..4b3d157 100644
> --- a/arch/arm/boot/dts/omap3-overo.dtsi
> +++ b/arch/arm/boot/dts/omap3-overo.dtsi
> @@ -55,3 +55,9 @@
>   &twl_gpio {
>   	ti,use-leds;
>   };
> +
> +&usb_otg_hs {
> +	interface_type = <0>;
> +	mode = <3>;
> +	power = <50>;
> +};
> diff --git a/arch/arm/boot/dts/omap3.dtsi b/arch/arm/boot/dts/omap3.dtsi
> index 1acc261..b6472f7 100644
> --- a/arch/arm/boot/dts/omap3.dtsi
> +++ b/arch/arm/boot/dts/omap3.dtsi
> @@ -397,5 +397,17 @@
>   			ti,timer-alwon;
>   			ti,timer-secure;
>   		};
> +
> +		usb_otg_hs: usb_otg_hs@480ab000 {
> +			compatible = "ti,omap3-musb";
> +			reg = <0x480ab000 0x1000>;
> +			interrupts = <0 92 0x4>, <0 93 0x4>;
> +			interrupt-names = "mc", "dma";
> +			ti,hwmods = "usb_otg_hs";
> +			usb-phy = <&usb2_phy>;
> +			multipoint = <1>;
> +			num_eps = <16>;
> +			ram_bits = <12>;

Where are these bindings documented? The general convention is to use
a '-' for property names and not '_'

> +		};
>   	};
>   };
> diff --git a/arch/arm/boot/dts/omap4-panda.dts b/arch/arm/boot/dts/omap4-panda.dts
> index 4122efe..612c9bb 100644
> --- a/arch/arm/boot/dts/omap4-panda.dts
> +++ b/arch/arm/boot/dts/omap4-panda.dts
> @@ -206,3 +206,9 @@
>   &twl_usb_comparator {
>   	usb-supply = <&vusb>;
>   };
> +
> +&usb_otg_hs {
> +	interface_type = <1>;
> +	mode = <3>;
> +	power = <50>;
> +};
> diff --git a/arch/arm/boot/dts/omap4-sdp.dts b/arch/arm/boot/dts/omap4-sdp.dts
> index 43e5258..582d7ee 100644
> --- a/arch/arm/boot/dts/omap4-sdp.dts
> +++ b/arch/arm/boot/dts/omap4-sdp.dts
> @@ -428,3 +428,9 @@
>   &twl_usb_comparator {
>   	usb-supply = <&vusb>;
>   };
> +
> +&usb_otg_hs {
> +	interface_type = <1>;
> +	mode = <3>;
> +	power = <50>;
> +};
> diff --git a/arch/arm/boot/dts/omap4.dtsi b/arch/arm/boot/dts/omap4.dtsi
> index c829d7e..5171739 100644
> --- a/arch/arm/boot/dts/omap4.dtsi
> +++ b/arch/arm/boot/dts/omap4.dtsi
> @@ -542,5 +542,18 @@
>   			reg-names = "control_dev_conf", "otghs_control";
>   			ti,type = <1>;
>   		};
> +
> +		usb_otg_hs: usb_otg_hs@4a0ab000 {
> +			compatible = "ti,omap4-musb";
> +			reg = <0x4a0ab000 0x7ff>;
> +			interrupts = <0 92 0x4>, <0 93 0x4>;
> +			interrupt-names = "mc", "dma";
> +			ti,hwmods = "usb_otg_hs";
> +			usb-phy = <&usb2_phy>;
> +			multipoint = <1>;
> +			num_eps = <16>;
> +			ram_bits = <12>;
> +			ti,has-mailbox;
> +		};
>   	};
>   };
> diff --git a/arch/arm/boot/dts/twl4030.dtsi b/arch/arm/boot/dts/twl4030.dtsi
> index ed0bc95..398d2c3 100644
> --- a/arch/arm/boot/dts/twl4030.dtsi
> +++ b/arch/arm/boot/dts/twl4030.dtsi
> @@ -67,7 +67,7 @@
>   		#interrupt-cells = <1>;
>   	};
>
> -	twl4030-usb {
> +	usb2_phy: twl4030-usb {
>   		compatible = "ti,twl4030-usb";
>   		interrupts = <10>, <4>;
>   		usb1v5-supply = <&vusb1v5>;
>


WARNING: multiple messages have this Message-ID (diff)
From: rnayak@ti.com (Rajendra Nayak)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/8] ARM: dts: omap: Add usb_otg and glue data
Date: Thu, 7 Feb 2013 11:51:28 +0530	[thread overview]
Message-ID: <511347E8.2030604@ti.com> (raw)
In-Reply-To: <1360162604-14320-4-git-send-email-kishon@ti.com>

[]...

>
> diff --git a/Documentation/devicetree/bindings/usb/omap-usb.txt b/Documentation/devicetree/bindings/usb/omap-usb.txt
> index 29a043e..4688265 100644
> --- a/Documentation/devicetree/bindings/usb/omap-usb.txt
> +++ b/Documentation/devicetree/bindings/usb/omap-usb.txt
> @@ -15,6 +15,7 @@ OMAP MUSB GLUE
>      represents PERIPHERAL.
>    - power : Should be "50". This signifies the controller can supply upto
>      100mA when operating in host mode.
> + - usb-phy : the phandle for the PHY device
>
>   SOC specific device node entry
>   usb_otg_hs: usb_otg_hs at 4a0ab000 {
> diff --git a/arch/arm/boot/dts/omap3-beagle-xm.dts b/arch/arm/boot/dts/omap3-beagle-xm.dts
> index 3705a81..cb07583 100644
> --- a/arch/arm/boot/dts/omap3-beagle-xm.dts
> +++ b/arch/arm/boot/dts/omap3-beagle-xm.dts
> @@ -107,3 +107,9 @@
>   	 */
>   	ti,pulldowns = <0x03a1c4>;
>   };
> +
> +&usb_otg_hs {
> +	interface_type = <0>;
> +	mode = <3>;
> +	power = <50>;
> +};
> diff --git a/arch/arm/boot/dts/omap3-evm.dts b/arch/arm/boot/dts/omap3-evm.dts
> index e8ba1c2..afb9ba9 100644
> --- a/arch/arm/boot/dts/omap3-evm.dts
> +++ b/arch/arm/boot/dts/omap3-evm.dts
> @@ -59,3 +59,9 @@
>   &twl_gpio {
>   	ti,use-leds;
>   };
> +
> +&usb_otg_hs {
> +	interface_type = <0>;
> +	mode = <3>;
> +	power = <50>;
> +};
> diff --git a/arch/arm/boot/dts/omap3-overo.dtsi b/arch/arm/boot/dts/omap3-overo.dtsi
> index 89808ce..4b3d157 100644
> --- a/arch/arm/boot/dts/omap3-overo.dtsi
> +++ b/arch/arm/boot/dts/omap3-overo.dtsi
> @@ -55,3 +55,9 @@
>   &twl_gpio {
>   	ti,use-leds;
>   };
> +
> +&usb_otg_hs {
> +	interface_type = <0>;
> +	mode = <3>;
> +	power = <50>;
> +};
> diff --git a/arch/arm/boot/dts/omap3.dtsi b/arch/arm/boot/dts/omap3.dtsi
> index 1acc261..b6472f7 100644
> --- a/arch/arm/boot/dts/omap3.dtsi
> +++ b/arch/arm/boot/dts/omap3.dtsi
> @@ -397,5 +397,17 @@
>   			ti,timer-alwon;
>   			ti,timer-secure;
>   		};
> +
> +		usb_otg_hs: usb_otg_hs at 480ab000 {
> +			compatible = "ti,omap3-musb";
> +			reg = <0x480ab000 0x1000>;
> +			interrupts = <0 92 0x4>, <0 93 0x4>;
> +			interrupt-names = "mc", "dma";
> +			ti,hwmods = "usb_otg_hs";
> +			usb-phy = <&usb2_phy>;
> +			multipoint = <1>;
> +			num_eps = <16>;
> +			ram_bits = <12>;

Where are these bindings documented? The general convention is to use
a '-' for property names and not '_'

> +		};
>   	};
>   };
> diff --git a/arch/arm/boot/dts/omap4-panda.dts b/arch/arm/boot/dts/omap4-panda.dts
> index 4122efe..612c9bb 100644
> --- a/arch/arm/boot/dts/omap4-panda.dts
> +++ b/arch/arm/boot/dts/omap4-panda.dts
> @@ -206,3 +206,9 @@
>   &twl_usb_comparator {
>   	usb-supply = <&vusb>;
>   };
> +
> +&usb_otg_hs {
> +	interface_type = <1>;
> +	mode = <3>;
> +	power = <50>;
> +};
> diff --git a/arch/arm/boot/dts/omap4-sdp.dts b/arch/arm/boot/dts/omap4-sdp.dts
> index 43e5258..582d7ee 100644
> --- a/arch/arm/boot/dts/omap4-sdp.dts
> +++ b/arch/arm/boot/dts/omap4-sdp.dts
> @@ -428,3 +428,9 @@
>   &twl_usb_comparator {
>   	usb-supply = <&vusb>;
>   };
> +
> +&usb_otg_hs {
> +	interface_type = <1>;
> +	mode = <3>;
> +	power = <50>;
> +};
> diff --git a/arch/arm/boot/dts/omap4.dtsi b/arch/arm/boot/dts/omap4.dtsi
> index c829d7e..5171739 100644
> --- a/arch/arm/boot/dts/omap4.dtsi
> +++ b/arch/arm/boot/dts/omap4.dtsi
> @@ -542,5 +542,18 @@
>   			reg-names = "control_dev_conf", "otghs_control";
>   			ti,type = <1>;
>   		};
> +
> +		usb_otg_hs: usb_otg_hs at 4a0ab000 {
> +			compatible = "ti,omap4-musb";
> +			reg = <0x4a0ab000 0x7ff>;
> +			interrupts = <0 92 0x4>, <0 93 0x4>;
> +			interrupt-names = "mc", "dma";
> +			ti,hwmods = "usb_otg_hs";
> +			usb-phy = <&usb2_phy>;
> +			multipoint = <1>;
> +			num_eps = <16>;
> +			ram_bits = <12>;
> +			ti,has-mailbox;
> +		};
>   	};
>   };
> diff --git a/arch/arm/boot/dts/twl4030.dtsi b/arch/arm/boot/dts/twl4030.dtsi
> index ed0bc95..398d2c3 100644
> --- a/arch/arm/boot/dts/twl4030.dtsi
> +++ b/arch/arm/boot/dts/twl4030.dtsi
> @@ -67,7 +67,7 @@
>   		#interrupt-cells = <1>;
>   	};
>
> -	twl4030-usb {
> +	usb2_phy: twl4030-usb {
>   		compatible = "ti,twl4030-usb";
>   		interrupts = <10>, <4>;
>   		usb1v5-supply = <&vusb1v5>;
>

WARNING: multiple messages have this Message-ID (diff)
From: Rajendra Nayak <rnayak@ti.com>
To: Kishon Vijay Abraham I <kishon@ti.com>
Cc: <b-cousson@ti.com>, <tony@atomide.com>, <linux@arm.linux.org.uk>,
	<rob.herring@calxeda.com>, <rob@landley.net>, <balbi@ti.com>,
	<linux-usb@vger.kernel.org>, <linux-omap@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>, <linux-doc@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<devicetree-discuss@lists.ozlabs.org>,
	<gregkh@linuxfoundation.org>
Subject: Re: [PATCH 3/8] ARM: dts: omap: Add usb_otg and glue data
Date: Thu, 7 Feb 2013 11:51:28 +0530	[thread overview]
Message-ID: <511347E8.2030604@ti.com> (raw)
In-Reply-To: <1360162604-14320-4-git-send-email-kishon@ti.com>

[]...

>
> diff --git a/Documentation/devicetree/bindings/usb/omap-usb.txt b/Documentation/devicetree/bindings/usb/omap-usb.txt
> index 29a043e..4688265 100644
> --- a/Documentation/devicetree/bindings/usb/omap-usb.txt
> +++ b/Documentation/devicetree/bindings/usb/omap-usb.txt
> @@ -15,6 +15,7 @@ OMAP MUSB GLUE
>      represents PERIPHERAL.
>    - power : Should be "50". This signifies the controller can supply upto
>      100mA when operating in host mode.
> + - usb-phy : the phandle for the PHY device
>
>   SOC specific device node entry
>   usb_otg_hs: usb_otg_hs@4a0ab000 {
> diff --git a/arch/arm/boot/dts/omap3-beagle-xm.dts b/arch/arm/boot/dts/omap3-beagle-xm.dts
> index 3705a81..cb07583 100644
> --- a/arch/arm/boot/dts/omap3-beagle-xm.dts
> +++ b/arch/arm/boot/dts/omap3-beagle-xm.dts
> @@ -107,3 +107,9 @@
>   	 */
>   	ti,pulldowns = <0x03a1c4>;
>   };
> +
> +&usb_otg_hs {
> +	interface_type = <0>;
> +	mode = <3>;
> +	power = <50>;
> +};
> diff --git a/arch/arm/boot/dts/omap3-evm.dts b/arch/arm/boot/dts/omap3-evm.dts
> index e8ba1c2..afb9ba9 100644
> --- a/arch/arm/boot/dts/omap3-evm.dts
> +++ b/arch/arm/boot/dts/omap3-evm.dts
> @@ -59,3 +59,9 @@
>   &twl_gpio {
>   	ti,use-leds;
>   };
> +
> +&usb_otg_hs {
> +	interface_type = <0>;
> +	mode = <3>;
> +	power = <50>;
> +};
> diff --git a/arch/arm/boot/dts/omap3-overo.dtsi b/arch/arm/boot/dts/omap3-overo.dtsi
> index 89808ce..4b3d157 100644
> --- a/arch/arm/boot/dts/omap3-overo.dtsi
> +++ b/arch/arm/boot/dts/omap3-overo.dtsi
> @@ -55,3 +55,9 @@
>   &twl_gpio {
>   	ti,use-leds;
>   };
> +
> +&usb_otg_hs {
> +	interface_type = <0>;
> +	mode = <3>;
> +	power = <50>;
> +};
> diff --git a/arch/arm/boot/dts/omap3.dtsi b/arch/arm/boot/dts/omap3.dtsi
> index 1acc261..b6472f7 100644
> --- a/arch/arm/boot/dts/omap3.dtsi
> +++ b/arch/arm/boot/dts/omap3.dtsi
> @@ -397,5 +397,17 @@
>   			ti,timer-alwon;
>   			ti,timer-secure;
>   		};
> +
> +		usb_otg_hs: usb_otg_hs@480ab000 {
> +			compatible = "ti,omap3-musb";
> +			reg = <0x480ab000 0x1000>;
> +			interrupts = <0 92 0x4>, <0 93 0x4>;
> +			interrupt-names = "mc", "dma";
> +			ti,hwmods = "usb_otg_hs";
> +			usb-phy = <&usb2_phy>;
> +			multipoint = <1>;
> +			num_eps = <16>;
> +			ram_bits = <12>;

Where are these bindings documented? The general convention is to use
a '-' for property names and not '_'

> +		};
>   	};
>   };
> diff --git a/arch/arm/boot/dts/omap4-panda.dts b/arch/arm/boot/dts/omap4-panda.dts
> index 4122efe..612c9bb 100644
> --- a/arch/arm/boot/dts/omap4-panda.dts
> +++ b/arch/arm/boot/dts/omap4-panda.dts
> @@ -206,3 +206,9 @@
>   &twl_usb_comparator {
>   	usb-supply = <&vusb>;
>   };
> +
> +&usb_otg_hs {
> +	interface_type = <1>;
> +	mode = <3>;
> +	power = <50>;
> +};
> diff --git a/arch/arm/boot/dts/omap4-sdp.dts b/arch/arm/boot/dts/omap4-sdp.dts
> index 43e5258..582d7ee 100644
> --- a/arch/arm/boot/dts/omap4-sdp.dts
> +++ b/arch/arm/boot/dts/omap4-sdp.dts
> @@ -428,3 +428,9 @@
>   &twl_usb_comparator {
>   	usb-supply = <&vusb>;
>   };
> +
> +&usb_otg_hs {
> +	interface_type = <1>;
> +	mode = <3>;
> +	power = <50>;
> +};
> diff --git a/arch/arm/boot/dts/omap4.dtsi b/arch/arm/boot/dts/omap4.dtsi
> index c829d7e..5171739 100644
> --- a/arch/arm/boot/dts/omap4.dtsi
> +++ b/arch/arm/boot/dts/omap4.dtsi
> @@ -542,5 +542,18 @@
>   			reg-names = "control_dev_conf", "otghs_control";
>   			ti,type = <1>;
>   		};
> +
> +		usb_otg_hs: usb_otg_hs@4a0ab000 {
> +			compatible = "ti,omap4-musb";
> +			reg = <0x4a0ab000 0x7ff>;
> +			interrupts = <0 92 0x4>, <0 93 0x4>;
> +			interrupt-names = "mc", "dma";
> +			ti,hwmods = "usb_otg_hs";
> +			usb-phy = <&usb2_phy>;
> +			multipoint = <1>;
> +			num_eps = <16>;
> +			ram_bits = <12>;
> +			ti,has-mailbox;
> +		};
>   	};
>   };
> diff --git a/arch/arm/boot/dts/twl4030.dtsi b/arch/arm/boot/dts/twl4030.dtsi
> index ed0bc95..398d2c3 100644
> --- a/arch/arm/boot/dts/twl4030.dtsi
> +++ b/arch/arm/boot/dts/twl4030.dtsi
> @@ -67,7 +67,7 @@
>   		#interrupt-cells = <1>;
>   	};
>
> -	twl4030-usb {
> +	usb2_phy: twl4030-usb {
>   		compatible = "ti,twl4030-usb";
>   		interrupts = <10>, <4>;
>   		usb1v5-supply = <&vusb1v5>;
>


  reply	other threads:[~2013-02-07  6:21 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-06 14:56 [PATCH 0/8] ARM: dts: omap: Add dts data for USB Kishon Vijay Abraham I
2013-02-06 14:56 ` Kishon Vijay Abraham I
2013-02-06 14:56 ` Kishon Vijay Abraham I
     [not found] ` <1360162604-14320-1-git-send-email-kishon-l0cyMroinI0@public.gmane.org>
2013-02-06 14:56   ` [PATCH 1/8] ARM: dts: omap: Add omap control usb data Kishon Vijay Abraham I
2013-02-06 14:56     ` Kishon Vijay Abraham I
2013-02-06 14:56     ` Kishon Vijay Abraham I
2013-02-06 14:56   ` [PATCH 2/8] ARM: dts: omap: Add omap-usb2 dt data Kishon Vijay Abraham I
2013-02-06 14:56     ` Kishon Vijay Abraham I
2013-02-06 14:56     ` Kishon Vijay Abraham I
2013-02-06 14:56   ` [PATCH 3/8] ARM: dts: omap: Add usb_otg and glue data Kishon Vijay Abraham I
2013-02-06 14:56     ` Kishon Vijay Abraham I
2013-02-06 14:56     ` Kishon Vijay Abraham I
2013-02-07  6:21     ` Rajendra Nayak [this message]
2013-02-07  6:21       ` Rajendra Nayak
2013-02-07  6:21       ` Rajendra Nayak
2013-02-07  6:31       ` kishon
2013-02-07  6:31         ` kishon
2013-02-07  6:31         ` kishon
2013-02-06 14:56   ` [PATCH 7/8] ARM: dts: omap5: add dwc3 omap dt data Kishon Vijay Abraham I
2013-02-06 14:56     ` Kishon Vijay Abraham I
2013-02-06 14:56     ` Kishon Vijay Abraham I
2013-02-06 14:56 ` [PATCH 4/8] ARM: dts: omap5: Add omap control usb data Kishon Vijay Abraham I
2013-02-06 14:56   ` Kishon Vijay Abraham I
2013-02-06 14:56   ` Kishon Vijay Abraham I
2013-02-06 14:56 ` [PATCH 5/8] ARM: dts: omap5: Add ocp2scp data Kishon Vijay Abraham I
2013-02-06 14:56   ` Kishon Vijay Abraham I
2013-02-06 14:56   ` Kishon Vijay Abraham I
2013-02-06 14:56 ` [PATCH 6/8] ARM: dts: omap5: Add omap-usb3 and omap-usb2 dt data Kishon Vijay Abraham I
2013-02-06 14:56   ` Kishon Vijay Abraham I
2013-02-06 14:56   ` Kishon Vijay Abraham I
2013-02-06 14:56 ` [PATCH 8/8] ARM: dts: omap5: add dwc3 core " Kishon Vijay Abraham I
2013-02-06 14:56   ` Kishon Vijay Abraham I
2013-02-06 14:56   ` Kishon Vijay Abraham I

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=511347E8.2030604@ti.com \
    --to=rnayak@ti.com \
    --cc=b-cousson@ti.com \
    --cc=balbi@ti.com \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=kishon@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=rob.herring@calxeda.com \
    --cc=rob@landley.net \
    --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.