All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rob Herring <robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: Robin Murphy <robin.murphy-5wv7dgnIgG8@public.gmane.org>
Cc: Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org>,
	linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
	heiko-4mtYJXux2i+zQB+pC5nmwQ@public.gmane.org,
	linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
	devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH v2 1/4] arm64: dts: rockchip: Add DT for NanoPi M4
Date: Wed, 16 Jan 2019 15:12:58 -0600	[thread overview]
Message-ID: <20190116211258.GA29888@bogus> (raw)
In-Reply-To: <a96995cfa599792b24e740ce46d53bd68ef1d462.1547466003.git.robin.murphy-5wv7dgnIgG8@public.gmane.org>

On Mon, 14 Jan 2019 12:05:31 +0000, Robin Murphy wrote:
> There are a number of subtle differences between the nanopi4 variants,
> and where they disagree, the common DTSI currently follows the details
> of NanoPi M4. In order to improve matters even more, let's add a
> separate DTS for the M4 to which we can start splitting things out
> appropriately. The third variant, NanoPi NEO4, is a lot closer to the M4
> than either is to the larger T4, so arguably could get away with just
> sharing the M4 DT for now (plus I have neither of the smaller boards to
> actually test with).
> 
> CC: Rob Herring <robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
> CC: Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org>
> Signed-off-by: Robin Murphy <robin.murphy-5wv7dgnIgG8@public.gmane.org>
> ---
> 
> v2: Fix the copy-paste binding thinko
> 
>  .../devicetree/bindings/arm/rockchip.yaml      |  6 ++++--
>  arch/arm64/boot/dts/rockchip/Makefile          |  1 +
>  .../boot/dts/rockchip/rk3399-nanopi-m4.dts     | 18 ++++++++++++++++++
>  3 files changed, 23 insertions(+), 2 deletions(-)
>  create mode 100644 arch/arm64/boot/dts/rockchip/rk3399-nanopi-m4.dts
> 

Reviewed-by: Rob Herring <robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>

WARNING: multiple messages have this Message-ID (diff)
From: Rob Herring <robh@kernel.org>
To: Robin Murphy <robin.murphy@arm.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
	linux-rockchip@lists.infradead.org, heiko@sntech.de,
	linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v2 1/4] arm64: dts: rockchip: Add DT for NanoPi M4
Date: Wed, 16 Jan 2019 15:12:58 -0600	[thread overview]
Message-ID: <20190116211258.GA29888@bogus> (raw)
In-Reply-To: <a96995cfa599792b24e740ce46d53bd68ef1d462.1547466003.git.robin.murphy@arm.com>

On Mon, 14 Jan 2019 12:05:31 +0000, Robin Murphy wrote:
> There are a number of subtle differences between the nanopi4 variants,
> and where they disagree, the common DTSI currently follows the details
> of NanoPi M4. In order to improve matters even more, let's add a
> separate DTS for the M4 to which we can start splitting things out
> appropriately. The third variant, NanoPi NEO4, is a lot closer to the M4
> than either is to the larger T4, so arguably could get away with just
> sharing the M4 DT for now (plus I have neither of the smaller boards to
> actually test with).
> 
> CC: Rob Herring <robh+dt@kernel.org>
> CC: Mark Rutland <mark.rutland@arm.com>
> Signed-off-by: Robin Murphy <robin.murphy@arm.com>
> ---
> 
> v2: Fix the copy-paste binding thinko
> 
>  .../devicetree/bindings/arm/rockchip.yaml      |  6 ++++--
>  arch/arm64/boot/dts/rockchip/Makefile          |  1 +
>  .../boot/dts/rockchip/rk3399-nanopi-m4.dts     | 18 ++++++++++++++++++
>  3 files changed, 23 insertions(+), 2 deletions(-)
>  create mode 100644 arch/arm64/boot/dts/rockchip/rk3399-nanopi-m4.dts
> 

Reviewed-by: Rob Herring <robh@kernel.org>

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  parent reply	other threads:[~2019-01-16 21:12 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-14 12:05 [PATCH v2 0/4] NanoPC-T4 (and a bit of NanoPi M4) support Robin Murphy
2019-01-14 12:05 ` Robin Murphy
2019-01-14 12:05 ` [PATCH v2 1/4] arm64: dts: rockchip: Add DT for NanoPi M4 Robin Murphy
2019-01-14 12:05   ` Robin Murphy
     [not found]   ` <a96995cfa599792b24e740ce46d53bd68ef1d462.1547466003.git.robin.murphy-5wv7dgnIgG8@public.gmane.org>
2019-01-16 21:12     ` Rob Herring [this message]
2019-01-16 21:12       ` Rob Herring
2019-01-14 12:05 ` [PATCH v2 2/4] arm64: dts: rockchip: Refine nanopi4 differences Robin Murphy
2019-01-14 12:05   ` Robin Murphy
2019-01-14 12:05 ` [PATCH v2 3/4] arm64: dts: rockchip: Add NanoPC-T4 IR receiver Robin Murphy
2019-01-14 12:05   ` Robin Murphy
2019-01-14 12:05 ` [PATCH v2 4/4] arm64: dts: rockchip: 'Fix' nanopi4 uSD card detect Robin Murphy
2019-01-14 12:05   ` Robin Murphy
     [not found] ` <cover.1547466003.git.robin.murphy-5wv7dgnIgG8@public.gmane.org>
2019-01-17 14:01   ` [PATCH v2 0/4] NanoPC-T4 (and a bit of NanoPi M4) support Heiko Stuebner
2019-01-17 14:01     ` Heiko Stuebner

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=20190116211258.GA29888@bogus \
    --to=robh-dgejt+ai2ygdnm+yrofe0a@public.gmane.org \
    --cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=heiko-4mtYJXux2i+zQB+pC5nmwQ@public.gmane.org \
    --cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
    --cc=linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
    --cc=mark.rutland-5wv7dgnIgG8@public.gmane.org \
    --cc=robin.murphy-5wv7dgnIgG8@public.gmane.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 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.