From: Chen-Yu Tsai <wens@kernel.org>
To: Heiko Stuebner <heiko@sntech.de>,
Rob Herring <robh+dt@kernel.org>,
Jacek Anaszewski <jacek.anaszewski@gmail.com>,
Pavel Machek <pavel@ucw.cz>, Dan Murphy <dmurphy@ti.com>
Cc: "open list:ARM/Rockchip SoC..."
<linux-rockchip@lists.infradead.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
devicetree <devicetree@vger.kernel.org>,
linux-leds@vger.kernel.org,
linux-kernel <linux-kernel@vger.kernel.org>,
Chen-Yu Tsai <wens@kernel.org>
Subject: Re: [PATCH v2 0/3] arm64: dts: rockchip: misc. cleanups and improvements
Date: Tue, 5 May 2020 14:24:25 +0800 [thread overview]
Message-ID: <CAGb2v67jPJA0hqXQg1Ufpkxt=7bqwoaQATRVuNg2AC5RZ9Os3w@mail.gmail.com> (raw)
In-Reply-To: <20200427073132.29997-1-wens@kernel.org>
Hi,
On Mon, Apr 27, 2020 at 3:31 PM Chen-Yu Tsai <wens@kernel.org> wrote:
>
> From: Chen-Yu Tsai <wens@csie.org>
>
> Hi,
>
> Here is the remaining patch for roc-rk3399-pc, along with a few other
> new patches.
>
> - Based on discussions from v1, patch one, newly added, drops the list
> of valid values for linux,default-triggers.
>
> - Patch two is the same as in v1
>
> - Patch three, new, sets dr_mode to "host" to the dwc2 OTG controller,
> matching what the board uses it for, a host port. This gets rid of
> a warning from the kernel.
>
> Please have a look.
Are there any comments from the maintainers?
I feel like this is getting needlessly sidetracked by the endless discussion
about GPIO LED node names which I left untouched on purpose in this series.
ChenYu
> Regards
> ChenYu
>
>
> Chen-Yu Tsai (3):
> dt-bindings: leds: common: Drop enumeration for linux,default-triggers
> arm64: dts: rockchip: rk3399-roc-pc: Fix MMC numbering for LED
> triggers
> arm64: dts: rockchip: rk3328-roc-cc: Set dr_mode to "host" for OTG
>
> .../devicetree/bindings/leds/common.yaml | 21 +------------------
> .../arm64/boot/dts/rockchip/rk3328-roc-cc.dts | 1 +
> .../dts/rockchip/rk3399-roc-pc-mezzanine.dts | 8 +++++++
> .../boot/dts/rockchip/rk3399-roc-pc.dtsi | 4 ++--
> 4 files changed, 12 insertions(+), 22 deletions(-)
>
> --
> 2.26.0
>
prev parent reply other threads:[~2020-05-05 6:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-27 7:31 [PATCH v2 0/3] arm64: dts: rockchip: misc. cleanups and improvements Chen-Yu Tsai
2020-04-27 7:31 ` [PATCH v2 1/3] dt-bindings: leds: common: Drop enumeration for linux,default-triggers Chen-Yu Tsai
2020-04-27 8:33 ` Johan Jonker
2020-04-27 9:21 ` Chen-Yu Tsai
2020-05-11 23:12 ` Rob Herring
2020-04-27 7:31 ` [PATCH v2 2/3] arm64: dts: rockchip: rk3399-roc-pc: Fix MMC numbering for LED triggers Chen-Yu Tsai
2020-04-27 8:57 ` Johan Jonker
2020-04-27 9:17 ` Chen-Yu Tsai
2020-04-27 10:08 ` Johan Jonker
2020-04-27 10:33 ` Chen-Yu Tsai
2020-04-27 10:55 ` Johan Jonker
2020-04-27 14:12 ` Johan Jonker
2020-04-27 14:45 ` Chen-Yu Tsai
2020-04-27 15:13 ` Robin Murphy
2020-04-27 7:31 ` [PATCH v2 3/3] arm64: dts: rockchip: rk3328-roc-cc: Set dr_mode to "host" for OTG Chen-Yu Tsai
2020-05-05 6:24 ` Chen-Yu Tsai [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='CAGb2v67jPJA0hqXQg1Ufpkxt=7bqwoaQATRVuNg2AC5RZ9Os3w@mail.gmail.com' \
--to=wens@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmurphy@ti.com \
--cc=heiko@sntech.de \
--cc=jacek.anaszewski@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=pavel@ucw.cz \
--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).