Hi Sylwester,
Thanks for your review.
On Fri, Dec 30, 2011 at 1:16 AM, Sylwester Nawrocki snj...@gmail.com wrote:
Hi Ming,
On 12/14/2011 03:00 PM, Ming Lei wrote:
This patch introduces object detection generic driver.
The driver is responsible for all v4l2 stuff, buffer management
and
TPS65217 power management IC supports various features, like
Battery charger, white LED driver along with basic regulator
Functionality.
This patch set adds support as an MFD device into the kernel
to facilitate adding additional drivers on top of it.
This device is used on one of AM335x
The TPS65217 chip is a power management IC for Portable Navigation Systems
and Tablet Computing devices. It contains the following components:
- Regulators
- White LED
- USB battery charger
This patch adds support for tps65217 mfd device. At this time only
the regulator functionality is made
This patch adds tps65217 PMIC as a regulator
The regulator module consists of 3 DCDCs and 4 LDOs. The output
voltages are configurable and are meant to supply power to the
main processor and other components
Signed-off-by: AnilKumar Ch anilku...@ti.com
---
drivers/regulator/Kconfig
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 v2: Incorporate
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
---
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
---
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
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
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
---
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 +
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
Hi Tomi,
On Tue, Jan 3, 2012 at 3:39 PM, Tomi Valkeinen tomi.valkei...@ti.com wrote:
Hi,
Again the subjects are cut off in mid sentence. And the patch series
contains patch 1 two times.
Please use git-format-patch and git-send-email to send proper patches,
and please check the patches
Hi Kevin,
On 12/14/2011 2:06 AM, Kevin Hilman wrote:
Benoit Coussonb-cous...@ti.com writes:
Add initial DT support to retrieve the frequency using a
DT attribute instead of the pdata pointer if of_node exist.
Add documentation for omap i2c controller binding.
Based on original patches from
Hi Colin,
On Wed, Dec 21, 2011 at 1:09 AM, Colin Cross ccr...@android.com wrote:
Split the code to enter a state and update the stats into a helper
function, cpuidle_enter_state, and export it. This function will
be called by the coupled state code to handle entering the safe
state and the
Hi Grant,
On 1/4/2012 8:17 AM, Grant Likely wrote:
On Mon, Dec 05, 2011 at 03:23:56PM +0100, Benoit Cousson wrote:
In a HW system, resources in general have name to identify them.
The is the case as well for IORESOURCE_IRQ resources filled by DT
interrupts entries.
The current DT mechanism is
On 01/03/2012 08:15 PM, Richard Zhao wrote:
On Fri, Dec 16, 2011 at 04:45:48PM -0800, Turquette, Mike wrote:
On Wed, Dec 14, 2011 at 5:18 AM, Thomas Gleixner t...@linutronix.de wrote:
On Tue, 13 Dec 2011, Mike Turquette wrote:
snip
+/**
+ * clk_init - initialize the data structures in a
I have found another circumstance in which the bus locks up which is possibly a
regression caused by this patch.
When performing a transfer with repeat starts, if one of the parts, that is is
NOT the last in the sequence AND is a master-write AND is NACKed by the remote
device,
On Wed, Jan 4, 2012 at 1:41 AM, Kevin Hilman khil...@ti.com wrote:
Colin Cross ccr...@android.com writes:
This patch series implements an alternative solution, where each
cpu will wait in the WFI state until all cpus are ready to enter
a coupled state, at which point the coupled state
On Fri, Dec 09, 2011 at 03:02:41PM +0100, Benoit Cousson wrote:
This mainly reverts the commit that was adding the i2c static init.
Since the i2c and twl nodes are now present, there is no need
for the static initialization anymore.
Signed-off-by: Benoit Cousson b-cous...@ti.com
Cc: Tony
On Fri, Dec 09, 2011 at 03:02:37PM +0100, Benoit Cousson wrote:
Add i2c controllers nodes into the main ocp bus.
Signed-off-by: Benoit Cousson b-cous...@ti.com
Cc: Grant Likely grant.lik...@secretlab.ca
Cc: Rob Herring rob.herr...@calxeda.com
Acked-by: Grant Likely grant.lik...@secretlab.ca
On Fri, Dec 09, 2011 at 03:02:32PM +0100, Benoit Cousson wrote:
In the case of DT, the PMIC and SR initialization will be done using
a completely different mechanism.
Disable this part if a DT blob is available.
Signed-off-by: Benoit Cousson b-cous...@ti.com
Acked-by: Grant Likely
On Fri, Dec 09, 2011 at 03:02:36PM +0100, Benoit Cousson wrote:
Add i2c controllers nodes into the main ocp bus.
Signed-off-by: Benoit Cousson b-cous...@ti.com
Cc: Grant Likely grant.lik...@secretlab.ca
Cc: Rob Herring rob.herr...@calxeda.com
Acked-by: Grant Likely grant.lik...@secretlab.ca
On Wed, Jan 04, 2012 at 02:36:24PM +0100, Cousson, Benoit wrote:
Hi Kevin,
On 12/14/2011 2:06 AM, Kevin Hilman wrote:
Benoit Coussonb-cous...@ti.com writes:
Add initial DT support to retrieve the frequency using a
DT attribute instead of the pdata pointer if of_node exist.
Add
On Fri, Dec 09, 2011 at 03:02:35PM +0100, Benoit Cousson wrote:
Add the DT support for the TI rtc-twl present in the twl4030
and twl6030 devices.
Signed-off-by: Benoit Cousson b-cous...@ti.com
Cc: Alessandro Zummo a.zu...@towertech.it
Acked-by: Grant Likely grant.lik...@secretlab.ca
---
On Fri, Dec 09, 2011 at 03:02:40PM +0100, Benoit Cousson wrote:
Add required clock frequencies for the i2c client devices existing
on beagle board.
Add the twl4030 basic description with only the twl_rtc module.
Add the EEPROM node.
Based on original patch from Manju:
On Fri, Dec 09, 2011 at 03:02:34PM +0100, Benoit Cousson wrote:
Add initial device-tree support for twl familly chips.
The current version is missing the regulator entries due
to the lack of DT regulator bindings for the moment.
Only the simple sub-modules that do not depend on
platform_data
On Fri, Dec 09, 2011 at 03:02:38PM +0100, Benoit Cousson wrote:
Update pandaboard dts file with required clock frequencies
for the i2c client devices existing on pandaboard.
Add the twl6030 node in i2c1 controller.
This is the minimal support needed to boot OMAP4 boards
without any crash.
On Fri, Dec 09, 2011 at 03:02:39PM +0100, Benoit Cousson wrote:
Update DTS file with required clock frequencies
for the i2c client devices existing on sdp4430.
Add the twl6030 node inside the i2c1 controller node.
This is the minimal support needed to boot OMAP4 boards
without any crash.
On Tue, Dec 27, 2011 at 12:08:31AM +0100, Ilya Yanok wrote:
Very basic support for TeeJet Mt.Ventoux board. Able to boot via
board-generic and ramdisk/initramfs, however most of peripherals are
not supported. Produces tons of twl4030 related errors as this board
doesn't have twl4030 installed.
On Tue, Dec 06, 2011 at 05:49:08PM +0100, Benoit Cousson wrote:
Since 3.2, the CONFIG_ARM_ATAG_DTB_COMPAT config allows
an old bootloader to still use ATAG to provide cmdline.
Remove chosen/bootargs from the DTS board files.
Signed-off-by: Benoit Cousson b-cous...@ti.com
Cc: Grant Likely
On Tue, Dec 6, 2011 at 9:49 AM, Benoit Cousson b-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.
Select as well the APPENDED_DTB and
Cousson, Benoit b-cous...@ti.com writes:
Hi Kevin,
On 12/14/2011 2:06 AM, Kevin Hilman wrote:
Benoit Coussonb-cous...@ti.com writes:
Add initial DT support to retrieve the frequency using a
DT attribute instead of the pdata pointer if of_node exist.
Add documentation for omap i2c
On Wed, Jan 4, 2012 at 2:28 PM, Kevin Hilman khil...@ti.com wrote:
Cousson, Benoit b-cous...@ti.com writes:
Hi Kevin,
On 12/14/2011 2:06 AM, Kevin Hilman wrote:
Benoit Coussonb-cous...@ti.com writes:
Add initial DT support to retrieve the frequency using a
DT attribute instead of the
+Felipe
NeilBrown ne...@suse.de writes:
On a board with OMAP3 processor and TWL4030 Power management,
we need to talk to the TWL4030 during late suspend but cannot
because the I2C interrupt is disabled (as late suspend disables
interrupt).
I'm not convinced this is the right solution to
Currently omap_hwmod_44xx_data.c has slimbus1/slimbus2 included in the
list of excluded IPs.
Is it possible to get a version of omap_hwmod_44xx_data.c generated
with slimbus1/2 included?
I want this as I am currently working on a driver for the slimbus
modules, based on the SLIMbus RFC patch
On Wed, Jan 4, 2012 at 6:32 AM, Rob Herring robherri...@gmail.com wrote:
On 01/03/2012 08:15 PM, Richard Zhao wrote:
On Fri, Dec 16, 2011 at 04:45:48PM -0800, Turquette, Mike wrote:
On Wed, Dec 14, 2011 at 5:18 AM, Thomas Gleixner t...@linutronix.de wrote:
On Tue, 13 Dec 2011, Mike Turquette
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 current master branch and so far, it has only
been
The cpu_is_omap35* macros for 3503, 3515, 3525) are unused.
Remove them in order to start removing IP detection from SoC family
detection.
Signed-off-by: Kevin Hilman khil...@ti.com
---
arch/arm/plat-omap/include/plat/cpu.h | 15 ---
1 files changed, 0 insertions(+), 15
The init for 3505/3517 specific clocks depends on the ordering of
cpu_is checks, is error prone and confusing (there are 2 separate
checks for cpu_is_omap3505()).
Remove the 3505-specific checking since CK_3505 flag is not used, and
treat all AM35x clocks the same.
This means that the SGX clock
There are several checks for AM35x devices done using
if (cpu_is_omap3517() || cpu_is_omap3505())
However, since the 3505 is just a 3517 without an SGX, the 3505 check
is redundant because cpu_is_omap3517() will always be true whenever
cpu_is_omap3505() is true. From plat/cpu.h:
#define
This flag is no longer used since clock init all AM35x devices
is now the same.
Signed-off-by: Kevin Hilman khil...@ti.com
---
arch/arm/plat-omap/include/plat/clkdev_omap.h |3 +--
1 files changed, 1 insertions(+), 2 deletions(-)
diff --git a/arch/arm/plat-omap/include/plat/clkdev_omap.h
The cpu_is_omap3530() macro is unused, remove.
Signed-off-by: Kevin Hilman khil...@ti.com
---
arch/arm/plat-omap/include/plat/cpu.h |3 ---
1 files changed, 0 insertions(+), 3 deletions(-)
diff --git a/arch/arm/plat-omap/include/plat/cpu.h
b/arch/arm/plat-omap/include/plat/cpu.h
index
The 3505 check is now unused and can be removed.
There are no longer any cpu_is_* checks that depend on specific IP
detection.
Signed-off-by: Kevin Hilman khil...@ti.com
---
arch/arm/plat-omap/include/plat/cpu.h |8 +---
1 files changed, 1 insertions(+), 7 deletions(-)
diff --git
The AM35x UART4 is common to all AM35x devices, so use CK_AM35XX instead
of (CK_3505 | CK_3517), which is equivalent.
Signed-off-by: Kevin Hilman khil...@ti.com
---
arch/arm/mach-omap2/clock3xxx_data.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git
On 01/04/2012 07:01 PM, Turquette, Mike wrote:
On Wed, Jan 4, 2012 at 6:32 AM, Rob Herring robherri...@gmail.com wrote:
On 01/03/2012 08:15 PM, Richard Zhao wrote:
On Fri, Dec 16, 2011 at 04:45:48PM -0800, Turquette, Mike wrote:
On Wed, Dec 14, 2011 at 5:18 AM, Thomas Gleixner
On Wed, Jan 4, 2012 at 6:11 PM, Rob Herring robherri...@gmail.com wrote:
On 01/04/2012 07:01 PM, Turquette, Mike wrote:
On Wed, Jan 4, 2012 at 6:32 AM, Rob Herring robherri...@gmail.com wrote:
On 01/03/2012 08:15 PM, Richard Zhao wrote:
On Fri, Dec 16, 2011 at 04:45:48PM -0800, Turquette, Mike
On Wed, 04 Jan 2012 14:19:48 -0800 Kevin Hilman khil...@ti.com wrote:
+Felipe
NeilBrown ne...@suse.de writes:
On a board with OMAP3 processor and TWL4030 Power management,
we need to talk to the TWL4030 during late suspend but cannot
because the I2C interrupt is disabled (as late
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.
Signed-off-by: Mythri P K mythr...@ti.com
---
drivers/video/omap2/dss/dss.h |2 +
On Wed, 2012-01-04 at 16:39 +0530, mythr...@ti.com wrote:
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
On Wed, 2012-01-04 at 17:23 +0530, mythr...@ti.com wrote:
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.
On Wed, 04 Jan 2012 09:50:56 +0200 Tomi Valkeinen tomi.valkei...@ti.com
wrote:
(dropping the Tony and Kevin, as they're probably not interested in
this)
Thanks takes a while to figure who cares about what :-)
On Fri, 2011-12-30 at 12:37 +1100, NeilBrown wrote:
When
On Thu, 2012-01-05 at 18:32 +1100, NeilBrown wrote:
On Wed, 04 Jan 2012 09:50:56 +0200 Tomi Valkeinen tomi.valkei...@ti.com
wrote:
yep, that looks likely. The 'disable' routines of other panels only call
omapdss_dpi_display_disable() if (dssdev-state == OMAP_DSS_DISPLAY_ACTIVE).
This
53 matches
Mail list logo
