From: Roger Quadros <rogerq@kernel.org>
To: Andrew Davis <afd@ti.com>, Nishanth Menon <nm@ti.com>
Cc: vigneshr@ti.com, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org,
srk@ti.com, linux-arm-kernel@lists.infradead.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Siddharth Vadapalli <s-vadapalli@ti.com>
Subject: Re: [PATCH 2/2] arm64: dts: ti: am642-evm: Add overlay for NAND expansion card
Date: Thu, 21 Sep 2023 14:37:29 +0300 [thread overview]
Message-ID: <6f2b38f8-1962-46f2-a095-b1eaf99ed407@kernel.org> (raw)
In-Reply-To: <c7ec6ccd-37de-244d-0b3b-cb5d13bae539@ti.com>
On 20/09/2023 20:06, Andrew Davis wrote:
> On 9/20/23 11:44 AM, Nishanth Menon wrote:
>> On 18:18-20230920, Roger Quadros wrote:
>>>
>>>
>>> On 20/09/2023 16:58, Nishanth Menon wrote:
>>>> On 16:34-20230920, Roger Quadros wrote:
>>>>> The NAND expansion card plugs in over the HSE (High Speed Expansion)
>>>>> connector. Add support for it.
>>>>>
>>>>> Signed-off-by: Roger Quadros <rogerq@kernel.org>
>>>>> ---
>>>>> arch/arm64/boot/dts/ti/Makefile | 1 +
>>>>> arch/arm64/boot/dts/ti/k3-am642-evm-nand.dtso | 140 ++++++++++++++++++
>>>>> 2 files changed, 141 insertions(+)
>>>>> create mode 100644 arch/arm64/boot/dts/ti/k3-am642-evm-nand.dtso
>>>>>
>>>>> diff --git a/arch/arm64/boot/dts/ti/Makefile b/arch/arm64/boot/dts/ti/Makefile
>>>>> index 06d6f264f292..ece74085a6be 100644
>>>>> --- a/arch/arm64/boot/dts/ti/Makefile
>>>>> +++ b/arch/arm64/boot/dts/ti/Makefile
>>>>> @@ -29,6 +29,7 @@ dtb-$(CONFIG_ARCH_K3) += k3-am62p5-sk.dtb
>>>>> # Boards with AM64x SoC
>>>>> dtb-$(CONFIG_ARCH_K3) += k3-am642-evm.dtb
>>>>> +dtb-$(CONFIG_ARCH_K3) += k3-am642-evm-nand.dtbo
>>>>> dtb-$(CONFIG_ARCH_K3) += k3-am642-phyboard-electra-rdk.dtb
>>>>> dtb-$(CONFIG_ARCH_K3) += k3-am642-sk.dtb
>>>>> dtb-$(CONFIG_ARCH_K3) += k3-am642-tqma64xxl-mbax4xxl.dtb
>>>>
>>>> Also see https://lore.kernel.org/all/20230911165610.GA1362932-robh@kernel.org/
>>>>
>>>> you may not get the dtbo installed when doing make dtbs_install
>>>>
>>>> [...]
>>>>
>>>
>>> $ v8make dtbs_install INSTALL_DTBS_PATH=/tmp
>>> INSTALL /tmp/ti/k3-am625-beagleplay.dtb
>>> INSTALL /tmp/ti/k3-am625-phyboard-lyra-rdk.dtb
>>> INSTALL /tmp/ti/k3-am625-sk.dtb
>>> INSTALL /tmp/ti/k3-am625-verdin-nonwifi-dahlia.dtb
>>> INSTALL /tmp/ti/k3-am625-verdin-nonwifi-dev.dtb
>>> INSTALL /tmp/ti/k3-am625-verdin-nonwifi-yavia.dtb
>>> INSTALL /tmp/ti/k3-am625-verdin-wifi-dahlia.dtb
>>> INSTALL /tmp/ti/k3-am625-verdin-wifi-dev.dtb
>>> INSTALL /tmp/ti/k3-am625-verdin-wifi-yavia.dtb
>>> INSTALL /tmp/ti/k3-am62-lp-sk.dtb
>>> INSTALL /tmp/ti/k3-am62x-sk-hdmi-audio.dtbo
>>> INSTALL /tmp/ti/k3-am62a7-sk.dtb
>>> INSTALL /tmp/ti/k3-am62p5-sk.dtb
>>> INSTALL /tmp/ti/k3-am642-evm.dtb
>>> INSTALL /tmp/ti/k3-am642-evm-nand.dtbo
>>> ^^^^
>>> INSTALL /tmp/ti/k3-am642-phyboard-electra-rdk.dtb
>>> INSTALL /tmp/ti/k3-am642-sk.dtb
>>>
>>>
>>> What did I miss?
>>
>> I missed it, actually. See Rob's comment:
>> https://lore.kernel.org/all/CAL_Jsq+GR3hP6hFvFn2z5aXvSXnh9butD3aKZ-y_XJgx0_YPTw@mail.gmail.com/
>>
>> Having orphan dtbo is apparently frowned upon
>>
>
> And if you apply these overlays to the base DTB then it gets
> symbols added automatically, no need for your patch [1/2] here.
>
Is this OK?
k3-am642-evm-nand-dtbs := k3-am642-evm.dtb k3-am642-evm-nand.dtbo
dtb-$(CONFIG_ARCH_K3) += k3-am642-evm-nand.dtb
So patch 1 is not required in this case but we have an
extra dtb file which is not really required.
I have 2 more issues to point out
1)
With existing examples e.g. J7200 EVM
wouldn't k3-j7200-evm.dtb include the k3-j7200-evm-quad-port-eth-exp.dtbo?
Is this what we really want?
likewise for k3-j721e-evm.dtb and k3-am654-gp-evm.dtb
2)
Another issue (unrelated to this change) is the below warning:
arch/arm64/boot/dts/ti/k3-am642-evm-nand.dtso:65.8-140.3: Warning (avoid_default_addr_size): /fragment@3/__overlay__: Relying on default #address-cells value
arch/arm64/boot/dts/ti/k3-am642-evm-nand.dtso:65.8-140.3: Warning (avoid_default_addr_size): /fragment@3/__overlay__: Relying on default #size-cells value
This is because we use the 'ranges' property in the gpmc0 node
and the compiler doesn't know the #address/size-cells of the
parent node.
Is there a trick to specify it in the dtso file?
--
cheers,
-roger
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Roger Quadros <rogerq@kernel.org>
To: Andrew Davis <afd@ti.com>, Nishanth Menon <nm@ti.com>
Cc: vigneshr@ti.com, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org,
srk@ti.com, linux-arm-kernel@lists.infradead.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Siddharth Vadapalli <s-vadapalli@ti.com>
Subject: Re: [PATCH 2/2] arm64: dts: ti: am642-evm: Add overlay for NAND expansion card
Date: Thu, 21 Sep 2023 14:37:29 +0300 [thread overview]
Message-ID: <6f2b38f8-1962-46f2-a095-b1eaf99ed407@kernel.org> (raw)
In-Reply-To: <c7ec6ccd-37de-244d-0b3b-cb5d13bae539@ti.com>
On 20/09/2023 20:06, Andrew Davis wrote:
> On 9/20/23 11:44 AM, Nishanth Menon wrote:
>> On 18:18-20230920, Roger Quadros wrote:
>>>
>>>
>>> On 20/09/2023 16:58, Nishanth Menon wrote:
>>>> On 16:34-20230920, Roger Quadros wrote:
>>>>> The NAND expansion card plugs in over the HSE (High Speed Expansion)
>>>>> connector. Add support for it.
>>>>>
>>>>> Signed-off-by: Roger Quadros <rogerq@kernel.org>
>>>>> ---
>>>>> arch/arm64/boot/dts/ti/Makefile | 1 +
>>>>> arch/arm64/boot/dts/ti/k3-am642-evm-nand.dtso | 140 ++++++++++++++++++
>>>>> 2 files changed, 141 insertions(+)
>>>>> create mode 100644 arch/arm64/boot/dts/ti/k3-am642-evm-nand.dtso
>>>>>
>>>>> diff --git a/arch/arm64/boot/dts/ti/Makefile b/arch/arm64/boot/dts/ti/Makefile
>>>>> index 06d6f264f292..ece74085a6be 100644
>>>>> --- a/arch/arm64/boot/dts/ti/Makefile
>>>>> +++ b/arch/arm64/boot/dts/ti/Makefile
>>>>> @@ -29,6 +29,7 @@ dtb-$(CONFIG_ARCH_K3) += k3-am62p5-sk.dtb
>>>>> # Boards with AM64x SoC
>>>>> dtb-$(CONFIG_ARCH_K3) += k3-am642-evm.dtb
>>>>> +dtb-$(CONFIG_ARCH_K3) += k3-am642-evm-nand.dtbo
>>>>> dtb-$(CONFIG_ARCH_K3) += k3-am642-phyboard-electra-rdk.dtb
>>>>> dtb-$(CONFIG_ARCH_K3) += k3-am642-sk.dtb
>>>>> dtb-$(CONFIG_ARCH_K3) += k3-am642-tqma64xxl-mbax4xxl.dtb
>>>>
>>>> Also see https://lore.kernel.org/all/20230911165610.GA1362932-robh@kernel.org/
>>>>
>>>> you may not get the dtbo installed when doing make dtbs_install
>>>>
>>>> [...]
>>>>
>>>
>>> $ v8make dtbs_install INSTALL_DTBS_PATH=/tmp
>>> INSTALL /tmp/ti/k3-am625-beagleplay.dtb
>>> INSTALL /tmp/ti/k3-am625-phyboard-lyra-rdk.dtb
>>> INSTALL /tmp/ti/k3-am625-sk.dtb
>>> INSTALL /tmp/ti/k3-am625-verdin-nonwifi-dahlia.dtb
>>> INSTALL /tmp/ti/k3-am625-verdin-nonwifi-dev.dtb
>>> INSTALL /tmp/ti/k3-am625-verdin-nonwifi-yavia.dtb
>>> INSTALL /tmp/ti/k3-am625-verdin-wifi-dahlia.dtb
>>> INSTALL /tmp/ti/k3-am625-verdin-wifi-dev.dtb
>>> INSTALL /tmp/ti/k3-am625-verdin-wifi-yavia.dtb
>>> INSTALL /tmp/ti/k3-am62-lp-sk.dtb
>>> INSTALL /tmp/ti/k3-am62x-sk-hdmi-audio.dtbo
>>> INSTALL /tmp/ti/k3-am62a7-sk.dtb
>>> INSTALL /tmp/ti/k3-am62p5-sk.dtb
>>> INSTALL /tmp/ti/k3-am642-evm.dtb
>>> INSTALL /tmp/ti/k3-am642-evm-nand.dtbo
>>> ^^^^
>>> INSTALL /tmp/ti/k3-am642-phyboard-electra-rdk.dtb
>>> INSTALL /tmp/ti/k3-am642-sk.dtb
>>>
>>>
>>> What did I miss?
>>
>> I missed it, actually. See Rob's comment:
>> https://lore.kernel.org/all/CAL_Jsq+GR3hP6hFvFn2z5aXvSXnh9butD3aKZ-y_XJgx0_YPTw@mail.gmail.com/
>>
>> Having orphan dtbo is apparently frowned upon
>>
>
> And if you apply these overlays to the base DTB then it gets
> symbols added automatically, no need for your patch [1/2] here.
>
Is this OK?
k3-am642-evm-nand-dtbs := k3-am642-evm.dtb k3-am642-evm-nand.dtbo
dtb-$(CONFIG_ARCH_K3) += k3-am642-evm-nand.dtb
So patch 1 is not required in this case but we have an
extra dtb file which is not really required.
I have 2 more issues to point out
1)
With existing examples e.g. J7200 EVM
wouldn't k3-j7200-evm.dtb include the k3-j7200-evm-quad-port-eth-exp.dtbo?
Is this what we really want?
likewise for k3-j721e-evm.dtb and k3-am654-gp-evm.dtb
2)
Another issue (unrelated to this change) is the below warning:
arch/arm64/boot/dts/ti/k3-am642-evm-nand.dtso:65.8-140.3: Warning (avoid_default_addr_size): /fragment@3/__overlay__: Relying on default #address-cells value
arch/arm64/boot/dts/ti/k3-am642-evm-nand.dtso:65.8-140.3: Warning (avoid_default_addr_size): /fragment@3/__overlay__: Relying on default #size-cells value
This is because we use the 'ranges' property in the gpmc0 node
and the compiler doesn't know the #address/size-cells of the
parent node.
Is there a trick to specify it in the dtso file?
--
cheers,
-roger
next prev parent reply other threads:[~2023-09-21 11:38 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-20 13:34 [PATCH 0/2] arm64: dts: ti: Add overlay for AM642-EVM NAND expansion card Roger Quadros
2023-09-20 13:34 ` Roger Quadros
2023-09-20 13:34 ` [PATCH 1/2] arm64: dts: ti: Enable support for overlays for relevant boards Roger Quadros
2023-09-20 13:34 ` Roger Quadros
2023-09-20 13:57 ` Nishanth Menon
2023-09-20 13:57 ` Nishanth Menon
2023-09-20 15:14 ` Roger Quadros
2023-09-20 15:14 ` Roger Quadros
2023-09-20 13:34 ` [PATCH 2/2] arm64: dts: ti: am642-evm: Add overlay for NAND expansion card Roger Quadros
2023-09-20 13:34 ` Roger Quadros
2023-09-20 13:58 ` Nishanth Menon
2023-09-20 13:58 ` Nishanth Menon
2023-09-20 15:18 ` Roger Quadros
2023-09-20 15:18 ` Roger Quadros
2023-09-20 16:44 ` Nishanth Menon
2023-09-20 16:44 ` Nishanth Menon
2023-09-20 17:06 ` Andrew Davis
2023-09-20 17:06 ` Andrew Davis
2023-09-21 11:37 ` Roger Quadros [this message]
2023-09-21 11:37 ` Roger Quadros
2023-09-21 17:23 ` Andrew Davis
2023-09-21 17:23 ` Andrew Davis
2023-09-22 9:03 ` Roger Quadros
2023-09-22 9:03 ` Roger Quadros
2023-09-22 14:54 ` Andrew Davis
2023-09-22 14:54 ` Andrew Davis
2023-09-22 20:09 ` Rob Herring
2023-09-22 20:09 ` Rob Herring
2024-01-23 20:07 ` Roger Quadros
2024-01-23 20:07 ` Roger Quadros
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=6f2b38f8-1962-46f2-a095-b1eaf99ed407@kernel.org \
--to=rogerq@kernel.org \
--cc=afd@ti.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--cc=robh+dt@kernel.org \
--cc=s-vadapalli@ti.com \
--cc=srk@ti.com \
--cc=vigneshr@ti.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.