Re: [PATCH/RFC 1/9] clk: shmobile: r8a7795: Add FCP clocks

Hi Laurent > > The parent clock isn't documented in the datasheet, use S2D1 as a best > > guess for now. > > Would you be able to find out what the parent clock is for the FCP and LVDS > (patch 2/9) clocks ? Thanks ! I asked it to HW team > Feel free to tell the documentation team that your

[PATCH 0/8] drivers/pinctrl: remove truly orphaned module code

This series of commits is a part of a larger project to ensure people don't reference modular support functions in non-modular code. Overall there was roughly 5k lines of dead code in the kernel due to this. So far we've fixed several areas, like tty, x86, net, ... and we continue to work on

[PATCH 4/8] drivers/pinctrl: make sh-pfc/core.c explicitly non-modular

The Kconfig / Makefile currently controlling compilation of this code is: drivers/pinctrl/sh-pfc/Makefile:obj-$(CONFIG_PINCTRL_SH_PFC)+= sh-pfc.o drivers/pinctrl/sh-pfc/Makefile:sh-pfc-objs = core.o pinctrl.o drivers/pinctrl/sh-pfc/Kconfig:config PINCTRL_SH_PFC

Re: [PATCH/RFC v6 net-next] ravb: Add dma queue interrupt support

Hello. On 02/28/2016 06:41 PM, Yoshihiro Kaneko wrote: 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,

Re: [GIT PULL] Second Round of Renesas ARM Based SoC DT Updates for v4.6

On Friday 26 February 2016 08:53:07 Simon Horman wrote: > Second Round of Renesas ARM Based SoC DT Updates for v4.6 > > * Add L2 cache-controller nodes to r8a779[0134] and r8a73a4 > * Add etheravb support to r8a7794 > * Correct JP3 jumper description on Porter > * Enable thermal zone on

Re: [GIT PULL] Second Round of Renesas ARM64 Based SoC DT Updates for v4.6

On Friday 26 February 2016 09:07:32 Simon Horman wrote: > Please consider these second round of Renesas ARM64 based SoC DT updates > for v4.6. > > This pull request is based on the previous round of > such requests, tagged as renesas-arm64-dt-for-v4.6, > which you have already pulled. Pulled

Re: [GIT PULL] Renesas ARM64 Based SoC SoC Updates for v4.6

On Friday 26 February 2016 08:52:55 Simon Horman wrote: > Renesas ARM64 Based SoC SoC Updates for v4.6 > > * Enable RENESAS_IRQC, and PM and PM_GENERIC_DOMAINS for SoCs with PM Domains > Pulled into next/arm64, thanks! Arnd

Re: [GIT PULL] Renesas ARM64 Based SoC Defconfig Updates for v4.6

On Friday 26 February 2016 08:51:45 Simon Horman wrote: > Please consider these Renesas ARM64 based SoC defconfig updates for v4.6. > > This pull request is based on the previous round of > such requests, tagged as v4.5-rc2, > which I have already sent a pull-request for. It looks like your

[PATCH] iommu/ipmmu-vmsa: Add r8a7795 DT binding

IPMMU instances and the main IPMMU. Signed-off-by: Magnus Damm <damm+rene...@opensource.se> --- Written against linux-next tag next-20160229 Documentation/devicetree/bindings/iommu/renesas,ipmmu-vmsa.txt | 15 -- 1 file changed, 13 insertions(+), 2 deletions(-) --- 0001/Documentati

[PATCH] arm64: dts: r8a7795: Add CAN support

Adds CAN controller nodes for r8a7795. Note: CAN channel register base address mentioned in R-Car Gen3 Hardware User Manual v0.5E is incorrect. The corrected base addresses are: CAN Channel 0 - 0xe6c3 CAN Channel 1 - 0xe6c38000 Signed-off-by: Ramesh Shanmugasundaram

Re: rcar_sata DMA warnings on Salvator-X

Hi Tejun, On Fri, Feb 26, 2016 at 9:21 AM, Geert Uytterhoeven wrote: > On Thu, Feb 25, 2016 at 10:42 PM, Tejun Heo wrote: >> On Thu, Feb 25, 2016 at 4:40 PM, Tejun Heo wrote: >>> Is this the problem fixed by the following patch from

Re: [PATCH/RFC 1/4] media: soc_camera: rcar_vin: Add UDS support

