From: Krzysztof Kozlowski <krzk@kernel.org>
To: Harini T <harini.t@amd.com>
Cc: mkl@pengutronix.de, mailhol@kernel.org, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org, michal.simek@amd.com,
appana.durga.kedareswara.rao@amd.com, linux-can@vger.kernel.org,
devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] dt-bindings: can: xilinx_can: Document phys property
Date: Fri, 17 Jul 2026 11:20:22 +0200 [thread overview]
Message-ID: <20260717-determined-mindful-dalmatian-bfa374@quoll> (raw)
In-Reply-To: <20260717021415.2234865-3-harini.t@amd.com>
On Fri, Jul 17, 2026 at 07:44:15AM +0530, Harini T wrote:
> The Xilinx CAN and CANFD controllers can be connected to an external
> CAN transceiver on the board. That connection is described with the
> standard "phys" property on the controller node, pointing to a CAN
> transceiver PHY node which models the transceiver and its control
> lines (for example the standby/enable signals).
>
> Describe the optional "phys" property (a single transceiver PHY) so
> the on-board CAN transceiver can be described in the device tree.
>
> Signed-off-by: Harini T <harini.t@amd.com>
> ---
> Documentation/devicetree/bindings/net/can/xilinx,can.yaml | 3 +++
> 1 file changed, 3 insertions(+)
Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
Best regards,
Krzysztof
prev parent reply other threads:[~2026-07-17 9:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-17 2:14 [PATCH 0/2] dt-bindings: can: xilinx_can: Document phys and update maintainer Harini T
2026-07-17 2:14 ` [PATCH 1/2] MAINTAINERS: Replace maintainer for Xilinx CAN driver Harini T
2026-07-17 9:19 ` Krzysztof Kozlowski
2026-07-17 2:14 ` [PATCH 2/2] dt-bindings: can: xilinx_can: Document phys property Harini T
2026-07-17 9:20 ` Krzysztof Kozlowski [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=20260717-determined-mindful-dalmatian-bfa374@quoll \
--to=krzk@kernel.org \
--cc=appana.durga.kedareswara.rao@amd.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=harini.t@amd.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mailhol@kernel.org \
--cc=michal.simek@amd.com \
--cc=mkl@pengutronix.de \
--cc=robh@kernel.org \
/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