On Tue, Mar 25, 2014 at 01:38:47AM +0100, Mike Turquette wrote:
Quoting Peter De Schrijver (2014-03-21 01:12:17)
On Thu, Mar 20, 2014 at 10:23:08PM +0100, Mike Turquette wrote:
Quoting Tero Kristo (2014-03-05 05:10:17)
Ping.
Mike, any feedback on this?
Hi Tero,
On 24 March 2014 17:34, Andreas Fenkart afenk...@gmail.com wrote:
2014-03-24 17:02 GMT+01:00 Ulf Hansson ulf.hans...@linaro.org:
On 24 March 2014 15:59, Andreas Fenkart afenk...@gmail.com wrote:
Hi,
2014-03-24 13:43 GMT+01:00 Ulf Hansson ulf.hans...@linaro.org:
On 21 March 2014 17:17, Balaji
On 03/19/2014 12:10 PM, George Cherian wrote:
Add USB and USB PHY reference clock data
Signed-off-by: George Cherian george.cher...@ti.com
Acked-by: Roger Quadros rog...@ti.com
cheers,
-roger
---
arch/arm/boot/dts/am43xx-clocks.dtsi | 32
1 file changed,
Hi,
On Mon, Mar 24, 2014 at 12:37:58AM -0400, David Miller wrote:
From: Nishanth Menon n...@ti.com
Date: Fri, 21 Mar 2014 01:52:48 -0500
Few platforms use external regulator to keep the ethernet MAC supplied.
So, request and enable the regulator for driver functionality.
Fixes:
From: Eduardo Valentin eduardo.valen...@ti.com
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
From: Eduardo Valentin eduardo.valen...@ti.com
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:
From: Eduardo Valentin eduardo.valen...@ti.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
From: Eduardo Valentin eduardo.valen...@ti.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
From: Eduardo Valentin eduardo.valen...@ti.com
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
Hi! We have a DART-4460 board which is based on TI OMAP4460.
It is shipped by Variscite with linux kernel v3.4.27 (as
/proc/config.gz states; uname -a shows Linux localhost.localdomain
3.4.0-1489-omap4 #28 SMP PREEMPT Wed Oct 30 10:58:36 IST 2013 armv7l
armv7l armv7l GNU/Linux).
We try to make it
to the lack of this patch.
next-20140325-omap2plus_defconfig
1: am335x-evm: Boot PASS: http://slexy.org/raw/s20o6CfGL8
2: am335x-sk: Boot PASS: http://slexy.org/raw/s2Ogu1zPtD
3: am3517-evm: Boot PASS: http://slexy.org/raw/s2m2WhHYO8
4: am37x-evm: Boot PASS: http://slexy.org/raw/s2jOybaVno
5
Hi
On Tue, Mar 25, 2014 at 4:00 PM, Andrey Utkin
andrey.krieger.ut...@gmail.com wrote:
Hi! We have a DART-4460 board which is based on TI OMAP4460.
It is shipped by Variscite with linux kernel v3.4.27 (as
/proc/config.gz states; uname -a shows Linux localhost.localdomain
3.4.0-1489-omap4 #28
On Tuesday 25 March 2014 01:37 PM, Ulf Hansson wrote:
On 24 March 2014 17:34, Andreas Fenkart afenk...@gmail.com wrote:
2014-03-24 17:02 GMT+01:00 Ulf Hansson ulf.hans...@linaro.org:
On 24 March 2014 15:59, Andreas Fenkart afenk...@gmail.com wrote:
Hi,
2014-03-24 13:43 GMT+01:00 Ulf Hansson
2014-03-25 17:17 GMT+02:00 Michael Trimarchi mich...@amarulasolutions.com:
I have already done somenthing like that more then 6 months ago. I was
in a good state, What camera sensors are you using?
Hi Michael, it is JAL-MIPI-OV5640.
--
Andrey Utkin
--
To unsubscribe from this list: send the
Hi
On Tue, Mar 25, 2014 at 5:33 PM, Andrey Utkin
andrey.krieger.ut...@gmail.com wrote:
2014-03-25 17:17 GMT+02:00 Michael Trimarchi mich...@amarulasolutions.com:
I have already done somenthing like that more then 6 months ago. I was
in a good state, What camera sensors are you using?
Hi
* Felipe Balbi ba...@ti.com [140320 12:39]:
This reverts commit 0324a821029e1f54e7a7f8fed48693cfce42dc0e.
That commit tried to fix a deadlock problem when using
hci_ldisc, but it turns out the bug was in hci_ldsic
all along where it was calling -write() from within
-write_wakeup() callback.
The lack of pm_runtime_resume handling for the device state leads into
device wake-up interrupts not working after a while for runtime PM.
Also, serial-omap is confused about the use of device_may_wakeup.
The checks for device_may_wakeup should only be done for suspend and
resume, not for
On Tue, Mar 25, 2014 at 11:48:47AM -0700, Tony Lindgren wrote:
The lack of pm_runtime_resume handling for the device state leads into
device wake-up interrupts not working after a while for runtime PM.
Also, serial-omap is confused about the use of device_may_wakeup.
The checks for
* Felipe Balbi ba...@ti.com [140325 11:57]:
On Tue, Mar 25, 2014 at 11:48:47AM -0700, Tony Lindgren wrote:
The lack of pm_runtime_resume handling for the device state leads into
device wake-up interrupts not working after a while for runtime PM.
Also, serial-omap is confused about the
* Tero Kristo t-kri...@ti.com [140304 08:23]:
There is a solitary write to this register every wakeup from off-mode,
which isn't doing anything, so remove it.
Argh, this chunk of code is for sure the the thing that's blocking all
the voltage scaling for idle modes that twl4030 is supposed to
20 matches
Mail list logo