Hello. On 2/29/2016 4:12 PM, Yoshihiro Kaneko wrote: From: Yoshihiko Mori Add UDS control for R-Car Gen3. Up down scaler can be vertical and horizontal scaling. Signed-off-by: Yoshihiko Mori Signed-off-by: Koji Matsuoka

Re: [PATCH/RFC 0/4] media: soc_camera: rcar_vin: Add UDS and NV16 scaling support

Huh, you must have missed Niklas's work the rcar-vin driver: http://www.spinics.net/lists/linux-media/msg97816.html I expect that the old soc-camera driver will be retired soon in favor of the new driver, so I don't want to accept patches for that one. I recommend that you check the new driver

[PATCH/RFC 2/4] media: soc_camera: rcar_vin: Add get_selection callback function

From: Koji Matsuoka Add get_selection callback function because it is required for clipping processing. Signed-off-by: Koji Matsuoka Signed-off-by: Yoshihiro Kaneko ---

[PATCH/RFC 1/4] media: soc_camera: rcar_vin: Add UDS support

From: Yoshihiko Mori Add UDS control for R-Car Gen3. Up down scaler can be vertical and horizontal scaling. Signed-off-by: Yoshihiko Mori Signed-off-by: Koji Matsuoka Signed-off-by: Yoshihiro Kaneko

[PATCH/RFC 0/4] media: soc_camera: rcar_vin: Add UDS and NV16 scaling support

This series adds UDS support, NV16 scaling support and callback functions to be required by a clipping process. This series is against the master branch of linuxtv.org/media_tree.git. Koji Matsuoka (3): media: soc_camera: rcar_vin: Add get_selection callback function media: soc_camera:

[PATCH/RFC 4/4] media: soc_camera: rcar_vin: Add NV16 scaling support

From: Koji Matsuoka The scaling function had been forbidden for the capture format of NV16 until now. With this patch, a horizontal scaling-up function is supported to the capture format of NV16. This patch adds the check of the capture width for NV16 format, too.

Re: [PATCH 1/2] can: rcar_can: Add r8a7795 support

On 02/29/2016 11:00 AM, Marc Kleine-Budde wrote: > I think it's better to fix the algorithm. I'll look into it. What about: > ./can-calc-bit-timing -c 3998 rcar_can > > Bit timing parameters for rcar_can with 39.98 MHz ref clock >

[PATCH] can: rcar_can: Add r8a7795 support

Added r8a7795 SoC support. Signed-off-by: Ramesh Shanmugasundaram --- Hi All, This patch is based on linux-can-next (tag:linux-can-next-for-4.6-20160226) Pinctrl & Clock related to the controller are already submitted as below:

Re: [RFC 1/7] pinctrl: sh-pfc: r8a7790: Implement voltage switching for SDHI

> Shouldn't the "From" line have Ben's authorship, too? I considered the changes to this patch significant enough to take over ownership. Even more so with the changes you suggested. > > @Uli, Geert: Since bias support is probably similar, what do you think? Does > > it make sense to add

RE: [PATCH 1/2] can: rcar_can: Add r8a7795 support

Hi Geert, > On Mon, Feb 29, 2016 at 10:21 AM, Ramesh Shanmugasundaram > wrote: > > --- a/drivers/net/can/rcar_can.c > > +++ b/drivers/net/can/rcar_can.c > > @@ -808,6 +808,10 @@ static int rcar_can_probe(struct platform_device > *pdev) > >

Re: sh7724 regression: commit 8222dbe21e79338de92d5e1956cd1e3994cc9f93

> On 02/29/2016 09:24 AM, David Hildenbrand wrote: > >> On 02/27/2016 03:28 PM, John Paul Adrian Glaubitz wrote: > >>> Hi Hans! > >>> > >>> On 02/27/2016 03:20 PM, Geert Uytterhoeven wrote: > > I noticed that 4.1 was ok and v4.2 wasn't, so I did a git bisect and > > ended up with >

Re: [RFC 1/7] pinctrl: sh-pfc: r8a7790: Implement voltage switching for SDHI

Hi Wolfram, On Fri, Feb 19, 2016 at 9:16 PM, 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_voltage operations

Re: [PATCH 1/2] can: rcar_can: Add r8a7795 support

