From: Horatiu Vultur <horatiu.vultur@microchip.com>
To: <kishon@ti.com>, <vkoul@kernel.org>, <robh+dt@kernel.org>,
<andrew@lunn.ch>, <alexandre.belloni@bootlin.com>,
<kuba@kernel.org>, <linux-phy@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH resend v4 0/3] phy: Add driver for lan966x Serdes driver
Date: Tue, 16 Nov 2021 11:21:51 +0100 [thread overview]
Message-ID: <20211116102151.k3evnn4f2rwsi5nk@soft-dev3-1.localhost> (raw)
In-Reply-To: <20211116100818.1615762-1-horatiu.vultur@microchip.com>
The 11/16/2021 11:08, Horatiu Vultur wrote:
Hi Kison, Vinod,
Can you let me know if you have more comments to this patch series?
Otherwise can you ack on it? Because I would like to have the patches
merged via netdev if that is OK for you.
Thanks
> This patch serie adds support for Microchip lan966x serdes. The lan966x
> device contains 7 interfaces, consisting of 2 copper transceivers,
> 3 Serdes and 2 RGMII interfaces. Two of the Serdes support QSGMII.
> The driver also adds the functionality of "muxing" the interfaces to
> different logical ports.
>
> The following table shows which interfaces can be supported by the port.
>
> PortNumber Max Speed Ethernet interface options
> 0 1Gbps CuPHY, 1G SGMII or QSGMII
> 1 1Gbps CuPHY, 1G SGMII or QSGMII
> 2 2.5Gbps 2.5G SGMII, QSGMII, RGMII
> 3 2.5Gbps 2.5G SGMII, QSGMII, RGMII
> 4 2.5Gbps 2.5G SGMII, QSGMII
> 5 1Gbps QSGMII, RGMII
> 6 1Gbps QSGMII, RGMII
> 7 1Gbps QSGMII
>
> v3->v4:
> - update description of the driver
> - removed unused registers
> - use bitfield operations in the registers
> - add macros for PLL configuration
> - move macros and structs at the top of the file
>
> v2->v3:
> - remove unused includes
> - add missing '...' in microchip,lan966x-serdes.yaml
> - rename lan966x-serdes.h to phy-lan966x-serdes.h
> - Rename CU->PHY and RG->RGMII
> - update commit message for PATCH 2
>
> v1->v2:
> - replace the regmap with iomem
> - update DT bindings
>
> Horatiu Vultur (3):
> dt-bindings: phy: Add lan966x-serdes binding
> dt-bindings: phy: Add constants for lan966x serdes
> phy: Add lan966x ethernet serdes PHY driver
>
> .../phy/microchip,lan966x-serdes.yaml | 59 ++
> drivers/phy/microchip/Kconfig | 8 +
> drivers/phy/microchip/Makefile | 1 +
> drivers/phy/microchip/lan966x_serdes.c | 548 ++++++++++++++++++
> drivers/phy/microchip/lan966x_serdes_regs.h | 209 +++++++
> include/dt-bindings/phy/phy-lan966x-serdes.h | 14 +
> 6 files changed, 839 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/phy/microchip,lan966x-serdes.yaml
> create mode 100644 drivers/phy/microchip/lan966x_serdes.c
> create mode 100644 drivers/phy/microchip/lan966x_serdes_regs.h
> create mode 100644 include/dt-bindings/phy/phy-lan966x-serdes.h
>
> --
> 2.33.0
>
--
/Horatiu
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
WARNING: multiple messages have this Message-ID (diff)
From: Horatiu Vultur <horatiu.vultur@microchip.com>
To: <kishon@ti.com>, <vkoul@kernel.org>, <robh+dt@kernel.org>,
<andrew@lunn.ch>, <alexandre.belloni@bootlin.com>,
<kuba@kernel.org>, <linux-phy@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH resend v4 0/3] phy: Add driver for lan966x Serdes driver
Date: Tue, 16 Nov 2021 11:21:51 +0100 [thread overview]
Message-ID: <20211116102151.k3evnn4f2rwsi5nk@soft-dev3-1.localhost> (raw)
In-Reply-To: <20211116100818.1615762-1-horatiu.vultur@microchip.com>
The 11/16/2021 11:08, Horatiu Vultur wrote:
Hi Kison, Vinod,
Can you let me know if you have more comments to this patch series?
Otherwise can you ack on it? Because I would like to have the patches
merged via netdev if that is OK for you.
Thanks
> This patch serie adds support for Microchip lan966x serdes. The lan966x
> device contains 7 interfaces, consisting of 2 copper transceivers,
> 3 Serdes and 2 RGMII interfaces. Two of the Serdes support QSGMII.
> The driver also adds the functionality of "muxing" the interfaces to
> different logical ports.
>
> The following table shows which interfaces can be supported by the port.
>
> PortNumber Max Speed Ethernet interface options
> 0 1Gbps CuPHY, 1G SGMII or QSGMII
> 1 1Gbps CuPHY, 1G SGMII or QSGMII
> 2 2.5Gbps 2.5G SGMII, QSGMII, RGMII
> 3 2.5Gbps 2.5G SGMII, QSGMII, RGMII
> 4 2.5Gbps 2.5G SGMII, QSGMII
> 5 1Gbps QSGMII, RGMII
> 6 1Gbps QSGMII, RGMII
> 7 1Gbps QSGMII
>
> v3->v4:
> - update description of the driver
> - removed unused registers
> - use bitfield operations in the registers
> - add macros for PLL configuration
> - move macros and structs at the top of the file
>
> v2->v3:
> - remove unused includes
> - add missing '...' in microchip,lan966x-serdes.yaml
> - rename lan966x-serdes.h to phy-lan966x-serdes.h
> - Rename CU->PHY and RG->RGMII
> - update commit message for PATCH 2
>
> v1->v2:
> - replace the regmap with iomem
> - update DT bindings
>
> Horatiu Vultur (3):
> dt-bindings: phy: Add lan966x-serdes binding
> dt-bindings: phy: Add constants for lan966x serdes
> phy: Add lan966x ethernet serdes PHY driver
>
> .../phy/microchip,lan966x-serdes.yaml | 59 ++
> drivers/phy/microchip/Kconfig | 8 +
> drivers/phy/microchip/Makefile | 1 +
> drivers/phy/microchip/lan966x_serdes.c | 548 ++++++++++++++++++
> drivers/phy/microchip/lan966x_serdes_regs.h | 209 +++++++
> include/dt-bindings/phy/phy-lan966x-serdes.h | 14 +
> 6 files changed, 839 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/phy/microchip,lan966x-serdes.yaml
> create mode 100644 drivers/phy/microchip/lan966x_serdes.c
> create mode 100644 drivers/phy/microchip/lan966x_serdes_regs.h
> create mode 100644 include/dt-bindings/phy/phy-lan966x-serdes.h
>
> --
> 2.33.0
>
--
/Horatiu
next prev parent reply other threads:[~2021-11-16 10:20 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-16 10:08 [PATCH resend v4 0/3] phy: Add driver for lan966x Serdes driver Horatiu Vultur
2021-11-16 10:08 ` Horatiu Vultur
2021-11-16 10:08 ` [PATCH resend v4 1/3] dt-bindings: phy: Add lan966x-serdes binding Horatiu Vultur
2021-11-16 10:08 ` Horatiu Vultur
2021-11-30 14:02 ` Geert Uytterhoeven
2021-11-30 14:02 ` Geert Uytterhoeven
2021-11-30 16:11 ` Horatiu Vultur
2021-11-30 16:11 ` Horatiu Vultur
2021-11-16 10:08 ` [PATCH resend v4 2/3] dt-bindings: phy: Add constants for lan966x serdes Horatiu Vultur
2021-11-16 10:08 ` Horatiu Vultur
2021-11-16 10:08 ` [PATCH resend v4 3/3] phy: Add lan966x ethernet serdes PHY driver Horatiu Vultur
2021-11-16 10:08 ` Horatiu Vultur
2021-11-16 10:21 ` Horatiu Vultur [this message]
2021-11-16 10:21 ` [PATCH resend v4 0/3] phy: Add driver for lan966x Serdes driver Horatiu Vultur
2021-11-16 10:45 ` Vinod Koul
2021-11-16 10:45 ` Vinod Koul
2021-11-16 10:56 ` Horatiu Vultur
2021-11-16 10:56 ` Horatiu Vultur
2021-11-16 11:43 ` Vinod Koul
2021-11-16 11:43 ` Vinod Koul
2021-11-16 11:52 ` Horatiu Vultur
2021-11-16 11:52 ` Horatiu Vultur
2021-11-16 18:12 ` Alexandre Belloni
2021-11-16 18:12 ` Alexandre Belloni
2021-11-16 22:05 ` Horatiu Vultur
2021-11-16 22:05 ` Horatiu Vultur
2021-11-23 7:39 ` Vinod Koul
2021-11-23 7:39 ` Vinod Koul
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=20211116102151.k3evnn4f2rwsi5nk@soft-dev3-1.localhost \
--to=horatiu.vultur@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=andrew@lunn.ch \
--cc=devicetree@vger.kernel.org \
--cc=kishon@ti.com \
--cc=kuba@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.