The new -e command line option allows selecting the exporter between the
V4L2 and DRM side. DRM is used as the exporter by default.
Signed-off-by: Laurent Pinchart
---
v4l2-drm-example/dmabuf-sharing.c | 99 +++
1 file changed, 89 insertions(+), 10 deletions(-
Hi Laurent,
On 15.11.2017 10:00, Laurent Pinchart wrote:
> The new -e command line option allows selecting the exporter between the
> V4L2 and DRM side. DRM is used as the exporter by default.
>
> Signed-off-by: Laurent Pinchart
> ---
> v4l2-drm-example/dmabuf-sharing.c | 99
> +
Rename CEU clock to match the new platform driver name used in Migo-R.
There are no other sh7722 based devices Migo-R apart, so we can safely
rename this.
Signed-off-by: Jacopo Mondi
---
arch/sh/kernel/cpu/sh4a/clock-sh7722.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/a
Add Capture Engine Unit (CEU) node to device tree.
Signed-off-by: Jacopo Mondi
---
arch/arm/boot/dts/r7s72100.dtsi | 12 ++--
1 file changed, 10 insertions(+), 2 deletions(-)
diff --git a/arch/arm/boot/dts/r7s72100.dtsi b/arch/arm/boot/dts/r7s72100.dtsi
index 4ed12a4..683d459 100644
---
Migo-R platform uses sh_mobile_ceu camera driver, which is now being
replaced by a proper V4L2 camera driver named 'renesas-ceu'.
Move Migo-R platform to use the v4l2 renesas-ceu camera driver
interface and get rid of soc_camera defined components used to register
sensor drivers.
Also, memory for
Add driver for Renesas Capture Engine Unit (CEU).
The CEU interface supports capturing 'data' (YUV422) and 'images'
(NV[12|21|16|61]).
This driver aims to replace the soc_camera based sh_mobile_ceu one.
Tested with ov7670 camera sensor, providing YUYV_2X8 data on Renesas RZ
platform GR-Peach.
T
Add renesas-ceu header file.
Do not remove the existing sh_mobile_ceu.h one as long as the original
driver does not go away.
Signed-off-by: Jacopo Mondi
---
include/media/drv-intf/renesas-ceu.h | 23 +++
1 file changed, 23 insertions(+)
create mode 100644 include/media/drv-
Copy the soc_camera based driver in v4l2 sensor driver directory.
This commit just copies the original file without modifying it.
Signed-off-by: Jacopo Mondi
---
drivers/media/i2c/ov772x.c | 1124
1 file changed, 1124 insertions(+)
create mode 100644
Remove soc_camera framework dependencies from ov772x sensor driver.
- Handle clock directly
- Register async subdevice
- Add platform specific enable/disable functions
- Adjust build system
This commit does not remove the original soc_camera based driver.
Signed-off-by: Jacopo Mondi
---
drivers
Copy the soc_camera based driver in v4l2 sensor driver directory.
This commit just copies the original file without modifying it.
Signed-off-by: Jacopo Mondi
---
drivers/media/i2c/tw9910.c | 999 +
1 file changed, 999 insertions(+)
create mode 100644
Hello,
this series implementes a modern V4L2 driver for Renesas Capture Engine
Unit (CEU). CEU is currently supported by the soc_camera based driver
drivers/media/platform/soc_camera/sh_mobile_ceu_camera.c
The driver supports capturing images in planar formats (NV12/21 and NV16/61)
and non-plan
Remove soc_camera framework dependencies from tw9910 sensor driver.
- Handle clock directly
- Register async subdevice
- Add platform specific enable/disable functions
- Adjust build system
This commit does not remove the original soc_camera based driver.
Signed-off-by: Jacopo Mondi
---
drivers
Add bindings documentation for Renesas Capture Engine Unit (CEU).
Signed-off-by: Jacopo Mondi
---
.../devicetree/bindings/media/renesas,ceu.txt | 87 ++
1 file changed, 87 insertions(+)
create mode 100644 Documentation/devicetree/bindings/media/renesas,ceu.txt
diff --g
Hi Jacopo,
A couple of minor language fixups inline.
On 15/11/17 10:55, Jacopo Mondi wrote:
> Add bindings documentation for Renesas Capture Engine Unit (CEU).
>
> Signed-off-by: Jacopo Mondi
> ---
> .../devicetree/bindings/media/renesas,ceu.txt | 87
> ++
> 1 file ch
Hi Jacopo,
Thanks for the patchset. Please see my comments below.
On Wed, Nov 15, 2017 at 11:55:54AM +0100, Jacopo Mondi wrote:
> Add bindings documentation for Renesas Capture Engine Unit (CEU).
>
> Signed-off-by: Jacopo Mondi
> ---
> .../devicetree/bindings/media/renesas,ceu.txt | 87
>
Hi Jacopo,
On Wed, Nov 15, 2017 at 11:55:55AM +0100, Jacopo Mondi wrote:
> Add renesas-ceu header file.
>
> Do not remove the existing sh_mobile_ceu.h one as long as the original
> driver does not go away.
Hmm. This isn't really not about not removing a file but adding a new one.
Do you really n
Hi Jacopo,
Could you remove the original driver and send the patch using git
send-email -C ? That way a single patch would address converting it to a
proper V4L2 driver as well as move it to the correct location. The changes
would be easier to review that way since then, well, it'd be easier to se
Hi Wolfram,
On Tue, Nov 14, 2017 at 11:55 PM, Wolfram Sang
wrote:
> Documentation/timers/timers-howto.txt recommends to use usleep_range for
> delays 1-20ms. Let's adhere to it. No need for messing with HZ and still
> do busy looping these days.
>
> Signed-off-by: Wolfram Sang
> ---
>
> Here is
Hi Jacopo,
CC devicetree folks
On Wed, Nov 15, 2017 at 11:55 AM, Jacopo Mondi
wrote:
> Add bindings documentation for Renesas Capture Engine Unit (CEU).
>
> Signed-off-by: Jacopo Mondi
> ---
> .../devicetree/bindings/media/renesas,ceu.txt | 87
> ++
> 1 file changed,
Hi Jacopo,
On Wed, Nov 15, 2017 at 11:55 AM, Jacopo Mondi
wrote:
> Rename CEU clock to match the new platform driver name used in Migo-R.
>
> There are no other sh7722 based devices Migo-R apart, so we can safely
> rename this.
>
> Signed-off-by: Jacopo Mondi
> ---
> arch/sh/kernel/cpu/sh4a/clo
On Fri, Nov 10, 2017 at 10:58:43PM +0100, Marek Vasut wrote:
> From: Kazufumi Ikeda
>
> This adds the suspend/resume supports for pcie-rcar. The resume handler
> reprograms the hardware based on the software state kept in specific
> device structures. Also it doesn't need to save any registers.
>
On Mon, Nov 13, 2017 at 07:11:54PM +0100, Marek Vasut wrote:
> On 11/13/2017 08:03 AM, Simon Horman wrote:
> > On Fri, Nov 10, 2017 at 10:58:40PM +0100, Marek Vasut wrote:
> >> Just clean up the macros in the RCar PCI driver, no functional change.
> >
> > Could you describe the cleanup in slightly
On Tue, Nov 14, 2017 at 09:59:03AM +, Biju Das wrote:
> Add support for r8a7743. The Renesas RZ/G1M(R8A7743)PCIe controller
> is identical to the R-Car Gen2 family.
>
> No driver change is needed due to the fallback compatible value
> "renesas,pcie-rcar-gen2".
> Adding the SoC-specific compati
On 14/11/17 17:08, Jacopo Mondi wrote:
On SH4 architecture, with SPARSEMEM memory model, translating page to
pfn hangs the CPU. Post-pone translation to pfn after
dma_mmap_from_dev_coherent() function call as it succeeds and make page
translation not necessary.
This patch was suggested by Lauren
Hi Simon,
On Tue, Nov 14, 2017 at 9:34 AM, Simon Horman
wrote:
> Support the r8a77970 (R-Car V3M) and r8a77995 (R-Car D3) IPMMUs by sharing
> feature flags with r8a7795 (R-Car H3) and r8a7796 (R-Car M3-W). Also update
> IOMMU_OF_DECLARE to hook up the compat strings.
>
> Based on work for the r8a
Hi Sakari,
thanks for review!
On Wed, Nov 15, 2017 at 02:45:51PM +0200, Sakari Ailus wrote:
> Hi Jacopo,
>
> Could you remove the original driver and send the patch using git
> send-email -C ? That way a single patch would address converting it to a
> proper V4L2 driver as well as move it to th
Hi Simon,
On Fri, Nov 10, 2017 at 2:25 PM, Simon Horman
wrote:
> From: Magnus Damm
>
> Add r8a7795 IPMMU nodes and keep all disabled by default.
>
> This includes all IPMMU devices for r8a7795 ES2.0. Those
> not present in r8a7795 ES1.x are removed from the DT for those
> SoCs using delete-node.
The datasheet was a bit vague, but after consultation with HW designers,
we came to the conclusion that we should set the SCP bit always when
dealing only with the ICE bit. A set SCP bit is ignored, and thus fine,
a cleared one may trigger STOP on the bus.
Signed-off-by: Wolfram Sang
---
Jacopo:
On Fri, Nov 10, 2017 at 2:25 PM, Simon Horman
wrote:
> From: Magnus Damm
>
> Add r8a7795 ES1.x IPMMU nodes and keep all disabled by default.
>
> This is a follow-up to a patch that adds IPMMU device nodes that
> are common to r8a7795 ES1.x and ES2.0
>
> Power domains are omitted as they appear to
From: Kieran Bingham
Hi Niklas,
Some minor updates to the 8camera-status tool, and a speed up fix for the
vin-tests core function 'mc_get_dev()'.
Kieran Bingham (3):
tools: 8camera-status: Fix write failure mis-allocations
tools: 8camera-status: Expand to 9 cameras
vin-tests: Refactor mc_
From: Kieran Bingham
The 8th camera has an address conflict on the Salvator-X.
As such it has been moved to the right by one address,
Include this '9th' camera in the reporting status
Signed-off-by: Kieran Bingham
---
tools/8camera-status | 10 +-
1 file changed, 5 insertions(+), 5 del
From: Kieran Bingham
Debug prints of the max9271_write call are appearing in the failure counts.
Fix the 'catcher' so that it is more specific to the failure
Signed-off-by: Kieran Bingham
---
tools/8camera-status | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/8camer
From: Kieran Bingham
Rather that using shell parsing of each file when looking for a device
node, use a combination of grep and sed to identify the device.
This is a remarkable speed optimisation for this code segment.
Signed-off-by: Kieran Bingham
---
scripts/vin-tests.sh | 14 +++---
Hi Simon,
On Fri, Nov 10, 2017 at 2:26 PM, Simon Horman
wrote:
> From: Magnus Damm
>
> Add r8a7796 IPMMU nodes and keep all disabled by default.
>
> Signed-off-by: Magnus Damm
> Signed-off-by: Simon Horman
> ---
> v2 [Simon Horman]
> * Drop mostly redundant comments from nodes
> * Add power do
> > I did mainly test the insert/eject cycle because powering up the cards
> > seemed to trigger most delays. Transferring data did not cause any calls
> > to mmc_delay() for me. Please let me know if someone knows a test pattern
> > which should be included before applying this change.
>
> JFTR,
On Fri, Sep 29, 2017 at 03:08:53PM +0200, Ulrich Hecht wrote:
> HSCIF has facilities that allow changing the timeout after which an RX
> interrupt is triggered even if the FIFO is not filled. This patch allows
> changing the default (15 bits of silence) using the existing sysfs
> attribute "rx_fifo
On Fri, Sep 29, 2017 at 03:08:54PM +0200, Ulrich Hecht wrote:
> HSCIF has facilities that allow moving the RX sampling point by between
> -8 and 7 sampling cycles (one sampling cycles equals 1/15 of a bit
> by default) to improve the error margin in case of slightly mismatched
> bit rates between s
Required for I2C0 operation.
Signed-off-by: Ulrich Hecht
---
drivers/pinctrl/sh-pfc/pfc-r8a77995.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/pinctrl/sh-pfc/pfc-r8a77995.c
b/drivers/pinctrl/sh-pfc/pfc-r8a77995.c
index 89b7541..2c9a71a 100644
--- a/drivers/pinctrl/sh-pfc/pfc-r
R8A77995's SYS-DMAC is R-Car Gen3-compatible.
Signed-off-by: Ulrich Hecht
---
Documentation/devicetree/bindings/dma/renesas,rcar-dmac.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/dma/renesas,rcar-dmac.txt
b/Documentation/devicetree/bindings/dma/renes
Same as other Gen3 SoCs.
Signed-off-by: Ulrich Hecht
---
drivers/i2c/busses/i2c-rcar.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/i2c/busses/i2c-rcar.c b/drivers/i2c/busses/i2c-rcar.c
index 15d764a..9469f01 100644
--- a/drivers/i2c/busses/i2c-rcar.c
+++ b/drivers/i2c/busses/i2c-
Defines R-Car D3 I2C controllers 0-3.
Signed-off-by: Ulrich Hecht
---
arch/arm64/boot/dts/renesas/r8a77995.dtsi | 64 +++
1 file changed, 64 insertions(+)
diff --git a/arch/arm64/boot/dts/renesas/r8a77995.dtsi
b/arch/arm64/boot/dts/renesas/r8a77995.dtsi
index 5fa757
Differs from other Gen3 SoCs in that each controller only supports eight
channels.
Signed-off-by: Ulrich Hecht
---
arch/arm64/boot/dts/renesas/r8a77995.dtsi | 72 +++
1 file changed, 72 insertions(+)
diff --git a/arch/arm64/boot/dts/renesas/r8a77995.dtsi
b/arch/arm6
Tested on Draak.
Signed-off-by: Ulrich Hecht
---
arch/arm64/boot/dts/renesas/r8a77995.dtsi | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arm64/boot/dts/renesas/r8a77995.dtsi
b/arch/arm64/boot/dts/renesas/r8a77995.dtsi
index 04a392a..5fa7572 100644
--- a/arch/arm64/boot/dts/renesas/
Enables EEPROM on I2C0 on the Draak board.
Signed-off-by: Ulrich Hecht
---
arch/arm64/boot/dts/renesas/r8a77995-draak.dts | 17 +
1 file changed, 17 insertions(+)
diff --git a/arch/arm64/boot/dts/renesas/r8a77995-draak.dts
b/arch/arm64/boot/dts/renesas/r8a77995-draak.dts
index
Hi!
This adds DT nodes and bindings for the SYS-DMAC on R-Car D3 and enables
the DMAs for SCIF2.
CU
Uli
Ulrich Hecht (3):
arm64: dts: r8a77995: add SYS-DMAC nodes
arm64: dts: r8a7795: add DMA for SCIF2
dmaengine: rcar-dmac: Document R-Car D3 bindings
.../devicetree/bindings/dma/renesas,
Hi!
This adds I2C controllers to the D3 device tree and enables I2C busses 0
and 1 on the Draak board. (I2C2 is not connected on that board.)
Includes missing pins, DMA support and the Draak's serial EEPROM.
CU
Uli
Ulrich Hecht (6):
pinctrl: sh-pfc: r8a77995: add missing pins SCL0 and SDA0 t
No devices to add, I2C1 has an external connector only.
Signed-off-by: Ulrich Hecht
---
arch/arm64/boot/dts/renesas/r8a77995-draak.dts | 11 +++
1 file changed, 11 insertions(+)
diff --git a/arch/arm64/boot/dts/renesas/r8a77995-draak.dts
b/arch/arm64/boot/dts/renesas/r8a77995-draak.dts
R-Car D3 has only one SDHI controller.
Signed-off-by: Ulrich Hecht
---
arch/arm64/boot/dts/renesas/r8a77995.dtsi | 12
1 file changed, 12 insertions(+)
diff --git a/arch/arm64/boot/dts/renesas/r8a77995.dtsi
b/arch/arm64/boot/dts/renesas/r8a77995.dtsi
index b3113003..89cb32e 100644
Hi!
This integrates the SDHI hardware on R-Car D3 and enables the Draak board's
eMMC drive. Includes whitelisting the internal DMAC on D3.
CU
Uli
Ulrich Hecht (4):
mmc: renesas_sdhi: enable R-Car D3 (r8a77995) support
arm64: dts: r8a77995: Add SDHI (MMC) support
arm64: dts: r8a77995: draa
Adds bindings for the R-Car D3 SoC's SDHI IP.
Signed-off-by: Ulrich Hecht
---
Documentation/devicetree/bindings/mmc/tmio_mmc.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/mmc/tmio_mmc.txt
b/Documentation/devicetree/bindings/mmc/tmio_mmc.txt
index 3c67
The single SDHI controller is connected to eMMC.
Signed-off-by: Ulrich Hecht
---
arch/arm64/boot/dts/renesas/r8a77995-draak.dts | 44 ++
1 file changed, 44 insertions(+)
diff --git a/arch/arm64/boot/dts/renesas/r8a77995-draak.dts
b/arch/arm64/boot/dts/renesas/r8a77995-d
R-Car D3 (R8A77995) SoC has a R-Car Gen3-compatible I2C controller.
Signed-off-by: Ulrich Hecht
---
Documentation/devicetree/bindings/i2c/i2c-rcar.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/i2c/i2c-rcar.txt
b/Documentation/devicetree/bindings/i2c/i
Adds compatible string and whitelists for internal DMAC implementation.
Signed-off-by: Ulrich Hecht
---
drivers/mmc/host/renesas_sdhi_internal_dmac.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/mmc/host/renesas_sdhi_internal_dmac.c
b/drivers/mmc/host/renesas_sdhi_internal_dmac
Hi Wolfram,
On Wed, Nov 15, 2017 at 4:06 PM, Wolfram Sang wrote:
> On Fri, Sep 29, 2017 at 03:08:53PM +0200, Ulrich Hecht wrote:
>> HSCIF has facilities that allow changing the timeout after which an RX
>> interrupt is triggered even if the FIFO is not filled. This patch allows
>> changing the de
> No need to resend, see commit fa2abb03637a5528 ("serial: sh-sci: Support
> for variable HSCIF hardware RX timeout") in today's upstream.
In deed. Nice!
signature.asc
Description: PGP signature
When matching and registering a sub-device from a sub-notifier use the
v4l2_device from the root parent notifier. Using the v4l2_dev stored in
the sub-notifier itself is incorrect as it might not be set.
This can be demonstrated by unbinding and rebinding the adv748x driver
and observing that it f
Hi,
I just noticed I made a small mistake in this patch, see bellow. I will
send out a new version in a few days with this fix included but I don't
want to spam the list too much so I give it a few more days if there is
any other feedback.
On 2017-11-11 01:25:26 +0100, Niklas Söderlund wrote:
On Mon, Nov 13, 2017 at 10:23 PM, Sergei Shtylyov
wrote:
> Describe all 6 GPIO controllers in the R8A77970 device tree.
>
> Signed-off-by: Sergei Shtylyov
Reviewed-by: Geert Uytterhoeven
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia
On Mon, Nov 13, 2017 at 10:23 PM, Sergei Shtylyov
wrote:
> Specify EtherAVB PHY IRQ in the Eagle board's device tree, now that we
> have the GPIO support (previously phylib had to resort to polling).
>
> Signed-off-by: Sergei Shtylyov
Reviewed-by: Geert Uytterhoeven
Gr{oetje,eeting}s,
Hi Fabrizio,
On Tue, Nov 14, 2017 at 4:41 PM, Fabrizio Castro
wrote:
> This patch adds can_clk function to r8a7743/r8a7791 which is cleaner,
> and allows for independent configuration.
> We keep the can_clk* pins definitions from within can0_groups and
> can1_groups for uniformity and backwards c
Hi Fabrizio,
On Tue, Nov 14, 2017 at 4:41 PM, Fabrizio Castro
wrote:
> This patch adds can_clk function to r8a7745/r8a7794 which is cleaner,
> and allows for independent configuration.
> We keep the can_clk* pins definitions from within can0_groups and
> can1_groups for uniformity and backwards c
Hi Sergei,
On Tue, Nov 14, 2017 at 7:00 PM, Sergei Shtylyov
wrote:
> On 11/14/2017 11:44 AM, Geert Uytterhoeven wrote:
>>> Add the (previously omitted) EtherAVB pin data to the Eagle board's
>>> device tree.
>>> --- renesas.orig/arch/arm64/boot/dts/renesas/r8a77970-eagle.dts
>>> +++ renesas/arch
Hi Kieran,
Thanks for your patch, applied.
On 2017-11-15 14:38:29 +, Kieran Bingham wrote:
> From: Kieran Bingham
>
> Debug prints of the max9271_write call are appearing in the failure counts.
>
> Fix the 'catcher' so that it is more specific to the failure
>
> Signed-off-by: Kieran Bing
Hi Kieran,
Thanks for your patch, applied.
On 2017-11-15 14:38:30 +, Kieran Bingham wrote:
> From: Kieran Bingham
>
> The 8th camera has an address conflict on the Salvator-X.
> As such it has been moved to the right by one address,
> Include this '9th' camera in the reporting status
>
> S
Hi Vladimir,
On Wed, Nov 8, 2017 at 1:21 PM, Vladimir Barinov
wrote:
> This supports USB2 PHY channel #0 on ULCB Kingfisher board
>
> The dedicated USB0_PWEN pin is used to control CN13 VBUS source from U43
> power supply.
> MAX3355 can also provide VBUS, hence it should be disabled via OTG_OFFVB
Hi Vladimir,
On Wed, Nov 8, 2017 at 2:06 PM, Vladimir Barinov
wrote:
> Adds the pfc node for USB3.0 channel 0.
>
> Signed-off-by: Vladimir Barinov
> ---
> arch/arm64/boot/dts/renesas/ulcb-kf.dtsi | 8
> 1 file changed, 8 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/renesas/ulcb-k
Hi Kieran,
Thanks for your patch.
Unfortunately I experience some problems with this patch.
On 2017-11-15 14:38:31 +, Kieran Bingham wrote:
> From: Kieran Bingham
>
> Rather that using shell parsing of each file when looking for a device
> node, use a combination of grep and sed to identif
On Wed, Nov 8, 2017 at 2:09 PM, Vladimir Barinov
wrote:
> ULCB-KF has a USB2.0 dual-role channel (CN13).
> This adds dr_mode property for USB2.0 channel 0 (EHCI/OHCI and HS-USB)
> as "otg".
>
> Signed-off-by: Vladimir Barinov
Reviewed-by: Geert Uytterhoeven
Gr{oetje,eeting}s,
Hi Wolfram,
On Wed, Nov 15, 2017 at 12:06 AM, Wolfram Sang wrote:
> here is a topic branch for renesas-drivers removing calls to udelay() in
> both, TMIO core and the MMC core itself. I hope they land upstream in
> v4.16. Would be nice to get them boot tested via renesas-drivers. The
> test page
5:22:49 +1000)
>
> are available in the git repository at:
>
> git://linuxtv.org/pinchartl/media.git drm-du-iommu-v1-20171115
>
> for you to fetch changes up to 6cb711c0fabae1101bfde1c8dce0dfd992822f6b:
>
> drm: rcar-du: Allow importing non-contiguous dma-buf with VSP (20
videobuf2 core reports an error when not all buffers have been returned
to the framework:
drivers/media/v4l2-core/videobuf2-core.c:1651
WARN_ON(atomic_read(&q->owned_by_drv_count))
Fix this returning all buffers currently in capture queue.
Signed-off-by: Jacopo Mondi
---
I know I'm working to
Hi Geert,
On Wed, Nov 15, 2017 at 02:07:31PM +0100, Geert Uytterhoeven wrote:
> Hi Jacopo,
>
> CC devicetree folks
Yeah, sorry I forgot them. Sorry about this and thanks for adding the
address back!
>
> On Wed, Nov 15, 2017 at 11:55 AM, Jacopo Mondi
> wrote:
> > Add bindings documentation for R
Hi Jacopo,
On Wed, Nov 15, 2017 at 7:15 PM, jacopo mondi wrote:
> On Wed, Nov 15, 2017 at 02:07:31PM +0100, Geert Uytterhoeven wrote:
>> On Wed, Nov 15, 2017 at 11:55 AM, Jacopo Mondi
>> wrote:
>> > --- /dev/null
>> > +++ b/Documentation/devicetree/bindings/media/renesas,ceu.txt
>> > @@ -0,0 +1,
On Fri, Nov 10, 2017 at 08:59:01PM +0300, Sergei Shtylyov wrote:
> Add the PFC support for the R8A77970 SoC including pin groups for some
> on-chip devices such as CAN-FD, EtherAVB, [H]SCIF, I2C, INTC-EX, MMC,
> MSIOF, PWM, VIN...
>
> Based on the original (and large) patch by Daisuke Matsushita
>
On Sat, Nov 11, 2017 at 01:25:25AM +0100, Niklas Söderlund wrote:
> Documentation for Renesas R-Car MIPI CSI-2 receiver. The CSI-2 receivers
> are located between the video sources (CSI-2 transmitters) and the video
> grabbers (VIN) on Gen3 of Renesas R-Car SoC.
>
> Each CSI-2 device is connected
On Sat, Nov 11, 2017 at 01:38:11AM +0100, Niklas Söderlund wrote:
> 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 info
Hello!
On 11/15/2017 07:21 PM, Geert Uytterhoeven wrote:
Add the (previously omitted) EtherAVB pin data to the Eagle board's
device tree.
--- renesas.orig/arch/arm64/boot/dts/renesas/r8a77970-eagle.dts
+++ renesas/arch/arm64/boot/dts/renesas/r8a77970-eagle.dts
@@ -34,6 +34,9 @@
[...]
@@
The rvin_dev data structure contains driver private data for an instance
of the VIN. It is allocated dynamically at probe time, and must be freed
once all users are gone.
The structure is currently allocated with devm_kzalloc(), which results
in memory being freed when the device is unbound. If a
Hi Rob,
Thanks for your feedback, much appreciated!
On 2017-11-15 14:02:26 -0600, Rob Herring wrote:
> On Sat, Nov 11, 2017 at 01:38:11AM +0100, Niklas Söderlund wrote:
> > Document the devicetree bindings for the CSI-2 inputs available on Gen3.
> >
> > There is a need to add a custom property '
Hi Rob,
Thanks for your feedback.
On 2017-11-15 13:59:36 -0600, Rob Herring wrote:
> On Sat, Nov 11, 2017 at 01:25:25AM +0100, Niklas Söderlund wrote:
> > Documentation for Renesas R-Car MIPI CSI-2 receiver. The CSI-2 receivers
> > are located between the video sources (CSI-2 transmitters) and th
Hi Laurent,
Thanks for your patch.
On 2017-11-16 00:49:07 +0200, Laurent Pinchart wrote:
> The rvin_dev data structure contains driver private data for an instance
> of the VIN. It is allocated dynamically at probe time, and must be freed
> once all users are gone.
>
> The structure is currently
Hi Niklas,
On Thursday, 16 November 2017 01:34:33 EET Niklas Söderlund wrote:
> On 2017-11-16 00:49:07 +0200, Laurent Pinchart wrote:
> > The rvin_dev data structure contains driver private data for an instance
> > of the VIN. It is allocated dynamically at probe time, and must be freed
> > once a
To avoid races between device access and unplug, call the
video_device_unplug() function in the platform driver remove handler.
This will unsure that all device access completes before the remove
handler proceeds to free resources.
Signed-off-by: Laurent Pinchart
---
drivers/media/platform/rcar-
Hello,
This small RFC is an attempt to handle the race condition that exists between
device access and device unbind.
Devices can be unbound from drivers in three different ways:
- When the driver module is unloaded, the driver is unregistered and unbound
from all devices it was bound to. As m
Device unplug being asynchronous, it naturally races with operations
performed by userspace through ioctls or other file operations on video
device nodes.
This leads to potential access to freed memory or to other resources
during device access if unplug occurs during device access. To solve
this,
From: Takeshi Kihara
This patch supports GP-1-28 port pin of R8A7795 ES2.0 SoC added in
Rev.0.54E of the R-Car Gen3 Hardware User's Manual or later version.
Signed-off-by: Takeshi Kihara
Signed-off-by: Yoshihiro Kaneko
---
This patch is based on the for-next branch of linux-pinctrl tree.
dr
From: Takeshi Kihara
This patch fixes the implementation incorrect of MOD_SEL1 bit[25:24]
value when STP_ISEN_1_D pin function is selected for IPSR16 bit[27:24].
This is a correction to the incorrect implementation of MOD_SEL register
pin assignment for R8A7795 SoC specification of R-Car Gen3 Ha
From: Takeshi Kihara
This patch fixes the macro definitions of A20..A25 pins function deleted.
This is a correction because IPSR register specification for R8A7795 ES2.0
SoC was changed in R-Car Gen3 Hardware User's Manual Rev.0.53E.
Fixes: b205914c8f82 ("pinctrl: sh-pfc: r8a7795: Add support f
From: Takeshi Kihara
This patch fixes the macro definitions of A20..A25 pins function deleted.
This is a correction because IPSR register specification for R8A7796 SoC
was changed in R-Car Gen3 Hardware User's Manual Rev.0.53E.
Fixes: f9aece7344bd ("pinctrl: sh-pfc: Initial R8A7796 PFC support"
On 14 November 2017 at 23:55, Wolfram Sang
wrote:
> Documentation/timers/timers-howto.txt recommends to use usleep_range for
> delays 1-20ms. Let's adhere to it. No need for messing with HZ and still
> do busy looping these days.
>
> Signed-off-by: Wolfram Sang
> ---
>
> Here is a more detailed t
90 matches
Mail list logo