On Tue, 2014-02-04 at 17:50 +0200, Tero Kristo wrote:
On 01/29/2014 01:21 PM, Christoph Fritz wrote:
Currently I only analyzed sys_clkout2 (see attachments for full
clk_summary files):
clk_summary__next-20140115__works_as_expected:
dpll4_m2_ck1 1
On Mon, 2014-01-27 at 01:33 +0100, Christoph Fritz wrote:
This set of patches adds board support for an omap3 system from INCOstartec.
It's based on next-20140124.
Due to a regression since next-20140115 the following errors are present:
- pin sys_clkout2, which gets configured to 24 Mhz
From: Afzal Mohammed af...@ti.com
Determine AM43x device features by reusing AM335x helper as feature
register layout is similar.
And also exporting AM43xx family name.
Signed-off-by: Afzal Mohammed af...@ti.com
Signed-off-by: Lokesh Vutla lokeshvu...@ti.com
---
arch/arm/mach-omap2/id.c |2
This patch series enables AM43xx SOC in omap2plus_deconfig along with
updating clocksource and adding support for ES1.1.
With this series using omap2plus_defconfig alone boots on AM43XX.
Changes since V1:
- Added a new patch to determine AM43x device features.
Tested on:
AM4372 EPOS EVM. log
Adding ID for AM437x ES1.1 silicon.
Signed-off-by: Lokesh Vutla lokeshvu...@ti.com
---
arch/arm/mach-omap2/id.c | 14 --
arch/arm/mach-omap2/soc.h |3 ++-
2 files changed, 14 insertions(+), 3 deletions(-)
diff --git a/arch/arm/mach-omap2/id.c b/arch/arm/mach-omap2/id.c
index
From: Rajendra Nayak rna...@ti.com
The SyncTimer in AM43x is clocked using the following two sources:
1) An inaccuarte 32k clock (CLK_32KHZ) derived from PER DPLL, causing system
time to go slowly (~10% deviation).
2) external 32KHz RTC clock, which may not always be available on board like
From: Afzal Mohammed af...@ti.com
Enable AM43x SoC in omap2plus_defconfig
Signed-off-by: Afzal Mohammed af...@ti.com
Signed-off-by: Lokesh Vutla lokeshvu...@ti.com
---
arch/arm/configs/omap2plus_defconfig |1 +
1 file changed, 1 insertion(+)
diff --git
Hi,
On 09/23/2013 04:59 PM, Roger Quadros wrote:
On 09/23/2013 03:59 PM, Sergei Shtylyov wrote:
Hello.
On 23-09-2013 11:37, Roger Quadros wrote:
Not sure why you asked -- I'm not using this driver, neither I'm
Well, you have better grip of what's going on in the embedded world
than
On Friday 07 February 2014 12:33:38 Roger Quadros wrote:
This means we need to make CONFIG_SATA_AHCI_PLATFORM depend on
CONFIG_GENERIC_PHY or
select it.
OR
Generic PHY layer must be fixed so that the API's are always built in.
What is the better option? I believe making the PHY
On 02/07/2014 12:39 PM, Arnd Bergmann wrote:
On Friday 07 February 2014 12:33:38 Roger Quadros wrote:
This means we need to make CONFIG_SATA_AHCI_PLATFORM depend on
CONFIG_GENERIC_PHY or
select it.
OR
Generic PHY layer must be fixed so that the API's are always built in.
What is the
On Thu, 06 Feb 2014, Keerthy wrote:
The TPS65218 chip is a power management IC for Portable Navigation Systems
and Tablet Computing devices. It contains the following components:
- Regulators.
- Over Temperature warning and Shut down.
This patch adds support for tps65218 mfd device. At
On Friday 07 February 2014 04:42 PM, Lee Jones wrote:
On Thu, 06 Feb 2014, Keerthy wrote:
The TPS65218 chip is a power management IC for Portable Navigation Systems
and Tablet Computing devices. It contains the following components:
- Regulators.
- Over Temperature warning and Shut down.
Hi,
On 07/02/14 12:12, Christoph Fritz wrote:
Yes, your patch fixes the issues for sys_clkout2. Thanks! If you want,
you can add my:
Tested-by: Christoph Fritz chf.fr...@googlemail.com
Below is my clock fix for dss:
From b90a62128068e1b6b0ba2a11c5cc0c8e587cf301 Mon Sep 17 00:00:00 2001
Hi Mark,
On Thursday 06 February 2014 11:20 AM, Keerthy wrote:
This patch adds support for TPS65218 PMIC regulators.
The regulators set consists of 6 DCDCs and 1 LDO. The output
voltages are configurable and are meant to supply power to the
main processor and other components.
If there are
Laurent,
On Thu, Feb 6, 2014 at 1:26 PM, Laurent Pinchart
laurent.pinch...@ideasonboard.com wrote:
Hi all,
On Friday 22 June 2012 11:33:51 Laurent Pinchart wrote:
On Thursday 10 February 2011 08:45:00 Kevin Hilman wrote:
Sanjeev Premi pr...@ti.com writes:
This patch adds support for
On Fri, Feb 07, 2014 at 07:28:29PM +0530, Keerthy wrote:
On Thursday 06 February 2014 11:20 AM, Keerthy wrote:
If there are no further comments on this could you
please pull this?
You've sent this mail a day after sending the original patch, don't do
that.
signature.asc
Description: Digital
This patch changes clockdomain handling for platforms using omap4
operations. Commit 65aa94b204d removed SW_SLEEP functionality
from the omap4 clockdomain controls with the intention that, because
all IPs support HW_AUTO, that should be used instead. This may make
sense for omap4, but many
Since commit 65aa94b204d (ARM: OMAP4: clockdomain/CM code: Update supported
transition modes), on OMAP4, all CLKDMs support HW_AUTO so this is used
instead of SW_SLEEP for the idling of clockdomains. However, additional
SoCs now leverage the OMAP4 clockdomain code so update it to use SW_SLEEP
if
On Mon, Jan 13, 2014 at 4:19 PM, Suman Anna s-a...@ti.com wrote:
This patch adds three new OF helper functions to use/request
locks from a hwspinlock device instantiated through a
device-tree blob.
Nice, I ran in to the problem of needing a probe deferral on a
hwspinlock earlier this week so I
19 matches
Mail list logo
