linux-renesas-soc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Fabrizio Castro <fabrizio.castro@bp.renesas.com>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: Biju Das <biju.das@bp.renesas.com>,
	Chris Paterson <Chris.Paterson2@renesas.com>,
	"linux-renesas-soc@vger.kernel.org" 
	<linux-renesas-soc@vger.kernel.org>,
	Simon Horman <horms@verge.net.au>,
	Magnus Damm <magnus.damm@gmail.com>
Subject: RE: [PATCH LOCAL 1/2] arm64: dts: renesas: r8a774a1: Add dummy board DTS
Date: Wed, 9 Jan 2019 11:37:28 +0000	[thread overview]
Message-ID: <TY1PR01MB17704BF382420D4D53B613B3C08B0@TY1PR01MB1770.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <20190104091316.12716-2-geert+renesas@glider.be>



> From: Geert Uytterhoeven <geert+renesas@glider.be>
> Sent: 04 January 2019 09:13
> Subject: [PATCH LOCAL 1/2] arm64: dts: renesas: r8a774a1: Add dummy board DTS
>
> Improve build coverage until a real board DTS surfaces.
>
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>

Reviewed-by: Fabrizio Castro <fabrizio.castro@bp.renesas.com>

> ---
>  arch/arm64/boot/dts/renesas/Makefile           | 3 +++
>  arch/arm64/boot/dts/renesas/r8a774a1-dummy.dts | 2 ++
>  2 files changed, 5 insertions(+)
>  create mode 100644 arch/arm64/boot/dts/renesas/r8a774a1-dummy.dts
>
> diff --git a/arch/arm64/boot/dts/renesas/Makefile b/arch/arm64/boot/dts/renesas/Makefile
> index a8ce6594342d993d..b4a006313cb66048 100644
> --- a/arch/arm64/boot/dts/renesas/Makefile
> +++ b/arch/arm64/boot/dts/renesas/Makefile
> @@ -14,3 +14,6 @@ dtb-$(CONFIG_ARCH_R8A77970) += r8a77970-eagle.dtb r8a77970-v3msk.dtb
>  dtb-$(CONFIG_ARCH_R8A77980) += r8a77980-condor.dtb r8a77980-v3hsk.dtb
>  dtb-$(CONFIG_ARCH_R8A77990) += r8a77990-ebisu.dtb
>  dtb-$(CONFIG_ARCH_R8A77995) += r8a77995-draak.dtb
> +
> +# SoCs lacking upstream board support
> +dtb-$(CONFIG_ARCH_R8A774A1) += r8a774a1-dummy.dtb
> diff --git a/arch/arm64/boot/dts/renesas/r8a774a1-dummy.dts b/arch/arm64/boot/dts/renesas/r8a774a1-dummy.dts
> new file mode 100644
> index 0000000000000000..dc4418ab8096fc4c
> --- /dev/null
> +++ b/arch/arm64/boot/dts/renesas/r8a774a1-dummy.dts
> @@ -0,0 +1,2 @@
> +/dts-v1/;
> +#include "r8a774a1.dtsi"
> --
> 2.17.1




Renesas Electronics Europe Ltd, Dukes Meadow, Millboard Road, Bourne End, Buckinghamshire, SL8 5FH, UK. Registered in England & Wales under Registered No. 04586709.

  reply	other threads:[~2019-01-09 11:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-04  9:13 [PATCH LOCAL 0/2] arm64: dts: renesas: Add dummy board files Geert Uytterhoeven
2019-01-04  9:13 ` [PATCH LOCAL 1/2] arm64: dts: renesas: r8a774a1: Add dummy board DTS Geert Uytterhoeven
2019-01-09 11:37   ` Fabrizio Castro [this message]
2019-01-04  9:13 ` [PATCH LOCAL 2/2] arm64: dts: renesas: r8a774c0: " Geert Uytterhoeven
2019-01-09 11:37   ` Fabrizio Castro
2019-01-04  9:47 ` [PATCH LOCAL 0/2] arm64: dts: renesas: Add dummy board files Simon Horman
2019-01-23 11:41   ` Simon Horman
2019-01-23 12:08     ` Geert Uytterhoeven
2019-01-24  9:59       ` Simon Horman

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=TY1PR01MB17704BF382420D4D53B613B3C08B0@TY1PR01MB1770.jpnprd01.prod.outlook.com \
    --to=fabrizio.castro@bp.renesas.com \
    --cc=Chris.Paterson2@renesas.com \
    --cc=biju.das@bp.renesas.com \
    --cc=geert+renesas@glider.be \
    --cc=horms@verge.net.au \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=magnus.damm@gmail.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 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).