From: Kevin Hilman <khilman@baylibre.com>
To: Rob Herring <robh+dt@kernel.org>
Cc: Arnd Bergmann <arnd@arndb.de>, SoC Team <soc@kernel.org>,
devicetree@vger.kernel.org,
"open list:ARM/Amlogic Meson..."
<linux-amlogic@lists.infradead.org>
Subject: Re: [PATCH] arm64: dts: amlogic: misc DT schema fixups
Date: Wed, 21 Apr 2021 13:44:43 -0700 [thread overview]
Message-ID: <7hmttrbc5g.fsf@baylibre.com> (raw)
In-Reply-To: <CAL_Jsq+Z2Mxy_m1QpqgFi0M7DGqMYUwZhrgk_CP7Vy1frAzUcA@mail.gmail.com>
Rob Herring <robh+dt@kernel.org> writes:
> On Tue, Apr 20, 2021 at 6:04 PM Kevin Hilman <khilman@baylibre.com> wrote:
>>
>> Take a pass at cleaning up a bunch of warnings
>> from 'make dtbs_check' that have crept in.
>>
>> Signed-off-by: Kevin Hilman <khilman@baylibre.com>
>> ---
>> .../devicetree/bindings/gpu/arm,mali-bifrost.yaml | 5 +++++
>> .../bindings/media/amlogic,axg-ge2d.yaml | 1 +
>> Documentation/devicetree/bindings/media/rc.yaml | 4 ++++
>> .../devicetree/bindings/sound/amlogic,t9015.yaml | 1 +
>> arch/arm64/boot/dts/amlogic/meson-a1.dtsi | 4 ++--
>> arch/arm64/boot/dts/amlogic/meson-g12-common.dtsi | 14 +++++++-------
>> .../arm64/boot/dts/amlogic/meson-g12b-gsking-x.dts | 2 +-
>> .../boot/dts/amlogic/meson-g12b-gtking-pro.dts | 4 ++--
>> arch/arm64/boot/dts/amlogic/meson-g12b-gtking.dts | 2 +-
>> .../boot/dts/amlogic/meson-g12b-odroid-n2.dtsi | 4 ++--
>> .../arm64/boot/dts/amlogic/meson-gxbb-odroidc2.dts | 2 +-
>> .../dts/amlogic/meson-gxl-s905d-mecool-kii-pro.dts | 2 +-
>> .../boot/dts/amlogic/meson-gxl-s905d-sml5442tw.dts | 8 ++++----
>> .../boot/dts/amlogic/meson-gxm-mecool-kiii-pro.dts | 2 +-
>> .../boot/dts/amlogic/meson-gxm-minix-neo-u9h.dts | 2 +-
>> .../boot/dts/amlogic/meson-gxm-wetek-core2.dts | 2 +-
>> arch/arm64/boot/dts/amlogic/meson-khadas-vim3.dtsi | 4 ++--
>> .../arm64/boot/dts/amlogic/meson-sm1-odroid-c4.dts | 2 +-
>> 18 files changed, 38 insertions(+), 27 deletions(-)
>>
>> diff --git a/Documentation/devicetree/bindings/gpu/arm,mali-bifrost.yaml b/Documentation/devicetree/bindings/gpu/arm,mali-bifrost.yaml
>> index 184492162e7e..db2240bad012 100644
>> --- a/Documentation/devicetree/bindings/gpu/arm,mali-bifrost.yaml
>> +++ b/Documentation/devicetree/bindings/gpu/arm,mali-bifrost.yaml
>> @@ -69,6 +69,11 @@ properties:
>>
>> where voltage is in V, frequency is in MHz.
>>
>> + dma-coherent:
>> + description: |
>> + Present if page table walks made by the SMMU are cache coherent with the
>> + CPU.
>
> Copied from the SMMU binding whose definition is a bit special?
Oops, yes. A mostly blind copy/paste.
> Just 'dma-coherent: true' is good.
OK
Kevin
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
prev parent reply other threads:[~2021-04-21 20:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-20 23:04 [PATCH] arm64: dts: amlogic: misc DT schema fixups Kevin Hilman
2021-04-21 6:32 ` Arnd Bergmann
2021-04-21 7:51 ` Neil Armstrong
2021-04-21 12:51 ` Rob Herring
2021-04-21 12:55 ` Rob Herring
2021-04-21 20:44 ` Kevin Hilman [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=7hmttrbc5g.fsf@baylibre.com \
--to=khilman@baylibre.com \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=linux-amlogic@lists.infradead.org \
--cc=robh+dt@kernel.org \
--cc=soc@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).