From: Chintan Vankar <c-vankar@ti.com>
To: Vignesh Raghavendra <vigneshr@ti.com>,
Conor Dooley <conor+dt@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Rob Herring <robh@kernel.org>, Tero Kristo <kristo@kernel.org>,
Nishanth Menon <nm@ti.com>
Cc: <s-vadapalli@ti.com>, <srk@ti.com>, <danishanwar@ti.com>,
<linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v2] arm64: dts: ti: k3-am62x-sk-common: Add bootph-all property in cpsw_mac_syscon node
Date: Wed, 13 Nov 2024 14:55:23 +0530 [thread overview]
Message-ID: <32200597-9c02-4d43-bf91-3fe0b8ce83bc@ti.com> (raw)
In-Reply-To: <b2dadb0a-fd85-42fc-b340-6c77fe5ded0a@ti.com>
On 28/10/24 22:06, Vignesh Raghavendra wrote:
>
>
> On 11/10/24 16:32, Chintan Vankar wrote:
>> Add bootph-all property in CPSW MAC's eFuse node cpsw_mac_syscon.
>>
>
> Why?
>
> Please make sure commit message is verbose enough to say why the change
> is needed vs what that change is (latter is obvious lookng at the diff)
>
Sure Vignesh. I will update the commit message accordingly in next
version.
>> Signed-off-by: Chintan Vankar <c-vankar@ti.com>
>> ---
>>
>> This patch is based on linux-next tagged next-20241011.
>>
>> arch/arm64/boot/dts/ti/k3-am62x-sk-common.dtsi | 4 ++++
>> 1 file changed, 4 insertions(+)
>>
>> diff --git a/arch/arm64/boot/dts/ti/k3-am62x-sk-common.dtsi b/arch/arm64/boot/dts/ti/k3-am62x-sk-common.dtsi
>> index 44ff67b6bf1e..82d34dfb91ed 100644
>> --- a/arch/arm64/boot/dts/ti/k3-am62x-sk-common.dtsi
>> +++ b/arch/arm64/boot/dts/ti/k3-am62x-sk-common.dtsi
>> @@ -303,6 +303,10 @@ AM62X_MCU_IOPAD(0x028, PIN_OUTPUT, 0) /* (C5/C6) WKUP_UART0_TXD */
>> };
>> };
>>
>> +&cpsw_mac_syscon {
>> + bootph-all;
>> +};
>> +
>> &wkup_uart0 {
>> /* WKUP UART0 is used by DM firmware */
>> bootph-pre-ram;
>
prev parent reply other threads:[~2024-11-13 9:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-11 11:02 Chintan Vankar
2024-10-14 6:14 ` Siddharth Vadapalli
2024-10-28 16:36 ` Vignesh Raghavendra
2024-11-13 9:25 ` Chintan Vankar [this message]
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=32200597-9c02-4d43-bf91-3fe0b8ce83bc@ti.com \
--to=c-vankar@ti.com \
--cc=conor+dt@kernel.org \
--cc=danishanwar@ti.com \
--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=robh@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 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®