Folks,
Dumb question:
Some one seen this one? is there a patch in the pipe for the fix?
scripts/kconfig/conf --silentoldconfig Kconfig
arch/arm/Kconfig:1277:error: recursive dependency detected!
arch/arm/Kconfig:1277: symbol SMP depends on CPU_V6K
arch/arm/mm/Kconfig:407:symbol CPU_V6K
+ Russell,
-Original Message-
From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap-
ow...@vger.kernel.org] On Behalf Of Menon, Nishanth
Sent: Saturday, March 05, 2011 1:51 PM
To: linux-omap
Subject: pm-core: recursive dependency on config
Folks,
Dumb question:
Some one seen
Hi,
On Fri, 2011-03-04 at 14:52 -0600, Steve Sakoman wrote:
This patch adds support for the Gumstix Palo35 expansion board
which utilizes the 320 x 240 pixel LG.Philips LB035Q02 LCD Panel
Signed-off-by: Steve Sakoman st...@sakoman.com
---
drivers/video/omap2/displays/Kconfig
The Series Updates OPP Table for MPU, add OPP enteries
for IVA and update Voltage Rail values for MPU/IVA.
It is based on the Patch which replaces
Voltage values with Macros, Submitted by
Nishanth Menon
https://patchwork.kernel.org/patch/607541/
Branch: pm-core
Tested on OMAP4430 SDP.
V2:
Almost all OMAP4 boards support OPP 800 MHz and OPP 1 GHz.
Enable them in OPP Table. For small minority of boards which use
OMAP4430-800 MHz device OPP 1GHz is not supported,
OPP 1GHz should be disabled from board file.
Signed-off-by: Shweta Gulati shweta.gul...@ti.com
Cc:
Update MPU/IVA voltage Rail values obtained from
OMAP4430 Data Manual Operating Condition Addendum_v0.3.
Tested on OMAP4430 SDP Board.
Signed-off-by: Shweta Gulati shweta.gul...@ti.com
Cc: linux-arm-ker...@lists.infradead.org
---
arch/arm/mach-omap2/opp4xxx_data.c | 14 +++---
1
This Patch adds OPP enteries for IVA in OMAP4 OPP Table
Tested on OMAP4430 SDP Board.
Signed-off-by: Shweta Gulati shweta.gul...@ti.com
Cc: linux-arm-ker...@lists.infradead.org
---
arch/arm/mach-omap2/opp4xxx_data.c |8 +++-
1 files changed, 7 insertions(+), 1 deletions(-)
diff --git
On Sat, Mar 05, 2011 at 02:11:29PM +0530, Santosh Shilimkar wrote:
+ Russell,
-Original Message-
From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap-
ow...@vger.kernel.org] On Behalf Of Menon, Nishanth
Sent: Saturday, March 05, 2011 1:51 PM
To: linux-omap
Subject:
2011/3/4 Nishanth Menon n...@ti.com:
From: Vishwanath BS vishwanath...@ti.com
Since all voltage data is now centralized in oppxxx_data.c, we can remove
the replace the values in the opp table with the macros used for voltage
values. This will avoid opp table and voltage layer having
From: Vishwanath BS vishwanath...@ti.com
Since all voltage data is now centralized in oppxxx_data.c, we can replace
the values in the opp table with the macros used for voltage values.
This will avoid opp table and voltage layer having conflicting values.
Signed-off-by: Vishwanath BS
On Sat, Mar 5, 2011 at 1:18 AM, Tomi Valkeinen tomi.valkei...@ti.com wrote:
Hi,
On Fri, 2011-03-04 at 14:52 -0600, Steve Sakoman wrote:
This patch adds support for the Gumstix Palo35 expansion board
which utilizes the 320 x 240 pixel LG.Philips LB035Q02 LCD Panel
Signed-off-by: Steve
This patch series adds support for the set of display devices available
for the Overo COM products: DVI, S-Video, the Samsung LTE430WQ-F0C LCD
panel, and the LG.Philips LB035Q02 panel.
Tested with applicable expansion boards for each option: Tobi, Palo43,
Chestnut43, and Palo35.
Changes from
This patch adds support for the Gumstix Palo35 expansion board
which utilizes the 320 x 240 pixel LG.Philips LB035Q02 LCD Panel
Signed-off-by: Steve Sakoman st...@sakoman.com
---
drivers/video/omap2/displays/Kconfig |6 +
drivers/video/omap2/displays/Makefile |
This patch adds DSS2 support for DVI, S-video, the 480x272 Samsung
LTE430WQ-F0C panel, and the 320x240 LG.Philips LB035Q02 panel.
Signed-off-by: Steve Sakoman st...@sakoman.com
---
arch/arm/mach-omap2/board-overo.c | 239 +++--
1 files changed, 202 insertions(+),
Allow build with CONFIG_PM disabled. Esp when bringing up new
Silicon, this is a useful and often important requirement.
Instead we allow for CONFIG_PM to be selectable as desired.
Currently voltage files messup the build
Note: this is just a proposal - I have'nt actually done a clean build,
On Sat, 2011-03-05 at 07:58 -0600, Steve Sakoman wrote:
This patch series adds support for the set of display devices available
for the Overo COM products: DVI, S-Video, the Samsung LTE430WQ-F0C LCD
panel, and the LG.Philips LB035Q02 panel.
Tested with applicable expansion boards for each
Hi,
This series intends to introduce SmartReflex AVS Class 1.5 support which
is now the recommended AVS class for usage in OMAP3630, OMAP4 and potentially
in later generation of silicon as well. Smartreflex class 1.5 is a software
controlled hardware calibration mechanism designed to improve DVFS
OMAP3 SmartReflex IRQs in hwmod structures with the same naming as
present in OMAP4. Without these IRQs being registered, SmartReflex
driver will be unable to get the IRQ numbers to handle notifications
Signed-off-by: Nishanth Menon n...@ti.com
---
arch/arm/mach-omap2/omap_hwmod_3xxx_data.c |
Handle the case for a future SoC where sys_ck_name might be
uninitialized. Fixes the build warning:
arch/arm/mach-omap2/voltage.c: In function 'omap_voltage_late_init':
arch/arm/mach-omap2/voltage.c:86:8: warning: 'sys_ck_name' may be used
uninitialized in this function
Signed-off-by: Nishanth
Blindly setting a 1.2V setting in the initial structure may not even
match the default voltages stored in the voltage table which are
supported for the domain. For example, OMAP3430 core domain does not
use 1.2V and ends up generating a warning on the first transition.
Further, since
cat of debugfs entry for vp_volt provides voltage. The additional pr_notice
is just spam on console and provides no additional information.
Signed-off-by: Nishanth Menon n...@ti.com
---
arch/arm/mach-omap2/voltage.c |1 -
1 files changed, 0 insertions(+), 1 deletions(-)
diff --git
Use IS_ERR_OR_NULL macro instead of !xyz || IS_ERR(xyz) usage.
Signed-off-by: Nishanth Menon n...@ti.com
---
arch/arm/mach-omap2/voltage.c | 22 +++---
1 files changed, 11 insertions(+), 11 deletions(-)
diff --git a/arch/arm/mach-omap2/voltage.c b/arch/arm/mach-omap2/voltage.c
Voltage values can get confusing in meaning with various SmartReflex
classes being active. Depending on the class used, the actual voltage
selected might be a variant. For example:
With SmartReflex AVS class 3:
a) If we don't have SR enabled, we will go to volt_nominal.
b) If have SR enabled, we
Transdone event in Voltage processor gives us fine grained status on
the current status of the voltage communication with the PMIC.
Unfortunately, IRQ generation by VP is based on the start of the
transmission to VC from VP, not at the end (or the completion of
the voltage setting). Hence any
Interrupt notification mechanism of SmartReflex can be used by the
choice of implementation of the class driver. For example, Class 2 and
Class 1.5 of SmartReflex can both use the interrupt notification to
identify the transition of voltage or other events.
Hence, the actual class does not matter
We will enable and disable interrupt on a need basis in the class
driver. We need to keep the IRQ disabled by default else the
forceupdate or vcbypass events could trigger events that we don't
need/expect to handle.
This is a preparation for SmartReflex AVS class drivers such as
class 2 and class
Since we already know the state of the autocomp enablement, we can
see if the requested state is different from the current state and
enable/disable SR only on the need basis.
Signed-off-by: Nishanth Menon n...@ti.com
---
arch/arm/mach-omap2/smartreflex.c | 11 +++
1 files changed, 7
Error label case seems to have a 2 tab indentation when just 1 is
necessary.
Signed-off-by: Nishanth Menon n...@ti.com
---
arch/arm/mach-omap2/smartreflex.c | 20 ++--
1 files changed, 10 insertions(+), 10 deletions(-)
diff --git a/arch/arm/mach-omap2/smartreflex.c
Certain class drivers such as class 1.5 drivers, will need specific
notification that they have to be started up or stopped independent
of smart reflex operation. They also may need private data to be
used for operations of their own, provide the same.
This allows the class driver to initialize
From: Jarkko Nikula jhnik...@gmail.com
sr_start_vddautocomp and sr_stop_autocomp functions can be reused from
omap_sr_enable, omap_sr_disable and omap_sr_disable_reset_volt and by
adding one additional argument sr_stop_autocomp. This allows us to have
a single point where SR enable and disable
SmartReflex IP V1 and V2 have different registers and offsets.
Currently, we pass the status as is to the class driver. However,
since we don't pass the version of the underlying SR hardware
to the Class driver, it will not be unable to make consistent
sense of the status bits coming over to it.
We need some mechanism from class drivers to control when notifiers
should be triggered and when not, currently we have none, which makes
Class driver usage of the interrupt events almost impossible.
Introduce an SmartReflex driver API for doing the same. This is useful
for SmartReflex AVS class
At times with bad SR configurations, especially during silicon bring-ups,
we could get continuous spurious interrupts which end up hanging the
platform in the form of an ISR call for status bits that are
automatically enabled by the hardware without any software clearing
option.
If we detect
Passing the volt_data pointers across allows us to save us the effort
of looking up the voltage data pointer from the voltage value at
multiple layers, we need to look at the voltage data in DVFS layer
for further processing, so modify the APIs to pass the voltage data
pointer all the way through
Traditional SmartReflex AVS(Automatic Voltage Scaling) classes are:
* Class 0 - Product test calibration
Silicon is calibration at production floor and fused with voltages
for each OPP
* Class 1 - Boot time calibration
Silicon is calibrated once at boot time and voltages
Use SmartReflex AVS Class3 initialization only for OMAP343x family of
processors.
Signed-off-by: Nishanth Menon n...@ti.com
---
arch/arm/mach-omap2/smartreflex-class3.c |5 +
1 files changed, 5 insertions(+), 0 deletions(-)
diff --git a/arch/arm/mach-omap2/smartreflex-class3.c
The ads7846 driver now requires a regulator. This patch adds the
necessary regulator to the overo board file. Without it, the
following error occurs (and the touchscreen will not function):
ads7846 spi1.0: unable to get regulator: -19
Signed-off-by: Steve Sakoman st...@sakoman.com
---
Note:
Hi Nishanth,
On Sat, Mar 5, 2011 at 5:29 PM, Nishanth Menon n...@ti.com wrote:
Use IS_ERR_OR_NULL macro instead of !xyz || IS_ERR(xyz) usage.
Signed-off-by: Nishanth Menon n...@ti.com
---
arch/arm/mach-omap2/voltage.c | 22 +++---
1 files changed, 11 insertions(+), 11
David Cohen wrote, on 03/05/2011 11:06 PM:
[..]
diff --git a/arch/arm/mach-omap2/voltage.c b/arch/arm/mach-omap2/voltage.c
index 53c399f..76bcaee 100644
--- a/arch/arm/mach-omap2/voltage.c
+++ b/arch/arm/mach-omap2/voltage.c
@@ -682,7 +682,7 @@ unsigned long omap_voltage_get_nom_volt(struct
39 matches
Mail list logo
