From: Conor Dooley <conor@kernel.org>
To: "Rob Herring (Arm)" <robh@kernel.org>
Cc: Conor Dooley <conor.dooley@microchip.com>,
devicetree@vger.kernel.org,
Marc Kleine-Budde <mkl@pengutronix.de>,
Vincent Mailhol <mailhol@kernel.org>,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-can@vger.kernel.org,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Daire McNamara <daire.mcnamara@microchip.com>
Subject: Re: [net-next v1] dt-bindings: can: mpfs: document resets
Date: Mon, 17 Nov 2025 18:41:56 +0000 [thread overview]
Message-ID: <20251117-edgy-extenuate-6850a9440802@spud> (raw)
In-Reply-To: <20251117-example-spoiled-6b098fb9fdcc@spud>
[-- Attachment #1: Type: text/plain, Size: 2596 bytes --]
On Mon, Nov 17, 2025 at 06:29:55PM +0000, Conor Dooley wrote:
> On Mon, Nov 17, 2025 at 12:27:44PM -0600, Rob Herring (Arm) wrote:
> >
> > On Mon, 17 Nov 2025 16:38:18 +0000, Conor Dooley wrote:
> > > From: Conor Dooley <conor.dooley@microchip.com>
> > >
> > > The CAN cores on Polarfire SoC both have a reset. The platform firmware
> > > brings both cores out of reset, but the linux driver must use them
> > > during normal operation. The resets should have been made required, but
> > > this is one of the things that can happen when the binding is written
> > > without driver support.
> > >
> > > Fixes: c878d518d7b6 ("dt-bindings: can: mpfs: document the mpfs CAN controller")
> > > Signed-off-by: Conor Dooley <conor.dooley@microchip.com>
> > > ---
> > > This is the second mistake in this binding, both spotted because of the
> > > driver being written (although this one sat downstream for a while for
> > > w/e reason). I wish I could say that I'd send the driver soon, but I am
> > > busy upstreaming things I wrote and therefore understand at the moment,
> > > so a driver that I'd have to go understand and review before sending is
> > > low priority, sorry!
> > >
> > > CC: Conor Dooley <conor.dooley@microchip.com>
> > > CC: Daire McNamara <daire.mcnamara@microchip.com>
> > > CC: Marc Kleine-Budde <mkl@pengutronix.de>
> > > CC: Vincent Mailhol <mailhol@kernel.org>
> > > CC: Rob Herring <robh@kernel.org>
> > > CC: Krzysztof Kozlowski <krzk+dt@kernel.org>
> > > CC: linux-riscv@lists.infradead.org
> > > CC: linux-can@vger.kernel.org
> > > CC: devicetree@vger.kernel.org
> > > CC: linux-kernel@vger.kernel.org
> > > ---
> > > .../devicetree/bindings/net/can/microchip,mpfs-can.yaml | 4 ++++
> > > 1 file changed, 4 insertions(+)
> > >
> >
> > My bot found errors running 'make dt_binding_check' on your patch:
> >
> > yamllint warnings/errors:
> >
> > dtschema/dtc warnings/errors:
> > /builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/net/can/microchip,mpfs-can.example.dtb: can@2010c000 (microchip,mpfs-can): 'resets' is a required property
> > from schema $id: http://devicetree.org/schemas/net/can/microchip,mpfs-can.yaml
>
> Two issues in the same branch now, there's something weird going on with
> my test script. /sigh guess that's my evening gone.
I can spend my evening playing poe after all, I am pretty sure this was
caused by running my test script and then immediately switching windows
back and doing a rebase... I'll send a v2 tomorrow or w/e.
pw-bot: changes-requested
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2025-11-17 18:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-17 16:38 [net-next v1] dt-bindings: can: mpfs: document resets Conor Dooley
2025-11-17 18:27 ` Rob Herring (Arm)
2025-11-17 18:29 ` Conor Dooley
2025-11-17 18:41 ` Conor Dooley [this message]
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=20251117-edgy-extenuate-6850a9440802@spud \
--to=conor@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=daire.mcnamara@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=mailhol@kernel.org \
--cc=mkl@pengutronix.de \
--cc=robh@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