From: Andrew Davis <afd@ti.com>
To: Nishanth Menon <nm@ti.com>
Cc: Vignesh Raghavendra <vigneshr@ti.com>,
Tero Kristo <kristo@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>, Dhruva Gole <d-gole@ti.com>,
<linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 07/13] arm64: dts: ti: k3-am64: Enable OSPI nodes at the board level
Date: Tue, 8 Aug 2023 09:19:04 -0500 [thread overview]
Message-ID: <8f4b8276-9285-4e90-e4f0-9af4925a8634@ti.com> (raw)
In-Reply-To: <20230808141725.65r25aoot54zcwex@turbojet>
On 8/8/23 9:17 AM, Nishanth Menon wrote:
> On 09:13-20230808, Andrew Davis wrote:
>> On 8/8/23 8:34 AM, Andrew Davis wrote:
>>> OSPI nodes defined in the top-level AM64 SoC dtsi files are incomplete
>>> and may not be functional unless they are extended with pinmux and
>>> device information.
>>>
>>> As the attached OSPI device is only known about at the board integration
>>> level, these nodes should only be enabled when provided with this
>>> information.
>>>
>>> Disable the OSPI nodes in the dtsi files and only enable the ones that
>>> are actually pinned out on a given board.
>>>
>>> Signed-off-by: Andrew Davis <afd@ti.com>
>>> Reviewed-by: Dhruva Gole <d-gole@ti.com>
>>> ---
>>
>> Oops, I see we have a new AM64 board in -next (tqma64xxl), I can either
>> rebase this again and enable the nodes in there. Or you can skip this
>> and the other AM64 patch in this series and I'll resend them next cycle
>> when that new board is settled.
>
> we should respin this series taking the new boards into consideration -
> am64 and am62 both have new boards.
>
No problem, v3 on the way.
Andrew
next prev parent reply other threads:[~2023-08-08 16:16 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-08 13:34 [PATCH v2 00/13] Another round of K3 DTSI disables Andrew Davis
2023-08-08 13:34 ` [PATCH v2 01/13] arm64: dts: ti: k3-j721e: Enable SDHCI nodes at the board level Andrew Davis
2023-08-08 13:34 ` [PATCH v2 02/13] arm64: dts: ti: k3-j7200: " Andrew Davis
2023-08-08 13:34 ` [PATCH v2 03/13] arm64: dts: ti: k3-j721s2: " Andrew Davis
2023-08-08 13:34 ` [PATCH v2 04/13] arm64: dts: ti: k3-am65: Enable OSPI " Andrew Davis
2023-08-08 13:34 ` [PATCH v2 05/13] arm64: dts: ti: k3-j721e: " Andrew Davis
2023-08-08 13:34 ` [PATCH v2 06/13] arm64: dts: ti: k3-j7200: " Andrew Davis
2023-08-08 13:34 ` [PATCH v2 07/13] arm64: dts: ti: k3-am64: " Andrew Davis
2023-08-08 14:13 ` Andrew Davis
2023-08-08 14:17 ` Nishanth Menon
2023-08-08 14:19 ` Andrew Davis [this message]
2023-08-08 13:34 ` [PATCH v2 08/13] arm64: dts: ti: k3-j721e: Enable GPIO " Andrew Davis
2023-08-08 13:34 ` [PATCH v2 09/13] arm64: dts: ti: k3-j721s2: " Andrew Davis
2023-08-08 13:34 ` [PATCH v2 10/13] arm64: dts: ti: k3-j7200: " Andrew Davis
2023-08-08 13:34 ` [PATCH v2 11/13] arm64: dts: ti: k3-j721e: Enable TSCADC " Andrew Davis
2023-08-08 13:34 ` [PATCH v2 12/13] arm64: dts: ti: k3-am65: " Andrew Davis
2023-08-08 13:34 ` [PATCH v2 13/13] arm64: dts: ti: k3-am64: " Andrew Davis
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=8f4b8276-9285-4e90-e4f0-9af4925a8634@ti.com \
--to=afd@ti.com \
--cc=conor+dt@kernel.org \
--cc=d-gole@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=kristo@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=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;
as well as URLs for NNTP newsgroup(s).