All of lore.kernel.org
 help / color / mirror / Atom feed
From: Frank Li <Frank.li@oss.nxp.com>
To: Stefan Wahren <wahrenst@gmx.net>
Cc: Frank Li <Frank.Li@nxp.com>,
	Christoph Stoidner <c.stoidner@phytec.de>,
	Vinod Koul <vkoul@kernel.org>, Conor Dooley <conor+dt@kernel.org>,
	linux-kernel@vger.kernel.org,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Fabio Estevam <festevam@gmail.com>,
	Pengutronix Kernel Team <kernel@pengutronix.de>,
	Neil Armstrong <neil.armstrong@linaro.org>,
	Marc Kleine-Budde <mkl@pengutronix.de>,
	devicetree@vger.kernel.org, linux-can@vger.kernel.org,
	linux-phy@lists.infradead.org, imx@lists.linux.dev,
	linux-arm-kernel@lists.infradead.org,
	Rob Herring <robh@kernel.org>,
	Vincent Mailhol <mailhol@kernel.org>,
	Aswath Govindraju <a-govindraju@ti.com>
Subject: Re: [PATCH V5 0/4] arm64: dts: freescale: Add chargebyte Charge Control Y
Date: Mon, 21 Sep 2026 09:46:41 -0500	[thread overview]
Message-ID: <arFDUby0v52HSNnU@SMW015318> (raw)
In-Reply-To: <9cb548d3-f3cf-4757-a9ff-5f878479c7d7@gmx.net>

On Mon, Sep 21, 2026 at 03:09:23PM +0200, Stefan Wahren wrote:
> Hi Frank,
>
> Am 07.09.26 um 17:04 schrieb Stefan Wahren:
> > This series adds support for the chargebyte Charge Control Y, which is
> > an Electrical Vehicle Supply Equipment (EVSE) for MCS (Megawatt
> > Charging System) charging stations.
> >
> > sashiko reported in the first version of the series [1] that X_nRST_LAN
> > is available via GPIO line names, but there is no reset mechanismn in the
> > device tree. This finding is valid. Since the reset line feature isn't
> > implemented for LAN8651 driver yet, I like to proceed with the current
> > version. The LAN8651 handles reset via SPI commands and in rare cases
> > we still have the possibility to control the reset from userspace.
> > Btw the pin has a pull resistor in hardware, so it's not floating.
> >
> > sashiko complained in the fourth version of the series [2] about the
> > reset polarity of ethphy2 and the different drive strength across the
> > data lines. Both is intended.
> >
> > [1] - https://lore.kernel.org/linux-devicetree/20260818093147.E556C1F000E9@smtp.kernel.org/
> > [2] - https://lore.kernel.org/linux-devicetree/20260903082122.A777C1F000E9@smtp.kernel.org/
> >
> > Changes in V5:
> > - fix delete-node for pinctrl_leds (reported by sashiko)
> > - add Krzysztof's Reviewed-by
> I didn't received any feedback for V5 yet. Do you have any comments or could
> it be merged?

Wait for vinod pick phy binding part.

Frank

>
> Best regards
>

WARNING: multiple messages have this Message-ID (diff)
From: Frank Li <Frank.li@oss.nxp.com>
To: Stefan Wahren <wahrenst@gmx.net>
Cc: Frank Li <Frank.Li@nxp.com>,
	Christoph Stoidner <c.stoidner@phytec.de>,
	Vinod Koul <vkoul@kernel.org>, Conor Dooley <conor+dt@kernel.org>,
	linux-kernel@vger.kernel.org,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Fabio Estevam <festevam@gmail.com>,
	Pengutronix Kernel Team <kernel@pengutronix.de>,
	Neil Armstrong <neil.armstrong@linaro.org>,
	Marc Kleine-Budde <mkl@pengutronix.de>,
	devicetree@vger.kernel.org, linux-can@vger.kernel.org,
	linux-phy@lists.infradead.org, imx@lists.linux.dev,
	linux-arm-kernel@lists.infradead.org,
	Rob Herring <robh@kernel.org>,
	Vincent Mailhol <mailhol@kernel.org>,
	Aswath Govindraju <a-govindraju@ti.com>
Subject: Re: [PATCH V5 0/4] arm64: dts: freescale: Add chargebyte Charge Control Y
Date: Mon, 21 Sep 2026 09:46:41 -0500	[thread overview]
Message-ID: <arFDUby0v52HSNnU@SMW015318> (raw)
In-Reply-To: <9cb548d3-f3cf-4757-a9ff-5f878479c7d7@gmx.net>

