From: horms@verge.net.au (Simon Horman)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Second Round of Renesas ARM Based SoC DT Updates for v4.10
Date: Mon, 21 Nov 2016 11:53:18 +0100 [thread overview]
Message-ID: <20161121105315.GA19845@verge.net.au> (raw)
In-Reply-To: <20161119014929.GE2543@localhost>
On Fri, Nov 18, 2016 at 05:49:29PM -0800, Olof Johansson wrote:
> On Thu, Nov 17, 2016 at 03:11:45PM +0100, Simon Horman wrote:
> > Hi Olof, Hi Kevin, Hi Arnd,
> >
> > Please consider these second round of Renesas ARM based SoC DT updates for v4.10.
> >
> > This pull request is based on a merge of:
> >
> > * The previous round of such requests, tagged as renesas-dt-for-v4.10,
> > which I have already sent a pull-request for.
> > * The rzg-clock-defs tag of Geert Uytterhoeven's renesas-driver's tree.
> > This is to provide dependencies for adding the r8a7743 and r8a7745 SoCs.
> > * The "Second Round of Renesas ARM Based SoC Drivers Updates for v4.10",
> > tagged as renesas-drivers2-for-v4.10, which I have also sent a pull
> > request for. This is included to provide dependencies for adding device
> > nodes for PRR, and adding the r8a7743 and r8a7745 SoCs.
>
> Again, nack. And again, I don't understand why you create dependencies that
> aren't needed. Please fix.
Hi Olof,
I agree that calling out PRR above was incorrect. Please disregard that.
However, there are dependencies for adding r8a7743 and r8a7745 SoCs
in the form of header files:
* The rzg-clock-defs tag provides dt-bindings/clock/r8a774[35]-cpg-mssr.h
* The renesas-drivers2-for-v4.10 tag provides
dt-bindings/power/r8a774[35]-sysc.h
The drivers branches are usually pretty light-weight. But this time it is a
bit heavy and you rightly raised some questions about it. After some
discussion with Geert we'd like to suggest that for future releases
we provide a "driver-defs" branch which both driver code and DT can
depend on. Thus avoiding pulling (non essential) driver changes into the DT
branch.
Unfortunately its a bit late to do that for v4.10 as the r8a7743 sysc
driver and its defines were already accepted accepted together
(renesas-drivers-for-v4.10 tag). So for this release we would be grateful
if you could re-consider the renesas-drivers2-for-v4.10 tag given the
feedback which Geert has provided. And in turn re-consider this pull
request.
next prev parent reply other threads:[~2016-11-21 10:53 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-17 14:11 [GIT PULL] Second Round of Renesas ARM Based SoC DT Updates for v4.10 Simon Horman
2016-11-17 14:11 ` [PATCH 01/31] ARM: dts: alt: Fix PFC names for DU Simon Horman
2016-11-17 14:11 ` [PATCH 02/31] ARM: dts: r8a7794: Correct hsusb parent clock Simon Horman
2016-11-17 14:11 ` [PATCH 03/31] ARM: dts: r8a7794: Use SYSC "always-on" PM Domain for sound Simon Horman
2016-11-17 14:11 ` [PATCH 04/31] ARM: dts: lager: rename and reindex i2cexio Simon Horman
2016-11-17 14:11 ` [PATCH 05/31] ARM: dts: lager: use demuxer for IIC1/I2C1 Simon Horman
2016-11-17 14:11 ` [PATCH 06/31] ARM: dts: koelsch: use demuxer for I2C1 Simon Horman
2016-11-17 14:11 ` [PATCH 07/31] ARM: dts: alt: use demuxer for I2C4 Simon Horman
2016-11-17 14:11 ` [PATCH 08/31] ARM: dts: lager: Enable UHS-I SDR-104 Simon Horman
2016-11-17 14:11 ` [PATCH 09/31] ARM: dts: koelsch: " Simon Horman
2016-11-17 14:11 ` [PATCH 10/31] ARM: dts: alt: " Simon Horman
2016-11-17 14:11 ` [PATCH 11/31] ARM: dts: r8a7743: initial SoC device tree Simon Horman
2016-11-17 14:11 ` [PATCH 12/31] ARM: dts: r8a7743: add SYS-DMAC support Simon Horman
2016-11-17 14:11 ` [PATCH 13/31] ARM: dts: r8a7743: add [H]SCIF{A|B} support Simon Horman
2016-11-17 14:11 ` [PATCH 14/31] ARM: dts: r8a7743: add Ether support Simon Horman
2016-11-17 14:11 ` [PATCH 15/31] ARM: dts: r8a7743: add IRQC support Simon Horman
2016-11-17 14:11 ` [PATCH 16/31] ARM: dts: sk-rzg1m: initial device tree Simon Horman
2016-11-17 14:11 ` [PATCH 17/31] ARM: dts: sk-rzg1m: add Ether support Simon Horman
2016-11-17 14:11 ` [PATCH 18/31] ARM: dts: r8a7745: initial SoC device tree Simon Horman
2016-11-17 14:11 ` [PATCH 19/31] ARM: dts: r8a7745: add SYS-DMAC support Simon Horman
2016-11-17 14:11 ` [PATCH 20/31] ARM: dts: r8a7745: add [H]SCIF{|A|B} support Simon Horman
2016-11-17 14:11 ` [PATCH 21/31] ARM: dts: r8a7745: add Ether support Simon Horman
2016-11-17 14:11 ` [PATCH 22/31] ARM: dts: r8a7745: add IRQC support Simon Horman
2016-11-17 14:11 ` [PATCH 23/31] ARM: dts: sk-rzg1e: initial device tree Simon Horman
2016-11-17 14:11 ` [PATCH 24/31] ARM: dts: sk-rzg1e: add Ether support Simon Horman
2016-11-17 14:11 ` [PATCH 25/31] ARM: dts: r8a73a4: Add device node for PRR Simon Horman
2016-11-17 14:11 ` [PATCH 26/31] ARM: dts: r8a7779: " Simon Horman
2016-11-17 14:11 ` [PATCH 27/31] ARM: dts: r8a7790: " Simon Horman
2016-11-17 14:11 ` [PATCH 28/31] ARM: dts: r8a7791: " Simon Horman
2016-11-17 14:11 ` [PATCH 29/31] ARM: dts: r8a7792: " Simon Horman
2016-11-17 14:11 ` [PATCH 30/31] ARM: dts: r8a7793: " Simon Horman
2016-11-17 14:11 ` [PATCH 31/31] ARM: dts: r8a7794: " Simon Horman
2016-11-19 1:49 ` [GIT PULL] Second Round of Renesas ARM Based SoC DT Updates for v4.10 Olof Johansson
2016-11-21 10:53 ` Simon Horman [this message]
2016-11-23 9:57 ` Simon Horman
2016-11-23 14:16 ` 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=20161121105315.GA19845@verge.net.au \
--to=horms@verge.net.au \
--cc=linux-arm-kernel@lists.infradead.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).