Re: [PATCH 00/13] ARM, arm64: dts: Remove unnecessary clock-output-names properties

On Tue, Mar 22, 2016 at 11:18:37AM +0100, Geert Uytterhoeven wrote: > On Tue, Mar 22, 2016 at 2:40 AM, Simon Horman > wrote: > > this series updates the device trees of Renesas ARM based SoCs. > > > > * Fixed rate and fixed factor clocks do not require an > >

[PATCH v2 0/2] ARM: dts: Remove unnecessary clock-output-names properties

Hi, this series updates the device trees of Renesas ARM based SoCs. * Fixed rate and fixed factor clocks do not require an clock-output-names property. * Since 07705583e920fef6 ("clk: shmobile: div6: Make clock-output-names optional") Renesas div6 clocks do not require a clock-output-names

[PATCH v2 1/2] ARM: dts: r8a73a4: Remove unnecessary clock-output-names properties

* Fixed rate and fixed factor clocks do not require an clock-output-names property. * Since 07705583e920fef6 ("clk: shmobile: div6: Make clock-output-names optional") Renesas div6 clocks do not require a clock-output-names property. In the above cases there is only one clock output and its

[PATCH v2 2/2] ARM: dts: sh73a0: Remove unnecessary clock-output-names properties

* Fixed rate and fixed factor clocks do not require an clock-output-names property. * Since 07705583e920fef6 ("clk: shmobile: div6: Make clock-output-names optional") Renesas div6 clocks do not require a clock-output-names property. In the above cases there is only one clock output and its

Re: [PATCH 0/2] ARM: dts: shmobile: Correct interrupt type for ARM TWD

On Tue, Mar 22, 2016 at 09:43:40AM +0100, Geert Uytterhoeven wrote: > Hi Simon, > > On Tue, Mar 22, 2016 at 2:28 AM, Simon Horman wrote: > > On Fri, Mar 18, 2016 at 11:19:19AM +0100, Geert Uytterhoeven wrote: > >> This patch series corrects the interrupt type for ARM TWD

Re: [PATCH 5/5] [media] media-device: make media_device_cleanup() static

On 03/16/2016 06:04 AM, Mauro Carvalho Chehab wrote: > When multiple drivers are sharing the media_device struct, > one driver cannot know the right moment to cleanup the > media_device struct, because it can happen only when the > struct is not used by the other drivers. > > So, let's call

Re: [PATCH v8 net-next] ravb: Add dma queue interrupt support

From: Yoshihiro Kaneko Date: Wed, 23 Mar 2016 00:22:00 +0900 > From: Kazuya Mizuguchi > > This patch supports the following interrupts. > > - One interrupt for multiple (timestamp, error, gPTP) > - One interrupt for emac > - Four

Re: [RFC 4/7] mmc: tmio: Add UHS-I mode support

Hi Ulf, > Okay, let me elaborate a bit more on what I really meant. > > In tmio_mmc_of_parse(), the mmc->ops gets assigned to the > _mmc_ops. Before doing that, you can conditionally assign > ->start_signal_voltage_switch() callback within the _mmc_ops, > right!? So, lets talk with code. Do you

Re: [RFC 4/5] WIP: clk: shmobile: r8a7795: add R clk

