devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Horatiu Vultur <horatiu.vultur@microchip.com>
Cc: kishon@ti.com, andrew@lunn.ch, devicetree@vger.kernel.org,
	linux-phy@lists.infradead.org, robh+dt@kernel.org,
	alexandre.belloni@bootlin.com, vkoul@kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 2/3] dt-bindings: phy: Add constants for lan966x serdes
Date: Wed, 27 Oct 2021 15:37:28 -0500	[thread overview]
Message-ID: <YXm4iO4r5Ka2VtKF@robh.at.kernel.org> (raw)
In-Reply-To: <20211020094229.1760793-3-horatiu.vultur@microchip.com>

On Wed, 20 Oct 2021 11:42:28 +0200, Horatiu Vultur wrote:
> Lan966x has: 2 integrated PHYs, 3 SerDes and 2 RGMII interfaces. Which
> requires to be muxed based on the HW representation.
> 
> So add constants for each interface to be able to distinguish them.
> 
> Signed-off-by: Horatiu Vultur <horatiu.vultur@microchip.com>
> ---
>  include/dt-bindings/phy/phy-lan966x-serdes.h | 14 ++++++++++++++
>  1 file changed, 14 insertions(+)
>  create mode 100644 include/dt-bindings/phy/phy-lan966x-serdes.h
> 

Reviewed-by: Rob Herring <robh@kernel.org>

  reply	other threads:[~2021-10-27 20:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-20  9:42 [PATCH v4 0/3] phy: Add driver for lan966x Serdes driver Horatiu Vultur
2021-10-20  9:42 ` [PATCH v4 1/3] dt-bindings: phy: Add lan966x-serdes binding Horatiu Vultur
2021-10-27 20:37   ` Rob Herring
2021-10-20  9:42 ` [PATCH v4 2/3] dt-bindings: phy: Add constants for lan966x serdes Horatiu Vultur
2021-10-27 20:37   ` Rob Herring [this message]
2021-10-20  9:42 ` [PATCH v4 3/3] phy: Add lan966x ethernet serdes PHY driver Horatiu Vultur
2021-11-04  8:58 ` [PATCH v4 0/3] phy: Add driver for lan966x Serdes driver Horatiu Vultur

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=YXm4iO4r5Ka2VtKF@robh.at.kernel.org \
    --to=robh@kernel.org \
    --cc=alexandre.belloni@bootlin.com \
    --cc=andrew@lunn.ch \
    --cc=devicetree@vger.kernel.org \
    --cc=horatiu.vultur@microchip.com \
    --cc=kishon@ti.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-phy@lists.infradead.org \
    --cc=robh+dt@kernel.org \
    --cc=vkoul@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;
as well as URLs for NNTP newsgroup(s).