From: Simon Horman <horms-/R6kz+dDXgpPR4JQBCEnsQ@public.gmane.org>
To: Sergei Shtylyov
<sergei.shtylyov-M4DtvfQ/ZS1MRgGoP+s0PdBPR1lH4CV8@public.gmane.org>
Cc: linux-renesas-soc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
mark.rutland-5wv7dgnIgG8@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
magnus.damm-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
linux-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: Re: [PATCH v3 0/11] Add R8A7743/SK-RZG1M board support
Date: Wed, 12 Oct 2016 10:09:05 +0200 [thread overview]
Message-ID: <20161012080905.GD31183@verge.net.au> (raw)
In-Reply-To: <5be99d76-a082-129b-1aa6-b6f7402ae79b-M4DtvfQ/ZS1MRgGoP+s0PdBPR1lH4CV8@public.gmane.org>
On Fri, Oct 07, 2016 at 07:40:34PM +0300, Sergei Shtylyov wrote:
> On 10/06/2016 12:23 AM, Sergei Shtylyov wrote:
>
> > Here's the set of 11 patches against Simon Horman's 'renesas.git' repo's
> >'renesas-devel-20161003-v4.8' tag. I'm adding the device tree support for
> >the R8A7743-based SK-RZG1M board. The SoC is close to R8A7791 and the board
> >seems identical to the R8A7791/Porter board. The device tree patches depend on
> >the R8A7743 CPG/MSSR driver series just posted in order to compile and work.
>
> Forgot to mention that this version causes a regression with the sh_eth
> driver (well, actually with phylib): since IRQC now gets a deferred probing,
> PHY IRQ doesn't work anymore -- phylib falls back to polling.
Is there a resolution to that problem?
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2016-10-12 8:09 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-05 21:23 [PATCH v3 0/11] Add R8A7743/SK-RZG1M board support Sergei Shtylyov
2016-10-05 21:31 ` [PATCH v3 01/11] ARM: shmobile: r8a7743: add power domain index macros Sergei Shtylyov
2016-10-07 3:14 ` Simon Horman
2016-10-05 21:35 ` [PATCH v3 02/11] soc: renesas: rcar-sysc: add R8A7743 support Sergei Shtylyov
[not found] ` <1691511.DcOcZO89eZ-gHKXc3Y1Z8zGSmamagVegGFoWSdPRAKMAL8bYrjMMd8@public.gmane.org>
2016-10-07 3:15 ` Simon Horman
2016-10-05 21:37 ` [PATCH v3 03/11] ARM: shmobile: r8a7743: basic SoC support Sergei Shtylyov
[not found] ` <15557770.lH5aPepOeZ-gHKXc3Y1Z8zGSmamagVegGFoWSdPRAKMAL8bYrjMMd8@public.gmane.org>
2016-10-07 3:15 ` Simon Horman
[not found] ` <20161007031537.GK13721-/R6kz+dDXgpPR4JQBCEnsQ@public.gmane.org>
2016-10-07 8:33 ` Laurent Pinchart
2016-10-07 10:02 ` Sergei Shtylyov
2016-10-07 10:11 ` Geert Uytterhoeven
2016-10-08 2:31 ` Simon Horman
2016-10-08 21:14 ` Laurent Pinchart
[not found] ` <2056698.ncAHq8vRQ3-gHKXc3Y1Z8zGSmamagVegGFoWSdPRAKMAL8bYrjMMd8@public.gmane.org>
2016-10-05 21:38 ` [PATCH v3 04/11] ARM: dts: r8a7743: initial SoC device tree Sergei Shtylyov
[not found] ` <2883940.Oo8sg10L7m-gHKXc3Y1Z8zGSmamagVegGFoWSdPRAKMAL8bYrjMMd8@public.gmane.org>
2016-10-07 3:09 ` Simon Horman
[not found] ` <20161007030932.GH13721-/R6kz+dDXgpPR4JQBCEnsQ@public.gmane.org>
2016-10-07 7:50 ` Geert Uytterhoeven
2016-10-07 9:57 ` Sergei Shtylyov
2016-10-08 2:28 ` Simon Horman
2016-10-19 8:16 ` Geert Uytterhoeven
2016-10-05 21:39 ` [PATCH v3 05/11] ARM: dts: r8a7743: add SYS-DMAC support Sergei Shtylyov
2016-10-05 21:41 ` [PATCH v3 06/11] ARM: dts: r8a7743: add [H]SCIF{A|B} support Sergei Shtylyov
2016-10-19 8:34 ` Geert Uytterhoeven
2016-10-05 21:45 ` [PATCH v3 09/11] DT: arm: shmobile: document SK-RZG1M board Sergei Shtylyov
[not found] ` <1619405.o5fA0fLKdG-gHKXc3Y1Z8zGSmamagVegGFoWSdPRAKMAL8bYrjMMd8@public.gmane.org>
2016-10-07 3:21 ` Simon Horman
2016-10-05 21:42 ` [PATCH v3 07/11] ARM: dts: r8a7743: add Ether support Sergei Shtylyov
2016-10-17 14:48 ` Geert Uytterhoeven
2016-10-05 21:43 ` [PATCH v3 08/11] ARM: dts: r8a7743: add IRQC support Sergei Shtylyov
[not found] ` <1550113.UvRQMtlFiI-gHKXc3Y1Z8zGSmamagVegGFoWSdPRAKMAL8bYrjMMd8@public.gmane.org>
2016-10-17 14:46 ` Geert Uytterhoeven
2016-10-05 21:47 ` [PATCH v3 10/11] ARM: dts: sk-rzg1m: initial device tree Sergei Shtylyov
2016-10-05 21:48 ` [PATCH v3 11/11] ARM: dts: sk-rzg1m: add Ether support Sergei Shtylyov
2016-10-19 8:17 ` Geert Uytterhoeven
2016-10-07 16:40 ` [PATCH v3 0/11] Add R8A7743/SK-RZG1M board support Sergei Shtylyov
[not found] ` <5be99d76-a082-129b-1aa6-b6f7402ae79b-M4DtvfQ/ZS1MRgGoP+s0PdBPR1lH4CV8@public.gmane.org>
2016-10-12 8:09 ` Simon Horman [this message]
[not found] ` <20161012080905.GD31183-/R6kz+dDXgpPR4JQBCEnsQ@public.gmane.org>
2016-10-12 8:29 ` Sergei Shtylyov
2016-10-20 9:24 ` Simon Horman
2016-10-20 9:56 ` Geert Uytterhoeven
-- strict thread matches above, loose matches on Subject: below --
2016-10-28 22:03 Sergei Shtylyov
2016-10-28 22:04 ` Sergei Shtylyov
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=20161012080905.GD31183@verge.net.au \
--to=horms-/r6kz+ddxgppr4jqbcensq@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org \
--cc=linux-renesas-soc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=magnus.damm-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=mark.rutland-5wv7dgnIgG8@public.gmane.org \
--cc=robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=sergei.shtylyov-M4DtvfQ/ZS1MRgGoP+s0PdBPR1lH4CV8@public.gmane.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).