When Gen3 support is added to the driver more then chip id will be
different for the different Soc. To avoid a lot of if statements in the
code create a struct chip_info to contain this information.
Signed-off-by: Niklas Söderlund
Reviewed-by: Kieran
It was a bad idea to reset the crop and compose settings when a new
format is set. This would overwrite any crop/compose set by s_select and
cause unexpected behaviors, remove it. Also fold the reset helper in to
the only remaining caller.
Signed-off-by: Niklas Söderlund
Add the SoC specific information for Renesas r8a7796.
Signed-off-by: Niklas Söderlund
---
.../devicetree/bindings/media/rcar_vin.txt | 1 +
drivers/media/platform/rcar-vin/rcar-core.c| 64 ++
2 files changed, 65
Add the SoC specific information for Renesas r8a7795.
Signed-off-by: Niklas Söderlund
---
drivers/media/platform/rcar-vin/Kconfig | 2 +-
drivers/media/platform/rcar-vin/rcar-core.c | 145
2 files changed, 146
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 different set
of v4l2 operations needs to be used.
Add a new set of v4l2 operations to support the
In media controller mode all VIN instances needs to be part of the same
media graph. There is also a need to each VIN instance to know and in
some cases be able to communicate with other VIN instances.
Add a allocator framework where the first VIN instance to be probed
creates a shared data
On Gen3 the max supported width and height will be different from Gen2.
Move the limits to the struct rvin_info to prepare for Gen3 support.
Signed-off-by: Niklas Söderlund
Reviewed-by: Kieran Bingham
---
It is possible on Gen2 to change the registers controlling composing and
scaling while the stream is running. Is however not a good idea to do so
and could result in trouble. There are also no good reason to allow
this, remove immediate reflection in hardware registers from
vidioc_s_selection and
In preparation of refactoring the scaling code move the code regarding
scaling to to the top of the file to avoid the need to add forward
declarations. No code is changed in this commit only whole functions
moved inside the same file.
Signed-off-by: Niklas Söderlund
On Gen3 a media controller API needs to be used to allow userspace to
configure the subdevices in the pipeline instead of directly controlling
a single source subdevice, which is and will continue to be the mode of
operation on Gen2.
Prepare for these two modes of operation by adding a flag to
Part of the format aliment and checking can be shared with the Gen3
format handling. Break that part out to it's own function. While doing
this clean up the checking and add more checks.
Signed-off-by: Niklas Söderlund
---
Parse the VIN Gen3 OF graph and register all CSI-2 devices in the VIN
group common media device. Once all CSI-2 subdevice is added to the
common media device create links between them.
The parsing and registering CSI-2 subdevices with the v4l2 async
framework is a collaborative effort shared
Instead of caching the subdevice format each time the video device
format is set read it directly when its needed. As it turns out the
format is only needed when figuring out the max rectangle for cropping.
This simplify the code and makes it clearer what the source format is
used for.
Each Gen3 SoC has a limited set of predefined routing possibilities for
which CSI-2 device and virtual channel can be routed to which VIN
instance. Prepare to store this information in the struct rvin_info.
Signed-off-by: Niklas Söderlund
---
The procedure to start or stop streaming using the none MC single
subdevice and the MC graph and multiple subdevices are quiet different.
Create a new function to abstract which method is used based on which
mode the driver is running in and add logic to start the MC graph.
Signed-off-by: Niklas
Bus configuration will once the driver is extended to to support Gen3
contain information not specific to only the directly connected parallel
subdevice. Move it to struct rvin_info to show it's not always coupled
to the parallel subdevice.
Signed-off-by: Niklas Söderlund
Add the ability to process media device link change request. Link
enablement are a bit complicated on Gen3, if it's possible to enable a
link depends on what other links already are enabled. On Gen3 the 8 VIN
are split into two subgroups (VIN0-3 and VIN4-7) and from a routing
perspective these two
When running in media controller mode a media pad is needed, register
one. Also set the media bus format to CSI-2.
Signed-off-by: Niklas Söderlund
---
drivers/media/platform/rcar-vin/rcar-core.c | 23 ++-
Add the register needed to work with Gen3 hardware. This patch adds
the logic for how to work with the Gen3 hardware. More work is required
to enable the subdevice structure needed to configure capturing.
Signed-off-by: Niklas Söderlund
---
It was never proper support in the VIN driver to deliver ALTERNATING
field format to user-space, remove this field option. For sources using
this field format instead use the VIN hardware feature of combining the
fields to an interlaced format. This mode of operation was previously
the default
The logic to preserve the requested format width and height are too
complex and come from a premature optimization for Gen3. All Gen2 SoC
can scale and the Gen3 implementation will not use these functions at
all so simply preserve the width and hight when interacting with the
subdevice much like
Document the devicetree bindings for the CSI-2 inputs available on Gen3.
There is a need to add a custom property 'renesas,id' and to define
which CSI-2 input is described in which endpoint under the port@1 node.
This information is needed since there are a set of predefined routes
between each
Hi,
This series adds Gen3 VIN support to rcar-vin driver for Renesas r8a7795
and r8a7796. It is based on the media-tree.
The driver is tested on both Renesas H3 (r8a7795, ES1.x + ES2.0) and
M3-W (r8a7796) together with the rcar-csi2 driver (posted separately and
not yet upstream) and the
Hi Florian,
On Tue, Aug 22, 2017 at 8:49 PM, Florian Fainelli wrote:
> On 08/22/2017 11:37 AM, Geert Uytterhoeven wrote:
>> If an Ethernet device is used while the device is suspended, the system may
>> crash.
>>
>> E.g. on sh73a0/kzm9g and r8a73a4/ape6evm, the external
On Tue, Aug 22, 2017 at 08:37:26PM +0200, Geert Uytterhoeven wrote:
Hi Geert
quieten. Has an E in the middle.
Otherwise this patch looks reasonable.
Andrew
On Tue, Aug 22, 2017 at 10:00 AM, Niklas Söderlund
wrote:
> Hi Rob,
>
> On 2017-08-22 09:49:35 -0500, Rob Herring wrote:
>> On Mon, Aug 21, 2017 at 7:19 PM, Niklas Söderlund
>> wrote:
>> > Using CONFIG_OF_DYNAMIC=y uncovered
Hi Naman,
On 2017-08-23 00:15:41 +0530, Naman Jain wrote:
> Hi Niklas,
>
> adv7281m driver powers up the CSI transmitter in s_power(), which is
> called before setting up of D-PHY layer of R-Car CSI-2 Receiver.
> I shifted the part of code which enables CSI transmitter in adv7281m
> (Low Power
On 08/22/2017 11:37 AM, Geert Uytterhoeven wrote:
> Hi all,
>
> If an Ethernet device is used while the device is suspended, the system may
> crash.
>
> E.g. on sh73a0/kzm9g and r8a73a4/ape6evm, the external Ethernet chip is
> driven by a PM controlled clock. If the Ethernet registers are
Hi Niklas,
adv7281m driver powers up the CSI transmitter in s_power(), which is
called before setting up of D-PHY layer of R-Car CSI-2 Receiver.
I shifted the part of code which enables CSI transmitter in adv7281m
(Low Power state to High Speed state) to s_stream() -
if (state->chip_info->flags
During system resume, the PHY state machine may be run from the
workqueue while the Ethernet device (and its PHY) are still suspended,
which may lead to a system crash.
E.g. on sh73a0/kzm9g and r8a73a4/ape6evm, the external Ethernet chip is
driven by a PM controlled clock. If the Ethernet
Hi all,
If an Ethernet device is used while the device is suspended, the system may
crash.
E.g. on sh73a0/kzm9g and r8a73a4/ape6evm, the external Ethernet chip is
driven by a PM controlled clock. If the Ethernet registers are accessed
while the clock is not running, the system will
If the network interface is kept running during suspend, the net core
may call net_device_ops.ndo_start_xmit() while the Ethernet device is
still suspended, which may lead to a system crash.
E.g. on sh73a0/kzm9g and r8a73a4/ape6evm, the external Ethernet chip is
driven by a PM controlled clock.
Add support for the bq32000 RTC to the iwg22m device tree.
Signed-off-by: Fabrizio Castro
---
This patch has some dependency:
* [1/2] ARM: dts: iwg22m: Add iWave RZG1E SODIMM SOM -
https://patchwork.kernel.org/patch/9901619/
* [2/2] ARM: dts: iwg22d-sodimm:
Hello Simon,
> From: Biju Das [mailto:biju@bp.renesas.com]
> Sent: 15 August 2017 11:54
>
> Hello,
>
> This series aims to add iWave RZ/G1E (R8A7745) based RainboW-G22M-SM
> SODIMM SoM and RainboW-G22D board support.
>
> This series has been tested against linux-next tag next-20170815 as
Add I2C[0-5] devices to the r8a7745 device tree.
Signed-off-by: Fabrizio Castro
---
arch/arm/boot/dts/r8a7745.dtsi | 93 ++
1 file changed, 93 insertions(+)
diff --git a/arch/arm/boot/dts/r8a7745.dtsi
Hi Rob,
On 2017-08-22 09:49:35 -0500, Rob Herring wrote:
> On Mon, Aug 21, 2017 at 7:19 PM, Niklas Söderlund
> wrote:
> > Using CONFIG_OF_DYNAMIC=y uncovered an imbalance in the usecount of the
> > node being passed to of_fwnode_graph_get_port_parent().
Hi Rob,
On Tue, Aug 22, 2017 at 4:49 PM, Rob Herring wrote:
> On Mon, Aug 21, 2017 at 7:19 PM, Niklas Söderlund
> wrote:
>> Using CONFIG_OF_DYNAMIC=y uncovered an imbalance in the usecount of the
>> node being passed to
On Mon, Aug 21, 2017 at 7:19 PM, Niklas Söderlund
wrote:
> Using CONFIG_OF_DYNAMIC=y uncovered an imbalance in the usecount of the
> node being passed to of_fwnode_graph_get_port_parent(). Preserve the
> usecount by using of_get_parent() instead of
The DU is already wired up to the HDMI encoder, all we need to do is
enable it.
Signed-off-by: Laurent Pinchart
---
arch/arm64/boot/dts/renesas/ulcb.dtsi | 4
1 file changed, 4 insertions(+)
This patch has been tested on the M3-W ULCB in Magnus'
On Mon, Aug 21, 2017 at 02:53:35PM +0900, Magnus Damm wrote:
> From: Magnus Damm
>
> Extend the driver to make use of iommu_device_sysfs_add()/remove()
> functions to hook up initial sysfs support.
>
> Suggested-by: Joerg Roedel
> Signed-off-by:
Document APMU and SMP enable method for RZ/G1E (also known as
r8a7745) SoC.
Signed-off-by: Fabrizio Castro
---
Documentation/devicetree/bindings/power/renesas,apmu.txt | 1 +
1 file changed, 1 insertion(+)
diff --git
On Wed, Aug 16, 2017 at 1:12 PM, Biju Das wrote:
> Renesas RZ/G1E (R8A7745) SoC GPIO blocks are identical to the R-Car Gen2
> family. Add support for its GPIO controllers.
>
> Signed-off-by: Biju Das
Patch applied with the ACKs
Yours,
Linus
On Wednesday, August 16, 2017 5:25:18 AM CEST Viresh Kumar wrote:
> On 11-08-17, 17:36, Simon Horman wrote:
> > From: Khiem Nguyen
> >
> > This patch adds the r8a7796 support the generic cpufreq driver
> > by adding an appropriate compat string. This is in
On Thu, Aug 17, 2017 at 11:30 AM, Geert Uytterhoeven
wrote:
> Hi Linus,
>
> The following changes since commit 5771a8c08880cdca3bfb4a3fc6d309d6bba20877:
>
> Linux v4.13-rc1 (2017-07-15 15:22:10 -0700)
>
> are available in the git repository at:
>
>
On 08/22/2017 12:10 PM, Chris Paterson wrote:
From: Biju Das [mailto:biju@bp.renesas.com]
Sent: 14 August 2017 10:53
Signed-off-by: Biju Das
---
v1-->v2
Corrected the resets property for i2c6 device node.
Are you happy with this version of the patch?
Or is
Hello!
On 08/14/2017 05:15 PM, Geert Uytterhoeven wrote:
From: Wolfram Sang [mailto:w...@the-dreams.de]
Sent: 10 August 2017 12:24
+i2c6: i2c@e60b {
I'd use iic0 as the label.
Sergei: I assume you meant "iic3"? ;-)
After having a look at the manual, yes. :-)
On 21 August 2017 at 14:25, Biju Das wrote:
> Add support for r8a7743/5 SoC. Renesas RZ/G1[ME] (R8A7743/5) SDHI
> is identical to the R-Car Gen2 family.
>
> Signed-off-by: Biju Das
Thanks, applied for next!
Kind regards
Uffe
> ---
> v1->v2
>
> -Original Message-
> From: Simon Horman [mailto:ho...@verge.net.au]
> Sent: 22 August 2017 09:08
> To: Biju Das
> Cc: Rob Herring ; Mark Rutland
> ; Magnus Damm ;
> Russell King
> -Original Message-
> From: Simon Horman [mailto:ho...@verge.net.au]
> Sent: 22 August 2017 09:03
> To: Biju Das
> Cc: Rob Herring ; Mark Rutland
> ; Magnus Damm ;
> Chris Paterson
Make these const as they are only stored in a const field of a
mdiobb_ctrl structure.
Signed-off-by: Bhumika Goyal
---
drivers/net/ethernet/renesas/ravb_main.c | 2 +-
drivers/net/ethernet/renesas/sh_eth.c| 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff
On Fri, Aug 18, 2017 at 05:58:08PM +0100, Biju Das wrote:
> Signed-off-by: Biju Das
> ---
> This patch tested against renesas-dev tag renesas-devel-20170815-v4.13-rc5
Thanks, I have applied this for v4.15.
There was some fuzz when applying this patch.
Please check that
On Fri, Aug 18, 2017 at 03:56:01PM +0100, Biju Das wrote:
> Describe GPIO blocks in the R8A7745 device tree.
>
> Signed-off-by: Biju Das
> ---
> This patch has run time dependency on the below patch
> [PATCH/RFC] gpio: rcar: add gen[123] fallback compatibility strings
>
On Mon, Aug 14, 2017 at 12:49:46PM +0100, Biju Das wrote:
> This series aims to add SDHI support for r8a7743 SoC.
>
> This series has been compiled and tested against renesas-dev tag
> renesas-devel-20170814-v4.13-rc5.
>
> There is no compile time dependencies.It has run time dependency on
>
On Mon, Aug 21, 2017 at 02:43:05PM +0200, Wolfram Sang wrote:
> On Mon, Aug 21, 2017 at 01:25:11PM +0100, Biju Das wrote:
> > Add support for r8a7743/5 SoC. Renesas RZ/G1[ME] (R8A7743/5) SDHI
> > is identical to the R-Car Gen2 family.
> >
> > Signed-off-by: Biju Das
>
>
On Mon, Aug 21, 2017 at 12:25:21PM +0300, Laurent Pinchart wrote:
> Hi Simon,
>
> On Thursday, 13 July 2017 14:21:10 EEST Laurent Pinchart wrote:
> > The r8a7796 has a single FDP1 instance.
> >
> > Signed-off-by: Laurent Pinchart
> > Reviewed-by:
On Fri, Aug 04, 2017 at 03:23:00PM +0200, Simon Horman wrote:
> From: Takeshi Kihara
>
> This patch adds Z2 clock for r8a7795 SoC.
>
> Signed-off-by: Takeshi Kihara
It seems that this is missing:
Signed-off-by: Simon Horman
> Btw, whats about HS400 support for the eMMC? As the eMMC is often the 'mass
> storage' device for the rootfs, the eMMC performance will have a direct
> influence to the overall system performance.
Sure, I know. We finally have Gen3 SDHI DMA upstream and SDR104 seems to
be stable as well (we
On 22.08.2017 08:56, Wolfram Sang wrote:
I'm not an expert on this, does SDR104 need 1.8V?
To my understanding, sd-uhs-sdr50 is the max speed for 3.3V?
Nope, everything with SDR* needs 1.8V. So, classic "highspeed" is the
maximum for your slot.
I ask because on my custom board the
Add SDHIx support for ES2.0. Taken from the Renesas BSP
https://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas-bsp.git/tree/drivers/pinctrl/sh-pfc/pfc-r8a7795.c
Signed-off-by: Dirk Behme
---
Note: Patch is generated against renesas-drivers-2017-08-16-v4.13-rc5
> I'm not an expert on this, does SDR104 need 1.8V?
>
> To my understanding, sd-uhs-sdr50 is the max speed for 3.3V?
Nope, everything with SDR* needs 1.8V. So, classic "highspeed" is the
maximum for your slot.
> I ask because on my custom board the hardware guys gave us 3.3V, only, for
> the
Hi Dirk
> Add SDHIx support for ES2.0. Taken from the Renesas BSP
>
> https://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas-bsp.git/tree/drivers/pinctrl/sh-pfc/pfc-r8a7795.c
>
> Signed-off-by: Dirk Behme
> ---
(snip)
> @@ -3182,7 +3453,7 @@ static const char *
On 21.08.2017 15:47, Wolfram Sang wrote:
It works, now :)
Great!
tmio_mmc_init_ocr()
fails (silently!). And with this the whole RCar3 SDHI, without any error
message.
I'll check next week about an error message there.
Many thanks for your help!
You're welcome. If you want, you can
Add SDHIx support for ES2.0. Taken from the Renesas BSP
https://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas-bsp.git/tree/drivers/pinctrl/sh-pfc/pfc-r8a7795.c
Signed-off-by: Dirk Behme
---
Note: Patch is generated against renesas-drivers-2017-08-16-v4.13-rc5
63 matches
Mail list logo