On Mon, Sep 21, 2026 at 03:09:23PM +0200, Stefan Wahren wrote:
> Hi Frank,
>
> Am 07.09.26 um 17:04 schrieb Stefan Wahren:
> > This series adds support for the chargebyte Charge Control Y, which is
> > an Electrical Vehicle Supply Equipment (EVSE) for MCS (Megawatt
> > Charging System) charging stations.
> >
> > sashiko reported in the first version of the series [1] that X_nRST_LAN
> > is available via GPIO line names, but there is no reset mechanismn in the
> > device tree. This finding is valid. Since the reset line feature isn't
> > implemented for LAN8651 driver yet, I like to proceed with the current
> > version. The LAN8651 handles reset via SPI commands and in rare cases
> > we still have the possibility to control the reset from userspace.
> > Btw the pin has a pull resistor in hardware, so it's not floating.
> >
> > sashiko complained in the fourth version of the series [2] about the
> > reset polarity of ethphy2 and the different drive strength across the
> > data lines. Both is intended.
> >
> > [1] - https://lore.kernel.org/linux-devicetree/20260818093147.E556C1F000E9@smtp.kernel.org/
> > [2] - https://lore.kernel.org/linux-devicetree/20260903082122.A777C1F000E9@smtp.kernel.org/
> >
> > Changes in V5:
> > - fix delete-node for pinctrl_leds (reported by sashiko)
> > - add Krzysztof's Reviewed-by
> I didn't received any feedback for V5 yet. Do you have any comments or could
> it be merged?

Wait for vinod pick phy binding part.

Frank

>
> Best regards
>

-- 
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy

  reply	other threads:[~2026-09-21 14:46 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-07 15:04 [PATCH V5 0/4] arm64: dts: freescale: Add chargebyte Charge Control Y Stefan Wahren
2026-09-07 15:04 ` Stefan Wahren
2026-09-07 15:04 ` [PATCH V5 1/4] dt-bindings: phy: ti,tcan104x-can: Fix property constrains Stefan Wahren
2026-09-07 15:04   ` Stefan Wahren
2026-09-07 15:04 ` [PATCH V5 2/4] dt-bindings: arm: fsl: Add chargebyte Charge Control Y Stefan Wahren
2026-09-07 15:04   ` Stefan Wahren
2026-09-07 15:04 ` [PATCH V5 3/4] dt-bindings: phy: ti,tcan104x-can: Document Microchip MCP2542 Stefan Wahren
2026-09-07 15:04   ` Stefan Wahren
2026-09-28 19:31   ` Frank Li
2026-09-28 19:31     ` Frank Li
2026-09-07 15:04 ` [PATCH V5 4/4] arm64: dts: freescale: Add chargebyte Charge Control Y Stefan Wahren
2026-09-07 15:04   ` Stefan Wahren
2026-09-21 13:09 ` [PATCH V5 0/4] " Stefan Wahren
2026-09-21 13:09   ` Stefan Wahren
2026-09-21 14:46   ` Frank Li [this message]
2026-09-21 14:46     ` Frank Li
2026-09-23  9:19     ` Stefan Wahren
2026-09-23  9:19       ` Stefan Wahren
2026-10-02 15:31       ` Stefan Wahren
2026-10-02 15:31         ` Stefan Wahren
2026-10-02 16:06         ` Frank Li
2026-10-02 16:06           ` Frank Li
2026-10-06 15:41           ` Stefan Wahren
2026-10-06 15:41             ` Stefan Wahren
2026-09-23 12:45     ` Vinod Koul
2026-09-23 12:45       ` Vinod Koul
2026-09-23 12:44 ` (subset) " Vinod Koul
2026-09-23 12:44   ` Vinod Koul
2026-09-23 16:11   ` Stefan Wahren
2026-09-23 16:11     ` Stefan Wahren
2026-10-03  9:06     ` Vinod Koul
2026-10-03  9:06       ` Vinod Koul
2026-10-03  9:36 ` Vinod Koul
2026-10-03  9:36   ` 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=arFDUby0v52HSNnU@SMW015318 \
    --to=frank.li@oss.nxp.com \
    --cc=Frank.Li@nxp.com \
    --cc=a-govindraju@ti.com \
    --cc=c.stoidner@phytec.de \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=festevam@gmail.com \
    --cc=imx@lists.linux.dev \
    --cc=kernel@pengutronix.de \
    --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=linux-phy@lists.infradead.org \
    --cc=mailhol@kernel.org \
    --cc=mkl@pengutronix.de \
    --cc=neil.armstrong@linaro.org \
    --cc=robh@kernel.org \
    --cc=vkoul@kernel.org \
    --cc=wahrenst@gmx.net \
    /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.