RE: [RFC/PATCH 3/7] ARM: OMAP3: clock data: treat all AM35x devices the same

2012-01-06 Thread Hiremath, Vaibhav
-Original Message- From: Hilman, Kevin Sent: Friday, January 06, 2012 5:34 AM To: Hiremath, Vaibhav Cc: linux-omap@vger.kernel.org; Paul Walmsley Subject: Re: [RFC/PATCH 3/7] ARM: OMAP3: clock data: treat all AM35x devices the same Hiremath, Vaibhav hvaib...@ti.com writes:

[PATCH v4 1/4] OMAPDSS: HDMI: remove duplicate video interface code

2012-01-06 Thread mythripk
From: Mythri P K mythr...@ti.com video interface structure is a duplicate structure with parameters which are already present in ip_data config structure, Thus removing the structure and modifying corresponding code. Signed-off-by: Mythri P K mythr...@ti.com ---

[PATCH v4 0/4] OMAPDSS: HDMI: Improve the timings logic in HDMI

2012-01-06 Thread mythripk
From: Mythri P K mythr...@ti.com There are some duplicate timing structure which are not needed thus removing them to clean the code. Also the static mapped timing structure is quite complicated to add new timings, so simplify it by using array indexed method. changes since v3: Remove double

[PATCH v4 3/4] OMAPDSS: HDMI: change the timing match logic

2012-01-06 Thread mythripk
From: Mythri P K mythr...@ti.com Change the timing match logic, Instead of the statically mapped method to get the corresponding timings for a given code and mode, move to a simpler array indexed method. It will help to scale up to add more timings when needed. Signed-off-by: Mythri P K

[PATCH v4 2/4] OMAPDSS: HDMI: update static timing table

2012-01-06 Thread mythripk
From: Mythri P K mythr...@ti.com Add the vsync polarity, hsync polarity, interlace to hdmi_video_timings. Remove the now duplicate structure hdmi_timings. update the static table structure in HDMI with CEA/VESA code and mode. Signed-off-by: Mythri P K mythr...@ti.com ---

[PATCH v4 4/4] OMAPDSS: HDMI: remove duplicate code and mode parameter

2012-01-06 Thread mythripk
From: Mythri P K mythr...@ti.com code and mode parameters are already a part of the ip_data structure so no need to keep the same parameters again in hdmi global structure. Signed-off-by: Mythri P K mythr...@ti.com --- drivers/video/omap2/dss/hdmi.c | 18 +++--- 1 files changed, 7

[PATCH v3 1/3] OMAPDSS: HDMI: Move Avi-infoframe struct to hdmi_ip_data

2012-01-06 Thread mythripk
From: Mythri P K mythr...@ti.com With AVI infoframe various parameters of video stream such as aspect ratio, quantization range, videocode etc will be indicated from source to sink.Thus AVI information needs to be set/accessed by the middle ware based on the video content. Thus this parameter is

[PATCH v3 3/3] OMAPDSS: HDMI: Sysfs support to configure quantization range

2012-01-06 Thread mythripk
From: Mythri P K mythr...@ti.com Add sysfs support for the uset space to configure limited range or full range quantization for HDMI. Signed-off-by: Mythri P K mythr...@ti.com --- drivers/video/omap2/dss/dss.h |2 + drivers/video/omap2/dss/dss_features.c |1 +

[PATCH v3 2/3] OMAPDSS: HDMI: Add quantization range support in IP lib

2012-01-06 Thread mythripk
From: Mythri P K mythr...@ti.com Configure the IP to support the limited range and full range quantization mode. If the full range is configured HDMI transmitter will expand the range of pixel data from 16-235 to full 8 bit 0-235. Signed-off-by: Mythri P K mythr...@ti.com ---

[PATCH v2 2/3] OMAPDSS: HDMI: Handle HPD event in ip

2012-01-06 Thread mythripk
From: Mythri P K mythr...@ti.com HPD event is notified to ip file and based on the notification appropriate action is taken. As the PHY should be in LDO_ON state and not TX_ON (transmission), this transition is handled in ip file. Signed-off-by: Mythri P K mythr...@ti.com ---

[PATCH v2 3/3] OMAPDSS: HDMI: HPD support added to HDMI driver

