From: Vinod Koul <vkoul@kernel.org>
To: Stefan Wahren <wahrenst@gmx.net>
Cc: Frank Li <Frank.Li@nxp.com>,
Christoph Stoidner <c.stoidner@phytec.de>,
Neil Armstrong <neil.armstrong@linaro.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Rob Herring <robh@kernel.org>,
linux-kernel@vger.kernel.org,
Aswath Govindraju <a-govindraju@ti.com>,
Fabio Estevam <festevam@gmail.com>,
devicetree@vger.kernel.org,
Marc Kleine-Budde <mkl@pengutronix.de>,
Conor Dooley <conor+dt@kernel.org>,
linux-can@vger.kernel.org, linux-phy@lists.infradead.org,
imx@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
Vincent Mailhol <mailhol@kernel.org>,
Pengutronix Kernel Team <kernel@pengutronix.de>
Subject: Re: (subset) [PATCH V5 0/4] arm64: dts: freescale: Add chargebyte Charge Control Y
Date: Sat, 3 Oct 2026 11:06:33 +0200 [thread overview]
Message-ID: <asDFmf_G0v_MWY3k@parshuram> (raw)
In-Reply-To: <72033c48-5219-4ed4-94fd-1b7d8ef8017c@gmx.net>
On 23-09-26, 18:11, Stefan Wahren wrote:
> 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
Not sure why I missed this, I have picked it now
--
~Vinod
next prev parent reply other threads:[~2026-10-03 9:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
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 ` [PATCH V5 2/4] dt-bindings: arm: fsl: Add chargebyte Charge Control Y Stefan Wahren
2026-09-07 15:04 ` [PATCH V5 3/4] dt-bindings: phy: ti,tcan104x-can: Document Microchip MCP2542 Stefan Wahren
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-21 13:09 ` [PATCH V5 0/4] " Stefan Wahren
2026-09-21 14:46 ` Frank Li
2026-09-23 9:19 ` Stefan Wahren
2026-10-02 15:31 ` Stefan Wahren
2026-10-02 16:06 ` Frank Li
2026-09-23 12:45 ` Vinod Koul
2026-09-23 12:44 ` (subset) " Vinod Koul
2026-09-23 16:11 ` Stefan Wahren
2026-10-03 9:06 ` Vinod Koul [this message]
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=asDFmf_G0v_MWY3k@parshuram \
--to=vkoul@kernel.org \
--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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®