From: Kevin Hilman <khilman@baylibre.com>
To: Serge Semin <Sergey.Semin@baikalelectronics.ru>,
Felipe Balbi <balbi@kernel.org>,
Krzysztof Kozlowski <krzk@kernel.org>,
Florian Fainelli <f.fainelli@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Neil Armstrong <narmstrong@baylibre.com>,
Jerome Brunet <jbrunet@baylibre.com>,
Martin Blumenstingl <martin.blumenstingl@googlemail.com>
Cc: Serge Semin <Sergey.Semin@baikalelectronics.ru>,
Serge Semin <fancer.lancer@gmail.com>,
linux-usb@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-amlogic@lists.infradead.org
Subject: Re: [PATCH v4 02/10] arm64: dts: amlogic: meson-g12: Set FL-adj property value
Date: Fri, 11 Dec 2020 11:06:00 -0800 [thread overview]
Message-ID: <7hpn3g9n8n.fsf@baylibre.com> (raw)
In-Reply-To: <20201210091756.18057-3-Sergey.Semin@baikalelectronics.ru>
Serge Semin <Sergey.Semin@baikalelectronics.ru> writes:
> In accordance with the DWC USB3 bindings the property is supposed to have
> uint32 type. It's erroneous from the DT schema and driver points of view
> to declare it as boolean. As Neil suggested set it to 0x20 so not break
> the platform and to make the dtbs checker happy.
>
> Link: https://lore.kernel.org/linux-usb/20201010224121.12672-16-Sergey.Semin@baikalelectronics.ru/
> Signed-off-by: Serge Semin <Sergey.Semin@baikalelectronics.ru>
> Reviewed-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
> Reviewed-by: Neil Armstrong <narmstrong@baylibre.com>
> Reviewed-by: Krzysztof Kozlowski <krzk@kernel.org>
Queuing for fixes after adding:
Fixes: 9baf7d6be730 ("arm64: dts: meson: g12a: Add G12A USB nodes")
Thanks,
Kevin
next prev parent reply other threads:[~2020-12-11 20:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-10 9:17 [PATCH RESEND v4 00/10] dt-bindings: usb: Harmonize xHCI/EHCI/OHCI/DWC3 nodes name Serge Semin
2020-12-10 9:17 ` [PATCH v4 01/10] arm: dts: keystone: Correct DWC USB3 compatible string Serge Semin
2020-12-10 9:17 ` [PATCH v4 02/10] arm64: dts: amlogic: meson-g12: Set FL-adj property value Serge Semin
2020-12-11 19:06 ` Kevin Hilman [this message]
2020-12-10 9:17 ` [PATCH v4 03/10] arc: dts: Harmonize EHCI/OHCI DT nodes name Serge Semin
2020-12-10 9:17 ` [PATCH v4 04/10] arm: dts: lpc18xx: " Serge Semin
2020-12-10 9:17 ` [PATCH v4 05/10] powerpc: dts: akebono: " Serge Semin
2020-12-10 9:17 ` [PATCH v4 06/10] arm: dts: keystone: Harmonize DWC USB3 " Serge Semin
2020-12-10 9:17 ` [PATCH v4 07/10] arm: dts: stih407-family: " Serge Semin
2020-12-10 9:17 ` [PATCH v4 08/10] arm64: dts: apm: " Serge Semin
2020-12-10 9:17 ` [PATCH v4 09/10] usb: dwc3: qcom: Detect DWC3 DT-nodes with "usb"-prefixed names Serge Semin
2020-12-10 9:17 ` [PATCH v4 10/10] arm64: dts: qcom: Harmonize DWC USB3 DT nodes name Serge Semin
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=7hpn3g9n8n.fsf@baylibre.com \
--to=khilman@baylibre.com \
--cc=Sergey.Semin@baikalelectronics.ru \
--cc=balbi@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=fancer.lancer@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jbrunet@baylibre.com \
--cc=krzk@kernel.org \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=narmstrong@baylibre.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).