From: Simon Horman <horms@verge.net.au>
To: Jacopo Mondi <jacopo+renesas@jmondi.org>
Cc: magnus.damm@gmail.com, robh+dt@kernel.org, mark.rutland@arm.com,
linux@armlinux.org.uk, linux-renesas-soc@vger.kernel.org,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/4] GR-Peach DTS update
Date: Thu, 24 Aug 2017 06:53:50 -0400 [thread overview]
Message-ID: <20170824105350.GD27788@verge.net.au> (raw)
In-Reply-To: <1503564523-31899-1-git-send-email-jacopo+renesas@jmondi.org>
On Thu, Aug 24, 2017 at 10:48:39AM +0200, Jacopo Mondi wrote:
> Hello Simon,
> now that RZ/A1 pin controller is merged, it's time to enable some peripheral
> devices on GR-Peach has it has been done for Genmai and RSK boards.
>
> The series is based on Simon's "renesas-dt2-for-v4.14" tag release, so it should
> be ideally applied after v4.14-rc1 is out, as it needs pin controller nodes to
> be defined in r7s72100.dtsi.
>
> Patch 2/4 enables EHTER interface, even if I've not been able to exchange any
> traffic on that. I can set the ip address and probe the device and double
> checked the pin configuration process against u-boot sources (where the
> interface is working instead). Sending the patch anyway and let you decide what
> to do with that.
>
> Thanks
> j
>
> Jacopo Mondi (4):
> arm: dts: gr-peach: Remove empty line
> arm: dts: gr-peach: Add SCIF2 pin group
> arm: dts: gr-peach: Add ETHER pin group
> arm: dts: gr-peach: Add user led device nodes
Thanks I have applied the 1st, 2nd and 4th (non-ETHER) patches above for v4.15.
I am leaving the 3rd (ETHER) patch pending resolution of the review
provided by Geert.
next prev parent reply other threads:[~2017-08-24 10:53 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-24 8:48 [PATCH 0/4] GR-Peach DTS update Jacopo Mondi
2017-08-24 8:48 ` [PATCH 1/4] arm: dts: gr-peach: Remove empty line Jacopo Mondi
2017-08-24 9:22 ` Geert Uytterhoeven
2017-08-24 8:48 ` [PATCH 2/4] arm: dts: gr-peach: Add SCIF2 pin group Jacopo Mondi
2017-08-24 9:27 ` Geert Uytterhoeven
[not found] ` <1503564523-31899-1-git-send-email-jacopo+renesas-AW8dsiIh9cEdnm+yROfE0A@public.gmane.org>
2017-08-24 8:48 ` [PATCH 3/4] arm: dts: gr-peach: Add ETHER " Jacopo Mondi
[not found] ` <1503564523-31899-4-git-send-email-jacopo+renesas-AW8dsiIh9cEdnm+yROfE0A@public.gmane.org>
2017-08-24 9:48 ` Geert Uytterhoeven
2017-08-24 11:46 ` jmondi
2017-08-24 11:56 ` Geert Uytterhoeven
2017-08-24 12:53 ` jmondi
2017-08-30 7:25 ` Simon Horman
2017-08-30 7:35 ` jmondi
2017-08-30 9:28 ` Simon Horman
2017-08-24 8:48 ` [PATCH 4/4] arm: dts: gr-peach: Add user led device nodes Jacopo Mondi
[not found] ` <1503564523-31899-5-git-send-email-jacopo+renesas-AW8dsiIh9cEdnm+yROfE0A@public.gmane.org>
2017-08-24 9:31 ` Geert Uytterhoeven
2017-08-24 10:53 ` Simon Horman [this message]
[not found] ` <20170824105350.GD27788-/R6kz+dDXgpPR4JQBCEnsQ@public.gmane.org>
2017-08-24 10:57 ` [PATCH 0/4] GR-Peach DTS update 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=20170824105350.GD27788@verge.net.au \
--to=horms@verge.net.au \
--cc=devicetree@vger.kernel.org \
--cc=jacopo+renesas@jmondi.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=magnus.damm@gmail.com \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.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).