From: Krzysztof Kozlowski <krzk@kernel.org>
To: Greg Ungerer <gerg@linux-m68k.org>, linux-m68k@lists.linux-m68k.org
Subject: Re: [PATCH 09/13] m68k: coldfire: add devicetree for mcf5475-evb platform
Date: Wed, 19 Feb 2025 09:26:37 +0100 [thread overview]
Message-ID: <4155980d-cee8-4d60-8ca2-51be1d351282@kernel.org> (raw)
In-Reply-To: <f509221c-1b56-4c43-8f60-86c419bc9c4d@linux-m68k.org>
On 19/02/2025 09:23, Greg Ungerer wrote:
> Hi Krzysztof,
>
> On 19/2/25 17:06, Krzysztof Kozlowski wrote:
>> On 18/02/2025 13:46, Greg Ungerer wrote:
>>> Add a simple devicetree to support the Freescale MCF5475-EVB platform.
>>>
>>> Signed-off-by: Greg Ungerer <gerg@linux-m68k.org>
>>> ---
>>> arch/m68k/boot/dts/Makefile | 1 +
>>> arch/m68k/boot/dts/mcf5475evb.dts | 55 +++++++++++++++++++++++++++++++
>>> 2 files changed, 56 insertions(+)
>>> create mode 100644 arch/m68k/boot/dts/mcf5475evb.dts
>>>
>>> diff --git a/arch/m68k/boot/dts/Makefile b/arch/m68k/boot/dts/Makefile
>>> index d69e37b48558..f0e9643e6b71 100644
>>> --- a/arch/m68k/boot/dts/Makefile
>>> +++ b/arch/m68k/boot/dts/Makefile
>>> @@ -1,4 +1,5 @@
>>> # SPDX-License-Identifier: GPL-2.0
>>>
>>> dtb-y += mcf5208evb.dtb
>>> +dtb-y += mcf5475evb.dtb
>>>
>>> diff --git a/arch/m68k/boot/dts/mcf5475evb.dts b/arch/m68k/boot/dts/mcf5475evb.dts
>>> new file mode 100644
>>> index 000000000000..247a938bfafd
>>> --- /dev/null
>>> +++ b/arch/m68k/boot/dts/mcf5475evb.dts
>>> @@ -0,0 +1,55 @@
>>> +// SPDX-License-Identifier: GPL-2.0
>>> +/dts-v1/;
>>> +
>>> +/ {
>>> + model = "Freescale MCF5475EVB";
>>> + compatible = "mcf5475evb";
>>
>> Incorrect format.
>>
>> Please run scripts/checkpatch.pl and fix reported warnings. After that,
>> run also `scripts/checkpatch.pl --strict` and (probably) fix more
>> warnings. Some warnings can be ignored, especially from --strict run,
>> but the code here looks like it needs a fix. Feel free to get in touch
>> if the warning is not clear.
>
> If that is an incorrect format then checkpatch is not reporting it.
There are two issues here.
1. Incorrect format: see DT spec or any other example.
2. Below checkpatch warning.
>
> Checkpatch here (even --strict) only reports that it is undocumented:
>
> WARNING: DT compatible string "mcf5475evb" appears un-documented -- check ./Documentation/devicetree/bindings/
> #36: FILE: arch/m68k/boot/dts/mcf5475evb.dts:6:
> + compatible = "mcf5475evb";
>
> Which I totally expect at this point. As pointed out in the cover letter this
> work is very much an incomplete proof-of-concept still. Much work still to do here.
Patch should be marked as RFC with that explanation in cover letter, so
you won't get such review comments.
>>> + #address-cells = <1>;
>>> + #size-cells = <1>;
>>> + interrupt-parent = <&intc>;
>>> +
>>> + coreclk: clock-266000000 {
>>> + #clock-cells = <0>;
>>> + compatible = "fixed-clock";
>>> + clock-frequency = <266000000>;
>>> + };
>>> +
>>> + intc: interrupt-controller@ff000700 {
>>> + compatible = "fsl,intc-2";
>>> + interrupt-controller;
>>> + #interrupt-cells = <1>;
>>> + reg = <0xff000700 0x80>;
>>> + };
>>> +
>>> + uart0: serial@ff008600 {
>>> + compatible = "fsl,mcfuart";
>>> + reg = <0xff008600 0x80>;
>>> + interrupts = <99>;
>>> + clocks = <&coreclk>;
>>> + status = "okay";
>>
>> Did you disable it anywhere?
>
> No.
So no need for that status.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-02-19 8:26 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-18 12:46 [PATCH 00/13] m68k: coldfire: proof-of-concept devicetree Greg Ungerer
2025-02-18 12:46 ` [PATCH 01/13] serial: mcf: convert to use proper platform resources Greg Ungerer
2025-02-18 12:46 ` [PATCH 02/13] serial: mcf: add devicetree support Greg Ungerer
2025-02-18 12:46 ` [PATCH 03/13] net: fec: add device tree support for ColdFire FEC Greg Ungerer
2025-02-19 7:05 ` Krzysztof Kozlowski
2025-02-19 13:25 ` Greg Ungerer
2025-02-18 12:46 ` [PATCH 04/13] m68k: coldfire: enable common clock framework Greg Ungerer
2025-02-18 12:46 ` [PATCH 05/13] m68k: coldfire: support devicetree binding for intc-simr Greg Ungerer
2025-02-18 12:46 ` [PATCH 06/13] m68k: coldfire: support devicetree binding for intc controller Greg Ungerer
2025-02-18 12:46 ` [PATCH 07/13] m68k: coldfire: support devicetree binding for intc-2 controller Greg Ungerer
2025-02-18 12:46 ` [PATCH 08/13] m68k: coldfire: add devicetree for mcf5208-evb platform Greg Ungerer
2025-02-18 12:46 ` [PATCH 09/13] m68k: coldfire: add devicetree for mcf5475-evb platform Greg Ungerer
2025-02-19 7:06 ` Krzysztof Kozlowski
2025-02-19 8:23 ` Greg Ungerer
2025-02-19 8:26 ` Krzysztof Kozlowski [this message]
2025-02-19 21:58 ` Greg Ungerer
2025-02-18 12:46 ` [PATCH 10/13] m68k: implement an embedded devicetree for nonmmu Greg Ungerer
2025-02-20 14:06 ` Geert Uytterhoeven
2025-02-23 14:25 ` Greg Ungerer
2025-02-18 12:46 ` [PATCH 11/13] m68k: implement an embedded devicetree for mm targets Greg Ungerer
2025-02-18 12:46 ` [PATCH 12/13] m68k: coldfire: disable platform device tree entries Greg Ungerer
2025-02-18 12:46 ` [PATCH 13/13] m68k: coldfire: enable devicetree use Greg Ungerer
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=4155980d-cee8-4d60-8ca2-51be1d351282@kernel.org \
--to=krzk@kernel.org \
--cc=gerg@linux-m68k.org \
--cc=linux-m68k@lists.linux-m68k.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