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
> > clock-output-names property.
> > * S
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
* 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 n
* 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 n
On Tue, Mar 22, 2016 at 11:17:09AM +0100, Geert Uytterhoeven wrote:
> 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
> >
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 timers on
> >> SH-Mobile
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 media_
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 interrupts for dma queue (best effort rx/tx, network control rx/
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
> &tmio_mmc_ops. Before doing that, you can conditionally assign
> ->start_signal_voltage_switch() callback within the &tmio_mmc_ops,
> right!?
So, lets talk with cod
> > + 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 kno
Hi Geert,
> > + DEF_DIV6_RO("osc", R8A7795_CLK_OSC, CLK_EXTAL, 0x0240, 8),
> > + DEF_DIV6_RO("r_int",R8A7795_CLK_RINT, CLK_EXTAL, 0x0240, 32),
Yes, we should ask the HW team if this is safe. I got the assumption
from Figure 8.1a. In the middle, after EXTAL divider, OSCCLK
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 interrupt handler by adding the
int
On Tue, Mar 22, 2016 at 3:30 PM, Geert Uytterhoeven
wrote:
> On Tue, Mar 22, 2016 at 2:18 PM, Linus Walleij
> wrote:
>> I wait for Geert to either queue this for his first v4.7 pull request
>> or tell me to apply it for fixes. Is it a regression?
>
> I'm not aware of any issues due to this.
OK
Hi Linus,
On Tue, Mar 22, 2016 at 2:18 PM, Linus Walleij wrote:
> 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
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 line over gpio (ofcourse irq line
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 recently I came across anot
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 before setting GPSRx
> registers in case that they need to be configur
On Mon, Mar 14, 2016 at 4:21 PM, Geert Uytterhoeven
wrote:
> This allows to set multiple outputs using a single register write.
>
> Signed-off-by: Geert Uytterhoeven
Patch applied for v4.7.
Yours,
Linus Walleij
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 clock-output-names
> optional"
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 clock-output-names
> proper
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 clock-output-names
> proper
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,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@linux-m68k.org
In personal conversatio
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 R_Internal. clk_mux doesn't help here because we don't want to
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 +++
> include/dt-bindings/clock/r8a7795-cpg-mssr.h | 5 +++--
> 2 files changed, 6 insertions(+), 2 deletions(-)
>
> d
Hi Wolfram,
On Mon, Mar 21, 2016 at 8:19 PM, Wolfram Sang wrote:
> From: Wolfram Sang
>
> Gen3 has two clocks (OSC and R) which look like a DIV6 clock but their
> divider value is read-only and depends on MD pins at bootup. Add support
> for such clocks by reading the value and adding a fixed cl
On Mon, Mar 21, 2016 at 8:19 PM, Wolfram Sang wrote:
> From: Wolfram Sang
>
> About SD clocks: The clock type is Gen3 specific, the callbacks are all
> Gen3 specific; I think the clock definition should also be Gen3 specific
> and not in the general header file.
Woops, missed that when the macro
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
>> >
>> > All the SHDIs can operate with either 3.3V or 1.8V signals, depending
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 peripheral interrupt
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 negotiation with the card.
> >
> > Implement the {get,set}_io_vol
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 on the latest Felipe's usb.git / tes
Yoshihiro-san,
Yoshihiro Shimoda writes:
>> 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
31 matches
Mail list logo