> > + if (0) { /* FIXME: how to check if EXTALR rate is > 0? */ > > Can't you just get its rate? > Please cc linux-clk for questions like this. I wondered if a clock provider has an easier method than simply becoming a clock consumer of its own clock. I thought some of you might

[PATCH v8 net-next] ravb: Add dma queue interrupt support

From: Kazuya Mizuguchi This patch supports the following interrupts. - One interrupt for multiple (timestamp, error, gPTP) - One interrupt for emac - Four interrupts for dma queue (best effort rx/tx, network control rx/tx) This patch improve efficiency of the

Re: [RFD] Sharing GPIOs for input (buttons) and output (LEDs)

On Tue, Mar 22, 2016 at 2:59 PM, Vaibhav Hiremath wrote: > On Thursday 17 March 2016 03:48 PM, Linus Walleij wrote: > but recently I came across another usecase of shared gpio, > > Say, for example, we have multiple external I2C peripheral which share > interrupt

Re: [RFD] Sharing GPIOs for input (buttons) and output (LEDs)

On Thursday 17 March 2016 03:48 PM, Linus Walleij wrote: On Mon, Feb 22, 2016 at 1:14 PM, Geert Uytterhoeven wrote: On the Renesas Salvator-X development board, 3 GPIO pins are connected to both push buttons and LEDs. Not exactly related to buttons and leds, but

Re: [PATCH 2/2] pinctrl: sh-pfc: IPSRx and MOD_SELx should be set before GPSRx

On Wed, Mar 16, 2016 at 1:48 AM, Kuninori Morimoto wrote: > From: Kuninori Morimoto > > Gen2 / Gen3 datasheet will have below note in next version. > This patch follows this note. > > IPSRx and MOD_SELx registers shall be set

Re: [PATCH 00/13] ARM, arm64: dts: Remove unnecessary clock-output-names properties

On Tue, Mar 22, 2016 at 2:40 AM, Simon Horman wrote: > this series updates the device trees of Renesas ARM based SoCs. > > * Fixed rate and fixed factor clocks do not require an > clock-output-names property. > * Since 07705583e920fef6 ("clk: shmobile: div6: Make

Re: [PATCH 03/13] ARM: dts: sh73a0: Remove unnecessary clock-output-names properties

On Tue, Mar 22, 2016 at 2:40 AM, Simon Horman wrote: > * Fixed rate and fixed factor clocks do not require an > clock-output-names property. > * Since 07705583e920fef6 ("clk: shmobile: div6: Make clock-output-names > optional") Renesas div6 clocks do not require a

Re: [PATCH 02/13] ARM: dts: r8a73a4: Remove unnecessary clock-output-names properties

On Tue, Mar 22, 2016 at 2:40 AM, Simon Horman wrote: > * Fixed rate and fixed factor clocks do not require an > clock-output-names property. > * Since 07705583e920fef6 ("clk: shmobile: div6: Make clock-output-names > optional") Renesas div6 clocks do not require a

Re: [RFC 5/5] clk: shmobile: r8a7795: add stop for R clk

On Mon, Mar 21, 2016 at 8:19 PM, Wolfram Sang wrote: > From: Wolfram Sang > > Signed-off-by: Wolfram Sang Acked-by: Geert Uytterhoeven Gr{oetje,eeting}s,

Re: [RFC 4/5] WIP: clk: shmobile: r8a7795: add R clk

Hi Wolfram, On Mon, Mar 21, 2016 at 8:19 PM, Wolfram Sang wrote: > From: Wolfram Sang > > This is a sketch how I think R clk should be handled. During > initialization, check if EXTALR is populated. If so, use it as R. If > not, use

Re: [RFC 3/5] clk: shmobile: r8a7795: add OSC and R_INT clocks

Hi Wolfram, On Mon, Mar 21, 2016 at 8:19 PM, Wolfram Sang wrote: > From: Wolfram Sang > > Signed-off-by: Wolfram Sang > --- > drivers/clk/shmobile/r8a7795-cpg-mssr.c | 3 +++ >

Re: [PATCH 01/10] pinctrl: sh-pfc: r8a7790: Implement voltage switching for SDHI

Hi Wolfram, On Tue, Mar 22, 2016 at 9:35 AM, Wolfram Sang wrote: > On Mon, Mar 14, 2016 at 10:47:23AM +0100, Geert Uytterhoeven wrote: >> On Sat, Mar 12, 2016 at 10:15 AM, Wolfram Sang wrote: >> > From: Wolfram Sang >> >

Re: [PATCH 0/2] ARM: dts: shmobile: Correct interrupt type for ARM TWD

Hi Simon, On Tue, Mar 22, 2016 at 2:28 AM, Simon Horman wrote: > On Fri, Mar 18, 2016 at 11:19:19AM +0100, Geert Uytterhoeven wrote: >> This patch series corrects the interrupt type for ARM TWD timers on >> SH-Mobile AG5 and R-Car H1. >> >> The ARM TWD interrupt is a private

Re: [PATCH 01/10] pinctrl: sh-pfc: r8a7790: Implement voltage switching for SDHI

On Mon, Mar 14, 2016 at 10:47:23AM +0100, Geert Uytterhoeven wrote: > On Sat, Mar 12, 2016 at 10:15 AM, Wolfram Sang wrote: > > From: Wolfram Sang > > > > All the SHDIs can operate with either 3.3V or 1.8V signals, depending > > on

RE: [PATCH v2 0/2] usb: renesas_usbhs: fix to avoid unexpected condition

Hi Felipe-san, > From: Felipe Balbi [mailto:ba...@kernel.org] > Sent: Tuesday, March 22, 2016 4:16 PM > > Yoshihiro-san, > > Yoshihiro Shimoda writes: > >> From: Yoshihiro Shimoda > >> Sent: Thursday, March 10, 2016 11:30 AM > >> > >> This patch set is based

RE: [PATCH v2 0/2] usb: renesas_usbhs: fix to avoid unexpected condition

Hi Felipe, > From: Yoshihiro Shimoda > Sent: Thursday, March 10, 2016 11:30 AM > > This patch set is based on the latest Felipe's usb.git / testing/next branch. > (commit id = ac5706631325ae3695bfa1527101ab2b2f64859f) Would you review the patch set? I confirmed that the patch set could be