On Tue, May 24, 2016 at 07:34:14PM +0900, Yoshihiro Shimoda wrote:
> This patch is based on the renesas-drivers / renesas-drivers-2016-05-17-v4.6
> tag.
Thanks, I have queued this up for v4.8.
Please let me know if that was not your intention.
On Wed, May 25, 2016 at 09:38:23AM +0200, Dirk Behme wrote:
> On 24.05.2016 03:54, Simon Horman wrote:
> >Basic support for the Gen 3 R-Car M3-W SoC.
> >
> >Based on work for the r8a7795 and r8a7796 SoCs by
> >Takeshi Kihara, Dirk Behme and Geert Uytterhoeven.
> >
> >Signed-off-by: Simon Horman
Hi Dirk,
On Wed, May 25, 2016 at 07:10:26AM +0200, Dirk Behme wrote:
> Hi Simon,
>
> On 25.05.2016 02:48, Simon Horman wrote:
> >Hi Dirk,
> >
> >On Tue, May 24, 2016 at 07:30:17AM +0200, Dirk Behme wrote:
> >>Hi Simon,
> >
> >[...]
> >
> >>With Renesas R-Car3 we will get a whole family of SoCs.
Hi Kieran
> Just to add to this request, could you ask the HW engineers to confirm
> the clock parents for the FCPF (0,1,2) as well please?
>
> They too are currently listed as R8A7795_CLK_S2D1, however now that I am
> trying to enable the FCPF and read registers from it - the VCR is
>
Renesas R-Car V2H (R8A7792) clocks are handled by R-Car gen2 clock driver.
Signed-off-by: Sergei Shtylyov
---
The patch is against the 'clk-next' branch of CLK group's 'linux.git' repo.
drivers/clk/renesas/Kconfig |1 +
drivers/clk/renesas/Makefile |
From: Niklas Söderlund
This is done to prepare for Gen3 support where there are more than one
subdevice and the usage of them are complex and can be shared between
multiple rcar-vin instances. There are a few trouble areas with Gen3
that needs to be solved
From: Niklas Söderlund
Add the register needed to work with Gen3 hardware. This patch just adds
the logic for how to work with the Gen3 hardware. More work is required
to enable the subdevice structure needed to support capturing.
Signed-off-by: Niklas
From: Niklas Söderlund
These are present in the soc-camera version of this driver and it's time
to add them to this driver as well.
Signed-off-by: Niklas Söderlund
---
drivers/media/platform/rcar-vin/rcar-core.c | 2
From: Ulrich Hecht
Adds ioctls DV_TIMINGS_CAP, ENUM_DV_TIMINGS, G_DV_TIMINGS, S_DV_TIMINGS,
and QUERY_DV_TIMINGS.
Signed-off-by: Ulrich Hecht
Signed-off-by: Niklas Söderlund
---
From: Niklas Söderlund
Signed-off-by: Niklas Söderlund
---
drivers/media/platform/rcar-vin/Kconfig | 2 +-
drivers/media/platform/rcar-vin/rcar-core.c | 1 +
2 files changed, 2 insertions(+), 1 deletion(-)
diff
From: Ulrich Hecht
Fix rcar_vin_try_fmt's use of an inappropriate pad number when calling
the subdev set_fmt function - for the ADV7612, IDs should be non-zero.
Signed-off-by: William Towle
Reviewed-by: Rob Taylor
From: Niklas Söderlund
Hi,
This series enable Gen3 support for the rcar-vin driver. It is based on
top of the media_tree:
git://linuxtv.org/media_tree.git master
And it depends on the first rcar-vin patch at which I hope soon will
enter the media tree:
From: Ulrich Hecht
Add detection of source pad number for drivers aware of the media controller
API, so that rcar-vin can create device nodes to support modern drivers such
as adv7604.c (for HDMI on Lager) and the converted adv7180.c (for composite)
underneath.
On Wed, May 25, 2016 at 08:37:45AM +0200, Wolfram Sang wrote:
> From: Wolfram Sang
>
> And move module_init/exit to the proper place while here.
>
> Signed-off-by: Wolfram Sang
Reviewed-by: Guenter Roeck
On Wed, May 25, 2016 at 08:37:46AM +0200, Wolfram Sang wrote:
> From: Wolfram Sang
>
> Signed-off-by: Wolfram Sang
Reviewed-by: Guenter Roeck
> ---
> drivers/watchdog/softdog.c | 8 +++-
> 1 file
On Wed, May 25, 2016 at 08:37:47AM +0200, Wolfram Sang wrote:
> From: Wolfram Sang
>
> Signed-off-by: Wolfram Sang
Reviewed-by: Guenter Roeck
> ---
> drivers/watchdog/softdog.c | 10 +-
> 1 file
On Wed, May 25, 2016 at 08:37:48AM +0200, Wolfram Sang wrote:
> From: Wolfram Sang
>
> If we leave set_timeout empty, the core will do exactly what is
> implemented here anyway.
>
> Signed-off-by: Wolfram Sang
Reviewed-by:
On Wed, May 25, 2016 at 08:37:49AM +0200, Wolfram Sang wrote:
> From: Wolfram Sang
>
> Signed-off-by: Wolfram Sang
Reviewed-by: Guenter Roeck
> ---
> drivers/watchdog/softdog.c | 6 +++---
> 1 file
On Wed, May 25, 2016 at 08:37:44AM +0200, Wolfram Sang wrote:
> From: Wolfram Sang
>
> Error string and comment say we fall back to a default, but in reality
> we bailed out. Refactor the code to use the core helper which then
> matches the described behaviour.
On 25/05/16 09:49, Kuninori Morimoto wrote:
>
> Hi Kieran
>
>> I have added an initial patch to support the FDP1 in the clock
>> framework, but I have not been able to correctly identify the actual
>> clock parent.
>>
>> For now I have assumed that it is R8A7795_CLK_S2D1.
>>
>> Could you please
So, here is the RFC series implementing the userspace governor. This is merely
meant as a proof-of-concept, so my patch series will have the same capabilities
as Vladimir's series. It does work (for me (tm)) and shows how the bottom half
handling can be better put to the watchdog device code,
From: Wolfram Sang
Mechanisms like pretimeout governors may want to notify userspace via
uevents. Add a helper because all the needed data is private to the
watchdog device. To allow calling it in atomic contexts, put actual
signalling to a workqueue.
From: Vladimir Zapolskiy
Userspace notifier watchdog pretimeout governor, on watchdog
pretimeout event sends a notification to userspace for further
handling.
Signed-off-by: Vladimir Zapolskiy
Signed-off-by: Wolfram Sang
From: Vladimir Zapolskiy
Noop watchdog pretimeout governor, only an informational message is
added to the kernel log buffer.
Signed-off-by: Vladimir Zapolskiy
Signed-off-by: Wolfram Sang
---
From: Vladimir Zapolskiy
Panic watchdog pretimeout governor, on watchdog pretimeout event the
kernel shall panic.
Signed-off-by: Vladimir Zapolskiy
Signed-off-by: Wolfram Sang
---
Changes since
From: Wolfram Sang
Give devices which do not have hardware support for pretimeout at least a
software version of it.
Signed-off-by: Wolfram Sang
---
drivers/watchdog/softdog.c | 20 +++-
1 file changed, 19
From: Wolfram Sang
Since the watchdog framework centrializes the IOCTL interfaces of device
drivers now, SETPRETIMEOUT and GETPRETIMEOUT need to be added in the
common code.
Signed-off-by: Robin Gong
Signed-off-by: Wolfram Sang
From: Wolfram Sang
Those paragraphs deal with the same topic, so tie them together for
easier reading.
Signed-off-by: Wolfram Sang
---
Documentation/watchdog/watchdog-kernel-api.txt | 4 ++--
1 file changed, 2 insertions(+),
From: Wolfram Sang
The change adds a simple watchdog pretimeout framework infrastructure,
its purpose is to allow users to select a desired handling of watchdog
pretimeout events, which may be generated by a watchdog driver.
By design every watchdog pretimeout
Hi Sato-san,
CC linux-serial
On Wed, Apr 27, 2016 at 5:49 PM, Yoshinori Sato
wrote:
> Add missing flag condition.
>
> Signed-off-by: Yoshinori Sato
Acked-by: Geert Uytterhoeven
Unfortunately magic SysRq only
The Renesas R-Car3 product register (PRR) helps us to identify the
SoC and revision we are running on. Add helper functions to check
for this easily in code where it's needed.
Signed-off-by: Dirk Behme
---
include/linux/soc/renesas/rcar3-prr.h | 51
Instead of hard coding the product register in the rcar-du, use
the framework for it to get the SoC version and the revision needed
for the enabling the workaround.
Signed-off-by: Dirk Behme
---
drivers/gpu/drm/rcar-du/rcar_du_crtc.c | 13 ++---
1 file changed,
Hi Morimoto-san,
I have added an initial patch to support the FDP1 in the clock
framework, but I have not been able to correctly identify the actual
clock parent.
For now I have assumed that it is R8A7795_CLK_S2D1.
Could you please confirm this selection, or help identify the true
parent
On 24.05.2016 03:54, Simon Horman wrote:
Basic support for the Gen 3 R-Car M3-W SoC.
Based on work for the r8a7795 and r8a7796 SoCs by
Takeshi Kihara, Dirk Behme and Geert Uytterhoeven.
Signed-off-by: Simon Horman
Reviewed-by: Geert Uytterhoeven
On 25.05.2016 07:10, Dirk Behme wrote:
Hi Simon,
On 25.05.2016 02:48, Simon Horman wrote:
Hi Dirk,
On Tue, May 24, 2016 at 07:30:17AM +0200, Dirk Behme wrote:
Hi Simon,
[...]
With Renesas R-Car3 we will get a whole family of SoCs. I.e. different
computing power (e.g. different number of
From: Wolfram Sang
Signed-off-by: Wolfram Sang
---
drivers/watchdog/softdog.c | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/drivers/watchdog/softdog.c b/drivers/watchdog/softdog.c
index
From: Wolfram Sang
And move module_init/exit to the proper place while here.
Signed-off-by: Wolfram Sang
---
drivers/watchdog/softdog.c | 21 ++---
1 file changed, 10 insertions(+), 11 deletions(-)
diff --git
While working on another series where I need the softdog, this series already
came out of it. It gets the driver prepared for the interesting stuff (coming
later today hopefully) but is orthogonal from that.
Buildbot is happy, branch is here:
From: Wolfram Sang
Error string and comment say we fall back to a default, but in reality
we bailed out. Refactor the code to use the core helper which then
matches the described behaviour. While updating the init message anyhow,
shorten it while we are here; no
From: Wolfram Sang
The history is obsolete, especially since we switched to watchdog
framework. The section markers also don't make sense anymore given
the small size of the driver.
Signed-off-by: Wolfram Sang
---
From: Wolfram Sang
If we leave set_timeout empty, the core will do exactly what is
implemented here anyway.
Signed-off-by: Wolfram Sang
---
drivers/watchdog/softdog.c | 7 ---
1 file changed, 7 deletions(-)
diff --git
From: Wolfram Sang
Signed-off-by: Wolfram Sang
---
drivers/watchdog/softdog.c | 8 +++-
1 file changed, 3 insertions(+), 5 deletions(-)
diff --git a/drivers/watchdog/softdog.c b/drivers/watchdog/softdog.c
index
From: Wolfram Sang
Signed-off-by: Wolfram Sang
---
drivers/watchdog/softdog.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/watchdog/softdog.c b/drivers/watchdog/softdog.c
index
43 matches
Mail list logo