From: Koji Matsuoka koji.matsuoka...@renesas.com
Signed-off-by: Koji Matsuoka koji.matsuoka...@renesas.com
Signed-off-by: Yoshihiro Kaneko ykaneko0...@gmail.com
---
This patch is against master branch of linuxtv.org/media_tree.git.
drivers/media/platform/soc_camera/rcar_vin.c | 10 ++
From: Koji Matsuoka koji.matsuoka...@renesas.com
Signed-off-by: Koji Matsuoka koji.matsuoka...@renesas.com
Signed-off-by: Yoshihiro Kaneko ykaneko0...@gmail.com
---
This patch is against master branch of linuxtv.org/media_tree.git.
drivers/media/platform/soc_camera/rcar_vin.c | 8
1
From: Koji Matsuoka koji.matsuoka...@renesas.com
By applying this patch, it sets to VSYNC field toggle mode not only
at the time of progressive mode but at the time of an interlace mode.
Signed-off-by: Koji Matsuoka koji.matsuoka...@renesas.com
Signed-off-by: Yoshihiro Kaneko
From: Koji Matsuoka koji.matsuoka...@renesas.com
This patch corrects the miscalculation of the capture buffer
size and clipping data update in VIDIOC_S_CROP sequence.
Signed-off-by: Koji Matsuoka koji.matsuoka...@renesas.com
Signed-off-by: Yoshihiro Kaneko ykaneko0...@gmail.com
---
This patch
This series is against master branch of linuxtv.org/media_tree.git.
Koji Matsuoka (3):
media: soc_camera: rcar_vin: Add scaling support
media: soc_camera: rcar_vin: Add capture width check for NV16 format
media: soc_camera: rcar_vin: Add NV16 horizontal scaling-up support
From: Koji Matsuoka koji.matsuoka...@renesas.com
At the time of NV16 capture format, the user has to specify the
capture output width of the multiple of 32 for H/W specification.
At the time of using NV16 format by ioctl of VIDIOC_S_FMT,
this patch adds align check and the error handling to
From: Koji Matsuoka koji.matsuoka...@renesas.com
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. a vertical scaling-up
by the capture format of NV16 is forbidden for the
From: Koji Matsuoka koji.matsuoka...@renesas.com
Signed-off-by: Koji Matsuoka koji.matsuoka...@renesas.com
Signed-off-by: Yoshihiro Kaneko ykaneko0...@gmail.com
---
drivers/media/platform/soc_camera/rcar_vin.c | 455 ++-
1 file changed, 446 insertions(+), 9 deletions(-)
This patchset fixup the PM support and adds some minor improvements to
potentially save some more power at runtime PM suspend.
Some background to this patchset, which are related to the generic PM domain:
http://marc.info/?l=linux-pmm=141217452218592w=2
http://marc.info/?t=141217462200011r=1w=2
To potentially save more power in runtime PM suspend state, let's also
prepare/unprepare the clock from the runtime PM callbacks.
Signed-off-by: Ulf Hansson ulf.hans...@linaro.org
---
drivers/media/platform/exynos-gsc/gsc-core.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff
There are no need to set up the runtime PM callbacks unless they are
being used. Let's make them available for CONFIG_PM.
Signed-off-by: Ulf Hansson ulf.hans...@linaro.org
---
drivers/media/platform/exynos-gsc/gsc-core.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git
Since gsc_m2m_resume() always returns 0, convert it into void instead.
Signed-off-by: Ulf Hansson ulf.hans...@linaro.org
---
drivers/media/platform/exynos-gsc/gsc-core.c | 7 +++
1 file changed, 3 insertions(+), 4 deletions(-)
diff --git a/drivers/media/platform/exynos-gsc/gsc-core.c
We had several issues with the system PM support.
1) It were depending on CONFIG_PM_RUNTIME.
2) It unnecessarily tracked the suspend state in a flag.
3) If userspace through sysfs prevents runtime PM operations, could
cause the device to stay in low power after a system PM resume, which
is not
The driver depended on CONFIG_PM_RUNTIME to be functional, which isn't
necessary.
The solution to the above is to enable all runtime PM resourses during
probe and update the device's runtime PM status to active.
Since driver core invokes pm_request_idle() after -probe(), unused gsc
devices will
We want to make sure that the clock is fully gated after -remove(). To
do this, we need to bring the device into full power and not only
unprepare the clock, but also disable it.
Signed-off-by: Ulf Hansson ulf.hans...@linaro.org
---
drivers/media/platform/exynos-gsc/gsc-core.c | 7 +--
1
Instead of having separate functions that fecthes, prepares and
unprepares the clock, let's encapsulate this code into -probe().
This makes error handling easier and decreases the lines of code.
Signed-off-by: Ulf Hansson ulf.hans...@linaro.org
---
drivers/media/platform/exynos-gsc/gsc-core.c |
From: Koji Matsuoka koji.matsuoka...@renesas.com
Signed-off-by: Koji Matsuoka koji.matsuoka...@renesas.com
Signed-off-by: Yoshihiro Kaneko ykaneko0...@gmail.com
---
drivers/media/platform/soc_camera/rcar_vin.c | 1 +
1 file changed, 1 insertion(+)
diff --git
This series is against master branch of linuxtv.org/media_tree.git.
Koji Matsuoka (2):
media: soc_camera: rcar_vin: Add r8a7794 device support
media: soc_camera: rcar_vin: Add r8a7793 device support
drivers/media/platform/soc_camera/rcar_vin.c | 2 ++
1 file changed, 2 insertions(+)
--
From: Koji Matsuoka koji.matsuoka...@renesas.com
Signed-off-by: Koji Matsuoka koji.matsuoka...@renesas.com
Signed-off-by: Yoshihiro Kaneko ykaneko0...@gmail.com
---
drivers/media/platform/soc_camera/rcar_vin.c | 1 +
1 file changed, 1 insertion(+)
diff --git
From: Thierry Reding tred...@nvidia.com
If power management is disabled these function become unused, so there
is no reason to build them. This fixes a couple of build warnings when
PM(_SLEEP,_RUNTIME) is not enabled.
Acked-by: Geert Uytterhoeven ge...@linux-m68k.org
Signed-off-by: Thierry
From: Thierry Reding tred...@nvidia.com
If power management is disabled these functions become unused, so there
is no reason to build them. This fixes a couple of build warnings when
PM(_SLEEP,_RUNTIME) is not enabled.
Signed-off-by: Thierry Reding tred...@nvidia.com
---
Changes in v2:
- add
Please keep the discussion on the mailing list at all times.
I couldn't figure out how to apply the patch using the patch file, so I
manually edited the file (drivers/media/pci/saa7164/saa7164-fw.c), but I
kept getting the image corrupt message.
That's probably the issue. Assuming you have
Hello.
On 10/14/2014 10:26 AM, Yoshihiro Kaneko wrote:
From: Koji Matsuoka koji.matsuoka...@renesas.com
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. a vertical
Hi Laura,
On 13 October 2014 13:42, Laura Abbott lau...@codeaurora.org wrote:
On 10/10/2014 1:07 PM, Sumit Semwal wrote:
Hi,
Why:
While sharing buffers using dma-buf, currently there's no mechanism to
let
devices share their memory access constraints with each other to allow for
Hi Greg, Daniel!
On 12 October 2014 00:10, Daniel Vetter dan...@ffwll.ch wrote:
On Fri, Oct 10, 2014 at 04:09:00PM -0700, Greg Kroah-Hartman wrote:
On Sat, Oct 11, 2014 at 01:37:56AM +0530, Sumit Semwal wrote:
Devices sharing buffers using dma-buf could benefit from sharing their
Hi Laura,
On 13 October 2014 14:05, Laura Abbott lau...@codeaurora.org wrote:
On 10/10/2014 1:07 PM, Sumit Semwal wrote:
Devices sharing buffers using dma-buf could benefit from sharing their
constraints via struct device, and dma-buf framework would manage the
common constraints for all
Add media token device resource framework to allow sharing
resources such as tuner, dma, audio etc. across media drivers
and non-media sound drivers that control media hardware. The
Media token resource is created at the main struct device that
is common to all drivers that claim various pieces of
Change snd_usb_capture_ops trigger to hold audio token prior
starting endpoints for SNDRV_PCM_TRIGGER_START request and
release after stopping endpoints for SNDRV_PCM_TRIGGER_STOP
request. Audio token is released from snd_usb_capture_ops
close interface to cover the case where an application exits
Changed au0828-core to create media token resource in its
usb_probe() and destroy it from usb_disconnect() interfaces.
It creates the resource on the main struct device which is
the parent device for the interface usb device. This is the
main struct device that is common for all the drivers that
Change dvb_frontend_open() to hold tuner and audio tokens
when frontend is opened in R/W mode. Tuner and audio tokens
are released when frontend is released in frontend exit state.
This change allows main dvb application process to hold the
tokens for all threads it creates and be able to handle
au0828-video driver uses vb1 api and needs changes to vb1
v4l2 interfaces that change the tuner status. In addition
to that this driver initializes the tuner from a some ioctls
that are query (read) tuner status. These ioctls are changed
to hold the tuner and audio tokens to avoid disrupting
Add media token device resource framework to allow sharing
resources such as tuner, dma, audio etc. across media drivers
and non-media sound drivers that control media hardware. The
Media token resource is created at the main struct device that
is common to all drivers that claim various pieces of
Changes to v4l2-core to hold tuner and audio tokens in v4l2
ioctl that change the tuner modes, and release the token from
fh exit. The changes are limited to vb2 calls that disrupt
digital stream. vb1 changes are made in the driver. The
following ioctls are changed:
S_INPUT, S_FMT, S_TUNER,
Hi Kaneko-san, Matsuoka-san,
On Tue, Oct 14, 2014 at 8:26 AM, Yoshihiro Kaneko ykaneko0...@gmail.com wrote:
From: Koji Matsuoka koji.matsuoka...@renesas.com
Thanks for our patch!
--- a/drivers/media/platform/soc_camera/rcar_vin.c
+++ b/drivers/media/platform/soc_camera/rcar_vin.c
@@ -120,6
Thanks for that, it's working now. I didn't realise you had to apply the
patch before building it, silly me.
Yours sincerely
serrin
On 14/10/2014 9:48 PM, Steven Toth wrote:
Please keep the discussion on the mailing list at all times.
I couldn't figure out how to apply the patch using the
This message is generated daily by a cron job that builds media_tree for
the kernels and architectures in the list below.
Results of the daily build of media_tree:
date: Wed Oct 15 04:00:21 CEST 2014
git branch: test
git hash: cf3167cf1e969b17671a4d3d956d22718a8ceb85
gcc
tree: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 2d65a9f48fcdf7866aab6457bc707ca233e0c791
commit: e75420dd25bc9d7b6f4e3b4c4f6c778b610c8cda [media] vivid: enable the
vivid driver
date: 6 weeks ago
config: i386-randconfig-ib0-10151216 (attached as .config)
On Tue, Oct 14, 2014 at 04:57:53PM +0400, Sergei Shtylyov wrote:
Hello.
On 10/14/2014 10:26 AM, Yoshihiro Kaneko wrote:
From: Koji Matsuoka koji.matsuoka...@renesas.com
The scaling function had been forbidden for the capture format of
NV16 until now. With this patch, a horizontal
38 matches
Mail list logo
