Message ID | 1405503050-16796-1-git-send-email-b29396@freescale.com |
---|---|
State | Accepted, archived |
Commit | e35430807dad7f89e2a27e70ea1d6c29819cb749 |
Headers | show |
On 07/16/2014 03:00 PM, Dong Aisheng wrote: > The patch adds the basic CAN TX/RX function support for Bosch M_CAN controller. > For TX, only one dedicated tx buffer is used for sending data. > For RX, RXFIFO 0 is used for receiving data to avoid overflow. > Rx FIFO 1 and Rx Buffers are not used currently, as well as Tx Event FIFO. > > Due to the message ram can be shared by multi m_can instances > and the fifo element is configurable which is SoC dependant, > the design is to parse the message ram related configuration data from device > tree rather than hardcode define it in driver which can make the message > ram sharing fully transparent to M_CAN controller driver, > then we can gain better driver maintainability and future features upgrade. > > M_CAN also supports CANFD protocol features like data payload up to 64 bytes > and bitrate switch at runtime, however, this patch still does not add the > support for these features. > > Cc: Wolfgang Grandegger <wg@grandegger.com> > Cc: Marc Kleine-Budde <mkl@pengutronix.de> > Cc: Mark Rutland <mark.rutland@arm.com> > Cc: Oliver Hartkopp <socketcan@hartkopp.net> > Cc: Varka Bhadram <varkabhadram@gmail.com> > Signed-off-by: Dong Aisheng <b29396@freescale.com> > --- > changes since v4: > some minor changes: > - introduce m_can_fifo_write and is_lec_err functin > - define macro M_CAN_FIFO_XXX for FIFO > - move m_can_of_table before platform_driver > - a few indent fix > > Changes since v3: > A few minor changes: > - use the updated name of bosch,mram-cfg > - remove .owner = THIS_MODULE > - add a line comment for mram_cfg structure > > Changes since v2: > - fix checkpatch warnings > - handle CAN_CTRLMODE_BERR_REPORTING properly that disable LEC error > interrupts (Bus error) if no CAN_CTRLMODE_BERR_REPORTING. > - introduce struct mram_cfg array to store message ram configuration data > for each fifo > - fix txb offset calculate wrong issue(should not plus mram_off again) > - check return for clk_prepare_enable > - split doc part into a separate patch > > Changes since v1: > Addressed all comments from Mark Rutland, Hartkopp and Marc Kleine-Budde > - merge three patches into one > - create directory drivers/net/can/m_can > - improve binding doc > - make sure using valid pointer before netif_receive_skb(skb) > - remove debug info a bit > - let the stats are updated even if alloc_can_err_skb() fails > - other small fixes > --- > drivers/net/can/Kconfig | 2 + > drivers/net/can/Makefile | 1 + > drivers/net/can/m_can/Kconfig | 4 + > drivers/net/can/m_can/Makefile | 7 + > drivers/net/can/m_can/m_can.c | 1202 ++++++++++++++++++++++++++++++++++++++++ > 5 files changed, 1216 insertions(+), 0 deletions(-) > create mode 100644 drivers/net/can/m_can/Kconfig > create mode 100644 drivers/net/can/m_can/Makefile > create mode 100644 drivers/net/can/m_can/m_can.c > > This series addressed all of my comments ...Thanks :-) Reviewed-by: Varka Bhadram <varkabhadram@gmail.com>
On 07/16/2014 11:30 AM, Dong Aisheng wrote: > add M_CAN device tree binding documentation > > Cc: Wolfgang Grandegger <wg@grandegger.com> > Cc: Marc Kleine-Budde <mkl@pengutronix.de> > Cc: Mark Rutland <mark.rutland@arm.com> > Cc: Oliver Hartkopp <socketcan@hartkopp.net> > Cc: Varka Bhadram <varkabhadram@gmail.com> > Signed-off-by: Dong Aisheng <b29396@freescale.com> > --- > Changes since v4: > - change the name of board dtsi to board dts which is more common > > Changes since v3: > - change mram-cfg property name to bosch,mram-cfg > - indent change > --- > .../devicetree/bindings/net/can/m_can.txt | 67 ++++++++++++++++++++ > 1 files changed, 67 insertions(+), 0 deletions(-) > create mode 100644 Documentation/devicetree/bindings/net/can/m_can.txt I'll apply this series once we've got an Ack for the DT folks. Marc
On Wed, Jul 16, 2014 at 03:28:09PM +0530, Varka Bhadram wrote: > On 07/16/2014 03:00 PM, Dong Aisheng wrote: > >The patch adds the basic CAN TX/RX function support for Bosch M_CAN controller. > >For TX, only one dedicated tx buffer is used for sending data. > >For RX, RXFIFO 0 is used for receiving data to avoid overflow. > >Rx FIFO 1 and Rx Buffers are not used currently, as well as Tx Event FIFO. > > > >Due to the message ram can be shared by multi m_can instances > >and the fifo element is configurable which is SoC dependant, > >the design is to parse the message ram related configuration data from device > >tree rather than hardcode define it in driver which can make the message > >ram sharing fully transparent to M_CAN controller driver, > >then we can gain better driver maintainability and future features upgrade. > > > >M_CAN also supports CANFD protocol features like data payload up to 64 bytes > >and bitrate switch at runtime, however, this patch still does not add the > >support for these features. > > > >Cc: Wolfgang Grandegger <wg@grandegger.com> > >Cc: Marc Kleine-Budde <mkl@pengutronix.de> > >Cc: Mark Rutland <mark.rutland@arm.com> > >Cc: Oliver Hartkopp <socketcan@hartkopp.net> > >Cc: Varka Bhadram <varkabhadram@gmail.com> > >Signed-off-by: Dong Aisheng <b29396@freescale.com> > >--- > >changes since v4: > >some minor changes: > >- introduce m_can_fifo_write and is_lec_err functin > >- define macro M_CAN_FIFO_XXX for FIFO > >- move m_can_of_table before platform_driver > >- a few indent fix > > > >Changes since v3: > >A few minor changes: > >- use the updated name of bosch,mram-cfg > >- remove .owner = THIS_MODULE > >- add a line comment for mram_cfg structure > > > >Changes since v2: > >- fix checkpatch warnings > >- handle CAN_CTRLMODE_BERR_REPORTING properly that disable LEC error > > interrupts (Bus error) if no CAN_CTRLMODE_BERR_REPORTING. > >- introduce struct mram_cfg array to store message ram configuration data > > for each fifo > >- fix txb offset calculate wrong issue(should not plus mram_off again) > >- check return for clk_prepare_enable > >- split doc part into a separate patch > > > >Changes since v1: > >Addressed all comments from Mark Rutland, Hartkopp and Marc Kleine-Budde > >- merge three patches into one > >- create directory drivers/net/can/m_can > >- improve binding doc > >- make sure using valid pointer before netif_receive_skb(skb) > >- remove debug info a bit > >- let the stats are updated even if alloc_can_err_skb() fails > >- other small fixes > >--- > > drivers/net/can/Kconfig | 2 + > > drivers/net/can/Makefile | 1 + > > drivers/net/can/m_can/Kconfig | 4 + > > drivers/net/can/m_can/Makefile | 7 + > > drivers/net/can/m_can/m_can.c | 1202 ++++++++++++++++++++++++++++++++++++++++ > > 5 files changed, 1216 insertions(+), 0 deletions(-) > > create mode 100644 drivers/net/can/m_can/Kconfig > > create mode 100644 drivers/net/can/m_can/Makefile > > create mode 100644 drivers/net/can/m_can/m_can.c > > > > > This series addressed all of my comments ...Thanks :-) > > Reviewed-by: Varka Bhadram <varkabhadram@gmail.com> > Thanks for the review! :-) Regards Dong Aisheng > -- > Regards, > Varka Bhadram. > -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
On Wed, Jul 16, 2014 at 12:05:05PM +0200, Marc Kleine-Budde wrote: > On 07/16/2014 11:30 AM, Dong Aisheng wrote: > > add M_CAN device tree binding documentation > > > > Cc: Wolfgang Grandegger <wg@grandegger.com> > > Cc: Marc Kleine-Budde <mkl@pengutronix.de> > > Cc: Mark Rutland <mark.rutland@arm.com> > > Cc: Oliver Hartkopp <socketcan@hartkopp.net> > > Cc: Varka Bhadram <varkabhadram@gmail.com> > > Signed-off-by: Dong Aisheng <b29396@freescale.com> > > --- > > Changes since v4: > > - change the name of board dtsi to board dts which is more common > > > > Changes since v3: > > - change mram-cfg property name to bosch,mram-cfg > > - indent change > > --- > > .../devicetree/bindings/net/can/m_can.txt | 67 ++++++++++++++++++++ > > 1 files changed, 67 insertions(+), 0 deletions(-) > > create mode 100644 Documentation/devicetree/bindings/net/can/m_can.txt > > I'll apply this series once we've got an Ack for the DT folks. > Okay, thanks! Copy Grant, Rob and Mark in case they have comments. Regards Dong Aisheng > 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 | > -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Ping... On Wed, Jul 16, 2014 at 6:40 PM, Dong Aisheng <b29396@freescale.com> wrote: > On Wed, Jul 16, 2014 at 12:05:05PM +0200, Marc Kleine-Budde wrote: >> On 07/16/2014 11:30 AM, Dong Aisheng wrote: >> > add M_CAN device tree binding documentation >> > >> > Cc: Wolfgang Grandegger <wg@grandegger.com> >> > Cc: Marc Kleine-Budde <mkl@pengutronix.de> >> > Cc: Mark Rutland <mark.rutland@arm.com> >> > Cc: Oliver Hartkopp <socketcan@hartkopp.net> >> > Cc: Varka Bhadram <varkabhadram@gmail.com> >> > Signed-off-by: Dong Aisheng <b29396@freescale.com> >> > --- >> > Changes since v4: >> > - change the name of board dtsi to board dts which is more common >> > >> > Changes since v3: >> > - change mram-cfg property name to bosch,mram-cfg >> > - indent change >> > --- >> > .../devicetree/bindings/net/can/m_can.txt | 67 ++++++++++++++++++++ >> > 1 files changed, 67 insertions(+), 0 deletions(-) >> > create mode 100644 Documentation/devicetree/bindings/net/can/m_can.txt >> >> I'll apply this series once we've got an Ack for the DT folks. >> > > Okay, thanks! > > Copy Grant, Rob and Mark in case they have comments. > > Regards > Dong Aisheng > >> 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 | >> > > > > _______________________________________________ > linux-arm-kernel mailing list > linux-arm-kernel@lists.infradead.org > http://lists.infradead.org/mailman/listinfo/linux-arm-kernel -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
On 07/16/2014 11:30 AM, Dong Aisheng wrote: > add M_CAN device tree binding documentation > > Cc: Wolfgang Grandegger <wg@grandegger.com> > Cc: Marc Kleine-Budde <mkl@pengutronix.de> > Cc: Mark Rutland <mark.rutland@arm.com> > Cc: Oliver Hartkopp <socketcan@hartkopp.net> > Cc: Varka Bhadram <varkabhadram@gmail.com> > Signed-off-by: Dong Aisheng <b29396@freescale.com> Are there any comment from the DT side to this patch? Preferred an Acked-by :) The series looks good to me, I'm waiting for an Ack to apply it to the linux-can-next tree. Marc > --- > Changes since v4: > - change the name of board dtsi to board dts which is more common > > Changes since v3: > - change mram-cfg property name to bosch,mram-cfg > - indent change > --- > .../devicetree/bindings/net/can/m_can.txt | 67 ++++++++++++++++++++ > 1 files changed, 67 insertions(+), 0 deletions(-) > create mode 100644 Documentation/devicetree/bindings/net/can/m_can.txt > > diff --git a/Documentation/devicetree/bindings/net/can/m_can.txt b/Documentation/devicetree/bindings/net/can/m_can.txt > new file mode 100644 > index 0000000..9e33177 > --- /dev/null > +++ b/Documentation/devicetree/bindings/net/can/m_can.txt > @@ -0,0 +1,67 @@ > +Bosch MCAN controller Device Tree Bindings > +------------------------------------------------- > + > +Required properties: > +- compatible : Should be "bosch,m_can" for M_CAN controllers > +- reg : physical base address and size of the M_CAN > + registers map and Message RAM > +- reg-names : Should be "m_can" and "message_ram" > +- interrupts : Should be the interrupt number of M_CAN interrupt > + line 0 and line 1, could be same if sharing > + the same interrupt. > +- interrupt-names : Should contain "int0" and "int1" > +- clocks : Clocks used by controller, should be host clock > + and CAN clock. > +- clock-names : Should contain "hclk" and "cclk" > +- pinctrl-<n> : Pinctrl states as described in bindings/pinctrl/pinctrl-bindings.txt > +- pinctrl-names : Names corresponding to the numbered pinctrl states > +- bosch,mram-cfg : Message RAM configuration data. > + Multiple M_CAN instances can share the same Message > + RAM and each element(e.g Rx FIFO or Tx Buffer and etc) > + number in Message RAM is also configurable, > + so this property is telling driver how the shared or > + private Message RAM are used by this M_CAN controller. > + > + The format should be as follows: > + <offset sidf_elems xidf_elems rxf0_elems rxf1_elems > + rxb_elems txe_elems txb_elems> > + The 'offset' is an address offset of the Message RAM > + where the following elements start from. This is > + usually set to 0x0 if you're using a private Message > + RAM. The remain cells are used to specify how many > + elements are used for each FIFO/Buffer. > + > + M_CAN includes the following elements according to user manual: > + 11-bit Filter 0-128 elements / 0-128 words > + 29-bit Filter 0-64 elements / 0-128 words > + Rx FIFO 0 0-64 elements / 0-1152 words > + Rx FIFO 1 0-64 elements / 0-1152 words > + Rx Buffers 0-64 elements / 0-1152 words > + Tx Event FIFO 0-32 elements / 0-64 words > + Tx Buffers 0-32 elements / 0-576 words > + > + Please refer to 2.4.1 Message RAM Configuration in > + Bosch M_CAN user manual for details. > + > +Example: > +SoC dtsi: > +m_can1: can@020e8000 { > + compatible = "bosch,m_can"; > + reg = <0x020e8000 0x4000>, <0x02298000 0x4000>; > + reg-names = "m_can", "message_ram"; > + interrupts = <0 114 0x04>, > + <0 114 0x04>; > + interrupt-names = "int0", "int1"; > + clocks = <&clks IMX6SX_CLK_CANFD>, > + <&clks IMX6SX_CLK_CANFD>; > + clock-names = "hclk", "cclk"; > + bosch,mram-cfg = <0x0 0 0 32 0 0 0 1>; > + status = "disabled"; > +}; > + > +Board dts: > +&m_can1 { > + pinctrl-names = "default"; > + pinctrl-0 = <&pinctrl_m_can1>; > + status = "enabled"; > +}; >
Ping... On Wed, Jul 30, 2014 at 7:52 PM, Marc Kleine-Budde <mkl@pengutronix.de> wrote: > On 07/16/2014 11:30 AM, Dong Aisheng wrote: >> add M_CAN device tree binding documentation >> >> Cc: Wolfgang Grandegger <wg@grandegger.com> >> Cc: Marc Kleine-Budde <mkl@pengutronix.de> >> Cc: Mark Rutland <mark.rutland@arm.com> >> Cc: Oliver Hartkopp <socketcan@hartkopp.net> >> Cc: Varka Bhadram <varkabhadram@gmail.com> >> Signed-off-by: Dong Aisheng <b29396@freescale.com> > > Are there any comment from the DT side to this patch? > Preferred an Acked-by :) > > The series looks good to me, I'm waiting for an Ack to apply it to the > linux-can-next tree. > > Marc > >> --- >> Changes since v4: >> - change the name of board dtsi to board dts which is more common >> >> Changes since v3: >> - change mram-cfg property name to bosch,mram-cfg >> - indent change >> --- >> .../devicetree/bindings/net/can/m_can.txt | 67 ++++++++++++++++++++ >> 1 files changed, 67 insertions(+), 0 deletions(-) >> create mode 100644 Documentation/devicetree/bindings/net/can/m_can.txt >> >> diff --git a/Documentation/devicetree/bindings/net/can/m_can.txt b/Documentation/devicetree/bindings/net/can/m_can.txt >> new file mode 100644 >> index 0000000..9e33177 >> --- /dev/null >> +++ b/Documentation/devicetree/bindings/net/can/m_can.txt >> @@ -0,0 +1,67 @@ >> +Bosch MCAN controller Device Tree Bindings >> +------------------------------------------------- >> + >> +Required properties: >> +- compatible : Should be "bosch,m_can" for M_CAN controllers >> +- reg : physical base address and size of the M_CAN >> + registers map and Message RAM >> +- reg-names : Should be "m_can" and "message_ram" >> +- interrupts : Should be the interrupt number of M_CAN interrupt >> + line 0 and line 1, could be same if sharing >> + the same interrupt. >> +- interrupt-names : Should contain "int0" and "int1" >> +- clocks : Clocks used by controller, should be host clock >> + and CAN clock. >> +- clock-names : Should contain "hclk" and "cclk" >> +- pinctrl-<n> : Pinctrl states as described in bindings/pinctrl/pinctrl-bindings.txt >> +- pinctrl-names : Names corresponding to the numbered pinctrl states >> +- bosch,mram-cfg : Message RAM configuration data. >> + Multiple M_CAN instances can share the same Message >> + RAM and each element(e.g Rx FIFO or Tx Buffer and etc) >> + number in Message RAM is also configurable, >> + so this property is telling driver how the shared or >> + private Message RAM are used by this M_CAN controller. >> + >> + The format should be as follows: >> + <offset sidf_elems xidf_elems rxf0_elems rxf1_elems >> + rxb_elems txe_elems txb_elems> >> + The 'offset' is an address offset of the Message RAM >> + where the following elements start from. This is >> + usually set to 0x0 if you're using a private Message >> + RAM. The remain cells are used to specify how many >> + elements are used for each FIFO/Buffer. >> + >> + M_CAN includes the following elements according to user manual: >> + 11-bit Filter 0-128 elements / 0-128 words >> + 29-bit Filter 0-64 elements / 0-128 words >> + Rx FIFO 0 0-64 elements / 0-1152 words >> + Rx FIFO 1 0-64 elements / 0-1152 words >> + Rx Buffers 0-64 elements / 0-1152 words >> + Tx Event FIFO 0-32 elements / 0-64 words >> + Tx Buffers 0-32 elements / 0-576 words >> + >> + Please refer to 2.4.1 Message RAM Configuration in >> + Bosch M_CAN user manual for details. >> + >> +Example: >> +SoC dtsi: >> +m_can1: can@020e8000 { >> + compatible = "bosch,m_can"; >> + reg = <0x020e8000 0x4000>, <0x02298000 0x4000>; >> + reg-names = "m_can", "message_ram"; >> + interrupts = <0 114 0x04>, >> + <0 114 0x04>; >> + interrupt-names = "int0", "int1"; >> + clocks = <&clks IMX6SX_CLK_CANFD>, >> + <&clks IMX6SX_CLK_CANFD>; >> + clock-names = "hclk", "cclk"; >> + bosch,mram-cfg = <0x0 0 0 32 0 0 0 1>; >> + status = "disabled"; >> +}; >> + >> +Board dts: >> +&m_can1 { >> + pinctrl-names = "default"; >> + pinctrl-0 = <&pinctrl_m_can1>; >> + status = "enabled"; >> +}; >> > > > -- > 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 | > > > _______________________________________________ > linux-arm-kernel mailing list > linux-arm-kernel@lists.infradead.org > http://lists.infradead.org/mailman/listinfo/linux-arm-kernel > -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
On 08/14/2014 11:30 AM, Dong Aisheng wrote: > Ping... > > On Wed, Jul 30, 2014 at 7:52 PM, Marc Kleine-Budde <mkl@pengutronix.de> wrote: >> On 07/16/2014 11:30 AM, Dong Aisheng wrote: >>> add M_CAN device tree binding documentation Applied both to linux-can-next. Thanks, Marc
diff --git a/Documentation/devicetree/bindings/net/can/m_can.txt b/Documentation/devicetree/bindings/net/can/m_can.txt new file mode 100644 index 0000000..9e33177 --- /dev/null +++ b/Documentation/devicetree/bindings/net/can/m_can.txt @@ -0,0 +1,67 @@ +Bosch MCAN controller Device Tree Bindings +------------------------------------------------- + +Required properties: +- compatible : Should be "bosch,m_can" for M_CAN controllers +- reg : physical base address and size of the M_CAN + registers map and Message RAM +- reg-names : Should be "m_can" and "message_ram" +- interrupts : Should be the interrupt number of M_CAN interrupt + line 0 and line 1, could be same if sharing + the same interrupt. +- interrupt-names : Should contain "int0" and "int1" +- clocks : Clocks used by controller, should be host clock + and CAN clock. +- clock-names : Should contain "hclk" and "cclk" +- pinctrl-<n> : Pinctrl states as described in bindings/pinctrl/pinctrl-bindings.txt +- pinctrl-names : Names corresponding to the numbered pinctrl states +- bosch,mram-cfg : Message RAM configuration data. + Multiple M_CAN instances can share the same Message + RAM and each element(e.g Rx FIFO or Tx Buffer and etc) + number in Message RAM is also configurable, + so this property is telling driver how the shared or + private Message RAM are used by this M_CAN controller. + + The format should be as follows: + <offset sidf_elems xidf_elems rxf0_elems rxf1_elems + rxb_elems txe_elems txb_elems> + The 'offset' is an address offset of the Message RAM + where the following elements start from. This is + usually set to 0x0 if you're using a private Message + RAM. The remain cells are used to specify how many + elements are used for each FIFO/Buffer. + + M_CAN includes the following elements according to user manual: + 11-bit Filter 0-128 elements / 0-128 words + 29-bit Filter 0-64 elements / 0-128 words + Rx FIFO 0 0-64 elements / 0-1152 words + Rx FIFO 1 0-64 elements / 0-1152 words + Rx Buffers 0-64 elements / 0-1152 words + Tx Event FIFO 0-32 elements / 0-64 words + Tx Buffers 0-32 elements / 0-576 words + + Please refer to 2.4.1 Message RAM Configuration in + Bosch M_CAN user manual for details. + +Example: +SoC dtsi: +m_can1: can@020e8000 { + compatible = "bosch,m_can"; + reg = <0x020e8000 0x4000>, <0x02298000 0x4000>; + reg-names = "m_can", "message_ram"; + interrupts = <0 114 0x04>, + <0 114 0x04>; + interrupt-names = "int0", "int1"; + clocks = <&clks IMX6SX_CLK_CANFD>, + <&clks IMX6SX_CLK_CANFD>; + clock-names = "hclk", "cclk"; + bosch,mram-cfg = <0x0 0 0 32 0 0 0 1>; + status = "disabled"; +}; + +Board dts: +&m_can1 { + pinctrl-names = "default"; + pinctrl-0 = <&pinctrl_m_can1>; + status = "enabled"; +};
add M_CAN device tree binding documentation Cc: Wolfgang Grandegger <wg@grandegger.com> Cc: Marc Kleine-Budde <mkl@pengutronix.de> Cc: Mark Rutland <mark.rutland@arm.com> Cc: Oliver Hartkopp <socketcan@hartkopp.net> Cc: Varka Bhadram <varkabhadram@gmail.com> Signed-off-by: Dong Aisheng <b29396@freescale.com> --- Changes since v4: - change the name of board dtsi to board dts which is more common Changes since v3: - change mram-cfg property name to bosch,mram-cfg - indent change --- .../devicetree/bindings/net/can/m_can.txt | 67 ++++++++++++++++++++ 1 files changed, 67 insertions(+), 0 deletions(-) create mode 100644 Documentation/devicetree/bindings/net/can/m_can.txt