.../devicetree/bindings/arm/fsl.yaml | 1 + .../bindings/phy/ti,tcan104x-can.yaml | 10 +- arch/arm64/boot/dts/freescale/Makefile | 1 + .../dts/freescale/imx93-charge-control-y.dts | 438 ++++++++++++++++++ .../boot/dts/freescale/imx93-phycore-som.dtsi | 2 +- 5 files changed, 447 insertions(+), 5 deletions(-) create mode 100644 arch/arm64/boot/dts/freescale/imx93-charge-control-y.dts
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 Changes in V4: - prepend constrains fix for ti,tcan104x-can binding (reported by sashiko) Changes in V3: - add Acked-by's from Conor - add missing SD2_VSELECT to default pinctrl of SD interface (reported by sashiko) - clarify LAN8651 GPIO usage in device tree (suggested by Frank Li) - move X_nRST_LAN into dedicated pinctrl group to make it more self-explaining Changes in V2: - drop phy-can-transceiver changes and make MCP2542 compatible to TI TCAN1042 as suggested by Marc Kleine-Budde & Frank Li - implemented SD2_nRESET as vmmc supply for SD card interface (reported by sashiko) - add UHS support for SD card interface - dropped downstream property ti,leds-polarity (reported by sashiko) - fix GPIO line name of X_LAN_nCS (reported by sashiko) - drop unconnected pins (X_TDI, X_TMS_SWDIO, X_TDO) from GPIO line names Stefan Wahren (4): dt-bindings: phy: ti,tcan104x-can: Fix property constrains dt-bindings: arm: fsl: Add chargebyte Charge Control Y dt-bindings: phy: ti,tcan104x-can: Document Microchip MCP2542 arm64: dts: freescale: Add chargebyte Charge Control Y .../devicetree/bindings/arm/fsl.yaml | 1 + .../bindings/phy/ti,tcan104x-can.yaml | 10 +- arch/arm64/boot/dts/freescale/Makefile | 1 + .../dts/freescale/imx93-charge-control-y.dts | 438 ++++++++++++++++++ .../boot/dts/freescale/imx93-phycore-som.dtsi | 2 +- 5 files changed, 447 insertions(+), 5 deletions(-) create mode 100644 arch/arm64/boot/dts/freescale/imx93-charge-control-y.dts -- 2.43.0
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? Best regards
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 >
On 21-09-26, 09:46, Frank Li wrote: > 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. Done now -- ~Vinod
Hi Frank, hi Vinod, Am 21.09.26 um 16:46 schrieb Frank Li: > 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. @Vinod are you fine with both PHY bindings? @Frank I noticed that this patch has a conflict with the Makefile in linux-next. Should I rebase or do you resolve the conflict? Best regards > > Frank > >> Best regards >>
On Mon, 07 Sep 2026 17:04:16 +0200, Stefan Wahren wrote:
> 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.
>
> [...]
Applied, thanks!
[1/4] dt-bindings: phy: ti,tcan104x-can: Fix property constrains
commit: c7f2322431cb6d108b18fb4154606b49e2bc50f7
Best regards,
--
~Vinod
Hi Vinod, Am 23.09.26 um 14:44 schrieb Vinod Koul: > On Mon, 07 Sep 2026 17:04:16 +0200, Stefan Wahren wrote: >> 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. >> >> [...] > Applied, thanks! > > [1/4] dt-bindings: phy: ti,tcan104x-can: Fix property constrains > commit: c7f2322431cb6d108b18fb4154606b49e2bc50f7 thanks, but what about [3/4] dt-bindings: phy: ti,tcan104x-can: Document Microchip MCP2542 Best regards > > Best regards,
© 2016 - 2026 Red Hat, Inc.