2012-01-06 Thread mythripk
From: Mythri P K mythr...@ti.com GPIO based handling of connect/disconnect of the HDMI cable (Hot-plug detect)is added to the HDMI driver. Signed-off-by: Mythri P K mythr...@ti.com --- drivers/video/omap2/dss/dss_features.c |1 + drivers/video/omap2/dss/hdmi.c | 49

[PATCH 0/3] OMAPDSS: HDMI: HDMI Hot-plug detect support.

2012-01-06 Thread mythripk
From: Mythri P K mythr...@ti.com HDMI phy should be in the LDO_ON state when cable is not connected. Only when cable is connected and transmission is possible HDMI Phy should move to TX_ON state. This is supported by the Hot-plug feature. Now when HDMI is enabled the following steps are followed:

[PATCH v2 1/3] OMAPDSS: HDMI: HPD support in boardfile

2012-01-06 Thread mythripk
From: Mythri P K mythr...@ti.com Add support for HPD GPIO configuration in board file. Also remove the enabling of GPIO's required for HDMI from hdmi driver file to display.c based on the GPIO #'s sent from board file. Signed-off-by: Mythri P K mythr...@ti.com Acked-by: Tony Lindgren

Re: [PATCH v2 3/3] OMAPDSS: HDMI: Sysfs support to configure quantization

2012-01-06 Thread K, Mythri P
Hi Tomi, On Thu, Jan 5, 2012 at 12:51 PM, Tomi Valkeinen tomi.valkei...@ti.com wrote: On Wed, 2012-01-04 at 17:23 +0530, mythr...@ti.com wrote: From: Mythri P K mythr...@ti.com Add sysfs support for the uset space to configure limited range or full range quantization for HDMI.

[BUG] perf_event: no PMU interrupt on OMAP4 with 3.2.0 (Pandaboard)

2012-01-06 Thread Stephane Eranian
Hi, I am trying to get perf_event to work properly on my OMAP4 Pandabaord running the 3.2.0 kernel. I am the developer on libpfm4 and a regular contributor to the perf_event subsystem and perf tool. I want to use a Pandaboard to test libpfm4 ARM support. I have been talking with Will Deacon and

Re: [PATCH] OMAP: I2C: add devexit to the remove code

2012-01-06 Thread Ben Dooks
On Tue, Dec 20, 2011 at 12:55:59PM +0530, Shubhrajyoti D wrote: The omap_i2c_remove function may not be needed after device exit so the memory could be freed. Signed-off-by: Shubhrajyoti D shubhrajy...@ti.com Will add this later. --- drivers/i2c/busses/i2c-omap.c |5 ++--- 1 files

Re: [PATCH 1/3] ARM: OMAP2+: kconfig: Enable devicetree by default for OMAP2+ systems

2012-01-06 Thread Cousson, Benoit
On 1/4/2012 9:11 PM, Grant Likely wrote: On Tue, Dec 6, 2011 at 9:49 AM, Benoit Coussonb-cous...@ti.com wrote: devicetree will become the mandatory boot method for OMAP2+. In order to avoid cluttering the OMAP code with #ifdef CONFIG_OF, select USE_OF by default for every OMAP2+ systems.

Re: [GIT PULL] I2C: OMAP: misc. updates for v3.3

2012-01-06 Thread Ben Dooks
On Thu, Jan 05, 2012 at 04:13:51PM -0800, Kevin Hilman wrote: Hi Ben, Here's a few OMAP I2C updates for the v3.3 merge window. ok, added these to my i2c-next and for-33/i2c/omap. Thanks, Kevin The following changes since commit 3f6b2a8bd6e4ff43269d89066a9fe06a0e5ba961: I2C:

Re: [PATCH v2 0/5] ARM: OMAP2+: Interrupt controllers adaptation to DT

2012-01-06 Thread Cousson, Benoit
Hi Rob/Grant, Gentle ping on that series too. This should the last one:-) Thanks, Benoit On 12/23/2011 10:46 AM, Cousson, Benoit wrote: Hi Rob, Are you OK with that update? Thanks, Benoit On 12/20/2011 2:39 PM, Benoit Cousson wrote: Hi Tony and Rob, Here is the series to take advantage

Re: [PATCH] irqdomain: Initialize number of IRQs for simple domains

2012-01-06 Thread Cousson, Benoit
Hi Thierry, On 1/6/2012 3:28 PM, Thierry Reding wrote: The irq_domain_add() function needs the number of interrupts in the domain to properly initialize them. In addition the allocated domain is now returned by the irq_domain_{add,generate}_simple() helpers. [...] diff --git

