From: J Keerthy j-keer...@ti.com
The SMPS10 regulator is not presesnt in all the variants
of the PALMAS PMIC family. Hence adding a feature to distingush
between them.
Signed-off-by: J Keerthy j-keer...@ti.com
---
drivers/mfd/palmas.c | 27 ---
From: J Keerthy j-keer...@ti.com
The Patch adds TPS659038 PMIC support in the palmas mfd driver.
The TPS659038 has almost the same registers as of the earlier
supported variants of PALMAS family such as the TWL6035.
The critical differences between TPS659038 and TWL6035 being:
1) TPS659038 has
From: J Keerthy j-keer...@ti.com
Check if irq value obtained is valid. If it is not valid
then skip the irq request step and go ahead with the probe.
Signed-off-by: J Keerthy j-keer...@ti.com
---
drivers/mfd/palmas.c |6 ++
1 files changed, 6 insertions(+), 0 deletions(-)
diff --git
From: J Keerthy j-keer...@ti.com
The Patch series adds TPS659038 PMIC support in the palmas MFD and Regulator
drivers. The TPS659038 has almost the same registers as of the earlier
supported variants of PALMAS family such as the TWL6035.
The critical differences between TPS659038 and TWL6035
Hi Benoit,
On 06/19/2013 04:17 AM, Benoit Cousson wrote:
Hi Roger,
On 06/18/2013 11:04 AM, Roger Quadros wrote:
Provide the RESET and Power regulators for the USB PHY,
the USB Host port mode and the PHY device.
Also provide pin multiplexer information for the USB host
pins.
* Roger Quadros rog...@ti.com [130619 00:42]:
Hi Benoit,
On 06/19/2013 04:17 AM, Benoit Cousson wrote:
Hi Roger,
On 06/18/2013 11:04 AM, Roger Quadros wrote:
Provide the RESET and Power regulators for the USB PHY,
the USB Host port mode and the PHY device.
Also provide pin
On Mon, 17 Jun 2013, J Keerthy wrote:
Remove code which is not necessary for a device tree boot.
So we're exclusively DT now right?
Boot tested on OMAP5-UEVM board.
Signed-off-by: J Keerthy j-keer...@ti.com
---
drivers/mfd/palmas.c | 106
Hi all,
These two patches introduces initial support for the IGEP AM335x-based
platforms. The first patch add support for IGEP COM AQUILA products, and the
second patch add support for the development board.
These patches apply on top of bcousson/for_3.11/dts repository.
Best regards,
Enric
The IGEP AQUILA EXPANSION board is a development platform for the IGEP COM
AQUILA AM335x boards.
The board adds the following connectivity:
o USB OTG
o USB HOST
o HDMI
o Ethernet
o Serial Debug (3.3V)
o 2x46 pin headers
o EEPROM
Signed-off-by: Enric Balletbo i Serra
The IGEP COM AQUILA is industrial processors SODIMM module with
following highlights:
o AM3352/AM3354/AM3358/AM3359 Texas Instruments processor
o Cortex-A8 ARM CPU
o 3.3 volts Inputs / Outputs use industrial
o 256 MB DDR3 SDRAM / 128 Megabytes FLASH
o MicroSD card reader on-board
Hi Lee,
On Wed, Jun 19, 2013 at 09:26:33AM +0100, Lee Jones wrote:
On Mon, 17 Jun 2013, J Keerthy wrote:
Remove code which is not necessary for a device tree boot.
So we're exclusively DT now right?
Boot tested on OMAP5-UEVM board.
Signed-off-by: J Keerthy j-keer...@ti.com
---
On Fri, 07 Jun 2013, Oleksandr Kozaruk wrote:
From: Graeme Gregory g...@slimlogic.co.uk
The TWL6025 was never released beyond sample form and was replaced by
the PhoenixLite range of chips - TWL6032. Change the references to
reference the TWL6032 class and name the registers to twl6032 in
On Wed, 19 Jun 2013, Lee Jones wrote:
On Mon, 17 Jun 2013, J Keerthy wrote:
Remove code which is not necessary for a device tree boot.
So we're exclusively DT now right?
Boot tested on OMAP5-UEVM board.
Signed-off-by: J Keerthy j-keer...@ti.com
---
drivers/mfd/palmas.c |
Now that MUSB for OMAP started using devm_usb_get_phy_by_name
which does not require PHY library to already have the binding
information, removed usb_bind_phy calls that binds the MUSB controller
with the PHY from the board files.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
Acked-by:
After the devices are created using PLATFORM_DEVID_AUTO,
devm_usb_get_phy_dev and usb_get_phy_dev can't be used reliably
as it relies on the device_names passed in usb_bind_phy. So used the
new API devm_usb_get_phy_by_name to get the PHY reference.
Signed-off-by: Kishon Vijay Abraham I
In order for controllers to get PHY in case of non dt boot, the phy
binding information (phy label) should be added in the platform
data of the controller.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
Acked-by: Felipe Balbi ba...@ti.com
Tested-by: Tomi Valkeinen tomi.valkei...@ti.com
---
In the case of non-dt boot, the platform specific initialization file
(board file) will do usb_bind_phy that binds the usb controller with the
PHY using device names. After the device names are created using
PLATFORM_DEVID_AUTO, our original method of binding by device names doesn't
work reliably
After the devices are created using PLATFORM_DEVID_AUTO,
devm_usb_get_phy_dev and usb_get_phy_dev can't be used reliably
as it relies on the device_names passed in usb_bind_phy. So
added a new API to get the PHY reference by PHY label (PHY label
should be filled which creating the PHY).
Hello,
Thank you for the review.
On 06/12/2013 03:05 PM, Grant Likely wrote:
On Tue, 11 Jun 2013 16:48:56 +0200, Florian Vaussard florian.vauss...@epfl.ch
wrote:
These constants can be used to easily declare MTD partitions inside
DTS.
The constants MTDPART_OFS_* are purposely not included.
Hello Benoit,
On 06/12/2013 06:18 PM, Cousson, Benoit wrote:
Hi Florian,
On 6/12/2013 8:42 AM, Florian Vaussard wrote:
Hello Grant,
On 06/11/2013 11:57 PM, Grant Likely wrote:
On Tue, 11 Jun 2013 16:50:50 +0200, Florian Vaussard
florian.vauss...@epfl.ch wrote:
Pinctrl headers were not
Hello Benoit,
Any comments on this series?
Regards,
Florian
On 06/11/2013 04:49 PM, Florian Vaussard wrote:
Hello,
This series performs several updates to omap3-overo and omap3-tobi.
Patch 1 is necessary to patch 2 for the IRQ constant. The SMSC911X is
largely taken from omap3-igep.
Hi Florian,
On 06/19/2013 04:28 AM, Florian Vaussard wrote:
Hello Benoit,
On 06/12/2013 06:18 PM, Cousson, Benoit wrote:
Hi Florian,
On 6/12/2013 8:42 AM, Florian Vaussard wrote:
Hello Grant,
On 06/11/2013 11:57 PM, Grant Likely wrote:
On Tue, 11 Jun 2013 16:50:50 +0200, Florian Vaussard
On 06/19/2013 04:29 AM, Florian Vaussard wrote:
Hello Benoit,
Any comments on this series?
That series looks good to me. I've just applied it.
Thanks,
Benoit
Regards,
Florian
On 06/11/2013 04:49 PM, Florian Vaussard wrote:
Hello,
This series performs several updates to omap3-overo and
Tony Lindgren t...@atomide.com writes:
Hi,
* Tony Lindgren t...@atomide.com [130617 03:32]:
* Arnaud Patard arnaud.pat...@rtp-net.org [130617 02:52]:
Tony Lindgren t...@atomide.com writes:
I understand your concerns but, please, cope with reality: the clock
work is not in -next so
On Wed, 19 Jun 2013, Samuel Ortiz wrote:
Hi Lee,
On Wed, Jun 19, 2013 at 09:26:33AM +0100, Lee Jones wrote:
On Mon, 17 Jun 2013, J Keerthy wrote:
Remove code which is not necessary for a device tree boot.
So we're exclusively DT now right?
Boot tested on OMAP5-UEVM board.
On 06/19/2013 12:53 AM, Mugunthan V N wrote:
On 6/7/2013 5:02 PM, Mugunthan V N wrote:
Add pinmux DT nodes to CPSW for the following AM335x boards
* AM335x Beaglebone
* AM335x EVM
* AM335x EVMsk
default state contains the pinmux required for active mode and
sleep mode contains pinmux reset
* Arnaud Patard arnaud.pat...@rtp-net.org [130619 02:52]:
Tony Lindgren t...@atomide.com writes:
Hi,
* Tony Lindgren t...@atomide.com [130617 03:32]:
* Arnaud Patard arnaud.pat...@rtp-net.org [130617 02:52]:
Tony Lindgren t...@atomide.com writes:
I understand your concerns but,
On Mon, Jun 03, 2013 at 10:37:20AM +0300, Oleksandr Dmytryshyn wrote:
We've been lucky not to have any interrupts fire during the suspend
path, otherwise we would have unpredictable behaviour in the kernel.
Based on the logic of the kernel code interrupts from i2c should be
prohibited during
On 06/19/2013 02:46 AM, Tony Lindgren wrote:
* Roger Quadros rog...@ti.com [130619 00:42]:
Hi Benoit,
On 06/19/2013 04:17 AM, Benoit Cousson wrote:
Hi Roger,
On 06/18/2013 11:04 AM, Roger Quadros wrote:
Provide the RESET and Power regulators for the USB PHY,
the USB Host port mode and the
On Fri, Jun 07, 2013 at 11:09:26AM +0200, Wolfram Sang wrote:
Class based instantiation can cause huge delays when booting. This
mechanism was used when it was not possible to describe slaves on I2C
busses. We now have other mechanisms, so most embedded I2C will not need
classes and it was
Hi Eduardo,
On 06/18/2013 09:36 PM, Eduardo Valentin wrote:
Add bandgap device DT entry for OMAP5 dtsi.
Cc: Benoît Cousson b-cous...@ti.com
Cc: Tony Lindgren t...@atomide.com
Cc: Russell King li...@arm.linux.org.uk
Cc: linux-omap@vger.kernel.org
Cc: devicetree-disc...@lists.ozlabs.org
Hi Afzal,
On 06/14/2013 09:03 AM, Afzal Mohammed wrote:
Add AM43x ePOS EVM minimal DT source - this is a minimal one to get
it booting. Also include it in omap2plus dtbs and document bindings.
The hardware is under development.
Signed-off-by: Afzal Mohammed af...@ti.com
---
Hi Benoit,
This
Hi Enric,
On 06/19/2013 03:27 AM, Enric Balletbo i Serra wrote:
The IGEP COM AQUILA is industrial processors SODIMM module with
following highlights:
o AM3352/AM3354/AM3358/AM3359 Texas Instruments processor
o Cortex-A8 ARM CPU
o 3.3 volts Inputs / Outputs use industrial
o 256
On 06/19/2013 01:10 PM, Benoit Cousson wrote:
On 06/19/2013 02:46 AM, Tony Lindgren wrote:
* Roger Quadros rog...@ti.com [130619 00:42]:
Hi Benoit,
On 06/19/2013 04:17 AM, Benoit Cousson wrote:
Hi Roger,
On 06/18/2013 11:04 AM, Roger Quadros wrote:
Provide the RESET and Power regulators
On 06/19/2013 06:03 AM, Roger Quadros wrote:
On 06/19/2013 01:10 PM, Benoit Cousson wrote:
On 06/19/2013 02:46 AM, Tony Lindgren wrote:
* Roger Quadros rog...@ti.com [130619 00:42]:
Hi Benoit,
On 06/19/2013 04:17 AM, Benoit Cousson wrote:
Hi Roger,
On 06/18/2013 11:04 AM, Roger Quadros
Hello,
On 06/19/2013 01:03 PM, Roger Quadros wrote:
On 06/19/2013 01:10 PM, Benoit Cousson wrote:
On 06/19/2013 02:46 AM, Tony Lindgren wrote:
* Roger Quadros rog...@ti.com [130619 00:42]:
Hi Benoit,
On 06/19/2013 04:17 AM, Benoit Cousson wrote:
Hi Roger,
On 06/18/2013 11:04 AM, Roger
On 19-06-2013 06:36, Benoit Cousson wrote:
Hi Eduardo,
On 06/18/2013 09:36 PM, Eduardo Valentin wrote:
Add bandgap device DT entry for OMAP5 dtsi.
Cc: Benoît Cousson b-cous...@ti.com
Cc: Tony Lindgren t...@atomide.com
Cc: Russell King li...@arm.linux.org.uk
Cc:
On 06/19/2013 07:05 AM, Florian Vaussard wrote:
Hello,
On 06/19/2013 01:03 PM, Roger Quadros wrote:
On 06/19/2013 01:10 PM, Benoit Cousson wrote:
On 06/19/2013 02:46 AM, Tony Lindgren wrote:
* Roger Quadros rog...@ti.com [130619 00:42]:
Hi Benoit,
On 06/19/2013 04:17 AM, Benoit Cousson
From: Graeme Gregory g...@slimlogic.co.uk
The TWL6025 was never released beyond sample form and was replaced by
the PhoenixLite range of chips - TWL6032. Change the references to
reference the TWL6032 class and name the registers to twl6032 in line with
an actual released chip name to avoid
* Benoit Cousson b-cous...@ti.com [130619 03:17]:
On 06/19/2013 02:46 AM, Tony Lindgren wrote:
We have a similar issue with the MMC1 PBIAS. I think in the long run we
should expand regulator (and possibly pinctrl) framework(s) to handle
comparators. We could just assume that a comparatator
* Benoit Cousson b-cous...@ti.com [130619 05:30]:
On 06/19/2013 07:05 AM, Florian Vaussard wrote:
+
+/* HS USB Port 1 RESET */
+hsusb1_reset: hsusb1_reset_reg {
+compatible = regulator-fixed;
+regulator-name = hsusb1_reset;
+regulator-min-microvolt = 330;
Hi Tony,
On 06/19/2013 07:27 AM, Tony Lindgren wrote:
* Benoit Cousson b-cous...@ti.com [130619 03:17]:
On 06/19/2013 02:46 AM, Tony Lindgren wrote:
We have a similar issue with the MMC1 PBIAS. I think in the long run we
should expand regulator (and possibly pinctrl) framework(s) to handle
* Benoit Cousson b-cous...@ti.com [130619 05:41]:
Hi Tony,
On 06/19/2013 07:27 AM, Tony Lindgren wrote:
* Benoit Cousson b-cous...@ti.com [130619 03:17]:
On 06/19/2013 02:46 AM, Tony Lindgren wrote:
We have a similar issue with the MMC1 PBIAS. I think in the long run we
should expand
clk_get_sys / clk_get can now find clocks from device-tree. If a DT clock
is found, an entry is added to the clk_lookup list also for subsequent
searches.
Signed-off-by: Tero Kristo t-kri...@ti.com
---
drivers/clk/clkdev.c | 32
1 file changed, 32 insertions(+)
of_property_read_u8 does not work properly because of endianess problem
with its current implementation, and this causes it to always return
0 with little endian architectures. Instead, use property_read_u32
until this is fixed.
Signed-off-by: Tero Kristo t-kri...@ti.com
---
Hi,
This set converts the OMAP4 clock data to device tree format.
This set also fixes a couple of problems detected in the basic clock
devicetree code (patches 2 3), and adds some generic support functions
for the transition phase when all the drivers are not fully devicetree
compliant (see
Some of the clock.h contents are needed by the new OMAP clock driver,
including dpll_data and clk_hw_omap. Thus, move these to the generic
omap header file which can be accessed by the driver.
Signed-off-by: Tero Kristo t-kri...@ti.com
---
arch/arm/mach-omap2/clock.h | 150
This node adds support for a clock node which allows control to the
clockdomain enable / disable.
Signed-off-by: Tero Kristo t-kri...@ti.com
---
drivers/clk/omap/Makefile |2 +-
drivers/clk/omap/clk.c|1 +
drivers/clk/omap/gate.c | 88 +
Some devices require their clocks to be available with a specific
dev-id con-id mapping. With DT, the clocks can be found by default
only with their name, or alternatively through the device node of
the consumer. With drivers, that don't support DT fully yet, add
mechanism to register specific
This patch creates a unique node for each clock in the OMAP4 power,
reset and clock manager (PRCM).
Signed-off-by: Tero Kristo t-kri...@ti.com
---
arch/arm/boot/dts/omap4-clocks.dtsi | 1704 +++
arch/arm/boot/dts/omap4.dtsi|2 +
2 files changed, 1706
Parses OMAP clock data from DT and registers those clocks with the clock
framework. dt_omap_clk_init must be called early during boot for timer
initialization so it is exported and called from the existing clock code
instead of probing like a real driver. Based on initial work done by
Mike
OMAP clk driver now routes some of the basic clocks through own
registration routine to allow autoidle support. This routine just
checks a couple of device node properties and adds autoidle support
if required, and just passes the registration forward to basic clocks.
Signed-off-by: Tero Kristo
The OMAP clock driver now supports DPLL clock type. This patch also
adds support for DT DPLL nodes.
Signed-off-by: Tero Kristo t-kri...@ti.com
---
drivers/clk/omap/Makefile |2 +-
drivers/clk/omap/clk.c|1 +
drivers/clk/omap/dpll.c | 307
The existing implementation had a couple of bugs:
1) table_size was attempted to read improperly, it has to be calculated
from the 'len' parameter of a property
2) Reading the integer entries from the table was reading only first
two entries of the DT data
Signed-off-by: Tero Kristo
On 16:19-20130619, Tero Kristo wrote:
snip
diff --git a/arch/arm/boot/dts/omap4-clocks.dtsi
b/arch/arm/boot/dts/omap4-clocks.dtsi
new file mode 100644
index 000..b420d8a
--- /dev/null
+++ b/arch/arm/boot/dts/omap4-clocks.dtsi
[...]
+/* XXX Missing round_rate, set_rate in ops */
could
Hi,
On Wed, Jun 19, 2013 at 12:46 PM, Benoit Cousson b-cous...@ti.com wrote:
Hi Enric,
On 06/19/2013 03:27 AM, Enric Balletbo i Serra wrote:
The IGEP COM AQUILA is industrial processors SODIMM module with
following highlights:
o AM3352/AM3354/AM3358/AM3359 Texas Instruments processor
On 06/19/2013 04:30 PM, Nishanth Menon wrote:
On 16:19-20130619, Tero Kristo wrote:
snip
diff --git a/arch/arm/boot/dts/omap4-clocks.dtsi
b/arch/arm/boot/dts/omap4-clocks.dtsi
new file mode 100644
index 000..b420d8a
--- /dev/null
+++ b/arch/arm/boot/dts/omap4-clocks.dtsi
[...]
+/* XXX
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
On 06/19/2013 02:30 PM, Benoit Cousson wrote:
On 06/19/2013 06:03 AM, Roger Quadros wrote:
On 06/19/2013 01:10 PM, Benoit Cousson wrote:
On 06/19/2013 02:46 AM, Tony Lindgren wrote:
* Roger Quadros rog...@ti.com [130619 00:42]:
Hi Benoit,
On 06/19/2013 04:17 AM, Benoit Cousson wrote:
Hi
On 06/19/2013 03:23 PM, Benoit Cousson wrote:
On 06/19/2013 07:05 AM, Florian Vaussard wrote:
Hello,
On 06/19/2013 01:03 PM, Roger Quadros wrote:
On 06/19/2013 01:10 PM, Benoit Cousson wrote:
On 06/19/2013 02:46 AM, Tony Lindgren wrote:
* Roger Quadros rog...@ti.com [130619 00:42]:
Hi
Hi,
This series attempts to suspend the OMAP EHCI host controller on USB
Bus suspend. This will cause its parent, the OMAP USB Host Module as well
as the USB TLL Module to be put in suspend and hence allow the USB power domain
to be put in a lower power state. Then we no longer prevent the rest
To ensure hardware context is restored while resuming from
OFF mode we need to enable the Hardware SAR bit for the
USB Host power domain.
Signed-off-by: Roger Quadros rog...@ti.com
---
arch/arm/mach-omap2/powerdomains3xxx_data.c |8 +---
1 files changed, 1 insertions(+), 7 deletions(-)
Add the Idle state pins for USB host and enable WAKEUP on
DIR, DAT0-3, so that the PHY can wakeup the OMAP SoC from
sleep on any USB activity (e.g. remote wakeup or connect/disconnect).
CC: Benoît Cousson b-cous...@ti.com
Signed-off-by: Roger Quadros rog...@ti.com
---
Runtime suspend the controller during bus suspend and resume it
during bus resume. This will ensure that the USB Host power domain
enters lower power state and does not prevent the SoC from
endering deeper sleep states.
Remote wakeup will come up as an interrupt while the controller
is suspended,
We no longer need to be initialized in any particular order
so move driver initialization to the standard place i.e. module_init()
CC: Samuel Ortiz sa...@linux.intel.com
Signed-off-by: Roger Quadros rog...@ti.com
---
drivers/mfd/omap-usb-host.c | 10 +-
drivers/mfd/omap-usb-tll.c |
In order to support wake up from suspend use the pinctrl
framework to put the USB host pins in IDLE state during suspend.
CC: Samuel Ortiz sa...@linux.intel.com
Signed-off-by: Roger Quadros rog...@ti.com
---
drivers/mfd/omap-usb-host.c | 46 +++
1 files
Some drivers (e.g. ehci_omap) need to do additional work in
bus suspend/resume and interrupt handler to support low power
modes and remote wakeup.
Allow drivers to override these functions through ehci_driver_overrides.
Also export the ehci_irq(), ehci_bus_suspend() and ehci_bus_resume()
On Wed, 19 Jun 2013, Roger Quadros wrote:
Hi,
This series attempts to suspend the OMAP EHCI host controller on USB
Bus suspend.
Why do you want to suspend the host controller during bus suspend?
They are two different operations and should be carried out at two
different times. The
Hi,
On 06/13/2013 10:43 AM, Kishon Vijay Abraham I wrote:
+/**
+ * phy_create() - create a new phy
+ * @dev: device that is creating the new phy
+ * @id: id of the phy
+ * @ops: function pointers for performing phy operations
+ * @label: label given to the phy
+ * @priv: private data from
From: Enric Balletbo i Serra eballe...@iseebcn.com
Platform code used to depend on bootloadres for correctly setting the mux
pin modes. But bootloaders should only set the minimum required mux pins.
So, DSS mux pins are not set in U-Boot anymore and video display is broken
on IGEPv2 when booting
On Wed, Jun 19, 2013 at 11:27:50AM +0530, Keerthy wrote:
From: J Keerthy j-keer...@ti.com
Add TPS659038 support.
Signed-off-by: J Keerthy j-keer...@ti.com
This doesn't apply against my current tree as the PMIC bindings document
isn't in mainline yet.
Acked-by: Mark Brown
On Wed, Jun 19, 2013 at 11:27:47AM +0530, Keerthy wrote:
From: J Keerthy j-keer...@ti.com
Check if irq value obtained is valid. If it is not valid
then skip the irq request step and go ahead with the probe.
Signed-off-by: J Keerthy j-keer...@ti.com
Reviewed-by: Mark Brown
On 06/18/2013 11:57 PM, Keerthy wrote:
From: J Keerthy j-keer...@ti.com
Check if irq value obtained is valid. If it is not valid
then skip the irq request step and go ahead with the probe.
Reviewed-by: Stephen Warren swar...@nvidia.com
--
To unsubscribe from this list: send the line
Hi Roger,
Roger Quadros rog...@ti.com writes:
In order to support wake up from suspend use the pinctrl
framework to put the USB host pins in IDLE state during suspend.
CC: Samuel Ortiz sa...@linux.intel.com
Signed-off-by: Roger Quadros rog...@ti.com
You should use helpers for this now in
On 06/18/2013 10:27 AM, Felipe Balbi wrote:
--- a/arch/arm/boot/dts/am33xx.dtsi +++
b/arch/arm/boot/dts/am33xx.dtsi @@ -341,6 +341,14 @@ port1-mode =
3; power = 250; ti,hwmods = usb_otg_hs; + phys =
nopphy0 nopphy1; + }; + + nopphy0: usbphy@0 { +
Hello.
On 06/19/2013 06:05 PM, Roger Quadros wrote:
To ensure hardware context is restored while resuming from
OFF mode we need to enable the Hardware SAR bit for the
USB Host power domain.
Signed-off-by: Roger Quadros rog...@ti.com
---
arch/arm/mach-omap2/powerdomains3xxx_data.c |8
Hi Roger,
Roger Quadros rog...@ti.com writes:
Runtime suspend the controller during bus suspend and resume it
during bus resume. This will ensure that the USB Host power domain
enters lower power state and does not prevent the SoC from
endering deeper sleep states.
Remote wakeup will come
is against linux-next 20130619.
arch/arm/mach-omap2/omap4-restart.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/mach-omap2/omap4-restart.c
b/arch/arm/mach-omap2/omap4-restart.c
index 652adde..7306d9b 100644
--- a/arch/arm/mach-omap2/omap4-restart.c
+++ b/arch/arm/mach-omap2/omap4
On 06/19/2013 09:05 AM, Roger Quadros wrote:
On 06/19/2013 03:23 PM, Benoit Cousson wrote:
On 06/19/2013 07:05 AM, Florian Vaussard wrote:
Hello,
On 06/19/2013 01:03 PM, Roger Quadros wrote:
On 06/19/2013 01:10 PM, Benoit Cousson wrote:
On 06/19/2013 02:46 AM, Tony Lindgren wrote:
* Roger
On 06/07/2013 12:09 PM, Wolfram Sang wrote:
Class based instantiation can cause huge delays when booting. This
mechanism was used when it was not possible to describe slaves on I2C
busses. We now have other mechanisms, so most embedded I2C will not need
classes and it was explicitly not
Hi Wolfram,
On 06/19/2013 01:15 PM, Wolfram Sang wrote:
On Fri, Jun 07, 2013 at 11:09:26AM +0200, Wolfram Sang wrote:
Class based instantiation can cause huge delays when booting. This
mechanism was used when it was not possible to describe slaves on I2C
busses. We now have other mechanisms,
Class based instantiation mechanism can cause huge delays when booting.
For example: when CONFIG_SENSORS_LM75 option is enabled for omap4-sdp board -
it introduces 5-6 ms boot delay.
It's not recommended to use this mechanism with embedded I2C, so disable
it by leaving I2C adapter class field
Class based instantiation mechanism can cause huge delays when booting.
For example: when CONFIG_SENSORS_LM75 option is enabled for or omap5-uevm board,
where i2c-gpio is used for HDMI edid reading - it introduces up to 5 sec boot
delay.
It's not recommended to use this mechanism with embedded
Roger Quadros rog...@ti.com writes:
Add the Idle state pins for USB host and enable WAKEUP on
DIR, DAT0-3, so that the PHY can wakeup the OMAP SoC from
sleep on any USB activity (e.g. remote wakeup or connect/disconnect).
CC: Benoît Cousson b-cous...@ti.com
Signed-off-by: Roger Quadros
Hi Felipe,
On 06/07/2013 10:05 PM, Felipe Balbi wrote:
Hi,
On Fri, Jun 07, 2013 at 09:46:06PM +0300, Grygorii Strashko wrote:
ARDY|NACK and ARDY|AL are set together in OMAP_I2C_STAT_REG, which will be
Have you seen that happen ever ? AL is Arbitration Lost, we never put
OMAP in a multi-master
Hi Felipe,
On 06/07/2013 10:02 PM, Felipe Balbi wrote:
Hi,
On Fri, Jun 07, 2013 at 09:46:05PM +0300, Grygorii Strashko wrote:
Add runtime check at the beginning of omap_i2c_isr/omap_i2c_isr_thread
to be sure that i2c is enabled, before performing IRQ handling and accessing
I2C IP registers:
Hi Felipe,
On 06/07/2013 10:07 PM, Felipe Balbi wrote:
Hi,
On Fri, Jun 07, 2013 at 09:46:08PM +0300, Grygorii Strashko wrote:
The omap_i2c_isr() does the irq check and schedules threaded handler if any of
enabled IRQs is active, but currently the I2C IRQs are enabled just once,
when I2C IP is
On 06/07/2013 11:51 PM, Kevin Hilman wrote:
Grygorii Strashko grygorii.stras...@ti.com writes:
From: Kevin Hilman khil...@deeprootsystems.com
Currently, runtime PM is used to keep the device enabled only during
active transfers and for a configurable runtime PM autosuspend timout
after an
Regulator consumers are not aware of the characteristics of regulator
used to supply. For example:
consumerX requests for voltage min_uV = 500mV, max_uV = 500mV
On a regulator which has a step size of 10mV, this can be exactly
achieved.
However, on a regulator which is non-exact divider step size
Hi,
On Wed, Jun 19, 2013 at 09:35:38PM +0300, Grygorii Strashko wrote:
On 06/07/2013 11:51 PM, Kevin Hilman wrote:
Grygorii Strashko grygorii.stras...@ti.com writes:
From: Kevin Hilman khil...@deeprootsystems.com
Currently, runtime PM is used to keep the device enabled only during
active
On Tue, Jun 18, 2013 at 12:57 PM, Stijn Devriendt high...@gmail.com wrote:
On Thu, Jun 6, 2013 at 4:05 PM, Archit Taneja arc...@ti.com wrote:
+static struct pcf857x_platform_data *of_gpio_pcf857x(struct device *dev)
+{
+ struct pcf857x_platform_data *pdata;
+ int r;
+
+
On Wed, Jun 19, 2013 at 03:24:02PM +0300, Oleksandr Kozaruk wrote:
There are non-mainline branches that use twl6032 by its name (for example
git://git.omapzoom.org/kernel/omap.git). There is intention to add support
of twl6032 device in mainline, but we'd like to know if we can use twl6032
On Mon, Jun 17, 2013 at 1:46 PM, Archit Taneja arc...@ti.com wrote:
On Monday 17 June 2013 02:35 PM, Linus Walleij wrote:
Just a query, there is an example in gpio.txt in the gpio
bindings documentation which sets #gpio-cells as 1. Is this is a wrong
example, or are 1 cell gpio controllers
On Wed, Jun 19, 2013 at 09:42:25PM +0300, Grygorii Strashko wrote:
Hi Felipe,
On 06/07/2013 10:02 PM, Felipe Balbi wrote:
Hi,
On Fri, Jun 07, 2013 at 09:46:05PM +0300, Grygorii Strashko wrote:
Add runtime check at the beginning of omap_i2c_isr/omap_i2c_isr_thread
to be sure that i2c is
On Wed, Jun 19, 2013 at 09:43:17PM +0300, Grygorii Strashko wrote:
Hi Felipe,
On 06/07/2013 10:07 PM, Felipe Balbi wrote:
Hi,
On Fri, Jun 07, 2013 at 09:46:08PM +0300, Grygorii Strashko wrote:
The omap_i2c_isr() does the irq check and schedules threaded handler if any
of
enabled IRQs
On Wed, Jun 19, 2013 at 09:43:04PM +0300, Grygorii Strashko wrote:
Hi Felipe,
On 06/07/2013 10:05 PM, Felipe Balbi wrote:
Hi,
On Fri, Jun 07, 2013 at 09:46:06PM +0300, Grygorii Strashko wrote:
ARDY|NACK and ARDY|AL are set together in OMAP_I2C_STAT_REG, which will be
Have you seen that
ARM errata 798181 is applicable for OMAP5 based devices. So enable
the same in the build. Errata extract and workaround information
is as below.
On Cortex-A15 (r0p0..r3p2) the TLBI*IS/DSB operations are not
adequately shooting down all use of the old entries. The
ARM_ERRATA_798181 option enables
Felipe Balbi ba...@ti.com writes:
[...]
If you have 200 pm_runtime_get() followed by 200 pm_runtime_put() (put
is called only after 200 gets, no put-get ping-pong), your
-runtime_resume() gets called once, your -runtime_suspend() gets
called once but your -runtime_idle() will get called 200
Hi,
On Wed, Jun 19, 2013 at 01:01:28PM -0700, Kevin Hilman wrote:
Felipe Balbi ba...@ti.com writes:
[...]
If you have 200 pm_runtime_get() followed by 200 pm_runtime_put() (put
is called only after 200 gets, no put-get ping-pong), your
-runtime_resume() gets called once, your
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 be tolerated? Your problem here is specifying
1 - 100 of 115 matches
Mail list logo
