From: Krzysztof Kozlowski <krzk@kernel.org>
To: Karan Sanghavi <karansanghvi98@gmail.com>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Florian Fainelli <florian.fainelli@broadcom.com>,
Broadcom internal kernel review list
<bcm-kernel-feedback-list@broadcom.com>,
Ray Jui <rjui@broadcom.com>,
Scott Branden <sbranden@broadcom.com>,
devicetree@vger.kernel.org, linux-rpi-kernel@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Shuah Khan <skhan@linuxfoundation.org>,
Alexander Aring <alex.aring@gmail.com>,
Eric Anholt <eric@anholt.net>
Subject: Re: [PATCH v2] dt-bindings: soc: bcm: Convert raspberrypi,bcm2835-power to Dt schema
Date: Sat, 26 Oct 2024 13:26:48 +0200 [thread overview]
Message-ID: <2d5f9959-17c9-4e61-a6df-ebd187f422e6@kernel.org> (raw)
In-Reply-To: <zaqykppssizdpd2mynpoatp4smbzkr7atuurxkkegbegk5dw6s@a2daqovt2aod>
On 25/10/2024 20:22, Karan Sanghavi wrote:
>>> +
>>> +examples:
>>> + - |
>>> + power: power {
>>
>> Drop label. Node name: power-controller
>>
>> I don't think this passes tests because of this. See power-domain.yaml
>> schema.
>>
>
> Below code is from bcm2711-rpi-4-b.dts decompiled from the dtb file.
Uh? Why would we ever care about decompiling some DTBs?
>
> firmware {
> compatible = "raspberrypi,bcm2835-firmware\0simple-mfd";
> mboxes = <0x1d>;
> phandle = <0x1e>;
> ...
> };
>
> power {
> compatible = "raspberrypi,bcm2835-power";
> firmware = <0x1e>;
> #power-domain-cells = <0x01>;
> phandle = <0x0b>;
> };
>
> I had a doubt that as above the raspberrypi,bcm2835-power compatible node
> is defined with power keyword, so should I still rename the node as
> power-controll or keep it has power?
I don't understand your arguments. Schema expects this to have proper
name (see bindings). DT spec as well.
>
> Also it does passes the dt_binding_check and CHECK_DTBS=y broadcom/bcm2711-rpi-4-b.dtb
> but does gives the message as
> soc: power: 'ranges' is a required property
> so do I need to add the range property here?
I have no clue what you are testing here. We do not care about some out
of tree DTB. And if you ask about upstream, then take conversions tasks
after reading this:
https://social.kernel.org/notice/Ai9hYRUKo8suzX3zNY
BTW, your patch has patch errors which *have to be fixed* as well. Apply
your patch to see them. Run checkpatch.
Best regards,
Krzysztof
prev parent reply other threads:[~2024-10-26 11:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-22 18:17 [PATCH v2] dt-bindings: soc: bcm: Convert raspberrypi,bcm2835-power to Dt schema Karan Sanghavi
2024-10-23 7:12 ` Krzysztof Kozlowski
2024-10-23 7:13 ` Krzysztof Kozlowski
2024-10-25 18:22 ` Karan Sanghavi
2024-10-26 11:26 ` Krzysztof Kozlowski [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=2d5f9959-17c9-4e61-a6df-ebd187f422e6@kernel.org \
--to=krzk@kernel.org \
--cc=alex.aring@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=eric@anholt.net \
--cc=florian.fainelli@broadcom.com \
--cc=karansanghvi98@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=rjui@broadcom.com \
--cc=robh@kernel.org \
--cc=sbranden@broadcom.com \
--cc=skhan@linuxfoundation.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;
as well as URLs for NNTP newsgroup(s).