From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: MIME-Version: 1.0 In-Reply-To: References: <404315f0-fc9e-93e2-54df-f85e484d9389@st.com> <65096fbe-3f06-c8db-fbe8-29f0be28cb61@st.com> From: =?UTF-8?Q?Rados=C5=82aw_Pietrzyk?= Date: Mon, 31 Oct 2016 19:58:15 +0100 Message-ID: Subject: Re: [PATCH] ARM: DT: stm32: move dma translation to board files Content-Type: multipart/alternative; boundary=001a113f16e05d7f5d05402dca11 To: Bruno Herrera Cc: Alexandre Torgue , mark.rutland@arm.com, devicetree@vger.kernel.org, Arnd Bergmann , linux@armlinux.org.uk, ">" , ">" , Maxime Coquelin , Lee Jones , linux-arm-kernel@lists.infradead.org List-ID: --001a113f16e05d7f5d05402dca11 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable I think wlcore driver searches dma-ranges in its parent that's why sdio node needs it. 2016-10-31 17:41 GMT+01:00 Bruno Herrera : > On Mon, Oct 31, 2016 at 12:14 PM, Rados=C5=82aw Pietrzyk > wrote: > > This is weird because dma ddresses are recalculated using parent's > > dma-ranges property and soc already has it so there should be absolutel= y > no > > problem. > > These are my DTS and DTSI file. > > > > 2016-10-31 11:27 GMT+01:00 Bruno Herrera : > >> > >> On Fri, Oct 28, 2016 at 5:09 AM, Rados=C5=82aw Pietrzyk > >> wrote: > >> > Have you defined your sdio node within soc node ? > >> > >> It is in the SOC node of the DSTI file. > >> > >> > > >> > 2016-10-27 14:57 GMT+02:00 Bruno Herrera : > >> >> > >> >> Hi Alex, > >> >> > >> >> On Thu, Oct 27, 2016 at 10:21 AM, Alexandre Torgue > >> >> wrote: > >> >> > Hi Bruno, > >> >> > > >> >> > > >> >> > On 10/27/2016 12:43 PM, Bruno Herrera wrote: > >> >> >> > >> >> >> Hi Alex, > >> >> >> > >> >> >> On Wed, Oct 26, 2016 at 7:09 AM, Alexandre Torgue > >> >> >> wrote: > >> >> >>> > >> >> >>> Hi Bruno, > >> >> >>> > >> >> >>> On 10/25/2016 11:06 PM, Bruno Herrera wrote: > >> >> >>>> > >> >> >>>> > >> >> >>>> Hi Alexandre, > >> >> >>>> > >> >> >>>>> > >> >> >>>>> stm32f469-disco and stm32f429-eval boards use SDRAM start > address > >> >> >>>>> remapping > >> >> >>>>> (to @0) to boost performances. A DMA translation through > >> >> >>>>> "dma-ranges" > >> >> >>>>> property was needed for other masters than the M4 CPU. > >> >> >>>>> stm32f429-disco doesn't use remapping so doesn't need this DM= A > >> >> >>>>> translation. > >> >> >>>>> This patches moves this DMA translation definition from > stm32f429 > >> >> >>>>> soc > >> >> >>>>> file > >> >> >>>>> to board files. > >> >> >>>>> > >> >> >>>>> Signed-off-by: Alexandre TORGUE > >> >> >>>>> > >> >> >>>>> diff --git a/arch/arm/boot/dts/stm32429i-eval.dts > >> >> >>>>> b/arch/arm/boot/dts/stm32429i-eval.dts > >> >> >>>>> index 13c7cd2..a763c15 100644 > >> >> >>>>> --- a/arch/arm/boot/dts/stm32429i-eval.dts > >> >> >>>>> +++ b/arch/arm/boot/dts/stm32429i-eval.dts > >> >> >>>>> @@ -82,6 +82,10 @@ > >> >> >>>>> }; > >> >> >>>>> }; > >> >> >>>>> > >> >> >>>>> + soc { > >> >> >>>>> + dma-ranges =3D <0xc0000000 0x0 0x10000000>; > >> >> >>>>> + }; > >> >> >>>>> + > >> >> >>>>> usbotg_hs_phy: usbphy { > >> >> >>>>> #phy-cells =3D <0>; > >> >> >>>>> compatible =3D "usb-nop-xceiv"; > >> >> >>>> > >> >> >>>> > >> >> >>>> > >> >> >>>> Shouldn't also the peripheral dma-ranges property move to boar= d > >> >> >>>> specific > >> >> >>>> too? > >> >> >>>> I had this patch for while but I didn't had the time to submi= t: > >> >> >>> > >> >> >>> > >> >> >>> > >> >> >>> Well spot I forgot it. Actually, discussing with Arnd ysterday = on > >> >> >>> IIRC, > >> >> >>> empty dma-ranges is not needed. Can you test on your side by > >> >> >>> removing > >> >> >>> dma-ranges in usb node please ? > >> >> >> > >> >> >> Unfortunately will take a time for me to set up this environment > on > >> >> >> the STM32F4-EVAL board. > >> >> >> And on the discovery boards we dont have this scenario. That was > the > >> >> >> main reason I did not submit the patch right away. > >> >> >> My conclusion and I might be wrong but is based on the my tests > with > >> >> >> SDIO device at STM32F469I-DISCO board. > >> >> >> > >> >> >> I started this issue as discussion at ST Forum but Maxime gave m= e > >> >> >> the > >> >> >> hint. > >> >> >> > >> >> >> > >> >> >> > >> >> >> > >> >> >> https://my.st.com/public/STe2ecommunities/mcu/Lists/ > cortex_mx_stm32/Flat.aspx?RootFolder=3Dhttps%3a%2f%2fmy%2est%2ecom%2fpubl= ic% > 2fSTe2ecommunities%2fmcu%2fLists%2fcortex_mx_stm32% > 2fDMA2%20and%20SYSCFG_MEMRMP%20relationship&FolderCTID=3D > 0x01200200770978C69A1141439FE559EB459D7580009C4E14902C3CDE46 > A77F0FFD06506F5B¤tviews=3D44 > >> >> >> > >> >> >>> I will push a v2 by removing empty dma-ranges if tests are ok i= n > >> >> >>> your > >> >> >>> side. > >> >> >> > >> >> >> > >> >> >> From my understating/conclusion is: when empty > property(dma-ranges) > >> >> >> is > >> >> >> the device node, the mapping will be taken in consideration when > >> >> >> using > >> >> >> DMA otherwise the mapping is ignored. > >> >> >> And in the SDIO case it is needed for DEV->MEM(SDRAM) and > >> >> >> MEM(SDRAM)->DEV. If it is not the case for the devices in questi= on > >> >> >> so > >> >> >> I suppose it can work without the property. > >> >> > > >> >> > > >> >> > For sure translation has to be done but I'm not sure that an empt= y > >> >> > "dma-ranges" is needed in device node to activate it. For Etherne= t > >> >> > empty > >> >> > "dma-ranges" is not needed. I will try with usb. > >> >> > >> >> In the case of SDIO it is needed. As example this is my working SDI= O > >> >> node: > >> >> > >> >> sdio: sdio@40012c00 { > >> >> compatible =3D "arm,pl18x", "arm,primecell"; > >> >> arm,primecell-periphid =3D <0x00480181>; > >> >> reg =3D <0x40012c00 0x400>; > >> >> dmas =3D <&dma2 6 4 0x10400 0x3>, /* Logical - DevToMem */ > >> >> <&dma2 3 4 0x10400 0x3>; /* Logical - MemToDev */ > >> >> dma-names =3D "rx", "tx"; > >> >> clocks =3D <&rcc 0 171>; > >> >> clock-names =3D "apb_pclk"; > >> >> interrupts =3D <49>; > >> >> status =3D "disabled"; > >> >> }; > >> >> > >> >> &sdio { > >> >> status =3D "okay"; > >> >> vmmc-supply =3D <&wlan_en>; > >> >> bus-width =3D <4>; > >> >> max-frequency =3D <24000000>; > >> >> pinctrl-names =3D "default"; > >> >> pinctrl-0 =3D <&sdio_pins>; > >> >> ti,non-removable; > >> >> ti,needs-special-hs-handling; > >> >> dma-ranges; > >> >> cap-power-off-card; > >> >> keep-power-in-suspend; > >> >> > >> >> #address-cells =3D <1>; > >> >> #size-cells =3D <0>; > >> >> wlcore: wlcore@0 { > >> >> compatible =3D "ti,wl1835"; > >> >> reg =3D <2>; > >> >> interrupt-parent =3D <&gpioa>; > >> >> interrupts =3D <8 IRQ_TYPE_EDGE_RISING>; > >> >> }; > >> >> }; > >> >> > >> >> > > >> >> > alex > >> >> > > >> >> > > >> >> >> > >> >> >>> > >> >> >>> Thanks in advance > >> >> >>> Alex > >> >> >>> > >> >> >>> > >> >> >>>> > >> >> >>>> Author: Bruno Herrera > >> >> >>>> Date: Sun Oct 16 14:50:00 2016 -0200 > >> >> >>>> > >> >> >>>> ARM: DT: STM32: Use dma-ranges property per board not at > dtsi > >> >> >>>> file > >> >> >>>> > >> >> >>>> diff --git a/arch/arm/boot/dts/stm32429i-eval.dts > >> >> >>>> b/arch/arm/boot/dts/stm32429i-eval.dts > >> >> >>>> index 6bfc595..2a22a82 100644 > >> >> >>>> --- a/arch/arm/boot/dts/stm32429i-eval.dts > >> >> >>>> +++ b/arch/arm/boot/dts/stm32429i-eval.dts > >> >> >>>> @@ -52,6 +52,10 @@ > >> >> >>>> model =3D "STMicroelectronics STM32429i-EVAL board"; > >> >> >>>> compatible =3D "st,stm32429i-eval", "st,stm32f429"; > >> >> >>>> > >> >> >>>> + soc { > >> >> >>>> + dma-ranges =3D <0xC0000000 0x0 0x10000000>; > >> >> >>>> + }; > >> >> >>>> + > >> >> >>>> chosen { > >> >> >>>> bootargs =3D "root=3D/dev/ram rdinit=3D/linuxr= c"; > >> >> >>>> stdout-path =3D "serial0:115200n8"; > >> >> >>>> @@ -96,6 +100,7 @@ > >> >> >>>> > >> >> >>>> ðernet0 { > >> >> >>>> status =3D "okay"; > >> >> >>>> + dma-ranges; > >> >> >>>> pinctrl-0 =3D <ðernet0_mii>; > >> >> >>>> pinctrl-names =3D "default"; > >> >> >>>> phy-mode =3D "mii-id"; > >> >> >>>> @@ -116,6 +121,7 @@ > >> >> >>>> }; > >> >> >>>> > >> >> >>>> &usbotg_hs { > >> >> >>>> + dma-ranges; > >> >> >>>> dr_mode =3D "host"; > >> >> >>>> phys =3D <&usbotg_hs_phy>; > >> >> >>>> phy-names =3D "usb2-phy"; > >> >> >>>> diff --git a/arch/arm/boot/dts/stm32f429.dtsi > >> >> >>>> b/arch/arm/boot/dts/stm32f429.dtsi > >> >> >>>> index 7d624a2..697a133 100644 > >> >> >>>> --- a/arch/arm/boot/dts/stm32f429.dtsi > >> >> >>>> +++ b/arch/arm/boot/dts/stm32f429.dtsi > >> >> >>>> @@ -59,7 +59,6 @@ > >> >> >>>> }; > >> >> >>>> > >> >> >>>> soc { > >> >> >>>> - dma-ranges =3D <0xc0000000 0x0 0x10000000>; > >> >> >>>> > >> >> >>>> timer2: timer@40000000 { > >> >> >>>> compatible =3D "st,stm32-timer"; > >> >> >>>> @@ -472,13 +471,11 @@ > >> >> >>>> st,syscon =3D <&syscfg 0x4>; > >> >> >>>> snps,pbl =3D <8>; > >> >> >>>> snps,mixed-burst; > >> >> >>>> - dma-ranges; > >> >> >>>> status =3D "disabled"; > >> >> >>>> }; > >> >> >>>> > >> >> >>>> usbotg_hs: usb@40040000 { > >> >> >>>> compatible =3D "snps,dwc2"; > >> >> >>>> - dma-ranges; > >> >> >>>> reg =3D <0x40040000 0x40000>; > >> >> >>>> interrupts =3D <77>; > >> >> >>>> clocks =3D <&rcc 0 29>; > >> >> >>>> > >> >> >>>> > >> >> >>>>> diff --git a/arch/arm/boot/dts/stm32f429.dtsi > >> >> >>>>> b/arch/arm/boot/dts/stm32f429.dtsi > >> >> >>>>> index 0596d60..3a1cfdd 100644 > >> >> >>>>> --- a/arch/arm/boot/dts/stm32f429.dtsi > >> >> >>>>> +++ b/arch/arm/boot/dts/stm32f429.dtsi > >> >> >>>>> @@ -59,8 +59,6 @@ > >> >> >>>>> }; > >> >> >>>>> > >> >> >>>>> soc { > >> >> >>>>> - dma-ranges =3D <0xc0000000 0x0 0x10000000>; > >> >> >>>>> - > >> >> >>>>> timer2: timer@40000000 { > >> >> >>>>> compatible =3D "st,stm32-timer"; > >> >> >>>>> reg =3D <0x40000000 0x400>; > >> >> >>>>> diff --git a/arch/arm/boot/dts/stm32f469-disco.dts > >> >> >>>>> b/arch/arm/boot/dts/stm32f469-disco.dts > >> >> >>>>> index 9e73656..c2213c0 100644 > >> >> >>>>> --- a/arch/arm/boot/dts/stm32f469-disco.dts > >> >> >>>>> +++ b/arch/arm/boot/dts/stm32f469-disco.dts > >> >> >>>>> @@ -64,6 +64,10 @@ > >> >> >>>>> aliases { > >> >> >>>>> serial0 =3D &usart3; > >> >> >>>>> }; > >> >> >>>>> + > >> >> >>>>> + soc { > >> >> >>>>> + dma-ranges =3D <0xc0000000 0x0 0x10000000>; > >> >> >>>>> + }; > >> >> >>>>> }; > >> >> >>>>> > >> >> >>>>> &clk_hse { > >> >> >>>>> -- > >> >> >>>> > >> >> >>>> > >> >> >>>> > >> >> >>>> > >> >> >>>> Br., > >> >> >>>> Bruno > >> >> >>>> > >> >> >>> > >> >> > > >> >> > >> >> _______________________________________________ > >> >> linux-arm-kernel mailing list > >> >> linux-arm-kernel@lists.infradead.org > >> >> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel > >> > > >> > > > > > > --001a113f16e05d7f5d05402dca11 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
I think wlcore driver searches dma-ranges in its parent th= at's why sdio node needs it.

2016-10-31 17:41 GMT+01:00 Bruno Herrera <bruherre= ra@gmail.com>:
On Mon, Oct 31, 2016 at 12:14 PM, Rados=C5=82aw Pietrzyk
<radoslaw.pietrzyk@gmail.= com> wrote:
> This is weird because dma ddresses ar= e recalculated using parent's
> dma-ranges property and soc already has it so there should be absolute= ly no
> problem.

These are my DTS and DTSI file.
>
> 2016-10-31 11:27 GMT+01= :00 Bruno Herrera <bruherrera@gm= ail.com>:
>>
>> On Fri, Oct 28, 2016 at 5:09 AM, Rados=C5=82aw Pietrzyk
>> <radoslaw.pietrz= yk@gmail.com> wrote:
>> > Have you defined your sdio node within soc node ?
>>
>> It is in the SOC node of the DSTI file.
>>
>> >
>> > 2016-10-27 14:57 GMT+02:00 Bruno Herrera <bruherrera@gmail.com>:
>> >>
>> >> Hi Alex,
>> >>
>> >> On Thu, Oct 27, 2016 at 10:21 AM, Alexandre Torgue
>> >> <alexandre.= torgue@st.com> wrote:
>> >> > Hi Bruno,
>> >> >
>> >> >
>> >> > On 10/27/2016 12:43 PM, Bruno Herrera wrote:
>> >> >>
>> >> >> Hi Alex,
>> >> >>
>> >> >> On Wed, Oct 26, 2016 at 7:09 AM, Alexandre Torgu= e
>> >> >> <a= lexandre.torgue@st.com> wrote:
>> >> >>>
>> >> >>> Hi Bruno,
>> >> >>>
>> >> >>> On 10/25/2016 11:06 PM, Bruno Herrera wrote:=
>> >> >>>>
>> >> >>>>
>> >> >>>> Hi Alexandre,
>> >> >>>>
>> >> >>>>>
>> >> >>>>> stm32f469-disco and stm32f429-eval b= oards use SDRAM start address
>> >> >>>>> remapping
>> >> >>>>> (to @0) to boost performances. A DMA= translation through
>> >> >>>>> "dma-ranges"
>> >> >>>>> property was needed for other master= s than the M4 CPU.
>> >> >>>>> stm32f429-disco doesn't use rema= pping so doesn't need this DMA
>> >> >>>>> translation.
>> >> >>>>> This patches moves this DMA translat= ion definition from stm32f429
>> >> >>>>> soc
>> >> >>>>> file
>> >> >>>>> to board files.
>> >> >>>>>
>> >> >>>>> Signed-off-by: Alexandre TORGUE <= alexandre.torgue@st.com><= br> >> >> >>>>>
>> >> >>>>> diff --git a/arch/arm/boot/dts/stm32= 429i-eval.dts
>> >> >>>>> b/arch/arm/boot/dts/stm32429i-e= val.dts
>> >> >>>>> index 13c7cd2..a763c15 100644
>> >> >>>>> --- a/arch/arm/boot/dts/stm32429i-eval.dts
>> >> >>>>> +++ b/arch/arm/boot/dts/stm32429i-eval.dts
>> >> >>>>> @@ -82,6 +82,10 @@
>> >> >>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0};
>> >> >>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0};<= br> >> >> >>>>>
>> >> >>>>> +=C2=A0 =C2=A0 =C2=A0 =C2=A0soc { >> >> >>>>> +=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0dma-ranges =3D <0xc0000000 0x0 0x10000000>;
>> >> >>>>> +=C2=A0 =C2=A0 =C2=A0 =C2=A0};
>> >> >>>>> +
>> >> >>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0usb= otg_hs_phy: usbphy {
>> >> >>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0#phy-cells =3D <0>;
>> >> >>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0compatible =3D "usb-nop-xceiv";
>> >> >>>>
>> >> >>>>
>> >> >>>>
>> >> >>>> Shouldn't also the peripheral dma-ra= nges property move to board
>> >> >>>> specific
>> >> >>>> too?
>> >> >>>> I=C2=A0 had this patch for while but I d= idn't had the time to submit:
>> >> >>>
>> >> >>>
>> >> >>>
>> >> >>> Well spot I forgot it. Actually, discussing = with Arnd ysterday on
>> >> >>> IIRC,
>> >> >>> empty dma-ranges is not needed. Can you test= on your side by
>> >> >>> removing
>> >> >>> dma-ranges in usb node please ?
>> >> >>
>> >> >> Unfortunately will take a time for me to set up = this environment on
>> >> >> the STM32F4-EVAL board.
>> >> >> And on the discovery boards we dont have this sc= enario. That was the
>> >> >> main reason I did not submit the patch right awa= y.
>> >> >> My conclusion and I might be wrong but is based = on the my tests with
>> >> >> SDIO device at STM32F469I-DISCO board.
>> >> >>
>> >> >> I started this issue as discussion at ST Forum b= ut Maxime gave me
>> >> >> the
>> >> >> hint.
>> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >> >> https://my.st.com/public/STe2e= communities/mcu/Lists/cortex_mx_stm32/Flat.aspx?RootFolder=3Dhttp= s%3a%2f%2fmy%2est%2ecom%2fpublic%2fSTe2ecommunities%2fmcu%2f= Lists%2fcortex_mx_stm32%2fDMA2%20and%20SYSCFG_MEMRMP%20relationsh= ip&FolderCTID=3D0x01200200770978C69A1141439FE559EB459D7580009= C4E14902C3CDE46A77F0FFD06506F5B&currentviews=3D44
>> >> >>
>> >> >>> I will push a v2 by removing empty dma-range= s if tests are ok in
>> >> >>> your
>> >> >>> side.
>> >> >>
>> >> >>
>> >> >> From my understating/conclusion is: when empty p= roperty(dma-ranges)
>> >> >> is
>> >> >> the device node, the mapping will be taken in co= nsideration when
>> >> >> using
>> >> >> DMA otherwise the mapping is ignored.
>> >> >> And in the SDIO case it is needed for DEV->ME= M(SDRAM) and
>> >> >> MEM(SDRAM)->DEV. If it is not the case for th= e devices in question
>> >> >> so
>> >> >> I suppose it can work without the property.
>> >> >
>> >> >
>> >> > For sure translation has to be done but I'm not = sure that an empty
>> >> > "dma-ranges" is needed in device node to a= ctivate it. For Ethernet
>> >> > empty
>> >> > "dma-ranges" is not needed. I will try wit= h usb.
>> >>
>> >> In the case of SDIO it is needed. As example this is my w= orking SDIO
>> >> node:
>> >>
>> >> sdio: sdio@40012c00 {
>> >> compatible =3D "arm,pl18x", "arm,primecell= ";
>> >> arm,primecell-periphid =3D <0x00480181>;
>> >> reg =3D <0x40012c00 0x400>;
>> >> dmas =3D=C2=A0 <&dma2 6 4 0x10400 0x3>, /* Logi= cal - DevToMem */
>> >> <&dma2 3 4 0x10400 0x3>; /* Logical - MemToDev = */
>> >> dma-names =3D "rx", "tx";
>> >> clocks =3D <&rcc 0 171>;
>> >> clock-names =3D "apb_pclk";
>> >> interrupts =3D <49>;
>> >> status =3D "disabled";
>> >> };
>> >>
>> >> &sdio {
>> >> status =3D "okay";
>> >> vmmc-supply =3D <&wlan_en>;
>> >> bus-width =3D <4>;
>> >> max-frequency =3D <24000000>;
>> >> pinctrl-names =3D "default";
>> >> pinctrl-0 =3D <&sdio_pins>;
>> >> ti,non-removable;
>> >> ti,needs-special-hs-handling;
>> >> dma-ranges;
>> >> cap-power-off-card;
>> >> keep-power-in-suspend;
>> >>
>> >> #address-cells =3D <1>;
>> >> #size-cells =3D <0>;
>> >> wlcore: wlcore@0 {
>> >> compatible =3D "ti,wl1835";
>> >> reg =3D <2>;
>> >> interrupt-parent =3D <&gpioa>;
>> >> interrupts =3D <8 IRQ_TYPE_EDGE_RISING>;
>> >> };
>> >> };
>> >>
>> >> >
>> >> > alex
>> >> >
>> >> >
>> >> >>
>> >> >>>
>> >> >>> Thanks in advance
>> >> >>> Alex
>> >> >>>
>> >> >>>
>> >> >>>>
>> >> >>>> Author: Bruno Herrera <bruherrera@gmail.com>
>> >> >>>> Date:=C2=A0 =C2=A0Sun Oct 16 14:50:00 20= 16 -0200
>> >> >>>>
>> >> >>>>=C2=A0 =C2=A0 =C2=A0ARM: DT: STM32: Use d= ma-ranges property per board not at dtsi
>> >> >>>> file
>> >> >>>>
>> >> >>>> diff --git a/arch/arm/boot/dts/stm32429i= -eval.dts
>> >> >>>> b/arch/arm/boot/dts/stm32429i-eval.= dts
>> >> >>>> index 6bfc595..2a22a82 100644
>> >> >>>> --- a/arch/arm/boot/dts/stm32429i-e= val.dts
>> >> >>>> +++ b/arch/arm/boot/dts/stm32429i-e= val.dts
>> >> >>>> @@ -52,6 +52,10 @@
>> >> >>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0model = =3D "STMicroelectronics STM32429i-EVAL board";
>> >> >>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0compati= ble =3D "st,stm32429i-eval", "st,stm32f429";
>> >> >>>>
>> >> >>>> +=C2=A0 =C2=A0 =C2=A0 =C2=A0soc {
>> >> >>>> +=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0dma-ranges =3D <0xC0000000 0x0 0x10000000>;
>> >> >>>> +=C2=A0 =C2=A0 =C2=A0 =C2=A0};
>> >> >>>> +
>> >> >>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0chosen = {
>> >> >>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0= =C2=A0 =C2=A0 =C2=A0bootargs =3D "root=3D/dev/ram rdinit=3D/linuxrc&q= uot;;
>> >> >>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0= =C2=A0 =C2=A0 =C2=A0stdout-path =3D "serial0:115200n8";
>> >> >>>> @@ -96,6 +100,7 @@
>> >> >>>>
>> >> >>>>=C2=A0 &ethernet0 {
>> >> >>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0status = =3D "okay";
>> >> >>>> +=C2=A0 =C2=A0 =C2=A0 =C2=A0dma-ranges;<= br> >> >> >>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0pinctrl= -0=C2=A0 =C2=A0 =C2=A0 =C2=A0=3D <&ethernet0_mii>;
>> >> >>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0pinctrl= -names=C2=A0 =C2=A0=3D "default";
>> >> >>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0phy-mod= e=C2=A0 =C2=A0 =C2=A0 =C2=A0 =3D "mii-id";
>> >> >>>> @@ -116,6 +121,7 @@
>> >> >>>>=C2=A0 };
>> >> >>>>
>> >> >>>>=C2=A0 &usbotg_hs {
>> >> >>>> +=C2=A0 =C2=A0 =C2=A0 =C2=A0dma-ranges;<= br> >> >> >>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0dr_mode= =3D "host";
>> >> >>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0phys = =3D <&usbotg_hs_phy>;
>> >> >>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0phy-nam= es =3D "usb2-phy";
>> >> >>>> diff --git a/arch/arm/boot/dts/stm32f429= .dtsi
>> >> >>>> b/arch/arm/boot/dts/stm32f429.dtsi<= br> >> >> >>>> index 7d624a2..697a133 100644
>> >> >>>> --- a/arch/arm/boot/dts/stm32f429.d= tsi
>> >> >>>> +++ b/arch/arm/boot/dts/stm32f429.d= tsi
>> >> >>>> @@ -59,7 +59,6 @@
>> >> >>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0};
>> >> >>>>
>> >> >>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0soc { >> >> >>>> -=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0dma-ranges =3D <0xc0000000 0x0 0x10000000>;
>> >> >>>>
>> >> >>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0= =C2=A0 =C2=A0 =C2=A0timer2: timer@40000000 {
>> >> >>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0= =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0compatible =3D "st,st= m32-timer";
>> >> >>>> @@ -472,13 +471,11 @@
>> >> >>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0= =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0st,syscon =3D <&sys= cfg 0x4>;
>> >> >>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0= =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0snps,pbl =3D <8>; >> >> >>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0= =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0snps,mixed-burst;
>> >> >>>> -=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0dma-ranges;
>> >> >>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0= =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0status =3D "disabled&= quot;;
>> >> >>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0= =C2=A0 =C2=A0 =C2=A0};
>> >> >>>>
>> >> >>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0= =C2=A0 =C2=A0 =C2=A0usbotg_hs: usb@40040000 {
>> >> >>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0= =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0compatible =3D "snps,= dwc2";
>> >> >>>> -=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0dma-ranges;
>> >> >>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0= =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0reg =3D <0x40040000 0x4= 0000>;
>> >> >>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0= =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0interrupts =3D <77>;=
>> >> >>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0= =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0clocks =3D <&rcc 0 = 29>;
>> >> >>>>
>> >> >>>>
>> >> >>>>> diff --git a/arch/arm/boot/dts/stm32= f429.dtsi
>> >> >>>>> b/arch/arm/boot/dts/stm32f429.d= tsi
>> >> >>>>> index 0596d60..3a1cfdd 100644
>> >> >>>>> --- a/arch/arm/boot/dts/stm32f429.dtsi
>> >> >>>>> +++ b/arch/arm/boot/dts/stm32f429.dtsi
>> >> >>>>> @@ -59,8 +59,6 @@
>> >> >>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0};<= br> >> >> >>>>>
>> >> >>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0soc= {
>> >> >>>>> -=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0dma-ranges =3D <0xc0000000 0x0 0x10000000>;
>> >> >>>>> -
>> >> >>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0timer2: timer@40000000 {
>> >> >>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0compatible =3D "= ;st,stm32-timer";
>> >> >>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0reg =3D <0x400000= 00 0x400>;
>> >> >>>>> diff --git a/arch/arm/boot/dts/stm32= f469-disco.dts
>> >> >>>>> b/arch/arm/boot/dts/stm32f469-d= isco.dts
>> >> >>>>> index 9e73656..c2213c0 100644
>> >> >>>>> --- a/arch/arm/boot/dts/stm32f469-disco.dts
>> >> >>>>> +++ b/arch/arm/boot/dts/stm32f469-disco.dts
>> >> >>>>> @@ -64,6 +64,10 @@
>> >> >>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0ali= ases {
>> >> >>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0serial0 =3D &usart3;
>> >> >>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0};<= br> >> >> >>>>> +
>> >> >>>>> +=C2=A0 =C2=A0 =C2=A0 =C2=A0soc { >> >> >>>>> +=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0dma-ranges =3D <0xc0000000 0x0 0x10000000>;
>> >> >>>>> +=C2=A0 =C2=A0 =C2=A0 =C2=A0};
>> >> >>>>>=C2=A0 };
>> >> >>>>>
>> >> >>>>>=C2=A0 &clk_hse {
>> >> >>>>> --
>> >> >>>>
>> >> >>>>
>> >> >>>>
>> >> >>>>
>> >> >>>> Br.,
>> >> >>>> Bruno
>> >> >>>>
>> >> >>>
>> >> >
>> >>
>> >> _______________________________________________
>> >> linux-arm-kernel mailing list
>> >> l= inux-arm-kernel@lists.infradead.org
>> >> http://lists.infradead= .org/mailman/listinfo/linux-arm-kernel
>> >
>> >
>
>

--001a113f16e05d7f5d05402dca11--