On Mon, Feb 26, 2018 at 12:18:19PM +, Michel Pollet wrote:
> This adds the Renesas RZ/N1 CPU and bare bone support.
>
> This currently only handles generic parts (gic, architected timer)
> and a UART.
> This also relies on the bootloader to set the pinctrl and clocks.
>
> Signed-off-by: Miche
On Sun, Feb 25, 2018 at 09:14:21PM +0300, Sergei Shtylyov wrote:
> Add the PFC support for the R8A77980 SoC including pin groups for some
> on-chip devices such as AVB, CAN-FD, GETHER, [H]SCIF, I2C, INTC-EX, MMC,
> MSIOF, PWM, and VIN...
>
> Based on the original (and large) patch by Vladimir Bari
Hi Sergei,
On Mon, Feb 26, 2018 at 5:53 PM, Sergei Shtylyov
wrote:
> On 02/26/2018 03:42 PM, Geert Uytterhoeven wrote:
>>> Add the PFC support for the R8A77980 SoC including pin groups for some
>>> on-chip devices such as AVB, CAN-FD, GETHER, [H]SCIF, I2C, INTC-EX, MMC,
>>> MSIOF, PWM, and VIN...
Hello,
now that CEU has been picked up for inclusion in v4.17, we can start moving
users of old sh_mobile_ceu_camera driver to use the newly introduced one.
Migo-R has been first, now it's SH7724 ECOVEC board turn.
ECOVEC has a camera board with two MT9T112 image sensor and one TW9910 video
de
SH4 7724 Ecovec platform uses sh_mobile_ceu camera driver, which is now
being replaced by a proper V4L2 camera driver named 'renesas-ceu'.
Get rid of soc_camera defined components used to register sensor drivers
and of platform specific enable/disable routines.
Register GPIOs for sensor drivers a
Add entry for Aptina/Micron MT9T112 camera sensor. The driver is
currently orphaned.
Signed-off-by: Jacopo Mondi
---
MAINTAINERS | 7 +++
1 file changed, 7 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 91ed6ad..1d8be25 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -9385,6 +9385
Remove soc_camera framework dependencies from mt9t112 sensor driver.
- Handle clk, gpios and power routines
- Register async subdev
- Remove deprecated g/s_mbus_config operations
- Remove driver flags
- Change driver interface and add kernel doc
- Adjust build system
This commit does not remove th
Fix code style issues reported by checkpatch run with --strict
options. Also fix other non reported style issues manually.
Signed-off-by: Jacopo Mondi
---
drivers/media/i2c/mt9t112.c | 256
1 file changed, 118 insertions(+), 138 deletions(-)
diff --g
Copy the soc_camera based driver in v4l2 sensor driver directory.
This commit just copies the original file without modifying it.
No modification to KConfig and Makefile as soc_camera framework
dependencies need to be removed first in next commit.
Signed-off-by: Jacopo Mondi
---
drivers/media/i2
The Stream Buffer for EtherAVB-IF (STBE) is an optional component, and
is not present on all SoCs.
Document this in the DT bindings, including a list of SoCs that do have
it.
Fixes: 785ec87483d1e24a ("ravb: document R8A77970 bindings")
Fixes: f231c4178a655b09 ("dt-bindings: net: renesas-ravb: Add
Hi Guenter,
thank you for your feedback!
> Subject: Re: [PATCH v7 1/3] watchdog: renesas_wdt: Add suspend/resume support
>
> On 03/02/2018 02:45 AM, Fabrizio Castro wrote:
> > Dear All,
> >
> > perhaps someone from this email thread could explain to me what's the actual
> > (general) expectation
Hi Thierry,
Here are two small fixes for the DT bindings of the Renesas Timer Pulse
Unit.
Changes compared to v1:
- Dropped DTS counterpart (applied),
- Add Acked-by, Reviewed-by.
Thanks for applying!
Geert Uytterhoeven (2):
dt-bindings: pwm: renesas-tpu: Correct example TPU regis
R8A73A4 (not R8A77A4) is R-Mobile APE6,
R8A7740 is R-Mobile (not R-Car) A1.
Signed-off-by: Geert Uytterhoeven
Acked-by: Simon Horman
Reviewed-by: Rob Herring
---
v2:
- Add Acked-by, Reviewed-by.
---
Documentation/devicetree/bindings/pwm/renesas,tpu-pwm.txt | 4 ++--
1 file changed, 2 inserti
The Timer Pulse Unit on R-Mobile A1 has registers that lie outside the
declared register block. Enlarge the register block size to fix this.
Signed-off-by: Geert Uytterhoeven
Reviewed-by: Simon Horman
Reviewed-by: Rob Herring
---
v2:
- Add Reviewed-by.
---
Documentation/devicetree/bindings/
On 03/02/2018 02:45 AM, Fabrizio Castro wrote:
Dear All,
perhaps someone from this email thread could explain to me what's the actual
(general) expectation from a system perspective (at resume) from the watchdog,
because I can see pitfalls whether 1) we simply start the watchdog at resume or
2)
Hi Niklas,
On Friday, 2 March 2018 02:42:18 EET Niklas Söderlund wrote:
> Hi Laurent,
>
> Thanks for your patch,
>
> All comments in this mail also applies to variant 2 of this patch as the
> difference between them are so small.
>
> First I got a question about your usage of __init thru out t
Hi Linus,
On Fri, Mar 2, 2018 at 1:39 PM, Linus Walleij wrote:
> On Fri, Mar 2, 2018 at 11:18 AM, Geert Uytterhoeven
> wrote:
>> The following changes since commit 7928b2cbe55b2a410a0f5c1f154610059c57b1b2:
>>
>> Linux 4.16-rc1 (2018-02-11 15:04:29 -0800)
>>
>> are available in the git reposito
On Fri, Mar 2, 2018 at 11:18 AM, Geert Uytterhoeven
wrote:
> Hi Linus,
>
> The following changes since commit 7928b2cbe55b2a410a0f5c1f154610059c57b1b2:
>
> Linux 4.16-rc1 (2018-02-11 15:04:29 -0800)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/ker
Hi Simon, Magnus,
This patch series disables CONFIG_EMBEDDED in shmobile_defconfig, which
stands in the way of using more sane defaults expressed in Kconfig
logic.
The first patch does a mandatory refresh of shmobile_defconfig as a
preparatory step/
The second patch actually disables CONF
- CONFIG_AEABI is enabled since commit 494609701e06a004 ("ARM: always
enable AEABI for ARMv6+"),
- CONFIG_SERIAL_SH_SCI_CONSOLE is enabled since commit
c5bb576d5e21e91a ("tty: serial: sh-sci: Hide serial console config
question"),
- CONFIG_SERIAL_SH_SCI_DMA is enabled since commit
CONFIG_EXPERT exposes too many config options that do not matter for
development. E.g. it prohibits using the default values for the various
SH_SCI options. However, CONFIG_EMBEDDED selects CONFIG_EXPERT, so it
cannot be disabled.
Hence disable CONFIG_EMBEDDED, and compensate for the loss of
CON
Document clearly which SoC this DTS applies to, to distinguish from
Salvator-XS boards equipped with other SoCs.
Signed-off-by: Geert Uytterhoeven
---
arch/arm64/boot/dts/renesas/r8a77965-salvator-xs.dts | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm64/boot/dts/rene
Hi Niklas,
Thank you for the patch.
On Friday, 2 March 2018 03:57:47 EET Niklas Söderlund wrote:
> Add the ability to process media device link change request. Link
s/request/requests/
> enabling is a bit complicated on Gen3, whether or not it's possible to
> enable a link depends on what other
Hi Niklas,
Thank you for the patch.
On Friday, 2 March 2018 03:57:45 EET Niklas Söderlund wrote:
> Each Gen3 SoC has a limited set of predefined routing possibilities for
> which CSI-2 device and channel can be routed to which VIN instance.
> Prepare to store this information in the struct rvin_i
Hi Niklas,
Thank you for the patch.
On Friday, 2 March 2018 03:57:40 EET Niklas Söderlund wrote:
> When the driver runs in media controller mode it should not directly
> control the subdevice instead userspace will be responsible for
> configuring the pipeline. To be able to run in this mode a di
Hi Niklas,
On Friday, 19 January 2018 02:46:03 EET Niklas Söderlund wrote:
> Hi Laurent,
>
> Thanks for your comments.
>
> Apart from the issue with the input API Hans pointed which indicates I
> need to keep that around until it's fixed in the framework I agree with
> all your comments but one.
Hi Niklas,
Thank you for the patch.
On Friday, 2 March 2018 03:57:38 EET Niklas Söderlund wrote:
> On Gen3 the CSI-2 routing is controlled by the VnCSI_IFMD register. One
> feature of this register is that it's only present in the VIN0 and VIN4
> instances. The register in VIN0 controls the routi
Hi Niklas,
Thank you for the patch.
On Friday, 2 March 2018 03:57:36 EET Niklas Söderlund wrote:
> Bus configuration will once the driver is extended to support Gen3
> contain information not specific to only the directly connected parallel
> subdevice. Move it to struct rvin_dev to show it's not
Hi Niklas,
Thank you for the patch.
On Friday, 2 March 2018 03:57:35 EET Niklas Söderlund wrote:
> Instead of caching the subdevice format each time the video device
> format is set read it directly when it's needed. As it turns out the
> format is only needed when figuring out the max rectangle
Hi Niklas,
Thank you for the patch.
On Friday, 2 March 2018 03:57:31 EET Niklas Söderlund wrote:
> There was never proper support in the VIN driver to deliver ALTERNATING
> field format to user-space, remove this field option. The problem is
> that ALTERNATING filed order requires the sequence nu
Dear All,
perhaps someone from this email thread could explain to me what's the actual
(general) expectation from a system perspective (at resume) from the watchdog,
because I can see pitfalls whether 1) we simply start the watchdog at resume or
2) we pick up from where we left.
If we have a syst
On Thu, Mar 01, 2018 at 06:28:29PM +0300, Sergei Shtylyov wrote:
> On 03/01/2018 12:54 PM, Simon Horman wrote:
>
> > Here's the set of 5 patches against Simon Horman's 'renesas.git' repo's
> > 'renesas-devel-20180227-v4.16-rc3' tag. We're adding the R8A77970
> > FCPVD/VSPD/
> > DU
On 3/2/2018 1:21 PM, Simon Horman wrote:
Here's the set of 5 patches against Simon Horman's 'renesas.git' repo's
'renesas-devel-20180227-v4.16-rc3' tag. We're adding the R8A77970 FCPVD/VSPD/
DU/LVDS device nodes and then describing the HDMI encoder connected to the LVDS
output (we're omitting th
Hi Mike, Stephen,
The following changes since commit 7928b2cbe55b2a410a0f5c1f154610059c57b1b2:
Linux 4.16-rc1 (2018-02-11 15:04:29 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/geert/renesas-drivers.git
tags/clk-renesas-for-v4.17-tag1
Hi Linus,
The following changes since commit 7928b2cbe55b2a410a0f5c1f154610059c57b1b2:
Linux 4.16-rc1 (2018-02-11 15:04:29 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/geert/renesas-drivers.git
tags/sh-pfc-for-v4.17-tag1
for you to f
2018-01-29 16:45 GMT+01:00 Ulrich Hecht :
> Both manufacturer and name variant.
>
> Signed-off-by: Ulrich Hecht
> ---
> Documentation/devicetree/bindings/eeprom/at24.txt | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/eeprom/at24.txt
> b/Documentation
Hi Niklas,
Thank you for the patch.
On Friday, 2 March 2018 03:57:41 EET Niklas Söderlund wrote:
> When the VIN driver is running in media centric mode (on Gen3) the
> colorspace is not retrieved from the video source instead the user is
> expected to set it as part of the format. There is no way
Hi Niklas,
Thank you for the patch.
On Friday, 2 March 2018 03:57:34 EET Niklas Söderlund wrote:
> Part of the format alignment and checking can be shared with the Gen3
> format handling. Break that part out to a separate function.
>
> Signed-off-by: Niklas Söderlund
> ---
> drivers/media/plat
Hi Niklas,
Thank you for the patch.
On Friday, 2 March 2018 03:57:32 EET Niklas Söderlund wrote:
> Remove over complicated logic to calculate the value for bytesperline
> and sizeimage that was carried over from the soc_camera port. There is
> no need to find the max value of bytesperline and siz
Hi Niklas,
Thank you for the patch.
On Friday, 2 March 2018 03:57:30 EET Niklas Söderlund wrote:
> If the field is not supported by the driver it should not try to keep
> the current field. Instead it should set it to a default fallback. Since
> trying a format should always result in the same st
Hi Niklas,
Thank you for the patch.
On Friday, 2 March 2018 03:57:21 EET Niklas Söderlund wrote:
> From: Fabrizio Castro
>
> Add compatible strings for r8a7743 and r8a7745. No driver change
> is needed as "renesas,rcar-gen2-vin" will activate the right code.
> However, it is good practice to do
Hi Niklas,
Thank you for the patch.
On Friday, 2 March 2018 03:57:20 EET Niklas Söderlund wrote:
> From: Fabrizio Castro
>
> Change the sorting of the part numbers from descending to ascending to
> match with other documentation.
>
> Signed-off-by: Fabrizio Castro
> Reviewed-by: Biju Das
> R
On Fri, Mar 2, 2018 at 9:20 AM, Geert Uytterhoeven wrote:
>
> On Thu, Mar 1, 2018 at 5:06 PM, Linus Walleij
> wrote:
>> On Mon, Feb 12, 2018 at 2:55 PM, Geert Uytterhoeven
>> wrote:
>>
>>> Since commit ab82fa7da4dce5c7 ("gpio: rcar: Prevent module clock disable
>>> when wake-up is enabled"), wh
Hello!
On 3/1/2018 9:17 PM, Fabrizio Castro wrote:
On R-Car Gen2 and RZ/G1 the watchdog IP clock needs to be always ON,
on R-Car Gen3 we power the IP down during suspend.
This commit adds suspend/resume support, so that the watchdog counting
"pauses" during suspend on all of the SoCs compatibl
Hi Linus,
On Thu, Mar 1, 2018 at 5:06 PM, Linus Walleij wrote:
> On Mon, Feb 12, 2018 at 2:55 PM, Geert Uytterhoeven
> wrote:
>
>> Since commit ab82fa7da4dce5c7 ("gpio: rcar: Prevent module clock disable
>> when wake-up is enabled"), when a GPIO is used for wakeup, the GPIO
>> block's module clo
On Tuesday 27 February 2018 11:22 AM, Yoshihiro Shimoda wrote:
> This patch adds support for r8a77965 (R-Car M3-N). This SoC has
> dedicated pins.
>
> Signed-off-by: Yoshihiro Shimoda
> ---
> Documentation/devicetree/bindings/phy/rcar-gen3-phy-usb2.txt | 2 ++
> drivers/phy/renesas/phy-rcar-ge
On Tuesday 27 February 2018 11:22 AM, Yoshihiro Shimoda wrote:
> This patch adds binding for r8a77965 (R-Car M3-N).
$subject should be dt-bindings: rcar-gen3-phy-usb3: Add binding for r8a77965
Thanks
Kishon
>
> Signed-off-by: Yoshihiro Shimoda
> ---
> Documentation/devicetree/bindings/phy/r
On Tue, Feb 27, 2018 at 1:56 PM, Ville Syrjala
wrote:
> From: Ville Syrjälä
>
> Currently we have a mix of static and dynamic information stored in
> the display info structure. That makes it rather difficult to repopulate
> the dynamic parts when a new EDID appears. Let's make life easier by
>
48 matches
Mail list logo