On 28/05/14 00:14, Tony Lindgren wrote:
FYI, I'm getting this with current linux next:
omapfb omapfb: failed to allocate framebuffer
omapfb omapfb: failed to allocate fbmem
omapfb omapfb: failed to setup omapfb
omapfb: probe of omapfb failed with error -12
You need the attached patch to
On 27/05/14 23:59, Tony Lindgren wrote:
In case you did not yet do it, here's this patch updated for you. I'm
assuming you'll apply this to your panel dts branch. Let me know when the
dependencies are in linux next and I'll test it one more time. The omap
changes finally hit linux next as of
Here's an updated set of patches to enable low-power idle modes
for some omap3 boards when booted with device tree.
This series when applied on top of the patches in tread
Thanks Tony, here's the pull-request:
The following changes since commit 455c6fdbd219161bd09b1165f11699d6d73de11c:
Linux 3.14 (2014-03-30 20:40:15 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/lee/mfd.git
tags/mfd-omap-v3.16-1
for you to
Changes since v2:
* RFC comments are fixed for all
* ti-usim:
** synchronous card support is added
** Timeout added for ATR
** BWT configuration
** softreset of IP at initialization added
** PM suspend/resume support added
* sc_phy : sync card support is added
* ARM: dts: AM43xx: fck clock
- Board specific DT entries for TI's USIM - smart card controller of AM43xx
platfrom.These entries are used by USIM driver for various configurations.
- Shutdown line of NXP phy is maped to GPIO5. So enabling same to have support
for NXP phy.
- i2c2 pinmux configuration - NxP tda8026 phy is
On 5/28/2014 6:11 AM, Greg KH wrote:
On Fri, May 16, 2014 at 09:14:34AM +0530, Satish Patel wrote:
On 1/30/2014 6:35 PM, Greg KH wrote:
On Thu, Jan 30, 2014 at 11:22:48AM +0530, Satish Patel wrote:
On 1/20/2014 10:03 AM, Satish Patel wrote:
Changes from v1:
* RFC(v1) comments are fixed
SoC specific DT entries added for TI's USIM - smart card controller of AM43xx
platfrom.
Signed-off-by: Satish Patel satish.pa...@ti.com
---
arch/arm/boot/dts/am4372.dtsi | 12
1 file changed, 12 insertions(+)
diff --git a/arch/arm/boot/dts/am4372.dtsi
TDA8026 is a SmartCard PHY from NXP.
The PHY interfaces with the main processor over the
I2C interface and acts as a slave device.
The driver also exposes the phy interface
(defined@include/linux/sc_phy.h) for SmartCard controller.
Controller uses this interface to communicate with smart card
SmartCard controller uses this interface to communicate with
SmartCard via PHY
Some SmartCard PHY has multiple slots for cards.
This inerface also enables controller to communicate
with one or more SmartCard connected over phy.
interface structure includes following APIs
- set/get config
-
Add tps65917 specific definitions and enums.
Signed-off-by: Keerthy j-keer...@ti.com
---
include/linux/mfd/palmas.h | 793
1 file changed, 793 insertions(+)
diff --git a/include/linux/mfd/palmas.h b/include/linux/mfd/palmas.h
index ccbb21f..52a24a9
The TPS65917 chip is a power management IC for Portable Navigation Systems
and Tablet Computing devices. It contains the following components:
- Regulators.
- GPADC.
- Over Temperature warning and Shut down.
This patch series adds support for TPS65917 mfd device. At this time only
the
add driver data and modularize the probe.
Signed-off-by: Keerthy j-keer...@ti.com
---
drivers/mfd/palmas.c | 42 +--
drivers/regulator/palmas-regulator.c | 656 --
2 files changed, 395 insertions(+), 303 deletions(-)
diff --git
Add tps65917 PMIC support.
Signed-off-by: Keerthy j-keer...@ti.com
---
drivers/regulator/palmas-regulator.c | 387 ++
1 file changed, 387 insertions(+)
diff --git a/drivers/regulator/palmas-regulator.c
b/drivers/regulator/palmas-regulator.c
index
Add palmas_pmic_driver_data structure.
Signed-off-by: Keerthy j-keer...@ti.com
---
include/linux/mfd/palmas.h | 25 +
1 file changed, 25 insertions(+)
diff --git a/include/linux/mfd/palmas.h b/include/linux/mfd/palmas.h
index 8d68452..70f0695 100644
---
Add tps65917 PMIC support. tps65917 is a subset of palmas PMIC.
Some of the register definitions and the interrupt mappings
are different.
Signed-off-by: Keerthy j-keer...@ti.com
---
drivers/mfd/palmas.c | 176 --
1 file changed, 171
Shift the reg_info structure definition to the header file.
Signed-off-by: Keerthy j-keer...@ti.com
---
drivers/regulator/palmas-regulator.c |9 -
include/linux/mfd/palmas.h |9 +
2 files changed, 9 insertions(+), 9 deletions(-)
diff --git
shift the palmas_sleep_requestor_info structure definition to the header file.
Signed-off-by: Keerthy j-keer...@ti.com
---
drivers/mfd/palmas.c | 10 --
include/linux/mfd/palmas.h | 10 ++
2 files changed, 10 insertions(+), 10 deletions(-)
diff --git
Add tps65917 compatible string.
Signed-off-by: Keerthy j-keer...@ti.com
---
.../devicetree/bindings/regulator/palmas-pmic.txt |1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/regulator/palmas-pmic.txt
Add DT bindings for tps65917 PMIC.
Signed-off-by: Keerthy j-keer...@ti.com
---
Documentation/devicetree/bindings/mfd/palmas.txt |2 ++
1 file changed, 2 insertions(+)
diff --git a/Documentation/devicetree/bindings/mfd/palmas.txt
b/Documentation/devicetree/bindings/mfd/palmas.txt
index
On 05/27/2014 06:03 PM, Joel Fernandes wrote:
On 05/27/2014 05:22 AM, Peter Ujfalusi wrote:
On 05/27/2014 12:32 AM, Olof Johansson wrote:
[..]
I came across this patch when I was looking at a pull request from
Sekhar for EDMA cleanups, and it made me look closer at the contents
of this
In DRA7x SoCs, the CONTROL_MODULE_CORE sub block in the control module has a
few register fields which perform gating or muxing of clocks.
These gate/muxes are generally SoC level clocks entering an IP, which didn't
manage to make it in the clock management related registers for the IP.
Other
The DESHDCP clock is required only by the DES-HDCP block within HDMI in DSS.
However, if the clock isn't set before DSS clock domian is enabled, the clock
domain never comes out of idle state.
The DESHDCP clock is enabled/disabled at the DSS boundary by the bit
DSS_DESHDCP_CLKEN in
The DESHDCP clock is required only by the DES-HDCP block within HDMI in DSS.
However, if the clock isn't set before DSS clock domian is enabled, the clock
domain never comes out of idle state.
This is because the DSS IP is designed in such a way that if DES-HDCP block
can't transition from idle
Add DT node for the ctrl-core sub module of the DRA7 control module. We map the
CTRL_MODULE_CORE address region up to 0x4a002d60, this region contains register
fields which configure clocks. The remainder of the registers are related to
pad configurations or cross-bar configurations, and therefore
From: Tero Kristo t-kri...@ti.com
Retry init is needed if clockdomains are registered before the corresponding
clocks are ready. In this case, the clockdomain info is added to a list
which will be processed once the clockdomains for next PRCM module are
processed.
Signed-off-by: Tero Kristo
This series tries to create CONTROL_MODULE_CORE as a new clock provider, and
create a clock using it required by DSS on DRA7.
The previous revision of the series added the new clock provider within prcm
driver code itself. Suggestions were made by Paul and Tero to move it to control
module driver
Currently, clock providers coming from CM, PRM, and SCRM are all initialized in
prm_common.c.
Move the DT-match tables to their respective files, and create separate init
functions for each module.
Originally worked on by: Tero Kristo t-kri...@ti.com
Cc: Tero Kristo t-kri...@ti.com
On Mon 26 May 2014 01:32:08 AM CDT, Tero Kristo wrote:
On 05/24/2014 12:07 AM, Mike Turquette wrote:
Quoting Nishanth Menon (2014-05-16 03:45:57)
Hi,
This patch series has been carried over in vendor kernel for quiet
few years now.
Unfortunately, it was very recently re-discovered and
On Tue, May 27, 2014 at 8:54 PM, Mike Turquette mturque...@linaro.org wrote:
Quoting Nishanth Menon (2014-05-15 05:33:13)
On 05/15/2014 07:18 AM, Kishon Vijay Abraham I wrote:
Hi,
On Thursday 15 May 2014 05:42 PM, Nishanth Menon wrote:
On Thu, May 15, 2014 at 6:59 AM, Kishon Vijay
* Lee Jones lee.jo...@linaro.org [140528 00:14]:
Thanks Tony, here's the pull-request:
The following changes since commit 455c6fdbd219161bd09b1165f11699d6d73de11c:
Linux 3.14 (2014-03-30 20:40:15 -0700)
are available in the git repository at:
The following changes since commit d712ff63b18309c939396f593510fbcccbafb9e4:
ARM: dts: Enable mcpdm and mcbsp1 on DuoVero (2014-05-19 17:20:31 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap
tags/omap-for-v3.16/dt-part3
for
Hi Aaro,
On Tue, 27 May 2014, Aaro Koskinen wrote:
Hi Paul,
On Tue, May 27, 2014 at 04:59:16PM +, Paul Walmsley wrote:
Here are some basic OMAP test results for Linux v3.15-rc7.
Logs and other details at:
http://www.pwsan.com/omap/testlogs/test_v3.15-rc7/20140526221127/
On Wed, May 28, 2014 at 02:27:13PM +0530, Satish Patel wrote:
+/**
+ * struct sc_phy - The basic smart card phy structure
+ *
+ * @dev: phy device
+ * @pdata: pointer to phy's private data structure
+ * @set_config: called to set phy's configuration
+ * @get_config: called to get phy's
On Wed, May 28, 2014 at 02:27:14PM +0530, Satish Patel wrote:
TDA8026 is a SmartCard PHY from NXP.
The PHY interfaces with the main processor over the
I2C interface and acts as a slave device.
The driver also exposes the phy interface
(defined@include/linux/sc_phy.h) for SmartCard
On Wed, May 28, 2014 at 02:27:13PM +0530, Satish Patel wrote:
SmartCard controller uses this interface to communicate with
SmartCard via PHY
Some SmartCard PHY has multiple slots for cards.
This inerface also enables controller to communicate
with one or more SmartCard connected over phy.
Here are some basic OMAP test results for Linux v3.15-rc7.
Logs and other details at:
http://www.pwsan.com/omap/testlogs/test_v3.15-rc7/20140528121000/
Test summary
Build: zImage:
Pass (14/14): multi_v7_defconfig, omap2plus_defconfig,
On Mon, May 19, 2014 at 6:20 AM, Tero Kristo t-kri...@ti.com wrote:
On 05/05/2014 10:49 AM, Tero Kristo wrote:
On 05/01/2014 10:00 PM, Mike Turquette wrote:
Quoting Tero Kristo (2014-04-29 07:51:14)
On 04/29/2014 05:15 PM, Sourav Poddar wrote:
We need tbclk clock data for the functioning
Hi,
This issue was originally reported by Russell on OMAP3-LDP platform,
and original attempt to solve this by Felipe[1] did not quiet work,
follow on attempt[2] seems to be effective, but in this resend, I have
added an shutdown attempt in case things dont quiet look right.
Based on: v3.15-rc7
Attempt to power off in case of critical events such as battery removal,
over voltage events.
There is no guarentee that we'd be in a safe scenario here, but the very
least we can try to do is to power off the device to prevent damage to
the system instead of just printing a message and hoping
TWL4030's Battery Charger seems to be designed for non-hotpluggable
batteries.
If battery is not present in the system, BATSTS is always set with the
expectation that software will take actions to move to a required safe
state (could be power down or disable various charger paths).
It does not
41 matches
Mail list logo
