The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: "Kumar, Udit" <u-kumar1@ti.com>
To: Nishanth Menon <nm@ti.com>, Prasanth Babu Mantena <p-mantena@ti.com>
Cc: <devicetree@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>, <vigneshr@ti.com>,
	<kristo@kernel.org>, <robh@kernel.org>, <krzk+dt@kernel.org>,
	<conor+dt@kernel.org>, <linux-kernel@vger.kernel.org>,
	<u-kumar1@ti.com>
Subject: Re: [PATCH] arm64: dts: ti: k3-j721e-common-proc-board: Enable OSPI1 on J721E
Date: Mon, 5 May 2025 18:23:26 +0530	[thread overview]
Message-ID: <5d2aa775-a374-419f-b800-e1db96986660@ti.com> (raw)
In-Reply-To: <20250505123832.shukji5gfx3erjdq@lustiness>

Hi Prasanth

On 5/5/2025 6:08 PM, Nishanth Menon wrote:
> On 16:57-20250505, Prasanth Babu Mantena wrote:
>> J721E SoM has MT25QU512AB Serial NOR flash connected to
>> OSPI1 controller. Enable ospi1 node in device tree.
>>
>> Signed-off-by: Prasanth Babu Mantena <p-mantena@ti.com>
>> ---
>> Test log : https://gist.github.com/PrasanthBabuMantena/9dda540dce88282117de7e0e945e24ca
>>   arch/arm64/boot/dts/ti/k3-j721e-common-proc-board.dts | 1 +
>>   1 file changed, 1 insertion(+)
>>
>> diff --git a/arch/arm64/boot/dts/ti/k3-j721e-common-proc-board.dts b/arch/arm64/boot/dts/ti/k3-j721e-common-proc-board.dts
>> index e3d0ef6913b2..3112b351c052 100644
>> --- a/arch/arm64/boot/dts/ti/k3-j721e-common-proc-board.dts
>> +++ b/arch/arm64/boot/dts/ti/k3-j721e-common-proc-board.dts
>> @@ -571,6 +571,7 @@ &usb1 {
>>   };
>>   
>>   &ospi1 {
>> +	status = "okay";
> Follow Documentation/devicetree/bindings/dts-coding-style.rst

Also, please use Fixes tag

Fixes: cb27354b38f3b ("arm64: dts: ti: k3-j721e: Add DT nodes for few 
peripherials"


>
>>   	pinctrl-names = "default";
>>   	pinctrl-0 = <&mcu_fss0_ospi1_pins_default>;
>>   
>> -- 
>> 2.34.1
>>

      reply	other threads:[~2025-05-05 12:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-05 11:27 [PATCH] arm64: dts: ti: k3-j721e-common-proc-board: Enable OSPI1 on J721E Prasanth Babu Mantena
2025-05-05 12:38 ` Nishanth Menon
2025-05-05 12:53   ` Kumar, Udit [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=5d2aa775-a374-419f-b800-e1db96986660@ti.com \
    --to=u-kumar1@ti.com \
    --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=p-mantena@ti.com \
    --cc=robh@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