[RFC/PATCH 8/7] ARM: OMAP: AM35xx: convert 3517 detection/flags to AM35xx

2012-01-06 Thread Kevin Hilman
Currently cpu_is_omap3517() actually detects any device in the AM35x family (3517 and no-SGX version 3505.) To make it more clear what is being detected, convert the names from 3517 to AM35xx. For the same reason, replace the CK_3517 flag used in the clock data to CK_AM35XX. Signed-off-by:

Re: [PATCH 0/7] ARM: OMAP: remove IP checks from SoC family detection

2012-01-06 Thread Kevin Hilman
Hiremath, Vaibhav hvaib...@ti.com writes: Currently, our SoC detection is based on SoC family detection (using die ID) and the presence of specific IP blocks (or feature.) This series begins the separation of the SoC family detection and specific IP detection. Applies on top of Tony's

Re: [PATCH v2 0/5] ARM: OMAP2+: Interrupt controllers adaptation to DT

2012-01-06 Thread Rob Herring
On 01/06/2012 10:38 AM, Cousson, Benoit wrote: Hi Rob/Grant, Gentle ping on that series too. This should the last one:-) Sorry about that. For the series: Acked-by: Rob Herring rob.herr...@calxeda.com Rob Thanks, Benoit On 12/23/2011 10:46 AM, Cousson, Benoit wrote: Hi Rob, Are

Re: [PATCH v2 1/5] arm/dts: OMAP4: Update DTS file with new GIC bindings

2012-01-06 Thread Grant Likely
On Tue, Dec 20, 2011 at 02:39:54PM +0100, Benoit Cousson wrote: The GIC binding was updated in 3.2 and expect 3 interrupt-cells. - Update the #interrupt-cells - interrupt-parent seems to be needed as well for the top level GIC Hmmm... it shouldn't be. If it is then it is a bug. g.

Re: [PATCH v2 2/5] ARM: OMAP2/3: intc: Add irqdomain support

2012-01-06 Thread Grant Likely
On Tue, Dec 20, 2011 at 02:39:55PM +0100, Benoit Cousson wrote: Introduce the usage of the irqdomain to prepare the DT support. The irq_base is still hard coded to 0 to allow non-DT drivers to work with the previous assumption that was hwirq = irq. Signed-off-by: Benoit Cousson

Re: [PATCH v2 3/5] ARM: OMAP2/3: intc: Add DT support for TI interrupt controller

2012-01-06 Thread Grant Likely
On Tue, Dec 20, 2011 at 02:39:56PM +0100, Benoit Cousson wrote: Add a function to initialize the OMAP2/3 interrupt controller (INTC) using a device tree node. Replace some printk() with the proper pr_ macro. Signed-off-by: Benoit Cousson b-cous...@ti.com Cc: Tony Lindgren t...@atomide.com

Re: [PATCH v2 4/5] arm/dts: OMAP3: Add interrupt-controller bindings for INTC

2012-01-06 Thread Grant Likely
On Tue, Dec 20, 2011 at 02:39:57PM +0100, Benoit Cousson wrote: Update the DTS with the proper information required by the INTC bindings. - Add the number of interrupt lines - Add the reg and the compatible entries. Signed-off-by: Benoit Cousson b-cous...@ti.com Cc: Rob Herring

Re: [PATCH v2 5/5] ARM: OMAP2+: board-generic: Use of_irq_init API

2012-01-06 Thread Grant Likely
On Tue, Dec 20, 2011 at 02:39:58PM +0100, Benoit Cousson wrote: Use the of_irq_init API introduced in 3.2 to handle interrupt-controller with DT. Update the irq_match table to map the proper XXX_of_init functions for INTC and GIC drivers. Signed-off-by: Benoit Cousson b-cous...@ti.com Cc:

Re: [PATCH v2 1/5] arm/dts: OMAP4: Update DTS file with new GIC bindings

2012-01-06 Thread Rob Herring
On 01/06/2012 03:15 PM, Grant Likely wrote: On Tue, Dec 20, 2011 at 02:39:54PM +0100, Benoit Cousson wrote: The GIC binding was updated in 3.2 and expect 3 interrupt-cells. - Update the #interrupt-cells - interrupt-parent seems to be needed as well for the top level GIC Hmmm... it shouldn't