On 02/29/2016 10:56 AM, Ramesh Shanmugasundaram wrote: > root@salvator-x:~# can-calc-bit-timing -c 3998 rcar_can Can you send me the patches to support the rcar_can. On the linux-can ML or github pull request. Thanks, Marc -- Pengutronix e.K. | Marc Kleine-Budde

Re: [PATCH 1/2] can: rcar_can: Add r8a7795 support

On 02/29/2016 10:56 AM, Ramesh Shanmugasundaram wrote: >> On 02/29/2016 10:21 AM, Ramesh Shanmugasundaram wrote: >>> Added r8a7795 SoC support. >>> >>> For smoother bit timing calculation, the rounded clock frequency is >> used. >> >> Why this? From my point of view this introduces a clock error.

RE: [PATCH 1/2] can: rcar_can: Add r8a7795 support

Hi Marc, > On 02/29/2016 10:21 AM, Ramesh Shanmugasundaram wrote: > > Added r8a7795 SoC support. > > > > For smoother bit timing calculation, the rounded clock frequency is > used. > > Why this? From my point of view this introduces a clock error. Thanks for the comments. Without the rounded

Re: [PATCH 1/2] can: rcar_can: Add r8a7795 support

Hi Ramesh, On Mon, Feb 29, 2016 at 10:21 AM, Ramesh Shanmugasundaram wrote: > --- a/drivers/net/can/rcar_can.c > +++ b/drivers/net/can/rcar_can.c > @@ -808,6 +808,10 @@ static int rcar_can_probe(struct platform_device *pdev) > priv->regs = addr; >

Re: [PATCHv2] [media] rcar-vin: add Renesas R-Car VIN driver

Hi Niklas, Thanks for your patch! Much appreciated. I have more comments for the v2, but nothing really big :-) One high-level comment I have is that you should create an rcar-v4l2.c (or video.c) source where all the v4l2 ioctls and file ops reside. Most of what is in rcar-dma has nothing to

Re: [PATCH 1/2] can: rcar_can: Add r8a7795 support

On 02/29/2016 10:21 AM, Ramesh Shanmugasundaram wrote: > Added r8a7795 SoC support. > > For smoother bit timing calculation, the rounded clock frequency is used. Why this? From my point of view this introduces a clock error. Marc -- Pengutronix e.K. | Marc Kleine-Budde

[PATCH 2/2] arm64: dts: r8a7795: Add CAN support

Adds CAN controller nodes for r8a7795. Note: CAN channel register base address mentioned in R-Car Gen3 Hardware User Manual v0.5E is incorrect. The corrected base addresses are: CAN Channel 0 - 0xe6c3 CAN Channel 1 - 0xe6c38000 Signed-off-by: Ramesh Shanmugasundaram

[PATCH 1/2] can: rcar_can: Add r8a7795 support

Added r8a7795 SoC support. For smoother bit timing calculation, the rounded clock frequency is used. Signed-off-by: Ramesh Shanmugasundaram --- Documentation/devicetree/bindings/net/can/rcar_can.txt | 12 drivers/net/can/Kconfig

[PATCH 0/2] Add CAN support to r8a7795 SoC

This patch set adds CAN support to r8a7795 SoC. This is based on linux-next (tag: next-20160225). Pinctrl & Clock related to the controller are already submitted as below: https://lkml.org/lkml/2016/2/25/546 https://lkml.org/lkml/2016/2/26/452

Re: sh7724 regression: commit 8222dbe21e79338de92d5e1956cd1e3994cc9f93

On 02/29/2016 09:24 AM, David Hildenbrand wrote: >> On 02/27/2016 03:28 PM, John Paul Adrian Glaubitz wrote: >>> Hi Hans! >>> >>> On 02/27/2016 03:20 PM, Geert Uytterhoeven wrote: > I noticed that 4.1 was ok and v4.2 wasn't, so I did a git bisect and > ended up with > commit

Re: sh7724 regression: commit 8222dbe21e79338de92d5e1956cd1e3994cc9f93

> On 02/27/2016 03:28 PM, John Paul Adrian Glaubitz wrote: > > Hi Hans! > > > > On 02/27/2016 03:20 PM, Geert Uytterhoeven wrote: > >>> I noticed that 4.1 was ok and v4.2 wasn't, so I did a git bisect and > >>> ended up with > >>> commit 8222dbe21e79338de92d5e1956cd1e3994cc9f93 (sched/preempt,