) world[1]
bindings documentation is available:
Documentation/devicetree/bindings/arm/omap/omap.txt
[1] http://omapedia.org/wiki/HWMOD
--
Regards,
Nishanth Menon
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More
On Thu, Jul 18, 2013 at 6:39 PM, Santosh Shilimkar
santosh.shilim...@ti.com wrote:
On Thursday 18 July 2013 02:56 PM, Nishanth Menon wrote:
On 07/18/2013 11:43 AM, Sricharan R wrote:
Some socs have a large number of interrupts/dma requests to service
the needs of its many peripherals
.
Reported-by: Marc Jüttner m-juett...@ti.com
Signed-off-by: Nishanth Menon n...@ti.com
---
arch/arm/boot/dts/omap5-uevm.dts | 12 +---
1 file changed, 9 insertions(+), 3 deletions(-)
diff --git a/arch/arm/boot/dts/omap5-uevm.dts b/arch/arm/boot/dts/omap5-uevm.dts
index ef05676..65d7b60
to SoC IP and is not enabled by PMIC by
default at boot.
Reported-by: Marc Jüttner m-juett...@ti.com
Signed-off-by: Nishanth Menon n...@ti.com
---
arch/arm/boot/dts/omap5-uevm.dts |6 ++
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git a/arch/arm/boot/dts/omap5-uevm.dts b/arch
-by: Nishanth Menon n...@ti.com
---
arch/arm/boot/dts/omap5-uevm.dts |8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/arch/arm/boot/dts/omap5-uevm.dts b/arch/arm/boot/dts/omap5-uevm.dts
index 3ff5874..ef05676 100644
--- a/arch/arm/boot/dts/omap5-uevm.dts
+++ b/arch/arm
- which is meant to be supported by this dts.
Reported-by: Marc Jüttner m-juett...@ti.com
Signed-off-by: Nishanth Menon n...@ti.com
---
arch/arm/boot/dts/omap5-uevm.dts | 18 ++
1 file changed, 18 insertions(+)
diff --git a/arch/arm/boot/dts/omap5-uevm.dts b/arch/arm/boot/dts
boards.
SMPS9 supplies TWL6040 over VDDA_2v1_AUD. This regulator needs to be
enabled only when audio is active. Since it does not come active by
default, it does not require always-on or boot-on.
Reported-by: Marc Jüttner m-juett...@ti.com
Signed-off-by: Nishanth Menon n...@ti.com
---
arch/arm
boards.
LDO6 supplies the board specified VDDS_1V2_WKUP supply going to
ldo_emu_wkup/vdds_hsic. To stay within the SoC specification supply
1.2V instead of 1.5V.
Reported-by: Marc Jüttner m-juett...@ti.com
Signed-off-by: Nishanth Menon n...@ti.com
---
arch/arm/boot/dts/omap5-uevm.dts |4
Data Manual: http://www.ti.com/product/OMAP5432
- TWL6037 / OTP information: Currently available only under NDA
Nishanth Menon (9):
ARM: dts: omap5-uevm: document regulator signals used on the actual
board
ARM: dts: omap5-uevm: update SMPS9 settings
ARM: dts: omap5-uevm: update and disable
Jüttner m-juett...@ti.com
Signed-off-by: Nishanth Menon n...@ti.com
---
arch/arm/boot/dts/omap5-uevm.dts |7 ---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/arch/arm/boot/dts/omap5-uevm.dts b/arch/arm/boot/dts/omap5-uevm.dts
index a55f4d8..c6d560b 100644
--- a/arch/arm/boot
...@ti.com
Signed-off-by: Nishanth Menon n...@ti.com
---
arch/arm/boot/dts/omap5-uevm.dts | 15 ---
1 file changed, 8 insertions(+), 7 deletions(-)
diff --git a/arch/arm/boot/dts/omap5-uevm.dts b/arch/arm/boot/dts/omap5-uevm.dts
index 6709f1e..87b3e9e 100644
--- a/arch/arm/boot/dts/omap5
'
supply to SoC IP and is not enabled by PMIC by default at boot.
Reported-by: Marc Jüttner m-juett...@ti.com
Signed-off-by: Nishanth Menon n...@ti.com
---
arch/arm/boot/dts/omap5-uevm.dts |6 ++
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git a/arch/arm/boot/dts/omap5-uevm.dts b/arch
commit 3c870e3f9d9d98f1ab98614b3b1fd5c79287d361
(regulator: palmas: Change the DT node property names to follow the convention)
Missed updating mode-sleep from sleep-mode. Fix the same.
Documentation seems proper for this property.
Signed-off-by: Nishanth Menon n...@ti.com
---
.../devicetree
We seem to have a few missing updates to device tree bindings with the
latest set of changes getting merged in.
Based on v3.11-rc1 tag
Nishanth Menon (2):
regulator: palmas-pmic: doc: fix typo for sleep-mode
regulator: palmas-pmic: doc: remove ti,tstep
.../devicetree/bindings/regulator
commit 28d1e8cd671a53d6b4f967abbbc2a55f7bd333f6
(regulator: palma: add ramp delay support through regulator constraints)
Removed the regulator's ti,step option from driver without updating the
documentation. remove the support from documentation and example as well.
Signed-off-by: Nishanth Menon
On 09:23-20130716, Nishanth Menon wrote:
We seem to have a few missing updates to device tree bindings with the
latest set of changes getting merged in.
Oops.. seems like I have an old mailID for Mark :(
Based on v3.11-rc1 tag
Nishanth Menon (2):
regulator: palmas-pmic: doc: fix typo
commit 3c870e3f9d9d98f1ab98614b3b1fd5c79287d361
(regulator: palmas: Change the DT node property names to follow the convention)
Missed updating mode-sleep from sleep-mode. Fix the same.
Documentation example seems proper for this property.
Signed-off-by: Nishanth Menon n...@ti.com
commit 28d1e8cd671a53d6b4f967abbbc2a55f7bd333f6
(regulator: palma: add ramp delay support through regulator constraints)
Removed the regulator's ti,step option from driver without updating the
documentation.
So, remove from documentation and example as well.
Signed-off-by: Nishanth Menon n
=137398467901450w=2
Based on v3.11-rc1 tag
Nishanth Menon (2):
regulator: palmas-pmic: doc: fix typo for sleep-mode
regulator: palmas-pmic: doc: remove ti,tstep
.../devicetree/bindings/regulator/palmas-pmic.txt |4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
--
1.7.9.5
Regards
34a38440689b06a515104d668494e0ff8a4e1537
(regulator: twl6030: add support for vdd1, vdd2 and vdd3 regulators)
will need a relook as well. currently part of the discussion with Mark
in [1]
[1] http://marc.info/?t=13718501633r=1w=2
--
Regards,
Nishanth Menon
--
To unsubscribe from this list: send
On 17:45-20130711, Peter Ujfalusi wrote:
On 07/11/2013 04:59 PM, Nishanth Menon wrote:
On 16:23-20130711, Peter Ujfalusi wrote:
OMAP4 no longer boots in legacy mode so the code here is no longer used.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
arch/arm/mach-omap2/twl
Balbi ba...@ti.com
Cc: Nishanth Menon n...@ti.com
works for O5.
Acked-by: Nishanth Menon n...@ti.com
--
Regards,
Nishanth Menon
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at http
be a bit of an overhead.
that said, replicating regmap logic in the driver looks a bit weird and
might allow the basis for other drivers to do the same as well as some
users of mmio would consider themselves performance sensitive :(.
--
Regards,
Nishanth Menon
--
To unsubscribe from this list
On 07/09/2013 01:51 AM, Felipe Balbi wrote:
On Mon, Jul 08, 2013 at 03:33:30PM -0500, Nishanth Menon wrote:
+static int dra7xxx_qspi_start_transfer_one(struct spi_master *master,
+ struct spi_message *m)
+{
+ struct dra7xxx_qspi *qspi = spi_master_get_devdata(master
On 15:40-20130709, Mark Brown wrote:
On Tue, Jul 09, 2013 at 07:50:55AM -0500, Nishanth Menon wrote:
with this input and looking closer, I think I see what you are saying now:
dra7xxx_qspi_prepare_xfer - does a pm_runtime_get_sync
dra7xxx_qspi_unprepare_xfer - does
On 07/09/2013 10:29 AM, Mark Brown wrote:
On Mon, Jul 08, 2013 at 12:22:36PM -0500, Nishanth Menon wrote:
case #1 - TPS62361 has a single SMPS and a single generic i2c bus,
one can talk on. In this case, you'd associate the regulator device
in one place - i2cX or on custom SoC hardware
On 07/05/2013 12:47 PM, Mark Brown wrote:
On Fri, Jul 05, 2013 at 12:33:10PM -0500, Nishanth Menon wrote:
Taking an example of twl-regulator and omap_pmic, are you suggesting
omap_pmic to be a user twl-regulator using
include/linux/regulator/consumer.h? or are you suggesting that
omap_pmic
-off-by: Amarinder Bindra a-bin...@ti.com
Acked-by: Felipe Balbi ba...@ti.com
Acked-by: Nishanth Menon n...@ti.com
Looks good to me,
Acked-by: Balaji T K balaj...@ti.com
I came across this same issue while trying MMC patches on AM3xx,
which is nor OMAP3 neither OMAP4
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Regards,
Nishanth Menon
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body
On 16:41-20130704, Mark Brown wrote:
On Fri, Jun 21, 2013 at 04:25:42PM -0500, Nishanth Menon wrote:
+static const struct omap_pmic_info omap_twl4030_vdd1 = {
+ .slave_addr = 0x12,
+ .voltage_reg_addr = 0x00,
+ .cmd_reg_addr = 0x00,
+ .i2c_timeout_us = 200,
+ .slew_rate_uV
On 07/05/2013 09:08 AM, Mark Brown wrote:
On Fri, Jul 05, 2013 at 08:55:07AM -0500, Nishanth Menon wrote:
Please write in paragraphs, an enormous wall of unbroken text isn't
helpful for legibility.
Apologies on the same. Will try to do better.
On 16:41-20130704, Mark Brown wrote:
So
On 07/05/2013 11:52 AM, Mark Brown wrote:
On Fri, Jul 05, 2013 at 09:50:34AM -0500, Nishanth Menon wrote:
On 07/05/2013 09:08 AM, Mark Brown wrote:
option 1) we just bypass get_voltage/set_voltage to point through to
this function. result will be something similar to what we got here[1]
I
state it is in.
Nope. I am not working on this.
--
Regards,
Nishanth Menon
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
... that's probably it :-(
to prevent this from happening again, Lokesh did post a patch:
https://patchwork.kernel.org/patch/2796921/
Will be good to ack it if we think it might prevent such scenarios in
the future.
--
Regards,
Nishanth Menon
--
To unsubscribe from this list: send the line
,
Nishanth Menon
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
CONFIG_WILINK_PLATFORM_DATA
--
1.7.10.4
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Regards,
Nishanth Menon
--
To unsubscribe from this list: send the line
Tony,
Any chance of picking these up?
I see that next-20130701 is broke as well in an OMAP5 only build. beyond
the fixes already merged in - the missing series seems to be the
$subject series to allow an OMAP5 only build.
On 06/26/2013 09:39 AM, Nishanth Menon wrote:
Hi,
Cortex-A15 based
On 11:47-20130627, Luciano Coelho wrote:
(added mailing lists and everyone back to the thread)
On Wed, 2013-06-26 at 23:38 -0500, Nishanth Menon wrote:
On 06/25/2013 03:35 AM, Luciano Coelho wrote:
+Optional properties:
+
+
+- refclock: the internal WLAN
On Thu, Jun 27, 2013 at 7:58 AM, Luciano Coelho coe...@ti.com wrote:
On Thu, 2013-06-27 at 07:51 -0500, Nishanth Menon wrote:
On 11:47-20130627, Luciano Coelho wrote:
(added mailing lists and everyone back to the thread)
On Wed, 2013-06-26 at 23:38 -0500, Nishanth Menon wrote:
On 06/25
,
Nishanth Menon
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
On 06/27/2013 08:19 AM, Luciano Coelho wrote:
On Thu, 2013-06-27 at 08:15 -0500, Nishanth Menon wrote:
On Thu, Jun 27, 2013 at 7:58 AM, Luciano Coelho coe...@ti.com wrote:
For the actual DTS files, I could add a wilink.dtsi with enumerations
for these values so they could be used in the node
On Thu, Jun 27, 2013 at 8:30 AM, Luciano Coelho coe...@ti.com wrote:
On Thu, 2013-06-27 at 08:23 -0500, Nishanth Menon wrote:
On 06/27/2013 08:19 AM, Luciano Coelho wrote:
On Thu, 2013-06-27 at 08:15 -0500, Nishanth Menon wrote:
On Thu, Jun 27, 2013 at 7:58 AM, Luciano Coelho coe...@ti.com
On 06/27/2013 01:51 PM, Luciano Coelho wrote:
On Thu, 2013-06-27 at 08:39 -0500, Nishanth Menon wrote:
On Thu, Jun 27, 2013 at 8:30 AM, Luciano Coelho coe...@ti.com wrote:
On Thu, 2013-06-27 at 08:23 -0500, Nishanth Menon wrote:
On 06/27/2013 08:19 AM, Luciano Coelho wrote:
On Thu, 2013-06
On 06/27/2013 02:46 PM, Luciano Coelho wrote:
On Thu, 2013-06-27 at 14:12 -0500, Nishanth Menon wrote:
[...]
Indexes to another entity is always a maintenance burden in the longer
run and needs judicious control. If it is possible to avoid it by
selecting the right parameters, I am a hard
-base))
return PTR_ERR(sr_info-base);
- }
irq = platform_get_resource(pdev, IORESOURCE_IRQ, 0);
Acked-by: Nishanth Menon n...@ti.com
--
Regards,
Nishanth Menon
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message
On Wed, Jun 26, 2013 at 3:03 AM, Ruslan Bilovol ruslan.bilo...@ti.com wrote:
Hi Nishanth,
On Tue, Jun 25, 2013 at 3:43 PM, Nishanth Menon n...@ti.com wrote:
On 06/25/2013 07:01 AM, Nishanth Menon wrote:
On 06/25/2013 06:32 AM, Ruslan Bilovol wrote:
The OMAP4 Blaze Tablet is TI OMAP4
to `scu_power_mode'
Reported-by: Pekon Gupta pe...@ti.com
Reported-by: Vincent Stehlé v-ste...@ti.com
Acked-by: Santosh Shilimkar santosh.shilim...@ti.com
Signed-off-by: Nishanth Menon n...@ti.com
---
arch/arm/mach-omap2/sleep44xx.S |6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git
-in.o: In function `omap4_smp_prepare_cpus':
arch/arm/mach-omap2/omap-smp.c:211: undefined reference to `scu_enable'
Reported-by: Pekon Gupta pe...@ti.com
Reported-by: Vincent Stehlé v-ste...@ti.com
Acked-by: Santosh Shilimkar santosh.shilim...@ti.com
Signed-off-by: Nishanth Menon n...@ti.com
to be fixed in various attempts in the past [2] [3].
This series applies on top of the other fixes in discussion for linux-next [4]
[5].
Based on:
git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git next-20130626
Nishanth Menon (2):
ARM: OMAP4: sleep: build OMAP4 specific functions only
://svtronics.com/omap/sevm4460,blaze,omap might help too :)
[...]
+
+#include twl6030.dtsi
+
Might be good to see the TWL interrupt pin information made available as
well?
[...]
Regards,
Nishanth Menon
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message
On 06/25/2013 07:01 AM, Nishanth Menon wrote:
On 06/25/2013 06:32 AM, Ruslan Bilovol wrote:
The OMAP4 Blaze Tablet is TI OMAP4 processor-based
development platform in a tablet formfactor.
The platform contains many of the features found in
present-day handsets (such as audio, video, wireless
On 15:55-20130625, Santosh Shilimkar wrote:
On Tuesday 25 June 2013 03:20 PM, Paul Walmsley wrote:
Santosh,
On Fri, 21 Jun 2013, Nishanth Menon wrote:
/*
* XXX Will depend on the process, validation, and binning
* for the currently-running IC. Use OMAP4 data for time
for it to boot, I suggest removing it.
Regards,
Nishanth Menon
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
On 16:59-20130625, Santosh Shilimkar wrote:
On Tuesday 25 June 2013 04:56 PM, Kevin Hilman wrote:
Santosh Shilimkar santosh.shilim...@ti.com writes:
On Tuesday 25 June 2013 04:17 PM, Nishanth Menon wrote:
On Tue, Jun 25, 2013 at 3:12 PM, Santosh Shilimkar
santosh.shilim...@ti.com wrote
On 18:43-20130625, Santosh Shilimkar wrote:
On Tuesday 25 June 2013 06:36 PM, Nishanth Menon wrote:
On 16:59-20130625, Santosh Shilimkar wrote:
On Tuesday 25 June 2013 04:56 PM, Kevin Hilman wrote:
Santosh Shilimkar santosh.shilim...@ti.com writes:
On Tuesday 25 June 2013 04:17 PM
.
This also fixes the build breakage for voltagedomains54xx_data.c when just
OMAP5 SoC is enabled: https://patchwork.kernel.org/patch/2764191/
Reported-by: Arnd Bergmann a...@arndb.de
Signed-off-by: Nishanth Menon n...@ti.com
Cc: Kevin Hilman khil...@deeprootsystems.com
Cc: Benoit Cousson b-cous
On 10:51-20130621, Mark Brown wrote:
On Thu, Jun 20, 2013 at 07:45:42AM -0500, Nishanth Menon wrote:
On 23:38-20130619, Mark Brown wrote:
If the consumer can tolerate a different voltage why not just request
the range that can be tolerated? Your problem here is specifying an
exact
,
__func__, shift, node-name);
--
1.7.9.5
--
Regards,
Nishanth Menon
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
;
omap5_voltdm_core.volt_data = omap446x_vdd_core_volt_data;
#endif
Should we just remove this instead? these are obviously wrong.
--
Regards,
Nishanth Menon
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info
TPS62361 is used for cpufreq regulation. As part of this change
use labels that can be used to reference cpu0 to setup it's supply.
Signed-off-by: Nishanth Menon n...@ti.com
---
arch/arm/boot/dts/omap4-panda-es.dts |4
arch/arm/boot/dts/omap4.dtsi |4 ++--
arch/arm/boot/dts
to the voltage processor.
[grygorii.stras...@ti.com, ta...@ti.com: co-developer]
Signed-off-by: Grygorii Strashko grygorii.stras...@ti.com
Signed-off-by: Taras Kondratiuk ta...@ti.com
Signed-off-by: Nishanth Menon n...@ti.com
---
.../devicetree/bindings/power/omap-vc.txt | 99 ++
drivers
-developer]
Signed-off-by: Grygorii Strashko grygorii.stras...@ti.com
Signed-off-by: Taras Kondratiuk ta...@ti.com
Signed-off-by: Nishanth Menon n...@ti.com
---
.../bindings/regulator/omap-pmic-regulator.txt | 41 ++
drivers/regulator/Kconfig | 12 +
drivers
discussion:
v1 of RFC: http://marc.info/?t=13692468965r=1w=2
related discussion: http://marc.info/?t=13716695495r=1w=2
Nishanth Menon (8):
regulator: Introduce OMAP regulator to control PMIC over VC/VP
PM / AVS: Introduce support for OMAP Voltage Controller(VC) with
device tree
Unlike other OMAP4 platforms including the the vanilla PandaBoard,
PandaBoard-ES uses TPS62361 to supply vdd_mpu.
Signed-off-by: Nishanth Menon n...@ti.com
---
arch/arm/boot/dts/omap4-panda-es.dts | 18 ++
arch/arm/boot/dts/tps62361_omap.dtsi | 18 ++
2 files
and OMAP Voltage Controller.
[grygorii.stras...@ti.com, ta...@ti.com: co-developer]
Signed-off-by: Grygorii Strashko grygorii.stras...@ti.com
Signed-off-by: Taras Kondratiuk ta...@ti.com
Signed-off-by: Nishanth Menon n...@ti.com
---
.../devicetree/bindings/power/omap-vp.txt | 39 +
drivers
OMAP443x, OMAP446x SoC use same offsets for voltage controller,
however their voltage characteristics differ a little.
Introduce the voltage controller nodes for the same.
Signed-off-by: Nishanth Menon n...@ti.com
---
arch/arm/boot/dts/omap4.dtsi| 26 ++
arch/arm
OMAP443x, OMAP446x SoC use same offsets for voltage processor,
however their voltage characteristics differ a little.
Introduce the voltage processor nodes for the same.
Signed-off-by: Nishanth Menon n...@ti.com
---
arch/arm/boot/dts/omap4.dtsi| 43
on 4460.
Signed-off-by: Nishanth Menon n...@ti.com
---
arch/arm/boot/dts/omap4-panda-common.dtsi |1 +
arch/arm/boot/dts/omap4-panda-es.dts | 13 +++
arch/arm/boot/dts/omap4-sdp.dts |1 +
arch/arm/boot/dts/omap4-var-som.dts |1 +
arch/arm/boot/dts
On 23:38-20130619, Mark Brown wrote:
On Wed, Jun 19, 2013 at 02:17:54PM -0500, Nishanth Menon wrote:
Account for step size accuracy when exact voltage requests are send for
step based regulators.
If the consumer can tolerate a different voltage why not just request
the range that can
On 07:45-20130620, Nishanth Menon wrote:
On 23:38-20130619, Mark Brown wrote:
On Wed, Jun 19, 2013 at 02:17:54PM -0500, Nishanth Menon wrote:
Account for step size accuracy when exact voltage requests are send for
step based regulators.
If the consumer can tolerate a different
to omap4460
+ */
+/*
+ * clocks specific to omap4430
+ */
+/*
+ * clocks common to omap44xx
+ */
could be dropped?
btw, are we differentiating 4430 and 4460?A
Example:
bandgap_fclk in 4430
Vs
div_ts_ck, bandgap_ts_fclk in 4460?
--
Regards,
Nishanth Menon
--
To unsubscribe from this list: send
On 16:49-20130619, Tero Kristo wrote:
On 06/19/2013 04:30 PM, Nishanth Menon wrote:
On 16:19-20130619, Tero Kristo wrote:
[...]
+
+/*
+ * clocks specific to omap4460
+ */
+/*
+ * clocks specific to omap4430
+ */
+/*
+ * clocks common to omap44xx
+ */
could be dropped?
Same
(example
12.66mV step size), the closest achievable would be 506.4.
regulator_set_voltage_tol does not work out either as 500mV is not an
operational voltage.
Account for step size accuracy when exact voltage requests are send for
step based regulators.
Signed-off-by: Nishanth Menon n...@ti.com
scenarios we had seen in the
past on OMAP.
Overall, I love this idea.
Acked-by: Nishanth Menon n...@ti.com
Then, in terms of merging, probably Kevin would be the right person for
this since he's done much of the voltagedomain work.
--
Regards,
Nishanth Menon
--
To unsubscribe from this list: send
On 19:01-20130610, Mark Brown wrote:
On Mon, Jun 10, 2013 at 12:51:42PM -0500, Nishanth Menon wrote:
a) Tegra seems to use Lookup Table for sending predefinied voltage
values to PMIC. OMAP has no concept of lookup table.
They seem to be doing basically the same thing here, you've got
On 15:47-20130613, Mark Brown wrote:
On Thu, Jun 13, 2013 at 08:39:50AM -0500, Nishanth Menon wrote:
I am having a bit of a difficulty trying to understand your concern
here.
Your device tree for this stuff appears to mostly consist of repeating
the description of the PMIC that we
On Thu, Jun 13, 2013 at 10:07 AM, Mark Brown broo...@kernel.org wrote:
On Thu, Jun 13, 2013 at 09:58:03AM -0500, Nishanth Menon wrote:
I am proposing moving the following into OF match data.
ti,i2c-slave-address
ti,i2c-voltage-register
ti,i2c-command-register
ti,slew-rate-microvolt
ti,step
+Paul.
On Mon, Jun 10, 2013 at 5:31 AM, Mark Brown broo...@kernel.org wrote:
On Wed, May 22, 2013 at 01:18:34PM -0500, Nishanth Menon wrote:
So, the biggest problem here has been patch 4 (having to have a hack to
deploy this stuff is a bit worrying) plus the general not having a real
driver
On Mon, Jun 10, 2013 at 11:49 AM, Mark Brown broo...@kernel.org wrote:
On Mon, Jun 10, 2013 at 11:16:59AM -0500, Nishanth Menon wrote:
On Mon, Jun 10, 2013 at 5:31 AM, Mark Brown broo...@kernel.org wrote:
On Wed, May 22, 2013 at 01:18:34PM -0500, Nishanth Menon wrote:
So, the biggest
on OMAP3-based
platforms with twl4030. Tested on 3530/Beagle, 3730/Beagle-xM,
3530/Overo, 3730/Overo-STORM.
Special thanks to Florian Vaussard for suggesting use of preprocessor
feature.
Cc: Florian Vaussard florian.vauss...@epfl.ch
Cc: Benoit Cousson b-cous...@ti.com
Cc: Nishanth Menon n
On 23:21-20130606, Sricharan R wrote:
Hi,
On Wednesday 05 June 2013 07:27 PM, Nishanth Menon wrote:
On 12:16-20130605, Sricharan R wrote:
From: Roger Quadros rog...@ti.com
[...]
diff --git a/arch/arm/boot/dts/omap5-uevm.dts
b/arch/arm/boot/dts/omap5-uevm.dts
index 843a001..cf862df
*/
+ ;
+ };
+};
--
Regards,
Nishanth Menon
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Regards,
Nishanth Menon
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
On Fri, May 24, 2013 at 5:15 PM, Kevin Hilman khil...@linaro.org wrote:
Kevin Hilman khil...@linaro.org writes:
Nishanth Menon n...@ti.com writes:
[...]
Actually 2 things:
a) patch seems to do the wrong thing for 4460 - 0x18 offset should
have been used instead of 0x14 which is correct
at http://vger.kernel.org/majordomo-info.html
--
Regards,
Nishanth Menon
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
On 15:09-20130524, Nishanth Menon wrote:
On 12:28-20130524, Kevin Hilman wrote:
Earlier commits ensured proper muxing of pins related to proper
TWL6030 behavior: see commit 265a2bc8 (ARM: OMAP3: TWL4030: ensure
sys_nirq1 is mux'd and wakeup enabled) and commit 1ef43369 (ARM:
OMAP4: TWL
On Fri, May 24, 2013 at 4:19 PM, Kevin Hilman khil...@linaro.org wrote:
Nishanth Menon n...@ti.com writes:
On 15:09-20130524, Nishanth Menon wrote:
On 12:28-20130524, Kevin Hilman wrote:
Earlier commits ensured proper muxing of pins related to proper
TWL6030 behavior: see commit 265a2bc8
for 4430 sdp: http://pastebin.com/SkAGB273
4. Once this approach is agreed upon, I can do the dts changes for all SoCs
OMAP3-5 and will post a formal series.
Related defects:
https://bugzilla.kernel.org/show_bug.cgi?id=58541
https://bugzilla.kernel.org/show_bug.cgi?id=58611
Nishanth Menon
-by: Nishanth Menon n...@ti.com
---
arch/arm/boot/dts/omap4-panda-es.dts | 55 +++--
arch/arm/boot/dts/omap4.dtsi | 84 +++
arch/arm/boot/dts/omap4460.dtsi |1 +
arch/arm/boot/dts/tps62361.dtsi | 90
and OMAP Voltage Controller.
[grygorii.stras...@ti.com: co-developer]
Signed-off-by: Grygorii Strashko grygorii.stras...@ti.com
Signed-off-by: Nishanth Menon n...@ti.com
---
.../devicetree/bindings/power/omap-vp.txt | 39 +
drivers/power/avs/Makefile |2
]
Signed-off-by: Grygorii Strashko grygorii.stras...@ti.com
Signed-off-by: Nishanth Menon n...@ti.com
---
.../bindings/regulator/omap-pmic-regulator.txt | 121 +
drivers/regulator/Kconfig | 12 +
drivers/regulator/Makefile |1 +
drivers
to the voltage processor.
[grygorii.stras...@ti.com: co-developer]
Signed-off-by: Grygorii Strashko grygorii.stras...@ti.com
Signed-off-by: Nishanth Menon n...@ti.com
---
.../devicetree/bindings/power/omap-vc.txt | 99 ++
drivers/power/avs/Kconfig | 15 +
drivers
to hold DDR power, maybe this is not
even relevant and the GPIO bank can safely be reset?
Thanks,
Vaibhav
--
Regards,
Nishanth Menon
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at http
(board dts)
b) reserve GPIO as well so that no other driver'd take it - if they
attempt ther'd at least be some form of warning.
--
Regards,
Nishanth Menon
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info
this
+ gpios = gpio4 14 0;
needed
+ linux,default-trigger = heartbeat;
can be dropped
+ };
+ mmc {
+ label = pandaboard::status2;
could be dropped
+ gpios = gpio1 8 0;
needed
+ linux,default-trigger = mmc0;
could be dropped.
--
Regards,
Nishanth
{
+ gpios = gpio4 14 0;
+ };
+ mmc {
+ gpios = gpio1 8 0;
+ };
+};
--
Regards,
Nishanth Menon
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at http
to do it IMHO. Will allow the driver to exist when
HWMOD will be eventually replaced by some other framework.
[1]: http://pastebin.com/XPmAB1Zb
--
Regards,
Nishanth Menon
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord
On Thu, May 16, 2013 at 10:35 AM, Dan Murphy dmur...@ti.com wrote:
I am not sure you really want to do this.
If I make the pinctrl part of the led structure then the only way the
gpio_wk7 on a1-a3 to be configured is when
the CONFIG_LEDS_GPIO flag is set.
Do you really want that dependency?
On Thu, May 16, 2013 at 3:22 PM, Dan Murphy dmur...@ti.com wrote:
On 05/16/2013 01:18 PM, Nishanth Menon wrote:
On Thu, May 16, 2013 at 10:35 AM, Dan Murphy dmur...@ti.com wrote:
I am not sure you really want to do this.
If I make the pinctrl part of the led structure then the only way
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Regards,
Nishanth Menon
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body
1101 - 1200 of 2389 matches
Mail list logo
