public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: "Kumar, Udit" <u-kumar1@ti.com>
To: <sabiya.d@mistralsolutions.com>, <nm@ti.com>, <vigneshr@ti.com>,
	<kristo@kernel.org>, <robh+dt@kernel.org>,
	<krzysztof.kozlowski+dt@linaro.org>, <linus.walleij@linaro.org>
Cc: <devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	Dasnavis Sabiya <sabiya.d@ti.com>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH V2 0/2] Add CAN and OSPI support for AM69-SK platform
Date: Wed, 7 Feb 2024 19:55:04 +0530	[thread overview]
Message-ID: <1d5c0570-fa10-4b87-9833-1710f33db01f@ti.com> (raw)
In-Reply-To: <20240205200744.216572-1-sabiya.d@ti.com>


On 2/6/2024 1:37 AM, sabiya.d@mistralsolutions.com wrote:
> From: Dasnavis Sabiya <sabiya.d@ti.com>
>
> Hi All,
>
> This series adds support for the below interfaces on AM69-SK platform:
> -  CAN support on both MCU and MAIN domains
> -  OSPI NOR flash support
>
> v2: Changelog:
> 1) Removed CAN interface aliasing.
> 2) Updated bootph property on the leaf nodes.
>
> Link to v1: https://lore.kernel.org/lkml/20240118153524.4135901-1-sabiya.d@ti.com/
>
> Dasnavis Sabiya (2):
>    arm64: dts: ti: k3-am69-sk: Enable CAN interfaces for AM69 SK board
>    arm64: dts: ti: k3-am69-sk: Add support for OSPI flash


For Series

Reviewed-by: Udit Kumar <u-kumar1@ti.com>


>   arch/arm64/boot/dts/ti/k3-am69-sk.dts | 162 ++++++++++++++++++++++++++
>   1 file changed, 162 insertions(+)
>

      parent reply	other threads:[~2024-02-07 14:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-05 20:07 [PATCH V2 0/2] Add CAN and OSPI support for AM69-SK platform sabiya.d
2024-02-05 20:07 ` [PATCH V2 1/2] arm64: dts: ti: k3-am69-sk: Enable CAN interfaces for AM69 SK board sabiya.d
2024-02-05 20:07 ` [PATCH V2 2/2] arm64: dts: ti: k3-am69-sk: Add support for OSPI flash sabiya.d
2024-02-07  9:15 ` [PATCH V2 0/2] Add CAN and OSPI support for AM69-SK platform Kumar, Udit
2024-02-07 12:55   ` Nishanth Menon
2024-02-07 14:25 ` 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=1d5c0570-fa10-4b87-9833-1710f33db01f@ti.com \
    --to=u-kumar1@ti.com \
    --cc=devicetree@vger.kernel.org \
    --cc=kristo@kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linus.walleij@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=sabiya.d@mistralsolutions.com \
    --cc=sabiya.d@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