Hi Manjunath,
On Friday 27 July 2012 05:49:24 Hadli, Manjunath wrote:
> On Thu, Jul 26, 2012 at 05:55:31, Laurent Pinchart wrote:
> > On Tuesday 17 July 2012 10:43:54 Hadli, Manjunath wrote:
> > > On Sun, Jul 15, 2012 at 18:16:25, Laurent Pinchart wrote:
> > > > On Wednesday 11 July 2012 21:09:26
add mediabus formats and pixel formats supported
as part of dm365 vpfe device.
The device supports media formats(transfer and storage)
which include-
1: ALAW compressed bayer.
2: UV interleaved without Y (for resizer).
3: YDYU
Changes for v7:
1: Fixed a comment from Laurent, removed subscript for
From: Manjunath Hadli
add new enum entries for supporting the media-bus formats on dm365.
These include some bayer and some non-bayer formats.
V4L2_MBUS_FMT_YDYUYDYV8_1X16 and V4L2_MBUS_FMT_UV8_1X8 are used
internal to the hardware by the resizer.
V4L2_MBUS_FMT_SBGGR10_ALAW8_1X8 represents the ba
From: Manjunath Hadli
add new macro V4L2_PIX_FMT_SGRBG10ALAW8 and associated formats
to represent Bayer format frames compressed by A-LAW algorithm,
add V4L2_PIX_FMT_UV8 to represent storage of CbCr data (UV interleaved)
only.
Signed-off-by: Manjunath Hadli
Signed-off-by: Lad, Prabhakar
Cc: La
On Friday 27 July 2012 16:25:03 Prabhakar Lad wrote:
> add mediabus formats and pixel formats supported
> as part of dm365 vpfe device.
> The device supports media formats(transfer and storage)
> which include-
> 1: ALAW compressed bayer.
> 2: UV interleaved without Y (for resizer).
> 3: YDYU
Acke
On Friday 27 July 2012 13:30:15 Laurent Pinchart wrote:
> On Friday 27 July 2012 16:25:03 Prabhakar Lad wrote:
> > add mediabus formats and pixel formats supported
> > as part of dm365 vpfe device.
> > The device supports media formats(transfer and storage)
> > which include-
> > 1: ALAW compressed
This patch series enables VPBE display driver on DM355.
Changes for v2:
1: Removed VPSS clock alias for master and slave which was
sent for VPSS driver. since this patch was dependent on
patch[1]. I will revist this patch once MC(captrure driver)
goes into mainline.
[1] http://www.spini
From: Manjunath Hadli
add support for V4L2 video display to DM355 EVM.
Support for SD modes is provided, along with Composite
output.
Signed-off-by: Manjunath Hadli
Signed-off-by: Lad, Prabhakar
---
Changes for v2: None
arch/arm/mach-davinci/board-dm355-evm.c | 71
From: Manjunath Hadli
Create platform devices for various video modules like venc,osd,
vpbe and v4l2 driver for dm355.
Signed-off-by: Manjunath Hadli
Signed-off-by: Lad, Prabhakar
---
Changes for v2:
1: Removed vpss master and slave clock aliases.
arch/arm/mach-davinci/board-dm355-evm.c |
This patch series enables VPBE display driver on DM365.
Changes for v3:
1: Removed VPSS clock alias for master and slave which was
sent for VPSS driver. since this patch was dependent on
patch[1]. I will revist this patch once MC(captrure driver)
goes into mainline.
[1] http://www.spinics
From: Manjunath Hadli
add support for V4L2 video display to DM365 EVM.
Support for SD and ED modes is provided, along with Composite
and Component outputs.
Signed-off-by: Manjunath Hadli
Signed-off-by: Lad, Prabhakar
---
arch/arm/mach-davinci/board-dm365-evm.c | 176 +
From: Manjunath Hadli
Create platform devices for various video modules like venc,osd,
vpbe and v4l2 driver for dm365.
Signed-off-by: Manjunath Hadli
Signed-off-by: Lad, Prabhakar
---
arch/arm/mach-davinci/board-dm365-evm.c |4 +-
arch/arm/mach-davinci/davinci.h |2 +-
arch/ar
Hi,
This series makes rtc-omap driver DT capable, adds AM33xx
RTC DT support along with a few enchancments to the driver.
rtc-omap driver is made intelligent enough to handle kicker
mechanism. This helps in removing kicker mechanism support
done for DaVinci at platform level.
This has been teste
OMAP RTC IP can have kicker feature. This prevents spurious
writes to register. To write to registers kicker lock has to
be released. Procedure to do it as follows,
1. write to kick0 register, 0x83e70b13
2. write to kick1 register, 0x95a4f1e0
Writing value other than 0x83e70b13 to kick0 enables w
rtc-omap driver can be reused for AM33xx RTC.
Provide dependency in Kconfig.
Signed-off-by: Afzal Mohammed
---
v2:
Modify Kconfig help, resolve checkpatch warning
drivers/rtc/Kconfig | 10 ++
1 files changed, 6 insertions(+), 4 deletions(-)
diff --git a/drivers/rtc/Kconfig b/driver
rtc-omap driver is now capable of handling kicker mechanism,
hence remove kicker handling at platform level, instead
provide proper device name so that driver can handle kicker
mechanism by itself
Signed-off-by: Afzal Mohammed
---
v2:
Use device name da830-rtc instead of am1808-rtc
arch/arm/m
Enhance rtc-omap driver with DT capability
Signed-off-by: Afzal Mohammed
---
v2:
Use compatible as ti,da830-rtc instead of ti,am1808-rtc
Documentation/devicetree/bindings/rtc/rtc-omap.txt | 20
drivers/rtc/rtc-omap.c | 18 ++
Add AM33xx rtc node.
Signed-off-by: Afzal Mohammed
---
v3:
Remove unit address in DT node
v2:
Use compatible as ti,da830-rtc instead of ti,am1808-rtc
arch/arm/boot/dts/am33xx.dtsi |5 +
1 files changed, 5 insertions(+), 0 deletions(-)
diff --git a/arch/arm/boot/dts/am33xx.dtsi b/ar
From: Vaibhav Hiremath
OMAP1 RTC driver is used in multiple devices like,
OMAPL138 and AM33XX. Driver currently doesn't handle any clocks,
which may be right for OMAP1 architecture but in case of AM33XX,
the clock/module needs to be enabled in order to access the registers.
So covert this driver
Hi Prabhakar,
Thanks for the patch, and my apologies for delayed answer!
On Fri, Jul 27, 2012 at 04:25:04PM +0530, Prabhakar Lad wrote:
> From: Manjunath Hadli
>
> add new enum entries for supporting the media-bus formats on dm365.
> These include some bayer and some non-bayer formats.
> V4L2_M
>>
>> On 7/25/2012 9:16 PM, Karicheri, Muralidharan wrote:
>> > All,
>> >
>> >
>> >
>> > I am working to migrate DaVinci platforms to common clock framework.
>> > While doing so I would need your support in terms of answering any
>> > questions that I have, reviewing patches and testing. I have st
21 matches
Mail list logo
