From: Krzysztof Kozlowski <krzk@kernel.org>
To: Marc Kleine-Budde <mkl@pengutronix.de>, Conor Dooley <conor@kernel.org>
Cc: linux-kernel@vger.kernel.org,
Conor Dooley <conor.dooley@microchip.com>,
Daire McNamara <daire.mcnamara@microchip.com>,
Vincent Mailhol <mailhol@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
linux-riscv@lists.infradead.org, linux-can@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [net-next v2] dt-bindings: can: mpfs: document resets
Date: Wed, 26 Nov 2025 11:26:17 +0100 [thread overview]
Message-ID: <b1511382-1fce-4a1b-a1c3-962a05fc07b5@kernel.org> (raw)
In-Reply-To: <20251126-famous-hummingbird-of-fruition-13a9ac-mkl@pengutronix.de>
On 26/11/2025 11:24, Marc Kleine-Budde wrote:
> Hello,
>
> can I get a review from the DT people?
We don't always review each other patches, so you kind of have DT review
already. I can review, but I just did not plan to review this... less
work needed...
>
> regards,
> Marc
>
> On 21.11.2025 13:42:30, 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!
>>
>> v2: update the example too...
>>
>> 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 | 5 +++++
>> 1 file changed, 5 insertions(+)
>>
>> diff --git a/Documentation/devicetree/bindings/net/can/microchip,mpfs-can.yaml b/Documentation/devicetree/bindings/net/can/microchip,mpfs-can.yaml
>> index 1219c5cb601f..519a11fbe972 100644
>> --- a/Documentation/devicetree/bindings/net/can/microchip,mpfs-can.yaml
>> +++ b/Documentation/devicetree/bindings/net/can/microchip,mpfs-can.yaml
>> @@ -32,11 +32,15 @@ properties:
>> - description: AHB peripheral clock
>> - description: CAN bus clock
>>
>> + resets:
>> + maxItems: 1
>> +
>> required:
>> - compatible
>> - reg
>> - interrupts
>> - clocks
>> + - resets
>>
>> additionalProperties: false
>>
>> @@ -46,6 +50,7 @@ examples:
>> compatible = "microchip,mpfs-can";
>> reg = <0x2010c000 0x1000>;
>> clocks = <&clkcfg 17>, <&clkcfg 37>;
>> + resets = <&clkcfg 17>;
>> interrupt-parent = <&plic>;
>> interrupts = <56>;
>> };
>> --
>> 2.51.0
>>
>>
>>
>
> --
> Pengutronix e.K. | Marc Kleine-Budde |
> Embedded Linux | https://www.pengutronix.de |
> Vertretung Nürnberg | Phone: +49-5121-206917-129 |
> Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-9 |
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-11-26 10:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-21 13:42 [net-next v2] dt-bindings: can: mpfs: document resets Conor Dooley
2025-11-26 10:24 ` Marc Kleine-Budde
2025-11-26 10:26 ` Krzysztof Kozlowski [this message]
2025-11-26 10:30 ` Marc Kleine-Budde
2025-11-26 18:14 ` Conor Dooley
2025-11-26 10:26 ` Krzysztof Kozlowski
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=b1511382-1fce-4a1b-a1c3-962a05fc07b5@kernel.org \
--to=krzk@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=conor@kernel.org \
--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