From: Geert Uytterhoeven
If CONFIG_DEBUG_RODATA=y, the kernel crashes during system suspend:
Freezing user space processes ... (elapsed 0.004 seconds) done.
Freezing remaining freezable tasks ... (elapsed 0.002 seconds)
done.
PM: suspend of devices
From: Geert Uytterhoeven
CPU boot configuration writes to shmobile_boot_arg, which is located in
the .text section, and thus should not be written to.
As of commit 1d33a354bbb618ba ("ARM: shmobile: Per-CPU SMP boot / sleep
code for SCU SoCs"), and ignoring accidental
From: Geert Uytterhoeven
Commit 0ca2894b5a900709 ("ARM: shmobile: Use shared SCU SMP boot code on
r8a7779") obsoleted the r8a7779-specific SCU boot code, but forgot to
remove the setup of shmobile_boot_fn and shmobile_boot_arg, which is
overwritten by
Hi Olof, Hi Kevin, Hi Arnd,
Please consider these Renesas ARM based SoC fixes for v4.5.
This pull request is comprised of patches from Geert Uytterhoeven to avoid
writing to .text.
* "ARM: shmobile: Move shmobile_scu_base from .text to .bss"
Resolves a problem for XIP kernels as writing to
From: Geert Uytterhoeven
shmobile_scu_base is being written to, so it doesn't belong in the .text
section. Fix this by moving it from asm .text to C .bss, as it's no
longer used from asm code since commit 4f6da36f7edd5790 ("ARM: shmobile:
Remove old SCU boot code").
Make use of ARCH_RENESAS in place of ARCH_SHMOBILE.
This is part of an ongoing process to migrate from ARCH_SHMOBILE to
ARCH_RENESAS the motivation for which being that RENESAS seems to be a more
appropriate name than SHMOBILE for the majority of Renesas ARM based SoCs.
Signed-off-by: Simon
Hi,
this short series makes use of of ARCH_RENESAS in place of ARCH_SHMOBILE.
This is part of an ongoing process to migrate from ARCH_SHMOBILE to
ARCH_RENESAS the motivation for which being that RENESAS seems to be a more
appropriate name than SHMOBILE for the majority of Renesas ARM based SoCs.
Hi Geert,
On Thursday 18 February 2016 18:18:56 Geert Uytterhoeven wrote:
> On Thu, Feb 18, 2016 at 3:38 PM, Rob Herring wrote:
> > On Mon, Feb 15, 2016 at 10:16:50PM +0100, Geert Uytterhoeven wrote:
> >> The Renesas R-Car System Controller provides power management for the
> >>
On Tue, Feb 16, 2016 at 11:22 AM, Geert Uytterhoeven
wrote:
> gpiochip_add_data() allocates the struct gpio_device using kmalloc(),
> which doesn't zero the returned memory.
>
> Hence when calling dev_set_name(), it may try to free a bogus old name,
> causing a crash:
On Thu, Feb 18, 2016 at 9:36 AM, Geert Uytterhoeven
wrote:
> On Wed, Feb 17, 2016 at 11:32 PM, Sergei Shtylyov
> wrote:
>> Add the EtherAVB pin groups to the R8A7794 PFC driver.
>>
>> Based on the patches by Mitsuhiro Kimura
On 02/18/2016 02:48 AM, Simon Horman wrote:
Define the generic R8A7794 part of the sound device node.
This sound device is a complex one and comprises the Audio Clock Generator
(ADG), Sampling Rate Converter Unit (SCU), Serial Sound Interface [Unit]
(SSI[U]), and Audio
Hello.
On 02/18/2016 11:36 AM, Geert Uytterhoeven wrote:
Add the EtherAVB pin groups to the R8A7794 PFC driver.
Based on the patches by Mitsuhiro Kimura .
Thank you for your patch!
Signed-off-by: Sergei Shtylyov
Hi Rob,
On Thu, Feb 18, 2016 at 3:38 PM, Rob Herring wrote:
> On Mon, Feb 15, 2016 at 10:16:50PM +0100, Geert Uytterhoeven wrote:
>> The Renesas R-Car System Controller provides power management for the
>> CPU cores and various coprocessors, following the generic PM domain
>>
Hi Laurent,
On Fri, Feb 19, 2016 at 1:07 AM, Laurent Pinchart
wrote:
> Hi Magnus,
>
> On Friday 19 February 2016 01:02:18 Magnus Damm wrote:
>> On Fri, Feb 19, 2016 at 12:33 AM, Laurent Pinchart wrote:
>> > On Thursday 18 February 2016 10:17:16 Geert
Hi Magnus,
On Friday 19 February 2016 01:02:18 Magnus Damm wrote:
> On Fri, Feb 19, 2016 at 12:33 AM, Laurent Pinchart wrote:
> > On Thursday 18 February 2016 10:17:16 Geert Uytterhoeven wrote:
> >> On Thu, Feb 18, 2016 at 10:01 AM, Kuninori Morimoto wrote:
> >> I tried this patch, but It
The R-Car GPIO driver handles Runtime PM for requested GPIOs only.
When using a GPIO purely as an interrupt source, no Runtime PM handling
is done, and the GPIO module's clock may not be enabled.
To fix this:
- Add .irq_request_resources() and .irq_release_resources() callbacks
to handle
Hi Geert,
On Thu, Feb 18, 2016 at 5:01 PM, Geert Uytterhoeven
wrote:
> Hi Magnus,
>
> On Thu, Feb 18, 2016 at 8:14 AM, Magnus Damm wrote:
>> From: Magnus Damm
>>
>> Add the "intc-ex" clock to the r8a7795 CPG MSSR driver
Hi Geert,
Thanks for the patch.
> From: Geert Uytterhoeven [mailto:geert+rene...@glider.be]
> Sent: 18 February 2016 14:30
>
> cpg_div6_clock_set_rate() only programs the new divisor if the clock isn't
> stopped. If the clock is stopped, it will update the cached divisor value
> only, which will
Hi Geert,
On Thursday 18 February 2016 10:17:16 Geert Uytterhoeven wrote:
> On Thu, Feb 18, 2016 at 10:01 AM, Kuninori Morimoto wrote:
> I tried this patch, but It didn't use this printk().
> Am I wrong ?
>
> -
> diff --git
Hi Jon,
On Tue, Feb 16, 2016 at 10:28 AM, Jon Hunter wrote:
> On 09/02/16 15:19, Geert Uytterhoeven wrote:
>> The R-Car GPIO driver handles Runtime PM for requested GPIOs only.
>>
>> When using a GPIO purely as an interrupt source, no Runtime PM handling
>> is done, and the
Hi Geert,
Thank you for the patch.
On Thursday 18 February 2016 15:30:12 Geert Uytterhoeven wrote:
> cpg_div6_clock_set_rate() only programs the new divisor if the clock
> isn't stopped. If the clock is stopped, it will update the cached
> divisor value only, which will be programmed into the
On Mon, Feb 15, 2016 at 10:16:50PM +0100, Geert Uytterhoeven wrote:
> The Renesas R-Car System Controller provides power management for the
> CPU cores and various coprocessors, following the generic PM domain
> bindings in Documentation/devicetree/bindings/power/power_domain.txt.
>
> This
Hello.
On 2/18/2016 10:52 AM, Geert Uytterhoeven wrote:
--- linux-pinctrl.orig/drivers/pinctrl/sh-pfc/pfc-r8a7794.c
+++ linux-pinctrl/drivers/pinctrl/sh-pfc/pfc-r8a7794.c
@@ -1,9 +1,9 @@
/*
* r8a7794 processor support - PFC hardware block.
*
- * Copyright (C) 2014 Renesas
Hi Morimoto-san,
On Thu, Feb 18, 2016 at 10:01 AM, Kuninori Morimoto
wrote:
>> > > I tried this patch, but It didn't use this printk().
>> > > Am I wrong ?
>> > >
>> > > -
>> > > diff --git a/drivers/regulator/da9210-regulator.c
>> > >
Hi Geert, again
> > > I tried this patch, but It didn't use this printk().
> > > Am I wrong ?
> > >
> > > -
> > > diff --git a/drivers/regulator/da9210-regulator.c
> > > b/drivers/regulator/da9210-regulator.c
> > > index 01c0e37..85c1166 100644
> > > ---
Hi Geert
> > I tried this patch, but It didn't use this printk().
> > Am I wrong ?
> >
> > -
> > diff --git a/drivers/regulator/da9210-regulator.c
> > b/drivers/regulator/da9210-regulator.c
> > index 01c0e37..85c1166 100644
> > --- a/drivers/regulator/da9210-regulator.c
> > +++
Hi Morimoto-san,
On Thu, Feb 18, 2016 at 9:39 AM, Kuninori Morimoto
wrote:
>> > [ 59.144598] irq 311: nobody cared (try booting with the "irqpoll"
>> > option)
>> > [ 59.151419] CPU: 0 PID: 410 Comm: irq/311-da9210 Not tainted
>> > 4.5.0-rc3-02009-g83c516e
Hi Geert
> > [ 59.144598] irq 311: nobody cared (try booting with the "irqpoll" option)
> > [ 59.151419] CPU: 0 PID: 410 Comm: irq/311-da9210 Not tainted
> > 4.5.0-rc3-02009-g83c516e #612
>
> Ugh, the da9210 interrupt.
>
> That probably means an event was set that isn't handled by
>
Hi Sergei,
On Wed, Feb 17, 2016 at 11:32 PM, Sergei Shtylyov
wrote:
> Add the EtherAVB pin groups to the R8A7794 PFC driver.
>
> Based on the patches by Mitsuhiro Kimura .
Thank you for your patch!
> Signed-off-by: Sergei
From: Kuninori Morimoto
Current rsnd supports multi SSI (maximum 4 SSI for 8ch),
and, it should determine whether using each SSI or not in runtime.
All SSIs are not used even if there are 4 SSI in case of stereo.
Current driver setups un-used SSI in such case.
From: Kuninori Morimoto
prepare for runtime judging for SSI work
Signed-off-by: Kuninori Morimoto
---
sound/soc/sh/rcar/ssi.c | 42 +-
1 file changed, 21 insertions(+), 21 deletions(-)
From: Kuninori Morimoto
Current rsnd supports multi SSI (maximum 4 SSI for 8ch),
and, it should determine whether using each SSI or not in runtime.
Current judgement is vague, and had broken by
c308abe45e2("ASoC: rsnd: rsnd_ssi_is_multi_slave() macro uses
From: Kuninori Morimoto
Parent SSI is needed if it is PIN sharing and clock master,
otherwise, not needed. But, whether clockk master is judged on
.set_fmt, thus, it can't call rsnd_ssi_parent_attach() on .probe.
Now, .pcm_new will be called after .set_fmt, so
From: Kuninori Morimoto
SSI want to have SSIWSR settings and SSICR settings without EN bit
when init, and SSICR EN bit only when start timing.
Otherwise, SSI output signal might be unstable.
Signed-off-by: Kuninori Morimoto
From: Kuninori Morimoto
commit b5b442abd9 ("ASoC: rsnd: add .irq callback")
added .irq support, and it cares both parent SSI and normal SSI.
But it should care only normal SSI. Otherwise SSI might be
forever loop if SSI is used as both parent SSI and normal SSI
From: Kuninori Morimoto
The channels number is not only for DVC. Let's rename it.
Signed-off-by: Kuninori Morimoto
---
sound/soc/sh/rcar/core.c | 2 +-
sound/soc/sh/rcar/dvc.c | 6 +++---
sound/soc/sh/rcar/rsnd.h | 4 ++--
3
From: Kuninori Morimoto
SRC_ROUTE_MODE0 determines whether to use SRC.
Thus, it should be setup before SRC_SRCIR.
Signed-off-by: Kuninori Morimoto
---
sound/soc/sh/rcar/src.c | 3 ++-
1 file changed, 2 insertions(+), 1
Hi Mark
Current rsnd driver is supporting many features, and now we are
confirming these register settings sequence.
These patches fixup not good sequence (and bug)
Kuninori Morimoto (11):
ASoC: rsnd: rename RSND_DVC_CHANNELS to RSND_MAX_CHANNELS
ASoC: rsnd: setup SRC_ROUTE_MODE0
Hi Magnus,
On Thu, Feb 18, 2016 at 8:14 AM, Magnus Damm wrote:
> From: Magnus Damm
>
> Add the "intc-ex" clock to the r8a7795 CPG MSSR driver V2.
>
> According to information from the hardware team the INTC_EX
> parent clock is CP. The next
39 matches
Mail list logo