From: Simon Horman <horms@verge.net.au>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Geert Uytterhoeven <geert+renesas@glider.be>,
Magnus Damm <magnus.damm@gmail.com>,
linux-renesas-soc@vger.kernel.org,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [PATCH v4 0/7] ARM: dts: r-car: Add BRG support for (H)SCIF
Date: Tue, 2 Feb 2016 13:57:50 +0100 [thread overview]
Message-ID: <20160202125749.GI15554@verge.net.au> (raw)
In-Reply-To: <CAMuHMdWjEn6RSLPOYq=zhY_gk6Lx9xTD1x1G+1igoDr=3h1R5w@mail.gmail.com>
On Tue, Feb 02, 2016 at 11:38:05AM +0100, Geert Uytterhoeven wrote:
> Hi Simon,
>
> On Tue, Feb 2, 2016 at 11:20 AM, Simon Horman <horms@verge.net.au> wrote:
> > On Fri, Jan 29, 2016 at 11:04:36AM +0100, Geert Uytterhoeven wrote:
> >> This patch series adds support for the Baud Rate Generator for External
> >> Clock (BRG), as found on SCIF and HSCIF, to the DTS files for all R-Car
> >> Gen1, Gen2, and Gen3 SoCs. This increases the range and accuracy of
> >> supported baud rates on (H)SCIF.
> >>
> >> Support for the extra clocks in the DT bindings and in the driver has
> >> been accepted in v4.5-rc1.
> >>
> >> Changes compared to v3:
> >> - Change one-line summary prefix to match current arm-soc practices,
> >> - Rebased,
> >>
> >> Changes compared to v2:
> >> - Rename "int_clk" to "brg_int",
> >> - Add support for R-Car M1A (r8a7778) and R-Car H1 (r8a7779),
> >> - Add support for R-Car H2 (r8a7790), R-Car M2-N (r8a7793), and R-Car
> >> E2 (r8a7794),
> >> - Correct internal clock source ZS_CLK to S3D1 in patch description
> >> for r8a7795,
> >>
> >> This has been tested on r8a7778/bockw, r8a7779/marzen, r8a7791/koelsch,
> >> r8a7794/alt, and r8a7795/salvator-x.
> >>
> >> Dependencies:
> >> - renesas-devel-20160129-v4.5-rc1,
> >> - series "[PATCH v4 0/7] ARM: dts: R-Car: Add SCIF fallback
> >> compatibility strings",
> >> - series "[PATCH v4 00/11] ARM: dts: shmobile: Rename the serial port
> >> clock to fck",
> >>
> >> Thanks for applying!
> >
> > Is it safe to apply this in the light of the dependency on
> > renesas-devel-20160129-v4.5-rc1?
>
> The dependency here (also for the other series) just means I rebased the
> series on top of renesas-devel-20160129-v4.5-rc1 + the mentioned
> series.
Thanks, I have queued these up.
> Do you have any DT changes there that are not queued for v4.6?
>
> 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
prev parent reply other threads:[~2016-02-02 12:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-29 10:04 [PATCH v4 0/7] ARM: dts: r-car: Add BRG support for (H)SCIF Geert Uytterhoeven
2016-01-29 10:04 ` [PATCH v4 1/7] ARM: dts: r8a7778: Add BRG support for SCIF Geert Uytterhoeven
2016-01-29 10:04 ` [PATCH v4 2/7] ARM: dts: r8a7779: " Geert Uytterhoeven
2016-01-29 10:04 ` [PATCH v4 3/7] ARM: dts: r8a7790: Add BRG support for (H)SCIF Geert Uytterhoeven
[not found] ` <1454061883-4043-1-git-send-email-geert+renesas-gXvu3+zWzMSzQB+pC5nmwQ@public.gmane.org>
2016-01-29 10:04 ` [PATCH v4 4/7] ARM: dts: r8a7791: " Geert Uytterhoeven
2016-01-29 10:04 ` [PATCH v4 7/7] arm64: dts: r8a7795: " Geert Uytterhoeven
2016-01-29 10:04 ` [PATCH v4 5/7] ARM: dts: r8a7793: Add BRG support for SCIF Geert Uytterhoeven
2016-01-29 10:04 ` [PATCH v4 6/7] ARM: dts: r8a7794: Add BRG support for (H)SCIF Geert Uytterhoeven
2016-02-02 10:20 ` [PATCH v4 0/7] ARM: dts: r-car: " Simon Horman
[not found] ` <20160202102031.GD15554-/R6kz+dDXgpPR4JQBCEnsQ@public.gmane.org>
2016-02-02 10:38 ` Geert Uytterhoeven
2016-02-02 12:52 ` Simon Horman
2016-02-02 12:57 ` Simon Horman [this message]
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=20160202125749.GI15554@verge.net.au \
--to=horms@verge.net.au \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=geert@linux-m68k.org \
--cc=linux-arm-kernel@lists.infradead.org \
--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).