The IPSR field names in the comments have been fat-fingered in a couple
places -- fix those silly typos...
Fixes: 508845196238 ("pinctrl: sh-pfc: r8a7791 PFC support")
Signed-off-by: Sergei Shtylyov
---
This patch is against the 'fixes' branch of Linus
On Sun, Mar 26, 2017 at 11:22:57AM +0200, Geert Uytterhoeven wrote:
> Hi Russell, Sjoerd,
>
> On Fri, Mar 24, 2017 at 5:42 PM, Russell King - ARM Linux
> wrote:
> > On Fri, Mar 24, 2017 at 05:26:32PM +0100, Sjoerd Simons wrote:
> >> When testing on a Renesas board with the
Hi Sergei,
On Thu, Mar 30, 2017 at 6:53 PM, Sergei Shtylyov
wrote:
> The R8A7791 PFC driver was apparently based on the preliminary revisions
> of the user's manual, which called all the I2C signals {SCL|SDA} and
> MOD_SEL register fields SEL_IIC without
On Thu, Mar 30, 2017 at 10:20 PM, Sergei Shtylyov
wrote:
> PINMUX_IPSR_MSEL() macro invocation for the TX2 signal has apparently wrong
> 1st argument -- most probably a result of cut programming...
>
> Fixes: 508845196238 ("pinctrl: sh-pfc: r8a7791 PFC
Hi Rob,
thanks for the ack
On Thu, Mar 30, 2017 at 05:39:03PM -0500, Rob Herring wrote:
> On Fri, Mar 24, 2017 at 04:22:09PM +0100, Jacopo Mondi wrote:
> > Add device tree bindings documentation for Renesas RZ/A1 gpio and pin
> > controller.
> >
> > Signed-off-by: Jacopo Mondi
Hi Linus,
The following changes since commit 3091ae775fae17084013021d01513bc1ad274e6a:
pinctrl: sh-pfc: Update info pointer after SoC-specific init (2017-03-21
11:21:55 +0100)
are available in the git repository at:
Hi Mike, Stephen,
The following changes since commit cecbe87d73006cb321dec79b349e3fefd1a80962:
clk: renesas: rcar-gen3: Add workaround for PLL0/2/4 errata on H3 ES1.0
(2017-03-21 11:12:23 +0100)
are available in the git repository at:
Hi Laurent,
On Fri, Mar 31, 2017 at 11:19 AM, Laurent Pinchart
wrote:
> On Monday 27 Mar 2017 13:05:48 Geert Uytterhoeven wrote:
>> On Mon, Mar 27, 2017 at 11:56 AM, Laurent Pinchart wrote:
>> > The property is used by the driver but is missing from the DT
Hi Mike, Stephen,
On Fri, Mar 24, 2017 at 10:39 AM, Geert Uytterhoeven
wrote:
> The following changes since commit c1ae3cfa0e89fa1a7ecc4c99031f5e9ae99d9201:
>
> Linux 4.11-rc1 (2017-03-05 12:59:56 -0800)
>
> are available in the git repository at:
>
>
Hi Geert,
On Monday 27 Mar 2017 13:05:48 Geert Uytterhoeven wrote:
> On Mon, Mar 27, 2017 at 11:56 AM, Laurent Pinchart wrote:
> > The property is used by the driver but is missing from the DT bindings.
> > Document it.
> >
> > Reported-by: Geert Uytterhoeven
> >
Power area A2VC0 was removed in revision ES2.0, cfr. R-Car Gen3 Hardware
User's Manual rev. 0.53E.
Hence remove it from the power area table when not running on ES1.x.
This is in line with the goal to:
1. Support both the ES1.x and ES2.0 SoC revisions in a single binary
for now,
2. Make
The same SoC may have different power areas, depending on SoC revision.
One option is to use different sets of power area tables for each SoC
revision. However, if the differences are small, it is much more
space-efficient to have a single set of tables, and fix those up at
runtime instead.
Hi Simon, Magnus,
This patch series adds power domain support for R-Car H3 ES2.0, which
differs from ES1.x in some areas.
The goal is twofold:
1. Support both the ES1.x and ES2.0 SoC revisions in a single binary
for now,
2. Make it clear which code supports ES1.x, so it can
The r8a7795 SYSC driver manages PM Domains, and thus is initialized from
an early_initcall(). However, this means the driver cannot check the
SoC revision, as the SoC device hasn't been registered yet.
Change renesas_soc_init() from a core_initcall() to an early_initcall()
to fix this
Hi Greg,
Hi Arnd, Kevin, Olof,
Hi Magnus, Simon,
The following changes since commit c470abd4fde40ea6a0846a2beab642a578c0b8cd:
Linux 4.10 (2017-02-19 14:34:00 -0800)
are available in the git repository at:
On Wed, Mar 29, 2017 at 09:48:48PM +0200, Arnd Bergmann wrote:
> On Wed, Mar 29, 2017 at 9:38 PM, Geert Uytterhoeven
> wrote:
> > Hi Arnd, Greg, Kevin, Magnus, Olof, Simon,
> >
> > This patch series contains two improvements for the SoC bus and
> >
On Thu, 30 Mar 2017 23:53:34 +0200,
Mark Brown wrote:
>
> On Wed, Mar 29, 2017 at 02:45:37AM +, Kuninori Morimoto wrote:
>
> > To avoid Sound Card crash in (2) case, what we can do now is, add dirty
> > flag on Sound Card, and avoid to open Sound Card.
> > This patch solved this issue.
>
>
17 matches
Mail list logo