From: Jan Kiszka <jan.kiszka@siemens.com>
To: Nishanth Menon <nm@ti.com>, Vignesh Raghavendra <vigneshr@ti.com>,
Tero Kristo <kristo@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
Bao Cheng Su <baocheng.su@siemens.com>,
Benedikt Niedermayr <benedikt.niedermayr@siemens.com>
Subject: Re: [PATCH v2 5/5] arm64: dts: ti: iot2050: Add icssg-prueth nodes for PG2 devices
Date: Fri, 3 Nov 2023 10:13:09 +0100 [thread overview]
Message-ID: <14e08512-8664-4290-b5a0-348f8a5f9e2d@siemens.com> (raw)
In-Reply-To: <c46fddcf96f59af0796cefbe51dfff844261f22d.1698773019.git.jan.kiszka@siemens.com>
On 31.10.23 18:23, Jan Kiszka wrote:
> From: Jan Kiszka <jan.kiszka@siemens.com>
>
> Add the required nodes to enable ICSSG SR2.0 based prueth networking.
>
> As the driver still needs to be extended for SR1.0 support, keep related
> nodes disabled on PG1 devices.
>
I've noticed some PG1 bits and some not yet upstreamed properties in
this. V3 will follow.
Jan
--
Siemens AG, Technology
Linux Expert Center
prev parent reply other threads:[~2023-11-03 9:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-31 17:23 [PATCH v2 0/5] arm64: dts: iot2050: DT fixes, cleanups and enhancements Jan Kiszka
2023-10-31 17:23 ` [PATCH v2 1/5] arm64: dts: ti: iot2050: Re-add aliases Jan Kiszka
2023-10-31 17:23 ` [PATCH v2 2/5] arm64: dts: ti: iot2050: Drop unused ecap0 PWM Jan Kiszka
2023-10-31 17:23 ` [PATCH v2 3/5] arm64: dts: ti: iot2050: Definitions for runtime pinmuxing Jan Kiszka
2023-10-31 17:23 ` [PATCH v2 4/5] arm64: dts: ti: iot2050: Refactor the m.2 and minipcie power pin Jan Kiszka
2023-10-31 17:23 ` [PATCH v2 5/5] arm64: dts: ti: iot2050: Add icssg-prueth nodes for PG2 devices Jan Kiszka
2023-11-03 9:13 ` Jan Kiszka [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=14e08512-8664-4290-b5a0-348f8a5f9e2d@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=baocheng.su@siemens.com \
--cc=benedikt.niedermayr@siemens.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
all inboxes | Powered by JetHome®