* [PATCH v2 0/2] Add D_CAN device tree data to AM335x-EVM
@ 2012-07-25 12:23 ` AnilKumar Ch
0 siblings, 0 replies; 26+ messages in thread
From: AnilKumar Ch @ 2012-07-25 12:23 UTC (permalink / raw)
To: linux-omap
Cc: tony, wg, mkl, linux-arm-kernel, devicetree-discuss,
grant.likely, AnilKumar Ch
Thid patch series adds device tree data to AM335x-EVM file and
adds pinmux settings required to configure two of the AM335x EVM
pins to D_CAN TX/RX pins.
Changes from v1:
- These two patches separated from c_can DT support
patch series.
AnilKumar Ch (2):
arm/dts: AM33XX: Add D_CAN device tree data
arm/dts: AM33XX: Configure pinmuxs for D_CAN1 on AM335x-EVM
arch/arm/boot/dts/am335x-evm.dts | 13 +++++++++++++
arch/arm/boot/dts/am33xx.dtsi | 5 +++++
2 files changed, 18 insertions(+)
--
1.7.9.5
^ permalink raw reply [flat|nested] 26+ messages in thread
* [PATCH v2 0/2] Add D_CAN device tree data to AM335x-EVM
@ 2012-07-25 12:23 ` AnilKumar Ch
0 siblings, 0 replies; 26+ messages in thread
From: AnilKumar Ch @ 2012-07-25 12:23 UTC (permalink / raw)
To: linux-arm-kernel
Thid patch series adds device tree data to AM335x-EVM file and
adds pinmux settings required to configure two of the AM335x EVM
pins to D_CAN TX/RX pins.
Changes from v1:
- These two patches separated from c_can DT support
patch series.
AnilKumar Ch (2):
arm/dts: AM33XX: Add D_CAN device tree data
arm/dts: AM33XX: Configure pinmuxs for D_CAN1 on AM335x-EVM
arch/arm/boot/dts/am335x-evm.dts | 13 +++++++++++++
arch/arm/boot/dts/am33xx.dtsi | 5 +++++
2 files changed, 18 insertions(+)
--
1.7.9.5
^ permalink raw reply [flat|nested] 26+ messages in thread
* [PATCH v2 1/2] arm/dts: AM33XX: Add D_CAN device tree data
2012-07-25 12:23 ` AnilKumar Ch
@ 2012-07-25 12:23 ` AnilKumar Ch
-1 siblings, 0 replies; 26+ messages in thread
From: AnilKumar Ch @ 2012-07-25 12:23 UTC (permalink / raw)
To: linux-omap
Cc: tony, wg, mkl, linux-arm-kernel, devicetree-discuss,
grant.likely, AnilKumar Ch
Add Bosch D_CAN controller device tree data to AM33XX dtsi file
by adding d_can device node with all the necessary parameters.
Signed-off-by: AnilKumar Ch <anilkumar@ti.com>
---
arch/arm/boot/dts/am33xx.dtsi | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/arch/arm/boot/dts/am33xx.dtsi b/arch/arm/boot/dts/am33xx.dtsi
index 9b974dc..2db2ffb 100644
--- a/arch/arm/boot/dts/am33xx.dtsi
+++ b/arch/arm/boot/dts/am33xx.dtsi
@@ -163,5 +163,10 @@
#size-cells = <0>;
ti,hwmods = "i2c3";
};
+
+ dcan1: d_can@481D0000 {
+ compatible = "bosch,d_can";
+ ti,hwmods = "d_can1";
+ };
};
};
--
1.7.9.5
^ permalink raw reply related [flat|nested] 26+ messages in thread
* [PATCH v2 1/2] arm/dts: AM33XX: Add D_CAN device tree data
@ 2012-07-25 12:23 ` AnilKumar Ch
0 siblings, 0 replies; 26+ messages in thread
From: AnilKumar Ch @ 2012-07-25 12:23 UTC (permalink / raw)
To: linux-arm-kernel
Add Bosch D_CAN controller device tree data to AM33XX dtsi file
by adding d_can device node with all the necessary parameters.
Signed-off-by: AnilKumar Ch <anilkumar@ti.com>
---
arch/arm/boot/dts/am33xx.dtsi | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/arch/arm/boot/dts/am33xx.dtsi b/arch/arm/boot/dts/am33xx.dtsi
index 9b974dc..2db2ffb 100644
--- a/arch/arm/boot/dts/am33xx.dtsi
+++ b/arch/arm/boot/dts/am33xx.dtsi
@@ -163,5 +163,10 @@
#size-cells = <0>;
ti,hwmods = "i2c3";
};
+
+ dcan1: d_can at 481D0000 {
+ compatible = "bosch,d_can";
+ ti,hwmods = "d_can1";
+ };
};
};
--
1.7.9.5
^ permalink raw reply related [flat|nested] 26+ messages in thread
* [PATCH v2 2/2] arm/dts: AM33XX: Configure pinmuxs for D_CAN1 on AM335x-EVM
2012-07-25 12:23 ` AnilKumar Ch
@ 2012-07-25 12:23 ` AnilKumar Ch
-1 siblings, 0 replies; 26+ messages in thread
From: AnilKumar Ch @ 2012-07-25 12:23 UTC (permalink / raw)
To: linux-omap-u79uwXL29TY76Z2rM5mHXA
Cc: devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ,
mkl-bIcnvbaLZ9MEGnE8C9+IrQ,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r
Add D_CAN1 pinctrl node to am3358_pinmux master node to export
D_CAN functionality on AM335x EVM according to pinctrl-single
driver.
Signed-off-by: AnilKumar Ch <anilkumar-l0cyMroinI0@public.gmane.org>
---
arch/arm/boot/dts/am335x-evm.dts | 13 +++++++++++++
1 file changed, 13 insertions(+)
diff --git a/arch/arm/boot/dts/am335x-evm.dts b/arch/arm/boot/dts/am335x-evm.dts
index e4e1ccb..7f0fd6c 100644
--- a/arch/arm/boot/dts/am335x-evm.dts
+++ b/arch/arm/boot/dts/am335x-evm.dts
@@ -46,3 +46,16 @@
regulator-boot-on;
regulator-always-on;
};
+
+&am3358_pinmux {
+
+ pinctrl-names = "default";
+ pinctrl-0 = <&d_can1_pins>;
+
+ d_can1_pins: pinmux_d_can_pins {
+ pinctrl-single,pins = <
+ 0x168 0x2 /* uart0_ctsn.d_can1_tx, OUTPUT | MODE2 */
+ 0x16C 0x32 /* uart0_rtsn.d_can1_rx, INPUT_PULLUP | MODE2 */
+ >;
+ };
+};
--
1.7.9.5
^ permalink raw reply related [flat|nested] 26+ messages in thread
* [PATCH v2 2/2] arm/dts: AM33XX: Configure pinmuxs for D_CAN1 on AM335x-EVM
@ 2012-07-25 12:23 ` AnilKumar Ch
0 siblings, 0 replies; 26+ messages in thread
From: AnilKumar Ch @ 2012-07-25 12:23 UTC (permalink / raw)
To: linux-arm-kernel
Add D_CAN1 pinctrl node to am3358_pinmux master node to export
D_CAN functionality on AM335x EVM according to pinctrl-single
driver.
Signed-off-by: AnilKumar Ch <anilkumar@ti.com>
---
arch/arm/boot/dts/am335x-evm.dts | 13 +++++++++++++
1 file changed, 13 insertions(+)
diff --git a/arch/arm/boot/dts/am335x-evm.dts b/arch/arm/boot/dts/am335x-evm.dts
index e4e1ccb..7f0fd6c 100644
--- a/arch/arm/boot/dts/am335x-evm.dts
+++ b/arch/arm/boot/dts/am335x-evm.dts
@@ -46,3 +46,16 @@
regulator-boot-on;
regulator-always-on;
};
+
+&am3358_pinmux {
+
+ pinctrl-names = "default";
+ pinctrl-0 = <&d_can1_pins>;
+
+ d_can1_pins: pinmux_d_can_pins {
+ pinctrl-single,pins = <
+ 0x168 0x2 /* uart0_ctsn.d_can1_tx, OUTPUT | MODE2 */
+ 0x16C 0x32 /* uart0_rtsn.d_can1_rx, INPUT_PULLUP | MODE2 */
+ >;
+ };
+};
--
1.7.9.5
^ permalink raw reply related [flat|nested] 26+ messages in thread
* Re: [PATCH v2 1/2] arm/dts: AM33XX: Add D_CAN device tree data
2012-07-25 12:23 ` AnilKumar Ch
@ 2012-07-25 12:43 ` Sergei Shtylyov
-1 siblings, 0 replies; 26+ messages in thread
From: Sergei Shtylyov @ 2012-07-25 12:43 UTC (permalink / raw)
To: AnilKumar Ch
Cc: linux-omap, tony, devicetree-discuss, grant.likely, mkl, wg,
linux-arm-kernel
Hello.
On 25-07-2012 16:23, AnilKumar Ch wrote:
> Add Bosch D_CAN controller device tree data to AM33XX dtsi file
> by adding d_can device node with all the necessary parameters.
> Signed-off-by: AnilKumar Ch <anilkumar@ti.com>
> ---
> arch/arm/boot/dts/am33xx.dtsi | 5 +++++
> 1 file changed, 5 insertions(+)
> diff --git a/arch/arm/boot/dts/am33xx.dtsi b/arch/arm/boot/dts/am33xx.dtsi
> index 9b974dc..2db2ffb 100644
> --- a/arch/arm/boot/dts/am33xx.dtsi
> +++ b/arch/arm/boot/dts/am33xx.dtsi
> @@ -163,5 +163,10 @@
> #size-cells = <0>;
> ti,hwmods = "i2c3";
> };
> +
> + dcan1: d_can@481D0000 {
Address postfix in the node name and no "reg" property?
> + compatible = "bosch,d_can";
> + ti,hwmods = "d_can1";
> + };
WBR, Sergei
^ permalink raw reply [flat|nested] 26+ messages in thread
* [PATCH v2 1/2] arm/dts: AM33XX: Add D_CAN device tree data
@ 2012-07-25 12:43 ` Sergei Shtylyov
0 siblings, 0 replies; 26+ messages in thread
From: Sergei Shtylyov @ 2012-07-25 12:43 UTC (permalink / raw)
To: linux-arm-kernel
Hello.
On 25-07-2012 16:23, AnilKumar Ch wrote:
> Add Bosch D_CAN controller device tree data to AM33XX dtsi file
> by adding d_can device node with all the necessary parameters.
> Signed-off-by: AnilKumar Ch <anilkumar@ti.com>
> ---
> arch/arm/boot/dts/am33xx.dtsi | 5 +++++
> 1 file changed, 5 insertions(+)
> diff --git a/arch/arm/boot/dts/am33xx.dtsi b/arch/arm/boot/dts/am33xx.dtsi
> index 9b974dc..2db2ffb 100644
> --- a/arch/arm/boot/dts/am33xx.dtsi
> +++ b/arch/arm/boot/dts/am33xx.dtsi
> @@ -163,5 +163,10 @@
> #size-cells = <0>;
> ti,hwmods = "i2c3";
> };
> +
> + dcan1: d_can at 481D0000 {
Address postfix in the node name and no "reg" property?
> + compatible = "bosch,d_can";
> + ti,hwmods = "d_can1";
> + };
WBR, Sergei
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: [PATCH v2 1/2] arm/dts: AM33XX: Add D_CAN device tree data
2012-07-25 12:43 ` Sergei Shtylyov
@ 2012-07-26 8:36 ` Daniel Mack
-1 siblings, 0 replies; 26+ messages in thread
From: Daniel Mack @ 2012-07-26 8:36 UTC (permalink / raw)
To: Sergei Shtylyov
Cc: AnilKumar Ch, tony, devicetree-discuss, grant.likely, mkl,
linux-arm-kernel, linux-omap, wg
On 25.07.2012 14:43, Sergei Shtylyov wrote:
> Hello.
>
> On 25-07-2012 16:23, AnilKumar Ch wrote:
>
>> Add Bosch D_CAN controller device tree data to AM33XX dtsi file
>> by adding d_can device node with all the necessary parameters.
>
>> Signed-off-by: AnilKumar Ch <anilkumar@ti.com>
>> ---
>> arch/arm/boot/dts/am33xx.dtsi | 5 +++++
>> 1 file changed, 5 insertions(+)
>
>> diff --git a/arch/arm/boot/dts/am33xx.dtsi b/arch/arm/boot/dts/am33xx.dtsi
>> index 9b974dc..2db2ffb 100644
>> --- a/arch/arm/boot/dts/am33xx.dtsi
>> +++ b/arch/arm/boot/dts/am33xx.dtsi
>> @@ -163,5 +163,10 @@
>> #size-cells = <0>;
>> ti,hwmods = "i2c3";
>> };
>> +
>> + dcan1: d_can@481D0000 {
>
> Address postfix in the node name and no "reg" property?
This still works due to the hwmod mappings OMAP relies on. I would still
put it there, so the switch to real DT definitions will be less painful.
Daniel
^ permalink raw reply [flat|nested] 26+ messages in thread
* [PATCH v2 1/2] arm/dts: AM33XX: Add D_CAN device tree data
@ 2012-07-26 8:36 ` Daniel Mack
0 siblings, 0 replies; 26+ messages in thread
From: Daniel Mack @ 2012-07-26 8:36 UTC (permalink / raw)
To: linux-arm-kernel
On 25.07.2012 14:43, Sergei Shtylyov wrote:
> Hello.
>
> On 25-07-2012 16:23, AnilKumar Ch wrote:
>
>> Add Bosch D_CAN controller device tree data to AM33XX dtsi file
>> by adding d_can device node with all the necessary parameters.
>
>> Signed-off-by: AnilKumar Ch <anilkumar@ti.com>
>> ---
>> arch/arm/boot/dts/am33xx.dtsi | 5 +++++
>> 1 file changed, 5 insertions(+)
>
>> diff --git a/arch/arm/boot/dts/am33xx.dtsi b/arch/arm/boot/dts/am33xx.dtsi
>> index 9b974dc..2db2ffb 100644
>> --- a/arch/arm/boot/dts/am33xx.dtsi
>> +++ b/arch/arm/boot/dts/am33xx.dtsi
>> @@ -163,5 +163,10 @@
>> #size-cells = <0>;
>> ti,hwmods = "i2c3";
>> };
>> +
>> + dcan1: d_can at 481D0000 {
>
> Address postfix in the node name and no "reg" property?
This still works due to the hwmod mappings OMAP relies on. I would still
put it there, so the switch to real DT definitions will be less painful.
Daniel
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: [PATCH v2 1/2] arm/dts: AM33XX: Add D_CAN device tree data
2012-07-25 12:23 ` AnilKumar Ch
@ 2012-07-26 8:46 ` Koen Kooi
-1 siblings, 0 replies; 26+ messages in thread
From: Koen Kooi @ 2012-07-26 8:46 UTC (permalink / raw)
To: AnilKumar Ch
Cc: linux-omap, tony, wg, mkl, linux-arm-kernel, devicetree-discuss,
grant.likely
Op 25 jul. 2012, om 14:23 heeft AnilKumar Ch <anilkumar@ti.com> het volgende geschreven:
> Add Bosch D_CAN controller device tree data to AM33XX dtsi file
> by adding d_can device node with all the necessary parameters.
>
> Signed-off-by: AnilKumar Ch <anilkumar@ti.com>
> ---
> arch/arm/boot/dts/am33xx.dtsi | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/arch/arm/boot/dts/am33xx.dtsi b/arch/arm/boot/dts/am33xx.dtsi
> index 9b974dc..2db2ffb 100644
> --- a/arch/arm/boot/dts/am33xx.dtsi
> +++ b/arch/arm/boot/dts/am33xx.dtsi
> @@ -163,5 +163,10 @@
> #size-cells = <0>;
> ti,hwmods = "i2c3";
> };
> +
> + dcan1: d_can@481D0000 {
> + compatible = "bosch,d_can";
> + ti,hwmods = "d_can1";
> + };
> };
I scanned the linux-networking mailinglist and l-o-ml, but I can't find the patchset that actually adds the d_can drivers, could you provide a link to that? I have 2 different CAN capes I'd like to test on beaglebone.
regards,
Koen
^ permalink raw reply [flat|nested] 26+ messages in thread
* [PATCH v2 1/2] arm/dts: AM33XX: Add D_CAN device tree data
@ 2012-07-26 8:46 ` Koen Kooi
0 siblings, 0 replies; 26+ messages in thread
From: Koen Kooi @ 2012-07-26 8:46 UTC (permalink / raw)
To: linux-arm-kernel
Op 25 jul. 2012, om 14:23 heeft AnilKumar Ch <anilkumar@ti.com> het volgende geschreven:
> Add Bosch D_CAN controller device tree data to AM33XX dtsi file
> by adding d_can device node with all the necessary parameters.
>
> Signed-off-by: AnilKumar Ch <anilkumar@ti.com>
> ---
> arch/arm/boot/dts/am33xx.dtsi | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/arch/arm/boot/dts/am33xx.dtsi b/arch/arm/boot/dts/am33xx.dtsi
> index 9b974dc..2db2ffb 100644
> --- a/arch/arm/boot/dts/am33xx.dtsi
> +++ b/arch/arm/boot/dts/am33xx.dtsi
> @@ -163,5 +163,10 @@
> #size-cells = <0>;
> ti,hwmods = "i2c3";
> };
> +
> + dcan1: d_can at 481D0000 {
> + compatible = "bosch,d_can";
> + ti,hwmods = "d_can1";
> + };
> };
I scanned the linux-networking mailinglist and l-o-ml, but I can't find the patchset that actually adds the d_can drivers, could you provide a link to that? I have 2 different CAN capes I'd like to test on beaglebone.
regards,
Koen
^ permalink raw reply [flat|nested] 26+ messages in thread
* RE: [PATCH v2 1/2] arm/dts: AM33XX: Add D_CAN device tree data
2012-07-26 8:46 ` Koen Kooi
@ 2012-07-26 9:03 ` AnilKumar, Chimata
-1 siblings, 0 replies; 26+ messages in thread
From: AnilKumar, Chimata @ 2012-07-26 9:03 UTC (permalink / raw)
To: Koen Kooi
Cc: devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ,
mkl-bIcnvbaLZ9MEGnE8C9+IrQ, linux-omap-u79uwXL29TY76Z2rM5mHXA,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r
On Thu, Jul 26, 2012 at 14:16:33, Koen Kooi wrote:
>
> Op 25 jul. 2012, om 14:23 heeft AnilKumar Ch <anilkumar-l0cyMroinI0@public.gmane.org> het volgende geschreven:
>
> > Add Bosch D_CAN controller device tree data to AM33XX dtsi file
> > by adding d_can device node with all the necessary parameters.
> >
> > Signed-off-by: AnilKumar Ch <anilkumar-l0cyMroinI0@public.gmane.org>
> > ---
> > arch/arm/boot/dts/am33xx.dtsi | 5 +++++
> > 1 file changed, 5 insertions(+)
> >
> > diff --git a/arch/arm/boot/dts/am33xx.dtsi b/arch/arm/boot/dts/am33xx.dtsi
> > index 9b974dc..2db2ffb 100644
> > --- a/arch/arm/boot/dts/am33xx.dtsi
> > +++ b/arch/arm/boot/dts/am33xx.dtsi
> > @@ -163,5 +163,10 @@
> > #size-cells = <0>;
> > ti,hwmods = "i2c3";
> > };
> > +
> > + dcan1: d_can@481D0000 {
> > + compatible = "bosch,d_can";
> > + ti,hwmods = "d_can1";
> > + };
> > };
>
> I scanned the linux-networking mailinglist and l-o-ml, but I can't find the patchset that actually adds the d_can drivers, could you provide a link to that? I have 2 different CAN capes I'd like to test on beaglebone.
>
You can find it from linux-next or net-next trees, D_CAN support is added
to C_CAN driver.
http://git.kernel.org/?p=linux/kernel/git/davem/net-next.git;
a=commitdiff;h=69927fccd96b15bd228bb82d356a7a2a0cfaeefb
Regards
AnilKumar
^ permalink raw reply [flat|nested] 26+ messages in thread
* [PATCH v2 1/2] arm/dts: AM33XX: Add D_CAN device tree data
@ 2012-07-26 9:03 ` AnilKumar, Chimata
0 siblings, 0 replies; 26+ messages in thread
From: AnilKumar, Chimata @ 2012-07-26 9:03 UTC (permalink / raw)
To: linux-arm-kernel
On Thu, Jul 26, 2012 at 14:16:33, Koen Kooi wrote:
>
> Op 25 jul. 2012, om 14:23 heeft AnilKumar Ch <anilkumar@ti.com> het volgende geschreven:
>
> > Add Bosch D_CAN controller device tree data to AM33XX dtsi file
> > by adding d_can device node with all the necessary parameters.
> >
> > Signed-off-by: AnilKumar Ch <anilkumar@ti.com>
> > ---
> > arch/arm/boot/dts/am33xx.dtsi | 5 +++++
> > 1 file changed, 5 insertions(+)
> >
> > diff --git a/arch/arm/boot/dts/am33xx.dtsi b/arch/arm/boot/dts/am33xx.dtsi
> > index 9b974dc..2db2ffb 100644
> > --- a/arch/arm/boot/dts/am33xx.dtsi
> > +++ b/arch/arm/boot/dts/am33xx.dtsi
> > @@ -163,5 +163,10 @@
> > #size-cells = <0>;
> > ti,hwmods = "i2c3";
> > };
> > +
> > + dcan1: d_can at 481D0000 {
> > + compatible = "bosch,d_can";
> > + ti,hwmods = "d_can1";
> > + };
> > };
>
> I scanned the linux-networking mailinglist and l-o-ml, but I can't find the patchset that actually adds the d_can drivers, could you provide a link to that? I have 2 different CAN capes I'd like to test on beaglebone.
>
You can find it from linux-next or net-next trees, D_CAN support is added
to C_CAN driver.
http://git.kernel.org/?p=linux/kernel/git/davem/net-next.git;
a=commitdiff;h=69927fccd96b15bd228bb82d356a7a2a0cfaeefb
Regards
AnilKumar
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: [PATCH v2 1/2] arm/dts: AM33XX: Add D_CAN device tree data
2012-07-26 9:03 ` AnilKumar, Chimata
@ 2012-07-26 9:14 ` Marc Kleine-Budde
-1 siblings, 0 replies; 26+ messages in thread
From: Marc Kleine-Budde @ 2012-07-26 9:14 UTC (permalink / raw)
To: AnilKumar, Chimata
Cc: Koen Kooi, linux-omap-u79uwXL29TY76Z2rM5mHXA,
devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r
[-- Attachment #1.1: Type: text/plain, Size: 1741 bytes --]
On 07/26/2012 11:03 AM, AnilKumar, Chimata wrote:
> On Thu, Jul 26, 2012 at 14:16:33, Koen Kooi wrote:
>>
>> Op 25 jul. 2012, om 14:23 heeft AnilKumar Ch <anilkumar-l0cyMroinI0@public.gmane.org> het volgende geschreven:
>>
>>> Add Bosch D_CAN controller device tree data to AM33XX dtsi file
>>> by adding d_can device node with all the necessary parameters.
>>>
>>> Signed-off-by: AnilKumar Ch <anilkumar-l0cyMroinI0@public.gmane.org>
>>> ---
>>> arch/arm/boot/dts/am33xx.dtsi | 5 +++++
>>> 1 file changed, 5 insertions(+)
>>>
>>> diff --git a/arch/arm/boot/dts/am33xx.dtsi b/arch/arm/boot/dts/am33xx.dtsi
>>> index 9b974dc..2db2ffb 100644
>>> --- a/arch/arm/boot/dts/am33xx.dtsi
>>> +++ b/arch/arm/boot/dts/am33xx.dtsi
>>> @@ -163,5 +163,10 @@
>>> #size-cells = <0>;
>>> ti,hwmods = "i2c3";
>>> };
>>> +
>>> + dcan1: d_can@481D0000 {
>>> + compatible = "bosch,d_can";
>>> + ti,hwmods = "d_can1";
>>> + };
>>> };
>>
>> I scanned the linux-networking mailinglist and l-o-ml, but I can't find the patchset that actually adds the d_can drivers, could you provide a link to that? I have 2 different CAN capes I'd like to test on beaglebone.
>>
>
> You can find it from linux-next or net-next trees, D_CAN support is added
> to C_CAN driver.
>
> http://git.kernel.org/?p=linux/kernel/git/davem/net-next.git;
> a=commitdiff;h=69927fccd96b15bd228bb82d356a7a2a0cfaeefb
Meanwhile it's in Linus's git tree.
Marc
--
Pengutronix e.K. | Marc Kleine-Budde |
Industrial Linux Solutions | Phone: +49-231-2826-924 |
Vertretung West/Dortmund | Fax: +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686 | http://www.pengutronix.de |
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
[-- Attachment #2: Type: text/plain, Size: 192 bytes --]
_______________________________________________
devicetree-discuss mailing list
devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org
https://lists.ozlabs.org/listinfo/devicetree-discuss
^ permalink raw reply [flat|nested] 26+ messages in thread
* [PATCH v2 1/2] arm/dts: AM33XX: Add D_CAN device tree data
@ 2012-07-26 9:14 ` Marc Kleine-Budde
0 siblings, 0 replies; 26+ messages in thread
From: Marc Kleine-Budde @ 2012-07-26 9:14 UTC (permalink / raw)
To: linux-arm-kernel
On 07/26/2012 11:03 AM, AnilKumar, Chimata wrote:
> On Thu, Jul 26, 2012 at 14:16:33, Koen Kooi wrote:
>>
>> Op 25 jul. 2012, om 14:23 heeft AnilKumar Ch <anilkumar@ti.com> het volgende geschreven:
>>
>>> Add Bosch D_CAN controller device tree data to AM33XX dtsi file
>>> by adding d_can device node with all the necessary parameters.
>>>
>>> Signed-off-by: AnilKumar Ch <anilkumar@ti.com>
>>> ---
>>> arch/arm/boot/dts/am33xx.dtsi | 5 +++++
>>> 1 file changed, 5 insertions(+)
>>>
>>> diff --git a/arch/arm/boot/dts/am33xx.dtsi b/arch/arm/boot/dts/am33xx.dtsi
>>> index 9b974dc..2db2ffb 100644
>>> --- a/arch/arm/boot/dts/am33xx.dtsi
>>> +++ b/arch/arm/boot/dts/am33xx.dtsi
>>> @@ -163,5 +163,10 @@
>>> #size-cells = <0>;
>>> ti,hwmods = "i2c3";
>>> };
>>> +
>>> + dcan1: d_can at 481D0000 {
>>> + compatible = "bosch,d_can";
>>> + ti,hwmods = "d_can1";
>>> + };
>>> };
>>
>> I scanned the linux-networking mailinglist and l-o-ml, but I can't find the patchset that actually adds the d_can drivers, could you provide a link to that? I have 2 different CAN capes I'd like to test on beaglebone.
>>
>
> You can find it from linux-next or net-next trees, D_CAN support is added
> to C_CAN driver.
>
> http://git.kernel.org/?p=linux/kernel/git/davem/net-next.git;
> a=commitdiff;h=69927fccd96b15bd228bb82d356a7a2a0cfaeefb
Meanwhile it's in Linus's git tree.
Marc
--
Pengutronix e.K. | Marc Kleine-Budde |
Industrial Linux Solutions | Phone: +49-231-2826-924 |
Vertretung West/Dortmund | Fax: +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686 | http://www.pengutronix.de |
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 262 bytes
Desc: OpenPGP digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20120726/074c155e/attachment.sig>
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: [PATCH v2 1/2] arm/dts: AM33XX: Add D_CAN device tree data
2012-07-26 9:03 ` AnilKumar, Chimata
@ 2012-07-26 9:35 ` Koen Kooi
-1 siblings, 0 replies; 26+ messages in thread
From: Koen Kooi @ 2012-07-26 9:35 UTC (permalink / raw)
To: AnilKumar, Chimata
Cc: linux-omap, tony, wg, mkl, linux-arm-kernel, devicetree-discuss,
grant.likely
Op 26 jul. 2012, om 11:03 heeft "AnilKumar, Chimata" <anilkumar@ti.com> het volgende geschreven:
> On Thu, Jul 26, 2012 at 14:16:33, Koen Kooi wrote:
>>
>> Op 25 jul. 2012, om 14:23 heeft AnilKumar Ch <anilkumar@ti.com> het volgende geschreven:
>>
>>> Add Bosch D_CAN controller device tree data to AM33XX dtsi file
>>> by adding d_can device node with all the necessary parameters.
>>>
>>> Signed-off-by: AnilKumar Ch <anilkumar@ti.com>
>>> ---
>>> arch/arm/boot/dts/am33xx.dtsi | 5 +++++
>>> 1 file changed, 5 insertions(+)
>>>
>>> diff --git a/arch/arm/boot/dts/am33xx.dtsi b/arch/arm/boot/dts/am33xx.dtsi
>>> index 9b974dc..2db2ffb 100644
>>> --- a/arch/arm/boot/dts/am33xx.dtsi
>>> +++ b/arch/arm/boot/dts/am33xx.dtsi
>>> @@ -163,5 +163,10 @@
>>> #size-cells = <0>;
>>> ti,hwmods = "i2c3";
>>> };
>>> +
>>> + dcan1: d_can@481D0000 {
>>> + compatible = "bosch,d_can";
>>> + ti,hwmods = "d_can1";
>>> + };
>>> };
>>
>> I scanned the linux-networking mailinglist and l-o-ml, but I can't find the patchset that actually adds the d_can drivers, could you provide a link to that? I have 2 different CAN capes I'd like to test on beaglebone.
>>
>
> You can find it from linux-next or net-next trees, D_CAN support is added
> to C_CAN driver.
>
> http://git.kernel.org/?p=linux/kernel/git/davem/net-next.git;
> a=commitdiff;h=69927fccd96b15bd228bb82d356a7a2a0cfaeefb
Thanks! I'll try merging net-next into l-o master and see if I can get the CAN boards to work.
regards,
Koen
^ permalink raw reply [flat|nested] 26+ messages in thread
* [PATCH v2 1/2] arm/dts: AM33XX: Add D_CAN device tree data
@ 2012-07-26 9:35 ` Koen Kooi
0 siblings, 0 replies; 26+ messages in thread
From: Koen Kooi @ 2012-07-26 9:35 UTC (permalink / raw)
To: linux-arm-kernel
Op 26 jul. 2012, om 11:03 heeft "AnilKumar, Chimata" <anilkumar@ti.com> het volgende geschreven:
> On Thu, Jul 26, 2012 at 14:16:33, Koen Kooi wrote:
>>
>> Op 25 jul. 2012, om 14:23 heeft AnilKumar Ch <anilkumar@ti.com> het volgende geschreven:
>>
>>> Add Bosch D_CAN controller device tree data to AM33XX dtsi file
>>> by adding d_can device node with all the necessary parameters.
>>>
>>> Signed-off-by: AnilKumar Ch <anilkumar@ti.com>
>>> ---
>>> arch/arm/boot/dts/am33xx.dtsi | 5 +++++
>>> 1 file changed, 5 insertions(+)
>>>
>>> diff --git a/arch/arm/boot/dts/am33xx.dtsi b/arch/arm/boot/dts/am33xx.dtsi
>>> index 9b974dc..2db2ffb 100644
>>> --- a/arch/arm/boot/dts/am33xx.dtsi
>>> +++ b/arch/arm/boot/dts/am33xx.dtsi
>>> @@ -163,5 +163,10 @@
>>> #size-cells = <0>;
>>> ti,hwmods = "i2c3";
>>> };
>>> +
>>> + dcan1: d_can at 481D0000 {
>>> + compatible = "bosch,d_can";
>>> + ti,hwmods = "d_can1";
>>> + };
>>> };
>>
>> I scanned the linux-networking mailinglist and l-o-ml, but I can't find the patchset that actually adds the d_can drivers, could you provide a link to that? I have 2 different CAN capes I'd like to test on beaglebone.
>>
>
> You can find it from linux-next or net-next trees, D_CAN support is added
> to C_CAN driver.
>
> http://git.kernel.org/?p=linux/kernel/git/davem/net-next.git;
> a=commitdiff;h=69927fccd96b15bd228bb82d356a7a2a0cfaeefb
Thanks! I'll try merging net-next into l-o master and see if I can get the CAN boards to work.
regards,
Koen
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: [PATCH v2 1/2] arm/dts: AM33XX: Add D_CAN device tree data
2012-07-26 8:36 ` Daniel Mack
@ 2012-07-26 13:04 ` Sergei Shtylyov
-1 siblings, 0 replies; 26+ messages in thread
From: Sergei Shtylyov @ 2012-07-26 13:04 UTC (permalink / raw)
To: Daniel Mack
Cc: AnilKumar Ch, tony, devicetree-discuss, grant.likely, mkl,
linux-arm-kernel, linux-omap, wg
Hello.
On 26-07-2012 12:36, Daniel Mack wrote:
>>> Add Bosch D_CAN controller device tree data to AM33XX dtsi file
>>> by adding d_can device node with all the necessary parameters.
>>> Signed-off-by: AnilKumar Ch <anilkumar@ti.com>
>>> ---
>>> arch/arm/boot/dts/am33xx.dtsi | 5 +++++
>>> 1 file changed, 5 insertions(+)
>>> diff --git a/arch/arm/boot/dts/am33xx.dtsi b/arch/arm/boot/dts/am33xx.dtsi
>>> index 9b974dc..2db2ffb 100644
>>> --- a/arch/arm/boot/dts/am33xx.dtsi
>>> +++ b/arch/arm/boot/dts/am33xx.dtsi
>>> @@ -163,5 +163,10 @@
>>> #size-cells = <0>;
>>> ti,hwmods = "i2c3";
>>> };
>>> +
>>> + dcan1: d_can@481D0000 {
>>
>> Address postfix in the node name and no "reg" property?
> This still works due to the hwmod mappings OMAP relies on.
I.e. the "reg" property is populated in runtime?
> I would still
> put it there, so the switch to real DT definitions will be less painful.
How it helps anything?
> Daniel
WBR, Sergei
^ permalink raw reply [flat|nested] 26+ messages in thread
* [PATCH v2 1/2] arm/dts: AM33XX: Add D_CAN device tree data
@ 2012-07-26 13:04 ` Sergei Shtylyov
0 siblings, 0 replies; 26+ messages in thread
From: Sergei Shtylyov @ 2012-07-26 13:04 UTC (permalink / raw)
To: linux-arm-kernel
Hello.
On 26-07-2012 12:36, Daniel Mack wrote:
>>> Add Bosch D_CAN controller device tree data to AM33XX dtsi file
>>> by adding d_can device node with all the necessary parameters.
>>> Signed-off-by: AnilKumar Ch <anilkumar@ti.com>
>>> ---
>>> arch/arm/boot/dts/am33xx.dtsi | 5 +++++
>>> 1 file changed, 5 insertions(+)
>>> diff --git a/arch/arm/boot/dts/am33xx.dtsi b/arch/arm/boot/dts/am33xx.dtsi
>>> index 9b974dc..2db2ffb 100644
>>> --- a/arch/arm/boot/dts/am33xx.dtsi
>>> +++ b/arch/arm/boot/dts/am33xx.dtsi
>>> @@ -163,5 +163,10 @@
>>> #size-cells = <0>;
>>> ti,hwmods = "i2c3";
>>> };
>>> +
>>> + dcan1: d_can at 481D0000 {
>>
>> Address postfix in the node name and no "reg" property?
> This still works due to the hwmod mappings OMAP relies on.
I.e. the "reg" property is populated in runtime?
> I would still
> put it there, so the switch to real DT definitions will be less painful.
How it helps anything?
> Daniel
WBR, Sergei
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: [PATCH v2 1/2] arm/dts: AM33XX: Add D_CAN device tree data
2012-07-25 12:23 ` AnilKumar Ch
@ 2012-08-03 6:28 ` Vaibhav Hiremath
-1 siblings, 0 replies; 26+ messages in thread
From: Vaibhav Hiremath @ 2012-08-03 6:28 UTC (permalink / raw)
To: AnilKumar Ch; +Cc: linux-omap, devicetree-discuss, mkl, linux-arm-kernel
On 7/25/2012 5:53 PM, AnilKumar Ch wrote:
> Add Bosch D_CAN controller device tree data to AM33XX dtsi file
> by adding d_can device node with all the necessary parameters.
>
> Signed-off-by: AnilKumar Ch <anilkumar@ti.com>
> ---
> arch/arm/boot/dts/am33xx.dtsi | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/arch/arm/boot/dts/am33xx.dtsi b/arch/arm/boot/dts/am33xx.dtsi
> index 9b974dc..2db2ffb 100644
> --- a/arch/arm/boot/dts/am33xx.dtsi
> +++ b/arch/arm/boot/dts/am33xx.dtsi
> @@ -163,5 +163,10 @@
> #size-cells = <0>;
> ti,hwmods = "i2c3";
> };
> +
> + dcan1: d_can@481D0000 {
> + compatible = "bosch,d_can";
> + ti,hwmods = "d_can1";
> + };
Anil,
Any reason why we are only specifying dcan1 instance? Shouldn't we
specify dcan0 as well here?
Thanks,
Vaibhav
> };
> };
>
^ permalink raw reply [flat|nested] 26+ messages in thread
* [PATCH v2 1/2] arm/dts: AM33XX: Add D_CAN device tree data
@ 2012-08-03 6:28 ` Vaibhav Hiremath
0 siblings, 0 replies; 26+ messages in thread
From: Vaibhav Hiremath @ 2012-08-03 6:28 UTC (permalink / raw)
To: linux-arm-kernel
On 7/25/2012 5:53 PM, AnilKumar Ch wrote:
> Add Bosch D_CAN controller device tree data to AM33XX dtsi file
> by adding d_can device node with all the necessary parameters.
>
> Signed-off-by: AnilKumar Ch <anilkumar@ti.com>
> ---
> arch/arm/boot/dts/am33xx.dtsi | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/arch/arm/boot/dts/am33xx.dtsi b/arch/arm/boot/dts/am33xx.dtsi
> index 9b974dc..2db2ffb 100644
> --- a/arch/arm/boot/dts/am33xx.dtsi
> +++ b/arch/arm/boot/dts/am33xx.dtsi
> @@ -163,5 +163,10 @@
> #size-cells = <0>;
> ti,hwmods = "i2c3";
> };
> +
> + dcan1: d_can at 481D0000 {
> + compatible = "bosch,d_can";
> + ti,hwmods = "d_can1";
> + };
Anil,
Any reason why we are only specifying dcan1 instance? Shouldn't we
specify dcan0 as well here?
Thanks,
Vaibhav
> };
> };
>
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: [PATCH v2 1/2] arm/dts: AM33XX: Add D_CAN device tree data
2012-07-26 13:04 ` Sergei Shtylyov
@ 2012-08-03 9:14 ` Vaibhav Hiremath
-1 siblings, 0 replies; 26+ messages in thread
From: Vaibhav Hiremath @ 2012-08-03 9:14 UTC (permalink / raw)
To: Sergei Shtylyov
Cc: devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ,
linux-omap-u79uwXL29TY76Z2rM5mHXA, mkl-bIcnvbaLZ9MEGnE8C9+IrQ,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r
On 7/26/2012 6:34 PM, Sergei Shtylyov wrote:
> Hello.
>
> On 26-07-2012 12:36, Daniel Mack wrote:
>
>>>> Add Bosch D_CAN controller device tree data to AM33XX dtsi file
>>>> by adding d_can device node with all the necessary parameters.
>
>>>> Signed-off-by: AnilKumar Ch <anilkumar-l0cyMroinI0@public.gmane.org>
>>>> ---
>>>> arch/arm/boot/dts/am33xx.dtsi | 5 +++++
>>>> 1 file changed, 5 insertions(+)
>
>>>> diff --git a/arch/arm/boot/dts/am33xx.dtsi b/arch/arm/boot/dts/am33xx.dtsi
>>>> index 9b974dc..2db2ffb 100644
>>>> --- a/arch/arm/boot/dts/am33xx.dtsi
>>>> +++ b/arch/arm/boot/dts/am33xx.dtsi
>>>> @@ -163,5 +163,10 @@
>>>> #size-cells = <0>;
>>>> ti,hwmods = "i2c3";
>>>> };
>>>> +
>>>> + dcan1: d_can@481D0000 {
>>>
>>> Address postfix in the node name and no "reg" property?
>
>> This still works due to the hwmod mappings OMAP relies on.
>
> I.e. the "reg" property is populated in runtime?
>
>> I would still
>> put it there, so the switch to real DT definitions will be less painful.
>
> How it helps anything?
>
This is required field if you want to use "of_dev_auxdata", without
"reg" property OF layer fails to create dev_id (name) bindings with what
you have specified as part of "of_dev_auxdata".
And with respect to CAN driver, even though we are using hwmod, I would
want to create dev_id = d_can.0 and d_can.1. And this is only possible
if Address and compatible string matches.
So this field is important and required in this case.
Thanks,
Vaibhav
^ permalink raw reply [flat|nested] 26+ messages in thread
* [PATCH v2 1/2] arm/dts: AM33XX: Add D_CAN device tree data
@ 2012-08-03 9:14 ` Vaibhav Hiremath
0 siblings, 0 replies; 26+ messages in thread
From: Vaibhav Hiremath @ 2012-08-03 9:14 UTC (permalink / raw)
To: linux-arm-kernel
On 7/26/2012 6:34 PM, Sergei Shtylyov wrote:
> Hello.
>
> On 26-07-2012 12:36, Daniel Mack wrote:
>
>>>> Add Bosch D_CAN controller device tree data to AM33XX dtsi file
>>>> by adding d_can device node with all the necessary parameters.
>
>>>> Signed-off-by: AnilKumar Ch <anilkumar@ti.com>
>>>> ---
>>>> arch/arm/boot/dts/am33xx.dtsi | 5 +++++
>>>> 1 file changed, 5 insertions(+)
>
>>>> diff --git a/arch/arm/boot/dts/am33xx.dtsi b/arch/arm/boot/dts/am33xx.dtsi
>>>> index 9b974dc..2db2ffb 100644
>>>> --- a/arch/arm/boot/dts/am33xx.dtsi
>>>> +++ b/arch/arm/boot/dts/am33xx.dtsi
>>>> @@ -163,5 +163,10 @@
>>>> #size-cells = <0>;
>>>> ti,hwmods = "i2c3";
>>>> };
>>>> +
>>>> + dcan1: d_can at 481D0000 {
>>>
>>> Address postfix in the node name and no "reg" property?
>
>> This still works due to the hwmod mappings OMAP relies on.
>
> I.e. the "reg" property is populated in runtime?
>
>> I would still
>> put it there, so the switch to real DT definitions will be less painful.
>
> How it helps anything?
>
This is required field if you want to use "of_dev_auxdata", without
"reg" property OF layer fails to create dev_id (name) bindings with what
you have specified as part of "of_dev_auxdata".
And with respect to CAN driver, even though we are using hwmod, I would
want to create dev_id = d_can.0 and d_can.1. And this is only possible
if Address and compatible string matches.
So this field is important and required in this case.
Thanks,
Vaibhav
^ permalink raw reply [flat|nested] 26+ messages in thread
* RE: [PATCH v2 1/2] arm/dts: AM33XX: Add D_CAN device tree data
2012-08-03 6:28 ` Vaibhav Hiremath
@ 2012-08-07 11:40 ` AnilKumar, Chimata
-1 siblings, 0 replies; 26+ messages in thread
From: AnilKumar, Chimata @ 2012-08-07 11:40 UTC (permalink / raw)
To: Hiremath, Vaibhav; +Cc: linux-omap, devicetree-discuss, mkl, linux-arm-kernel
Vaibhav,
Thanks for the review.
On Fri, Aug 03, 2012 at 11:58:41, Hiremath, Vaibhav wrote:
>
>
> On 7/25/2012 5:53 PM, AnilKumar Ch wrote:
> > Add Bosch D_CAN controller device tree data to AM33XX dtsi file
> > by adding d_can device node with all the necessary parameters.
> >
> > Signed-off-by: AnilKumar Ch <anilkumar@ti.com>
> > ---
> > arch/arm/boot/dts/am33xx.dtsi | 5 +++++
> > 1 file changed, 5 insertions(+)
> >
> > diff --git a/arch/arm/boot/dts/am33xx.dtsi b/arch/arm/boot/dts/am33xx.dtsi
> > index 9b974dc..2db2ffb 100644
> > --- a/arch/arm/boot/dts/am33xx.dtsi
> > +++ b/arch/arm/boot/dts/am33xx.dtsi
> > @@ -163,5 +163,10 @@
> > #size-cells = <0>;
> > ti,hwmods = "i2c3";
> > };
> > +
> > + dcan1: d_can@481D0000 {
> > + compatible = "bosch,d_can";
> > + ti,hwmods = "d_can1";
> > + };
>
> Anil,
>
> Any reason why we are only specifying dcan1 instance? Shouldn't we
> specify dcan0 as well here?
>
Yes, I agree dcan0 needs to add because SoC support two instances. I
have added d_can1 only because on AM335x-EVM d_can1 is available and
in other case AM335x-bone have two instances available. I will send next
version of these patches.
Regards
AnilKumar
^ permalink raw reply [flat|nested] 26+ messages in thread
* [PATCH v2 1/2] arm/dts: AM33XX: Add D_CAN device tree data
@ 2012-08-07 11:40 ` AnilKumar, Chimata
0 siblings, 0 replies; 26+ messages in thread
From: AnilKumar, Chimata @ 2012-08-07 11:40 UTC (permalink / raw)
To: linux-arm-kernel
Vaibhav,
Thanks for the review.
On Fri, Aug 03, 2012 at 11:58:41, Hiremath, Vaibhav wrote:
>
>
> On 7/25/2012 5:53 PM, AnilKumar Ch wrote:
> > Add Bosch D_CAN controller device tree data to AM33XX dtsi file
> > by adding d_can device node with all the necessary parameters.
> >
> > Signed-off-by: AnilKumar Ch <anilkumar@ti.com>
> > ---
> > arch/arm/boot/dts/am33xx.dtsi | 5 +++++
> > 1 file changed, 5 insertions(+)
> >
> > diff --git a/arch/arm/boot/dts/am33xx.dtsi b/arch/arm/boot/dts/am33xx.dtsi
> > index 9b974dc..2db2ffb 100644
> > --- a/arch/arm/boot/dts/am33xx.dtsi
> > +++ b/arch/arm/boot/dts/am33xx.dtsi
> > @@ -163,5 +163,10 @@
> > #size-cells = <0>;
> > ti,hwmods = "i2c3";
> > };
> > +
> > + dcan1: d_can at 481D0000 {
> > + compatible = "bosch,d_can";
> > + ti,hwmods = "d_can1";
> > + };
>
> Anil,
>
> Any reason why we are only specifying dcan1 instance? Shouldn't we
> specify dcan0 as well here?
>
Yes, I agree dcan0 needs to add because SoC support two instances. I
have added d_can1 only because on AM335x-EVM d_can1 is available and
in other case AM335x-bone have two instances available. I will send next
version of these patches.
Regards
AnilKumar
^ permalink raw reply [flat|nested] 26+ messages in thread
end of thread, other threads:[~2012-08-07 11:40 UTC | newest]
Thread overview: 26+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2012-07-25 12:23 [PATCH v2 0/2] Add D_CAN device tree data to AM335x-EVM AnilKumar Ch
2012-07-25 12:23 ` AnilKumar Ch
2012-07-25 12:23 ` [PATCH v2 1/2] arm/dts: AM33XX: Add D_CAN device tree data AnilKumar Ch
2012-07-25 12:23 ` AnilKumar Ch
2012-07-25 12:43 ` Sergei Shtylyov
2012-07-25 12:43 ` Sergei Shtylyov
2012-07-26 8:36 ` Daniel Mack
2012-07-26 8:36 ` Daniel Mack
2012-07-26 13:04 ` Sergei Shtylyov
2012-07-26 13:04 ` Sergei Shtylyov
[not found] ` <50114069.7070605-Igf4POYTYCDQT0dZR+AlfA@public.gmane.org>
2012-08-03 9:14 ` Vaibhav Hiremath
2012-08-03 9:14 ` Vaibhav Hiremath
2012-07-26 8:46 ` Koen Kooi
2012-07-26 8:46 ` Koen Kooi
[not found] ` <9D2B44C8-820E-4E96-A480-7A650583BC92-QLwJDigV5abLmq1fohREcCpxlwaOVQ5f@public.gmane.org>
2012-07-26 9:03 ` AnilKumar, Chimata
2012-07-26 9:03 ` AnilKumar, Chimata
[not found] ` <331ABD5ECB02734CA317220B2BBEABC13EA04433-Er742YJ7I/eIQmiDNMet8wC/G2K4zDHf@public.gmane.org>
2012-07-26 9:14 ` Marc Kleine-Budde
2012-07-26 9:14 ` Marc Kleine-Budde
2012-07-26 9:35 ` Koen Kooi
2012-07-26 9:35 ` Koen Kooi
2012-08-03 6:28 ` Vaibhav Hiremath
2012-08-03 6:28 ` Vaibhav Hiremath
2012-08-07 11:40 ` AnilKumar, Chimata
2012-08-07 11:40 ` AnilKumar, Chimata
[not found] ` <1343219012-19472-1-git-send-email-anilkumar-l0cyMroinI0@public.gmane.org>
2012-07-25 12:23 ` [PATCH v2 2/2] arm/dts: AM33XX: Configure pinmuxs for D_CAN1 on AM335x-EVM AnilKumar Ch
2012-07-25 12:23 ` AnilKumar Ch
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.