From: Michael Walle <michael@walle.cc>
To: Peng Ma <peng.ma@nxp.com>
Cc: dmaengine@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Vinod Koul <vkoul@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Shawn Guo <shawnguo@kernel.org>, Leo Li <leoyang.li@nxp.com>
Subject: Re: [EXT] [PATCH 2/2] arm64: dts: ls1028a: add "fsl,vf610-edma" compatible
Date: Sat, 07 Mar 2020 10:25:55 +0100 [thread overview]
Message-ID: <e0be23f7d1307621151594dd66d2b8fd@walle.cc> (raw)
In-Reply-To: <VI1PR04MB44312A940BC5BFC7F13A5706EDE00@VI1PR04MB4431.eurprd04.prod.outlook.com>
Hi Peng,
Am 2020-03-07 03:09, schrieb Peng Ma:
>> -----Original Message-----
>> From: Michael Walle <michael@walle.cc>
>> Sent: 2020年3月7日 4:54
>> To: dmaengine@vger.kernel.org; devicetree@vger.kernel.org;
>> linux-kernel@vger.kernel.org; linux-arm-kernel@lists.infradead.org
>> Cc: Vinod Koul <vkoul@kernel.org>; Rob Herring <robh+dt@kernel.org>;
>> Mark
>> Rutland <mark.rutland@arm.com>; Shawn Guo <shawnguo@kernel.org>; Leo
>> Li
>> <leoyang.li@nxp.com>; Peng Ma <peng.ma@nxp.com>; Michael Walle
>> <michael@walle.cc>
>> Subject: [EXT] [PATCH 2/2] arm64: dts: ls1028a: add "fsl,vf610-edma"
>> compatible
>>
>> Caution: EXT Email
>>
>> The bootloader does the IOMMU fixup and dynamically adds the "iommus"
>> property to devices according to its compatible string. In case of the
>> eDMA
>> controller this property is missing. Add it. After that the IOMMU will
>> work with
>> the eDMA core.
>>
>> Signed-off-by: Michael Walle <michael@walle.cc>
>> ---
>> arch/arm64/boot/dts/freescale/fsl-ls1028a.dtsi | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/arch/arm64/boot/dts/freescale/fsl-ls1028a.dtsi
>> b/arch/arm64/boot/dts/freescale/fsl-ls1028a.dtsi
>> index b152fa90cf5c..aa467bff2209 100644
>> --- a/arch/arm64/boot/dts/freescale/fsl-ls1028a.dtsi
>> +++ b/arch/arm64/boot/dts/freescale/fsl-ls1028a.dtsi
>> @@ -447,7 +447,7 @@
>>
>> edma0: dma-controller@22c0000 {
>> #dma-cells = <2>;
>> - compatible = "fsl,ls1028a-edma";
>> + compatible = "fsl,ls1028a-edma",
>> + "fsl,vf610-edma";
> Hi Michael,
>
> You should change it on bootloader instead of kernel, Some Reg of
> LS1028a is different
> from others, So we used compatible "fsl,ls1028a-edm" to distinguish "
> fsl,vf610-edma".
Yes this might be the right thing to do. So since it is NXPs bootloader
feel free to fix that ;) Looking at the u-boot code right now, I don't
even know it that is the right fix at all. The fixup code in u-boot is
SoC independent (its in fsl_icid.h and is enabled with CONFIG_LSCH3, ie
your chassis version). For example, the sdhc fixup will scan the nodes
for "compatible = fsl,esdhc", which is also the secondary compatible
for the "ls1028a-esdhc" compatible.
And here is another reason to have it this way: we need backwards
compatibility, the are already boards out there whose bootloader will
fix-up the "old" node. Thus I don't see any other possibilty.
-michael
>
> Thanks,
> Peng
>> reg = <0x0 0x22c0000 0x0 0x10000>,
>> <0x0 0x22d0000 0x0 0x10000>,
>> <0x0 0x22e0000 0x0 0x10000>;
>> --
>> 2.20.1
next prev parent reply other threads:[~2020-03-07 9:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-06 20:54 [PATCH 1/2] dt-bindings: dma: fsl-edma: fix ls1028a-edma compatible Michael Walle
2020-03-06 20:54 ` [PATCH 2/2] arm64: dts: ls1028a: add "fsl,vf610-edma" compatible Michael Walle
2020-03-07 2:09 ` [EXT] " Peng Ma
2020-03-07 9:25 ` Michael Walle [this message]
2020-03-07 10:32 ` Peng Ma
2020-03-07 13:10 ` Michael Walle
2020-03-23 14:36 ` Michael Walle
2020-03-23 19:43 ` [PATCH 1/2] dt-bindings: dma: fsl-edma: fix ls1028a-edma compatible Rob Herring
2020-04-13 14:18 ` Shawn Guo
2020-05-11 9:08 ` Michael Walle
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=e0be23f7d1307621151594dd66d2b8fd@walle.cc \
--to=michael@walle.cc \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=leoyang.li@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=peng.ma@nxp.com \
--cc=robh+dt@kernel.org \
--cc=shawnguo@kernel.org \
--cc=vkoul@kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®