From: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
To: Lukasz Luba <lukasz.luba@arm.com>
Cc: Rob Herring <robh+dt@kernel.org>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, linux-pm@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: memory: convert Samsung Exynos DMC to dtschema
Date: Mon, 16 Aug 2021 10:32:20 +0200 [thread overview]
Message-ID: <0ec05a0b-9499-3bf4-a231-ea53b1cf99ed@canonical.com> (raw)
In-Reply-To: <73eebe7b-46da-137b-1938-09a5b453320a@arm.com>
On 16/08/2021 09:53, Lukasz Luba wrote:
> Hi Krzysztof,
>
> On 8/13/21 1:54 PM, Krzysztof Kozlowski wrote:
>> Convert Samsung Exynos5422 SoC frequency and voltage scaling for
>> Dynamic Memory Controller to DT schema format using json-schema.
>>
>> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
>> ---
>> .../memory-controllers/exynos5422-dmc.txt | 84 -----------
>> .../samsung,exynos5422-dmc.yaml | 137 ++++++++++++++++++
>> MAINTAINERS | 2 +-
>
> I'm not an expert in this DT scripts and why it complains. Maybe it
> complains because the "samsung,exynos-ppmu" is defined in the .txt
> file... (?)
> Although, in general looks OK.
>
> Acked-by: Lukasz Luba <lukasz.luba@arm.com>
I think the warning (triggered by DT_CHECKER_FLAGS=-m) can be ignored
because it complains about compatible in example which is not present in
the bindings. Usually it means someone wrote example not matching the
bindings (e.g. a typo in compatible) but here it is on purpose.
Best regards,
Krzysztof
next prev parent reply other threads:[~2021-08-16 8:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-13 12:54 [PATCH] dt-bindings: memory: convert Samsung Exynos DMC to dtschema Krzysztof Kozlowski
2021-08-13 16:49 ` Rob Herring
2021-08-16 7:53 ` Lukasz Luba
2021-08-16 8:32 ` Krzysztof Kozlowski [this message]
2021-08-16 8:35 ` Lukasz Luba
2021-08-18 14:31 ` Rob Herring
2021-08-18 14:43 ` Krzysztof Kozlowski
2021-08-20 13:31 ` Rob Herring
2021-08-20 13:53 ` 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=0ec05a0b-9499-3bf4-a231-ea53b1cf99ed@canonical.com \
--to=krzysztof.kozlowski@canonical.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=lukasz.luba@arm.com \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).