From: Tony Lindgren <tony@atomide.com>
To: Nishanth Menon <nm@ti.com>
Cc: Wadim Egorov <w.egorov@phytec.de>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-hardening@vger.kernel.org, upstream@lists.phytec.de,
vigneshr@ti.com, kristo@kernel.org, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, keescook@chromium.org,
tony.luck@intel.com, gpiccoli@igalia.com
Subject: Re: [PATCH 2/2] arm64: dts: ti: Add basic support for phyBOARD-Lyra-AM625
Date: Fri, 5 May 2023 12:39:30 +0300 [thread overview]
Message-ID: <20230505093930.GS14287@atomide.com> (raw)
In-Reply-To: <20230504142643.pkzsftrsrqph4vql@banked>
* Nishanth Menon <nm@ti.com> [230504 14:33]:
> Just wondering: if the carrier board can easily work with different
> SoMs.. in which case, we could do overlay to create the som + carrier
> overlay to create rdk dtb - this might allow the scheme to scale to
> additional SoMs and carrier combinations.. and the SoM dtb could be
> sufficient for something like a bootloader.
It might be best to limit the overlay usage to devices that might see
dual use on the carrier board.. Not sure if setting up the entire
carrier board makes sense as an overlay :) Not sure if folks want to
debug boot issues on a remote server for example if an overlay is
needed to boot with Ethernet :)
Regards,
Tony
next prev parent reply other threads:[~2023-05-05 9:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-04 14:01 [PATCH 1/2] dt-bindings: arm: ti: Add bindings for PHYTEC AM62x based hardware Wadim Egorov
2023-05-04 14:01 ` [PATCH 2/2] arm64: dts: ti: Add basic support for phyBOARD-Lyra-AM625 Wadim Egorov
2023-05-04 14:26 ` Nishanth Menon
2023-05-05 9:39 ` Tony Lindgren [this message]
2023-05-05 13:38 ` Wadim Egorov
2023-05-08 8:41 ` Tony Lindgren
2023-05-05 9:41 ` Tony Lindgren
2023-05-05 6:53 ` [PATCH 1/2] dt-bindings: arm: ti: Add bindings for PHYTEC AM62x based hardware Krzysztof Kozlowski
2023-05-05 9:40 ` Tony Lindgren
2023-06-15 10:45 ` Vignesh Raghavendra
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=20230505093930.GS14287@atomide.com \
--to=tony@atomide.com \
--cc=devicetree@vger.kernel.org \
--cc=gpiccoli@igalia.com \
--cc=keescook@chromium.org \
--cc=kristo@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--cc=robh+dt@kernel.org \
--cc=tony.luck@intel.com \
--cc=upstream@lists.phytec.de \
--cc=vigneshr@ti.com \
--cc=w.egorov@phytec.de \
/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;
as well as URLs for NNTP newsgroup(s).