From: Brian Norris <briannorris@chromium.org>
To: Heiko Stuebner <heiko@sntech.de>
Cc: linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
Caesar Wang <wxt@rock-chips.com>,
Doug Anderson <dianders@chromium.org>,
devicetree@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
Stephen Barber <smbarber@chromium.org>,
linux-arm-kernel@lists.infradead.org,
Chris Zhong <zyw@rock-chips.com>
Subject: Re: [PATCH 6/9] dt-bindings: Document rk3399 Gru/Kevin
Date: Wed, 7 Dec 2016 09:41:39 -0800 [thread overview]
Message-ID: <20161207174139.GA87970@google.com> (raw)
In-Reply-To: <1720836.rjtWqG8OD3@phil>
On Wed, Dec 07, 2016 at 06:12:13PM +0100, Heiko Stuebner wrote:
> Hi Brian,
>
> Am Donnerstag, 1. Dezember 2016, 18:27:30 CET schrieb Brian Norris:
> > Gru is a base dev board for a family of devices, including Kevin. Both
> > utilize Rockchip RK3399, and they share much of their design.
> >
> > Signed-off-by: Brian Norris <briannorris@chromium.org>
> > ---
> > Documentation/devicetree/bindings/arm/rockchip.txt | 20
> > ++++++++++++++++++++ 1 file changed, 20 insertions(+)
> >
> > diff --git a/Documentation/devicetree/bindings/arm/rockchip.txt
> > b/Documentation/devicetree/bindings/arm/rockchip.txt index
> > cc4ace6397ab..830e13f5890c 100644
> > --- a/Documentation/devicetree/bindings/arm/rockchip.txt
> > +++ b/Documentation/devicetree/bindings/arm/rockchip.txt
> > @@ -99,6 +99,26 @@ Rockchip platforms device tree bindings
> > "google,veyron-speedy-rev3", "google,veyron-speedy-rev2",
> > "google,veyron-speedy", "google,veyron", "rockchip,rk3288";
> >
> > +- Google Gru (dev-board):
>
> boards sorted alphabetically please
>
> Brian, Gru, Jaq, ... Kevin, ...
>
> While the sorting of old boards is not right yet, new boards should be sorted.
I got the idea that there was some attempt to group logically before
alphabetically. Like keeping board/SoC families together. But maybe not.
I can do as you suggested, if you don't care about keeping actual
similar boards together (i.e., veyron/3288 vs gru/3399).
Brian
WARNING: multiple messages have this Message-ID (diff)
From: Brian Norris <briannorris-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
To: Heiko Stuebner <heiko-4mtYJXux2i+zQB+pC5nmwQ@public.gmane.org>
Cc: linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Caesar Wang <wxt-TNX95d0MmH7DzftRWevZcw@public.gmane.org>,
Doug Anderson <dianders-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Rob Herring <robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
Stephen Barber <smbarber-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
Chris Zhong <zyw-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
Subject: Re: [PATCH 6/9] dt-bindings: Document rk3399 Gru/Kevin
Date: Wed, 7 Dec 2016 09:41:39 -0800 [thread overview]
Message-ID: <20161207174139.GA87970@google.com> (raw)
In-Reply-To: <1720836.rjtWqG8OD3@phil>
On Wed, Dec 07, 2016 at 06:12:13PM +0100, Heiko Stuebner wrote:
> Hi Brian,
>
> Am Donnerstag, 1. Dezember 2016, 18:27:30 CET schrieb Brian Norris:
> > Gru is a base dev board for a family of devices, including Kevin. Both
> > utilize Rockchip RK3399, and they share much of their design.
> >
> > Signed-off-by: Brian Norris <briannorris-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
> > ---
> > Documentation/devicetree/bindings/arm/rockchip.txt | 20
> > ++++++++++++++++++++ 1 file changed, 20 insertions(+)
> >
> > diff --git a/Documentation/devicetree/bindings/arm/rockchip.txt
> > b/Documentation/devicetree/bindings/arm/rockchip.txt index
> > cc4ace6397ab..830e13f5890c 100644
> > --- a/Documentation/devicetree/bindings/arm/rockchip.txt
> > +++ b/Documentation/devicetree/bindings/arm/rockchip.txt
> > @@ -99,6 +99,26 @@ Rockchip platforms device tree bindings
> > "google,veyron-speedy-rev3", "google,veyron-speedy-rev2",
> > "google,veyron-speedy", "google,veyron", "rockchip,rk3288";
> >
> > +- Google Gru (dev-board):
>
> boards sorted alphabetically please
>
> Brian, Gru, Jaq, ... Kevin, ...
>
> While the sorting of old boards is not right yet, new boards should be sorted.
I got the idea that there was some attempt to group logically before
alphabetically. Like keeping board/SoC families together. But maybe not.
I can do as you suggested, if you don't care about keeping actual
similar boards together (i.e., veyron/3288 vs gru/3399).
Brian
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: briannorris@chromium.org (Brian Norris)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 6/9] dt-bindings: Document rk3399 Gru/Kevin
Date: Wed, 7 Dec 2016 09:41:39 -0800 [thread overview]
Message-ID: <20161207174139.GA87970@google.com> (raw)
In-Reply-To: <1720836.rjtWqG8OD3@phil>
On Wed, Dec 07, 2016 at 06:12:13PM +0100, Heiko Stuebner wrote:
> Hi Brian,
>
> Am Donnerstag, 1. Dezember 2016, 18:27:30 CET schrieb Brian Norris:
> > Gru is a base dev board for a family of devices, including Kevin. Both
> > utilize Rockchip RK3399, and they share much of their design.
> >
> > Signed-off-by: Brian Norris <briannorris@chromium.org>
> > ---
> > Documentation/devicetree/bindings/arm/rockchip.txt | 20
> > ++++++++++++++++++++ 1 file changed, 20 insertions(+)
> >
> > diff --git a/Documentation/devicetree/bindings/arm/rockchip.txt
> > b/Documentation/devicetree/bindings/arm/rockchip.txt index
> > cc4ace6397ab..830e13f5890c 100644
> > --- a/Documentation/devicetree/bindings/arm/rockchip.txt
> > +++ b/Documentation/devicetree/bindings/arm/rockchip.txt
> > @@ -99,6 +99,26 @@ Rockchip platforms device tree bindings
> > "google,veyron-speedy-rev3", "google,veyron-speedy-rev2",
> > "google,veyron-speedy", "google,veyron", "rockchip,rk3288";
> >
> > +- Google Gru (dev-board):
>
> boards sorted alphabetically please
>
> Brian, Gru, Jaq, ... Kevin, ...
>
> While the sorting of old boards is not right yet, new boards should be sorted.
I got the idea that there was some attempt to group logically before
alphabetically. Like keeping board/SoC families together. But maybe not.
I can do as you suggested, if you don't care about keeping actual
similar boards together (i.e., veyron/3288 vs gru/3399).
Brian
next prev parent reply other threads:[~2016-12-07 17:41 UTC|newest]
Thread overview: 79+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-02 2:27 [PATCH 0/9] arm64: dts: rockchip: support Google Kevin Brian Norris
2016-12-02 2:27 ` Brian Norris
2016-12-02 2:27 ` Brian Norris
2016-12-02 2:27 ` [PATCH 1/9] arm64: dts: Add symlinks for cros-ec-keyboard and cros-ec-sbs Brian Norris
2016-12-02 2:27 ` Brian Norris
2016-12-02 2:27 ` Brian Norris
2016-12-02 2:27 ` [PATCH 2/9] arm64: dts: rockchip: add rk3399 thermal_zones phandle Brian Norris
2016-12-02 2:27 ` Brian Norris
2016-12-02 2:27 ` Brian Norris
2016-12-07 16:55 ` Heiko Stuebner
2016-12-07 16:55 ` Heiko Stuebner
2016-12-02 2:27 ` [PATCH 3/9] arm64: dts: rockchip: add rk3399 eDP HPD pinctrl Brian Norris
2016-12-02 2:27 ` Brian Norris
2016-12-02 2:27 ` Brian Norris
2016-12-07 16:56 ` Heiko Stuebner
2016-12-07 16:56 ` Heiko Stuebner
2016-12-02 2:27 ` [PATCH 4/9] arm64: dts: rockchip: support dwc3 USB for rk3399 Brian Norris
2016-12-02 2:27 ` Brian Norris
2016-12-02 2:27 ` Brian Norris
2016-12-07 17:09 ` Heiko Stuebner
2016-12-07 17:09 ` Heiko Stuebner
2016-12-07 17:52 ` Brian Norris
2016-12-07 17:52 ` Brian Norris
2016-12-07 17:52 ` Brian Norris
2016-12-07 19:01 ` Heiko Stuebner
2016-12-07 19:01 ` Heiko Stuebner
2016-12-07 19:01 ` Heiko Stuebner
2016-12-07 19:03 ` Brian Norris
2016-12-07 19:03 ` Brian Norris
2016-12-07 19:03 ` Brian Norris
2016-12-07 19:09 ` Heiko Stuebner
2016-12-07 19:09 ` Heiko Stuebner
2016-12-02 2:27 ` [PATCH 5/9] arm64: dts: rockchip: add rk3399 OPPs Brian Norris
2016-12-02 2:27 ` Brian Norris
2016-12-02 2:27 ` Brian Norris
2016-12-02 2:27 ` [PATCH 6/9] dt-bindings: Document rk3399 Gru/Kevin Brian Norris
2016-12-02 2:27 ` Brian Norris
2016-12-02 2:27 ` Brian Norris
2016-12-07 17:12 ` Heiko Stuebner
2016-12-07 17:12 ` Heiko Stuebner
2016-12-07 17:12 ` Heiko Stuebner
2016-12-07 17:41 ` Brian Norris [this message]
2016-12-07 17:41 ` Brian Norris
2016-12-07 17:41 ` Brian Norris
2016-12-07 19:15 ` Heiko Stuebner
2016-12-07 19:15 ` Heiko Stuebner
2016-12-09 17:54 ` Rob Herring
2016-12-09 17:54 ` Rob Herring
2016-12-09 18:28 ` Heiko Stuebner
2016-12-09 18:28 ` Heiko Stuebner
2016-12-09 18:28 ` Heiko Stuebner
2016-12-02 2:27 ` [PATCH 7/9] arm64: dts: rockchip: add Gru/Kevin DTS Brian Norris
2016-12-02 2:27 ` Brian Norris
2016-12-02 2:27 ` Brian Norris
2016-12-02 2:27 ` [PATCH 8/9] arm64: dts: rockchip: partially describe PWM regulators for Gru Brian Norris
2016-12-02 2:27 ` Brian Norris
2016-12-02 2:27 ` Brian Norris
2016-12-07 16:48 ` Heiko Stuebner
2016-12-07 16:48 ` Heiko Stuebner
2016-12-07 16:48 ` Heiko Stuebner
2016-12-07 17:09 ` Brian Norris
2016-12-07 17:09 ` Brian Norris
2016-12-13 17:48 ` Heiko Stuebner
2016-12-13 17:48 ` Heiko Stuebner
2016-12-22 16:09 ` Heiko Stübner
2016-12-22 16:09 ` Heiko Stübner
2016-12-22 16:09 ` Heiko Stübner
2016-12-02 2:27 ` [PATCH 9/9] arm64: dts: rockchip: add regulator info for Kevin digitizer Brian Norris
2016-12-02 2:27 ` Brian Norris
2016-12-02 2:27 ` Brian Norris
2016-12-13 17:36 ` Heiko Stuebner
2016-12-13 17:36 ` Heiko Stuebner
2016-12-13 17:36 ` Heiko Stuebner
2017-02-08 1:01 ` [PATCH 0/9] arm64: dts: rockchip: support Google Kevin Heiko Stuebner
2017-02-08 1:01 ` Heiko Stuebner
2017-02-08 1:01 ` Heiko Stuebner
2017-02-08 1:03 ` Brian Norris
2017-02-08 1:03 ` Brian Norris
2017-02-08 1:03 ` Brian Norris
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=20161207174139.GA87970@google.com \
--to=briannorris@chromium.org \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=heiko@sntech.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=robh+dt@kernel.org \
--cc=smbarber@chromium.org \
--cc=wxt@rock-chips.com \
--cc=zyw@rock-chips.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.