On Mon, 2013-11-11 at 21:59 +0100, Maxime Ripard wrote:
Hi Luca,
On Mon, Nov 11, 2013 at 09:50:56PM +0200, Luca Coelho wrote:
On Mon, 2013-11-11 at 13:42 -0600, Felipe Balbi wrote:
+ if (of_property_read_bool(node, clock-xtal))
+ flags |= CLK_IS_TYPE_XTAL;
+
On Tue, Oct 22, 2013 at 12:14:02PM +0200, Sebastian Andrzej Siewior wrote:
Hi Vinod,
this series contains patches which are floating on the mainling list so
I hope it is easier to collect them. It contains two of Daniel's which
were not yet applied and two of mine.
The patch redo descriptor
Hi Andreas
On Mon, Nov 11, 2013 at 9:06 PM, Andreas Fenkart afenk...@gmail.com wrote:
For now, only support SDIO interrupt if we are booted with
DT. This is because some platforms need special quirks. And
we don't want to add new legacy mux platform init code
callbacks any longer as we are
From: Lokesh Vutla lokeshvu...@ti.com
AM437x GP EVM DTS with pinmux information to make I2C on EVM usable.
Signed-off-by: Lokesh Vutla lokeshvu...@ti.com
Signed-off-by: Sourav Poddar sourav.pod...@ti.com
Signed-off-by: Afzal Mohammed af...@ti.com
---
.../devicetree/bindings/arm/omap/omap.txt
Hi
On Mon, Nov 11, 2013 at 9:06 PM, Andreas Fenkart afenk...@gmail.com wrote:
The am335x can't detect pending cirq in PM runtime suspend.
This patch reconfigures dat1 as a GPIO before going to suspend.
SDIO interrupts are detected with the GPIO, the GPIO will only wake
the module from
Hi,
On Tue, Nov 12, 2013 at 04:54:26PM +0530, Afzal Mohammed wrote:
From: Lokesh Vutla lokeshvu...@ti.com
AM437x GP EVM DTS with pinmux information to make I2C on EVM usable.
Signed-off-by: Lokesh Vutla lokeshvu...@ti.com
Signed-off-by: Sourav Poddar sourav.pod...@ti.com
Signed-off-by:
On Tuesday 12 November 2013 01:36 AM, Andreas Fenkart wrote:
For now, only support SDIO interrupt if we are booted with
DT. This is because some platforms need special quirks. And
we don't want to add new legacy mux platform init code
callbacks any longer as we are moving to DT based booting
Hi,
This is an updated series addressing the review comments from the
v2 series. The hwmod patches have been dropped from the repost
as per Paul's request, they have already been queued.
Mark,
Any comments on this series? Tony has picked up the OMAP DTS patches for
3.13, and so
the
On Fri, Oct 11, 2013 at 7:23 PM, Tony Lindgren t...@atomide.com wrote:
* Linus Walleij linus.wall...@linaro.org [131011 09:27]:
On Fri, Oct 11, 2013 at 6:13 PM, Roger Quadros rog...@ti.com wrote:
On OMAPs the IO ring must be rearmed each time the pad wakeup
configuration is changed. So call
Small fix on representation. Bandgap node belongs to OCP.
Cc: Benoît Cousson bcous...@baylibre.com
Cc: Tony Lindgren t...@atomide.com
Cc: Rob Herring rob.herr...@calxeda.com
Cc: Pawel Moll pawel.m...@arm.com
Cc: Mark Rutland mark.rutl...@arm.com
Cc: Stephen Warren swar...@wwwdotorg.org
Cc: Ian
OMAP5 devices can reach high temperatures and thus
needs to have cpufreq-cooling on systems running on it.
This patch adds the required cooling device properties
so that cpufreq-cpu0 driver loads the cooling device.
Cc: Benoît Cousson bcous...@baylibre.com
Cc: Tony Lindgren t...@atomide.com
Cc:
Small fix on representation. Bandgap node belongs to OCP.
Cc: Benoît Cousson bcous...@baylibre.com
Cc: Tony Lindgren t...@atomide.com
Cc: Rob Herring rob.herr...@calxeda.com
Cc: Pawel Moll pawel.m...@arm.com
Cc: Mark Rutland mark.rutl...@arm.com
Cc: Stephen Warren swar...@wwwdotorg.org
Cc: Ian
This patch changes the dtsi entry on omap5 to contain
the thermal data. This data will enable the passive
cooling with CPUfreq cooling device at 100C. The
system will do a thermal shutdown at 125C whenever
any of its sensors sees this level.
Cc: Benoît Cousson bcous...@baylibre.com
Cc: Tony
This patch changes a dtsi file to contain the thermal data
for GPU domain on OMAP5 and later SoCs. This data will
enable a thermal shutdown at 125C.
This thermal data can be reused across TI SoC devices.
Cc: Benoît Cousson bcous...@baylibre.com
Cc: Tony Lindgren t...@atomide.com
Cc: Rob Herring
This patch changes a dtsi file to contain the thermal data
for MPU domain on OMAP4 and later SoCs. This data will
enable the passive cooling with CPUfreq cooling device
at 100C and the system will do a thermal shutdown at 125C.
This thermal data can be reused across TI SoC devices.
Cc: Benoît
* Linus Walleij linus.wall...@linaro.org [131112 10:45]:
On Fri, Oct 11, 2013 at 7:23 PM, Tony Lindgren t...@atomide.com wrote:
* Linus Walleij linus.wall...@linaro.org [131011 09:27]:
On Fri, Oct 11, 2013 at 6:13 PM, Roger Quadros rog...@ti.com wrote:
On OMAPs the IO ring must be
This patch changes the dtsi entry on omap4460 to contain
the thermal data. This data will enable the passive
cooling with CPUfreq cooling device at 100C and the
system will do a thermal shutdown at 125C.
Cc: Benoît Cousson bcous...@baylibre.com
Cc: Tony Lindgren t...@atomide.com
Cc: Rob Herring
This patch changes the dtsi entry on omap4430 to contain
the thermal data. This data will enable the passive
cooling with CPUfreq cooling device at 100C and the
system will do a thermal shutdown at 125C.
Cc: Benoît Cousson bcous...@baylibre.com
Cc: Tony Lindgren t...@atomide.com
Cc: Russell King
OMAP4430 devices can reach high temperatures and thus
needs to have cpufreq-cooling on systems running on it.
This patch adds the required cooling device properties
so that cpufreq-cpu0 driver loads the cooling device.
Cc: Benoît Cousson bcous...@baylibre.com
Cc: Tony Lindgren t...@atomide.com
OMAP4460 devices can reach high temperatures and thus
needs to have cpufreq-cooling on systems running on it.
This patch adds the required cooling device properties
so that cpufreq-cpu0 driver loads the cooling device.
Cc: Benoît Cousson bcous...@baylibre.com
Cc: Tony Lindgren t...@atomide.com
This patch changes a dtsi file to contain the thermal data
for CORE domain on OMAP5 and later SoCs. This data will
enable a thermal shutdown at 125C.
This thermal data can be reused across TI SoC devices.
Cc: Benoît Cousson bcous...@baylibre.com
Cc: Tony Lindgren t...@atomide.com
Cc: Rob Herring
In omap_sham_probe() and omap_sham_remove(), 'dd-dma_lch'
is released without checking to see if it was successfully
requested or not. This is a bug and was identified and
reported by Dan Carpenter here:
http://www.spinics.net/lists/devicetree/msg11023.html
Add code to only release
On Fri, Oct 25, 2013 at 11:26:06AM +, Gupta, Pekon wrote:
From: Ezequiel Garcia [mailto:ezequiel.gar...@free-electrons.com]
Subject: [PATCH v2 3/5] mtd: nand: omap2: Fix OMAP_BCH option
dependency
This option does not need to depend in MTD_NAND, for it's enclosed
under it. Also,
Hey Javier,
On Sat, Nov 09, 2013 at 05:34:02PM +0100, Javier Martinez Canillas wrote:
The OMAP2+ General-Purpose Memory Controller (GPMC) driver
should eventually be moved from arch/arm/mach-omap2 to
drivers/memory. Unfortunately this is not trivial since it
includes headers files that still
Nishanth Menon n...@ti.com writes:
On 16:38-20131107, Kevin Hilman wrote:
[...]
That's debatable I guess. The ideal world is that runtime PM hides all
of this, but I'm not sure it's achievable in all cases.
Agreed. some drivers like edma need to save and restore context around
suspend.
On 11/12/2013 09:51 PM, Ezequiel Garcia wrote:
Hey Javier,
Hi Ezequiel, thanks a lot for your feedback.
On Sat, Nov 09, 2013 at 05:34:02PM +0100, Javier Martinez Canillas wrote:
The OMAP2+ General-Purpose Memory Controller (GPMC) driver
should eventually be moved from arch/arm/mach-omap2 to
* Javier Martinez Canillas javier.marti...@collabora.co.uk [131112 13:58]:
On 11/12/2013 09:51 PM, Ezequiel Garcia wrote:
I'm not too convinced about the above diffstat. Maybe you can try a
a better approach of making the move by: 1) renaming/moving a file,
using 'git format-patch -M'
On Tue, Nov 12, 2013 at 05:45:56PM -0300, Ezequiel Garcia wrote:
On Fri, Oct 25, 2013 at 11:26:06AM +, Gupta, Pekon wrote:
From: Ezequiel Garcia [mailto:ezequiel.gar...@free-electrons.com]
Subject: [PATCH v2 3/5] mtd: nand: omap2: Fix OMAP_BCH option
dependency
This option
OMAP device hooks around suspend|resume_noirq ensures that hwmod
devices are forced to idle using omap_device_idle/enable as part of
the last stage of suspend activity.
For a device such as i2c who uses autosuspend, it is possible to enter
the suspend path with dev-power.runtime_status =
On Tue, Nov 12, 2013 at 02:56:47PM -0800, Brian Norris wrote:
On Tue, Nov 12, 2013 at 05:45:56PM -0300, Ezequiel Garcia wrote:
On Fri, Oct 25, 2013 at 11:26:06AM +, Gupta, Pekon wrote:
From: Ezequiel Garcia [mailto:ezequiel.gar...@free-electrons.com]
Subject: [PATCH v2 3/5] mtd:
On 11/12/2013 03:26 PM, Kevin Hilman wrote:
[..]
Yes, the updated version looks much more sensible. Please repost in its
own thread so it gets a better chance at broader review, and feel free
to add
Acked-by: Kevin Hilman khil...@linaro.org
Thanks. this is done[1]
[1]
On 11/12/2013 11:12 PM, Tony Lindgren wrote:
* Javier Martinez Canillas javier.marti...@collabora.co.uk [131112 13:58]:
On 11/12/2013 09:51 PM, Ezequiel Garcia wrote:
I'm not too convinced about the above diffstat. Maybe you can try a
a better approach of making the move by: 1)
On Thu, Oct 31, 2013 at 05:05:50PM +1100, NeilBrown wrote:
This allows the charger to be enabled with devicetree, and
allows the parameters for charging the backup battery to be set.
Signed-off-by: NeilBrown ne...@suse.de
Acked-by: Kumar Gala ga...@codeaurora.org
Acked-by: Grant Likely
Hi Felipe,
On Tuesday 12 November 2013 07:52 PM, Felipe Balbi wrote:
On Tue, Nov 12, 2013 at 04:54:26PM +0530, Afzal Mohammed wrote:
From: Lokesh Vutla lokeshvu...@ti.com
AM437x GP EVM DTS with pinmux information to make I2C on EVM usable.
Signed-off-by: Lokesh Vutla lokeshvu...@ti.com
34 matches
Mail list logo
