From: Wadim Egorov <w.egorov@phytec.de>
To: Nathan Morrisson <nmorrisson@phytec.com>, <nm@ti.com>,
<vigneshr@ti.com>, <kristo@kernel.org>, <robh@kernel.org>,
<krzk+dt@kernel.org>, <conor+dt@kernel.org>
Cc: <linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<upstream@lists.phytec.de>
Subject: Re: [PATCH v3 0/4] Add overlays to disable optional hardware in k3-am6xx-phycore-som boards
Date: Mon, 17 Jun 2024 16:03:55 +0200 [thread overview]
Message-ID: <fefe9e73-ee4d-4d7a-804b-baf8398a4893@phytec.de> (raw)
In-Reply-To: <20240613230759.1984966-1-nmorrisson@phytec.com>
Am 14.06.24 um 01:07 schrieb Nathan Morrisson:
> Add three overlays to disable the eth phy, rtc, and spi nor. These
> overlays will be used to disable device tree nodes for components
> that are optionally not populated.
>
> v3:
> - Explain the logic behind adding the overlays in commit messages
Looks like you forgot to pick up my Reviewed-by
https://lore.kernel.org/linux-arm-kernel/20240528225137.3629698-4-nmorrisson@phytec.com/T/#me4ddd3a713c4ff65e36fad333d59979ef1a92e8f
>
> v2:
> - Add build time tests in makefile
>
> Nathan Morrisson (4):
> arm64: dts: ti: k3-am64-phycore-som: Add serial_flash label
> arm64: dts: ti: k3-am6xx-phycore-som: Add overlay to disable eth phy
> arm64: dts: ti: k3-am6xx-phycore-som: Add overlay to disable rtc
> arm64: dts: ti: k3-am6xx-phycore-som: Add overlay to disable spi nor
>
> arch/arm64/boot/dts/ti/Makefile | 17 +++++++++++++++++
> .../boot/dts/ti/k3-am64-phycore-som.dtsi | 2 +-
> .../ti/k3-am6xx-phycore-disable-eth-phy.dtso | 19 +++++++++++++++++++
> .../dts/ti/k3-am6xx-phycore-disable-rtc.dtso | 15 +++++++++++++++
> .../ti/k3-am6xx-phycore-disable-spi-nor.dtso | 15 +++++++++++++++
> 5 files changed, 67 insertions(+), 1 deletion(-)
> create mode 100644 arch/arm64/boot/dts/ti/k3-am6xx-phycore-disable-eth-phy.dtso
> create mode 100644 arch/arm64/boot/dts/ti/k3-am6xx-phycore-disable-rtc.dtso
> create mode 100644 arch/arm64/boot/dts/ti/k3-am6xx-phycore-disable-spi-nor.dtso
>
next prev parent reply other threads:[~2024-06-17 14:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-13 23:07 [PATCH v3 0/4] Add overlays to disable optional hardware in k3-am6xx-phycore-som boards Nathan Morrisson
2024-06-13 23:07 ` [PATCH v3 1/4] arm64: dts: ti: k3-am64-phycore-som: Add serial_flash label Nathan Morrisson
2024-06-13 23:07 ` [PATCH v3 2/4] arm64: dts: ti: k3-am6xx-phycore-som: Add overlay to disable eth phy Nathan Morrisson
2024-06-13 23:07 ` [PATCH v3 3/4] arm64: dts: ti: k3-am6xx-phycore-som: Add overlay to disable rtc Nathan Morrisson
2024-06-13 23:07 ` [PATCH v3 4/4] arm64: dts: ti: k3-am6xx-phycore-som: Add overlay to disable spi nor Nathan Morrisson
2024-06-17 14:03 ` Wadim Egorov [this message]
2024-06-21 15:23 ` [PATCH v3 0/4] Add overlays to disable optional hardware in k3-am6xx-phycore-som boards 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=fefe9e73-ee4d-4d7a-804b-baf8398a4893@phytec.de \
--to=w.egorov@phytec.de \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kristo@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--cc=nmorrisson@phytec.com \
--cc=robh@kernel.org \
--cc=upstream@lists.phytec.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox