From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Simon Horman <horms@verge.net.au>
Cc: Geert Uytterhoeven <geert+renesas@glider.be>,
Magnus Damm <magnus.damm@gmail.com>,
Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Vladimir Barinov <vladimir.barinov@cogentembedded.com>
Subject: Re: [PATCH/RFC 0/5] arm64: dts: renesas: Break out common board support
Date: Thu, 27 Apr 2017 15:32:49 +0200 [thread overview]
Message-ID: <CAMuHMdV1SQoeEACaNLZbByRLbosMj5oxEysNDVevYgxqStDaug@mail.gmail.com> (raw)
In-Reply-To: <CAMuHMdXbe=rkeS+-teg7nqbjULWY0_5pBO1XEzCGdYA4gB57oA@mail.gmail.com>
Hi Simon,
On Wed, Apr 26, 2017 at 10:11 AM, Geert Uytterhoeven
<geert@linux-m68k.org> wrote:
> CC Vladimir (which I forgot to CC initially, sorry for that)
>
> On Wed, Apr 26, 2017 at 10:06 AM, Simon Horman <horms@verge.net.au> wrote:
>> On Fri, Apr 21, 2017 at 02:55:16PM +0200, Geert Uytterhoeven wrote:
>>> The Renesas Salvator-X and ULCB development board can be equipped with
>>> either an R-Car H3 or M3-W SiP, which are pin-compatible. All boards
>>> use separate DTBs, but currently there's no sharing of board-specific
>>> devices in DTS.
>>>
>>> This series reduces duplication by extracting common board support into
>>> their own .dtsi files. As the level of support varies across boards and
>>> SoCs, this requires the addition of a few external clocks and
>>> placeholder devices on R-Car M3-W, so the common board support DTS can
>>> refer to them.
>>>
>>> - Patches 1 and 2 add the external audio and PCIe bus clocks on R-Car
>>> M3-W, which are present in r8a7795.dtsi, and used in
>>> r8a7795-salvator-x.dts,
>>> - RFC patch 3 adds placeholders for devices that are not yet supported
>>> and/or tested on R-Car M3-W, but used on R-Car H3,
>>> - RFC patch 4 extracts common Salvator-X board support,
>>> - RFC patch 5 extracts common ULCB board support.
>>>
>>> For R-Car H3 based boards, there are no functional changes.
>>> For R-Car M3-W based boards, some new devices are now described in DT.
>>>
>>> Dependencies:
>>> - renesas-devel-20170420-v4.11-rc7,
>>> - Patches 1 and 2 can be applied as-is,
>>> - Patches 4 and 5 depend on "[PATCH 0/8] arm64: dts: renesas: Break
>>> out R-Car H3 and M3-W SiP"
>>> (http://www.spinics.net/lists/devicetree/msg173820.html).
>>>
>>> DTB changes have been inspected using scripts/dtc/dtx_diff.
>>> This has been tested on Salvator-X (both H3 and M3-W).
>>> This has not been tested on H3ULCB and M3ULCB due to lack of hardware.
>>>
>>> Thanks for your comments!
>>
>> Thanks for tackling this important problem. I have looked over the changes
>> and they seem nice to me. I would, however, be more comfortable applying
>> them if they were rested on the ULCB boards.
>
> tested?
>
> I've pushed a branch for testing to topic/rcar3-dtsi-sharing in
> git://git.kernel.org/pub/scm/linux/kernel/git/geert/renesas-drivers.git.
I managed to test it on the new H3ULCB and M3ULCB baords in Magnus' farm.
No issues detected.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2017-04-27 13:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-21 12:55 [PATCH/RFC 0/5] arm64: dts: renesas: Break out common board support Geert Uytterhoeven
[not found] ` <1492779321-23939-1-git-send-email-geert+renesas-gXvu3+zWzMSzQB+pC5nmwQ@public.gmane.org>
2017-04-21 12:55 ` [PATCH 1/5] arm64: renesas: r8a7796: Add external audio clocks Geert Uytterhoeven
2017-04-23 23:56 ` Kuninori Morimoto
2017-04-21 12:55 ` [PATCH 2/5] arm64: renesas: r8a7796: Add external PCIe bus clock Geert Uytterhoeven
2017-04-21 12:55 ` [PATCH/RFC 3/5] arm64: dts: r8a7796: Add placeholders for various devices Geert Uytterhoeven
2017-04-21 12:55 ` [PATCH/RFC 4/5] arm64: dts: renesas: Extract common Salvator-X board support Geert Uytterhoeven
2017-04-21 12:55 ` [PATCH/RFC 5/5] arm64: dts: renesas: Extract common ULCB " Geert Uytterhoeven
2017-04-24 7:25 ` [PATCH/RFC 0/5] arm64: dts: renesas: Break out common " Geert Uytterhoeven
2017-04-26 8:06 ` Simon Horman
2017-04-26 8:11 ` Geert Uytterhoeven
2017-04-26 8:56 ` Simon Horman
2017-04-27 13:32 ` Geert Uytterhoeven [this message]
[not found] ` <CAMuHMdV1SQoeEACaNLZbByRLbosMj5oxEysNDVevYgxqStDaug-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-04-28 7:04 ` Simon Horman
2017-04-28 7:11 ` Geert Uytterhoeven
2017-04-28 7:32 ` Simon Horman
[not found] ` <20170428073256.GG10196-/R6kz+dDXgpPR4JQBCEnsQ@public.gmane.org>
2017-04-28 12:28 ` Geert Uytterhoeven
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=CAMuHMdV1SQoeEACaNLZbByRLbosMj5oxEysNDVevYgxqStDaug@mail.gmail.com \
--to=geert@linux-m68k.org \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=horms@verge.net.au \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=vladimir.barinov@cogentembedded.com \
--cc=yoshihiro.shimoda.uh@renesas.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).