Hi Paul,
On 09/10/14 17:03, Tomi Valkeinen wrote:
This is an RFC to fix the issues with boot time DSS hwmod setup.
There was an earlier series sent by Archit here:
http://www.spinics.net/lists/linux-omap/msg107700.html
This series takes different approach, and just tries to fix the
2014-11-13 13:56 GMT+01:00 Kishon Vijay Abraham I kis...@ti.com:
From: Balaji T K balaj...@ti.com
MMC tuning procedure is required to support SD card
UHS1-SDR104 mode and EMMC HS200 mode.
The tuning function omap_execute_tuning() will only
be called by the MMC/SD core if the corresponding
From: Hans Verkuil hans.verk...@cisco.com
The omap2 camera driver has been deprecated for a year and is now
going to be removed. It is unmaintained and it uses an internal API
that has long since been superseded by a much better API. Worse, that
internal API has been abused by out-of-kernel trees
On 11/13/2014 05:06 PM, Wolfram Sang wrote:
On Fri, Nov 07, 2014 at 04:49:22PM +0200, Roger Quadros wrote:
AM3352 SoC has 2 DCAN modules. Add compatible id and
raminit driver data for am3352 DCAN.
Signed-off-by: Roger Quadros rog...@ti.com
Acked-by: Wolfram Sang w...@the-dreams.de
For the
On Fri, Nov 14, 2014 at 10:23:13AM +0100, Hans Verkuil wrote:
From: Hans Verkuil hans.verk...@cisco.com
The omap2 camera driver has been deprecated for a year and is now
going to be removed. It is unmaintained and it uses an internal API
that has long since been superseded by a much better
On Thu, 13 Nov 2014 17:44:38 +0200
Tomi Valkeinen tomi.valkei...@ti.com wrote:
[snip]
a) Always keep the audio device operational, no matter what is the
status of the video side. How should this work if the HDMI videomode or
the HDMI monitor does not support audio? Is it desirable
On Fri, Nov 14, 2014 at 10:25:55AM +0100, Marc Kleine-Budde wrote:
On 11/13/2014 05:06 PM, Wolfram Sang wrote:
On Fri, Nov 07, 2014 at 04:49:22PM +0200, Roger Quadros wrote:
AM3352 SoC has 2 DCAN modules. Add compatible id and
raminit driver data for am3352 DCAN.
Signed-off-by: Roger
On 11/13/2014 06:03 PM, Marc Kleine-Budde wrote:
On 11/13/2014 04:23 PM, Roger Quadros wrote:
DRA7 CAN IP suffers from a problem which causes it to be prevented
from fully turning OFF (i.e. stuck in transition) if the module was
disabled while there was traffic on the CAN_RX line.
To work
Hello,
On 2014-11-13 14:18, Marek Szyprowski wrote:
This is an updated patchset, which intends to add support for L2 cache
on Exynos4 SoCs on boards running under secure firmware, which requires
certain initialization steps to be done with help of firmware, as
selected registers are writable
Hi Jyri,
On 12.11.2014 16:41, Jyri Sarha wrote:
Signed-off-by: Jyri Sarha jsa...@ti.com
---
drivers/video/fbdev/omap2/dss/hdmi.h |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/video/fbdev/omap2/dss/hdmi.h
b/drivers/video/fbdev/omap2/dss/hdmi.h
index
On Fri, Nov 14, 2014 at 1:58 AM, Tony Lindgren t...@atomide.com wrote:
* Paul Walmsley p...@pwsan.com [141113 15:01]:
Hi
On Thu, 13 Nov 2014, Tony Lindgren wrote:
* Tomi Valkeinen tomi.valkei...@ti.com [141113 03:33]:
On 12/11/14 17:02, Tony Lindgren wrote:
And, with a quick grep,
On Friday 14 November 2014 15:11:58 Marek Szyprowski wrote:
I assume that after all comments from previous versions, no more changes
are needed
to this patchset and I would really like to have it queued to v3.19.
Arnd, Olof: could you take this patchset thought arm-soc tree? It already
On 11/14/2014 04:37 PM, Vladimir Zapolskiy wrote:
Hi Jyri,
On 12.11.2014 16:41, Jyri Sarha wrote:
Signed-off-by: Jyri Sarha jsa...@ti.com
---
drivers/video/fbdev/omap2/dss/hdmi.h |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/video/fbdev/omap2/dss/hdmi.h
Some TI SoCs like DRA7 have a RAMINIT register specification
different from the other AMxx SoCs and as expected by the
existing driver.
To add more insanity, this register is shared with other
IPs like DSS, PCIe and PWM.
Provides a more generic mechanism to specify the RAMINIT
register location
DRA7 CAN IP suffers from a problem which causes it to be prevented
from fully turning OFF (i.e. stuck in transition) if the module was
disabled while there was traffic on the CAN_RX line.
To work around this issue we select the SLEEP pin state by default
on probe and use the DEFAULT pin state on
On 11/14/2014 04:40 PM, Roger Quadros wrote:
DRA7 CAN IP suffers from a problem which causes it to be prevented
from fully turning OFF (i.e. stuck in transition) if the module was
disabled while there was traffic on the CAN_RX line.
To work around this issue we select the SLEEP pin state by
On 11/07/2014 03:49 PM, Roger Quadros wrote:
DRA7 SoC has 2 CAN IPs. Provide compatible IDs and RAMINIT
register data for both.
Signed-off-by: Roger Quadros rog...@ti.com
---
Documentation/devicetree/bindings/net/can/c_can.txt | 1 +
drivers/net/can/c_can/c_can_platform.c |
* Grazvydas Ignotas nota...@gmail.com [141114 06:38]:
On Fri, Nov 14, 2014 at 1:58 AM, Tony Lindgren t...@atomide.com wrote:
* Paul Walmsley p...@pwsan.com [141113 15:01]:
Hi
On Thu, 13 Nov 2014, Tony Lindgren wrote:
* Tomi Valkeinen tomi.valkei...@ti.com [141113 03:33]:
On
On 11/14/2014 05:49 PM, Marc Kleine-Budde wrote:
On 11/14/2014 04:40 PM, Roger Quadros wrote:
DRA7 CAN IP suffers from a problem which causes it to be prevented
from fully turning OFF (i.e. stuck in transition) if the module was
disabled while there was traffic on the CAN_RX line.
To work
Hi,
On Thu, Nov 13, 2014 at 09:40:31AM -0800, Tony Lindgren wrote:
[snip]
From: Tony Lindgren t...@atomide.com
Date: Tue, 11 Nov 2014 07:53:55 -0800
Subject: [PATCH] genirq: Add support for wake-up interrupts to fix irq
reentry issues in drivers
As pointed out by Thomas Gleixner, at
On 11/13/2014 07:40 PM, Tony Lindgren wrote:
* Marc Kleine-Budde m...@pengutronix.de [141113 06:55]:
On 11/13/2014 03:49 PM, Roger Quadros wrote:
On 11/13/2014 04:44 PM, Marc Kleine-Budde wrote:
On 11/13/2014 03:40 PM, Roger Quadros wrote:
On 11/13/2014 04:07 PM, Marc Kleine-Budde wrote:
On
On 11/14/2014 04:37 PM, Roger Quadros wrote:
Some TI SoCs like DRA7 have a RAMINIT register specification
different from the other AMxx SoCs and as expected by the
existing driver.
To add more insanity, this register is shared with other
IPs like DSS, PCIe and PWM.
Provides a more
On 11/14/2014 06:32 PM, Marc Kleine-Budde wrote:
On 11/14/2014 04:37 PM, Roger Quadros wrote:
Some TI SoCs like DRA7 have a RAMINIT register specification
different from the other AMxx SoCs and as expected by the
existing driver.
To add more insanity, this register is shared with other
IPs
On Fri, Nov 14, 2014 at 08:37:56AM +0100, Pavel Machek wrote:
I'm using nfsroot (no modules), .config is attached. Debian v7.7,
ofono installed.
To launch ofono, I'm using:
rmdir /dev/cmt
ln -s /sys/bus/hsi/devices/n900-modem/ /dev/cmt
At least with Debian as base you can add this to
On Tuesday 26 August 2014 02:22 PM, Daniel Mack wrote:
This patch makes the edma driver resume correctly after suspend. Tested
on an AM33xx platform with cyclic audio streams and omap_hsmmc.
All information can be reconstructed by already known runtime
information.
As we now use some
Hi Sekhar,
On 11/14/2014 06:03 PM, Sekhar Nori wrote:
I think I have asked this before, and I am still not sure why this call
to pm_runtime_get_sync() is needed here. From my testing today, this
does seem to be a a no-op and this call returns from rpm_resume()
because of this check:
* Felipe Balbi ba...@ti.com [141114 08:20]:
On Thu, Nov 13, 2014 at 09:40:31AM -0800, Tony Lindgren wrote:
+/**
+ * handle_wakeirq_thread - call device runtime pm calls on wake-up
interrupt
+ * @wakeirq: device specific wake-up interrupt
+ * @dev_id: struct device entry
+ */
Hi Ohad,
On 11/14/2014 01:11 AM, Ohad Ben-Cohen wrote:
Hi Suman,
On Thu, Nov 13, 2014 at 11:02 PM, Suman Anna s-a...@ti.com wrote:
OK, lets take an example. I have say 2 device instances, say
hwlock1: hwlock@0 {
hwlock-num-locks = 32
hwlock-base-id
Hi,
On Fri, Nov 14, 2014 at 09:04:23AM +0200, Ivaylo Dimitrov wrote:
[...]
https://gitorious.org/linux-n900/freemangordons-linux-n900/commits/30e9a5c498a89cea4c29523f69e436bf0af3c631
commits 89ce13b, b81d80d, ec4d0dc, 91256e2 and 8022a6d - e29f558 (no idea
why gitorious shows those mixed
On Fri, Nov 14, 2014 at 09:08:17AM -0800, Tony Lindgren wrote:
* Felipe Balbi ba...@ti.com [141114 08:20]:
On Thu, Nov 13, 2014 at 09:40:31AM -0800, Tony Lindgren wrote:
+/**
+ * handle_wakeirq_thread - call device runtime pm calls on wake-up
interrupt
+ * @wakeirq:
On Friday 14 November 2014 18:20:09 Sebastian Reichel wrote:
Hi,
On Fri, Nov 14, 2014 at 09:04:23AM +0200, Ivaylo Dimitrov
wrote:
[...]
https://gitorious.org/linux-n900/freemangordons-linux-n900/c
ommits/30e9a5c498a89cea4c29523f69e436bf0af3c631
commits 89ce13b, b81d80d, ec4d0dc,
Hi,
On Thu, Nov 13, 2014 at 06:26:18PM +0530, Kishon Vijay Abraham I wrote:
@@ -233,6 +263,48 @@ struct omap_mmc_of_data {
u8 controller_flags;
};
+static const u32 ref_tuning_4bits[] = {
+ 0x00FF0FFF, 0xCCC3CCFF, 0xFFCC3CC3, 0xEFFEFFFE,
+ 0xDDFFDFFF, 0xFBFFFBFF,
On 11/07/2014 03:49 PM, Roger Quadros wrote:
Some platforms (e.g. TI) need special RAMINIT register handling.
Provide a way to store RAMINIT register description in driver data.
Signed-off-by: Roger Quadros rog...@ti.com
---
drivers/net/can/c_can/c_can.h | 6 ++
* Tero Kristo t-kri...@ti.com [141113 23:33]:
On 11/14/2014 01:58 AM, Tony Lindgren wrote:
The PRCM/clock cleanups that I have under work basically splits the clock
inits under their respective IP blocks; currently everything is registered
under generic PRCM. System control module will be
On Fri, Nov 14, 2014 at 11:41:52AM -0600, Felipe Balbi wrote:
Hi,
On Thu, Nov 13, 2014 at 06:26:18PM +0530, Kishon Vijay Abraham I wrote:
@@ -233,6 +263,48 @@ struct omap_mmc_of_data {
u8 controller_flags;
};
+static const u32 ref_tuning_4bits[] = {
+ 0x00FF0FFF,
* Roger Quadros rog...@ti.com [141114 08:24]:
On 11/13/2014 07:40 PM, Tony Lindgren wrote:
* Marc Kleine-Budde m...@pengutronix.de [141113 06:55]:
On 11/13/2014 03:49 PM, Roger Quadros wrote:
On 11/13/2014 04:44 PM, Marc Kleine-Budde wrote:
On 11/13/2014 03:40 PM, Roger Quadros wrote:
Picking up Roger's work:
Changes since v7:
- combined raminit start and done bit into a struct (3/8, 7/8, 8/8)
- constified struct c_can_driver_data (2/8, 7/8, 8/8)
- silenced compiler warning in c_can_hw_raminit_{wait,}_syscon (4/8)
- use platform_get_device_id in probe() instead of open coding
From: Roger Quadros rog...@ti.com
TI's RAMINIT DONE mechanism is buggy on AM43xx SoC and may not always
be set after the START bit is set. Although it seems to work fine even
in that case. So add a timeout mechanism to c_can_hw_raminit_wait_ti().
Don't bail out in that failure case but just print
From: Roger Quadros rog...@ti.com
Some SoCs e.g. (TI DRA7xx) need a START pulse to start the
RAMINIT sequence i.e. START bit must be set and cleared before
checking for the DONE bit status.
Signed-off-by: Roger Quadros rog...@ti.com
Signed-off-by: Marc Kleine-Budde m...@pengutronix.de
---
From: Roger Quadros rog...@ti.com
AM3352 SoC has 2 DCAN modules. Add compatible id and
raminit driver data for am3352 DCAN.
Signed-off-by: Roger Quadros rog...@ti.com
Acked-by: Wolfram Sang w...@the-dreams.de
Signed-off-by: Marc Kleine-Budde m...@pengutronix.de
---
From: Roger Quadros rog...@ti.com
We want to have more data than just can_dev_id to be present
in the driver data e.g. TI platforms need RAMINIT register
description. Introduce the c_can_driver_data structure and move
the can_dev_id into it.
Tidy up the way it is used on probe().
Signed-off-by:
From: Roger Quadros rog...@ti.com
Some TI SoCs like DRA7 have a RAMINIT register specification
different from the other AMxx SoCs and as expected by the
existing driver.
To add more insanity, this register is shared with other
IPs like DSS, PCIe and PWM.
Provides a more generic mechanism to
From: Roger Quadros rog...@ti.com
DRA7 CAN IP suffers from a problem which causes it to be prevented
from fully turning OFF (i.e. stuck in transition) if the module was
disabled while there was traffic on the CAN_RX line.
To work around this issue we select the SLEEP pin state by default
on
From: Roger Quadros rog...@ti.com
Some platforms (e.g. TI) need special RAMINIT register handling.
Provide a way to store RAMINIT register description in driver data.
Signed-off-by: Roger Quadros rog...@ti.com
Signed-off-by: Marc Kleine-Budde m...@pengutronix.de
---
From: Roger Quadros rog...@ti.com
DRA7 SoC has 2 CAN IPs. Provide compatible IDs and RAMINIT
register data for both.
Signed-off-by: Roger Quadros rog...@ti.com
Signed-off-by: Marc Kleine-Budde m...@pengutronix.de
---
Documentation/devicetree/bindings/net/can/c_can.txt | 1 +
* Vignesh R vigne...@ti.com [141113 21:42]:
The charge delay value is by default 0x400. But it can be set to lower
values on some boards, as long as false pen-ups are avoided. Lowering the
value increases the sampling rate (though current sampling rate is
sufficient for TSC operation). In some
* Tero Kristo t-kri...@ti.com [141112 22:11]:
On 11/12/2014 05:25 PM, Tony Lindgren wrote:
* Tony Lindgren t...@atomide.com [141112 07:26]:
* Tomi Valkeinen tomi.valkei...@ti.com [141013 01:52]:
The clock nodes for DSS VIDEO1/2 and HDMI have wrong register addresses.
This patch fixes the
* Hans Verkuil hverk...@xs4all.nl [141114 01:25]:
From: Hans Verkuil hans.verk...@cisco.com
The omap2 camera driver has been deprecated for a year and is now
going to be removed. It is unmaintained and it uses an internal API
that has long since been superseded by a much better API. Worse,
* Paul Walmsley p...@pwsan.com [141113 14:52]:
The following changes since commit f114040e3ea6e07372334ade75d1ee0775c355e1:
Linux 3.18-rc1 (2014-10-19 18:08:38 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/pjw/omap-pending.git
* Vignesh R vigne...@ti.com [141113 20:09]:
On Tuesday 04 November 2014 04:45 PM, Vignesh R wrote:
This series of patches enable ADC on am437x-gp-evm and am43x-epos-evm.
The ADC clock hwmod data of am33xx has been moved to commom place so that
both am43xx and am33xx can reuse them.
On 14.11.2014 19:20, Sebastian Reichel wrote:
The patch looks ok. It does not cleanup the cmt-speech driver for
mainline usage, but it should work. Before adding this driver to the
mainline kernel there should be open source userspace support anyway.
I am aware of that(patch not ready),
On Fri, Nov 14, 2014 at 7:09 PM, Suman Anna s-a...@ti.com wrote:
It seems to me that hwspin_lock_request_specific failures should be
used by clients to defer their probing. Why wouldn't such a simple
solution work?
Because the API always returns NULL on failures and there is no way for
the
The following changes since commit cac7f2429872d3733dc3f9915857b1691da2eb2f:
Linux 3.18-rc2 (2014-10-26 16:48:41 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap
tags/omap-for-v3.19/w1-and-l3-noc
for you to fetch changes up to
The following changes since commit cac7f2429872d3733dc3f9915857b1691da2eb2f:
Linux 3.18-rc2 (2014-10-26 16:48:41 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap
tags/omap-for-v3.19/clocks-and-pm
for you to fetch changes up to
Hi!
On Fri 2014-11-14 21:54:42, Ivaylo Dimitrov wrote:
On 14.11.2014 19:20, Sebastian Reichel wrote:
The patch looks ok. It does not cleanup the cmt-speech driver for
mainline usage, but it should work. Before adding this driver to the
mainline kernel there should be open source userspace
Hi,
On Fri, Nov 14, 2014 at 09:54:42PM +0200, Ivaylo Dimitrov wrote:
On 14.11.2014 19:20, Sebastian Reichel wrote:
The patch looks ok. It does not cleanup the cmt-speech driver for
mainline usage, but it should work. Before adding this driver to the
mainline kernel there should be open source
Hi,
On Fri, Nov 14, 2014 at 06:34:18PM +0100, Pali Rohár wrote:
Anyway what is /dev/cmt_speech doing? If it exports gsm voice
call data, [...]
Right.
[...] should not it have alsa snd interface?
Sounds also like a promising standardized kernel interface.
I wonder why a custom interface has
Felipe,
Thank you for your reply.
+ vbat: fixedregulator@0 {
+ compatible = regulator-fixed;
+ regulator-name = vbat;
+ regulator-min-microvolt = 500;
+ regulator-max-microvolt = 500;
+ regulator-boot-on;
+ };
I
commit 1d7afc95946487945cc7f5019b41255b72224b70 (i2c: omap: ack IRQ in parts)
changed the interrupt handler to complete transfers without clearing
XRDY (AL case) and ARDY (NACK case) flags. XRDY or ARDY interrupt will be
fired again (in parallel with omap_i2c_xfer_msg). Interrupt handler will
commit 66b9298878742f08cb6e79b7c7d5632d782fd1e1 (i2c: omap: switch over
to do {} while loop) changed the interrupt handler to abort transfers
in case interrupt serviced 100 times but commit's comment states that
No functional changes otherwise..
Also, original commit could report status 0 (no
commit 1d7afc95946487945cc7f5019b41255b72224b70 (i2c: omap: ack IRQ in parts)
changed the interrupt handler to complete transfers without clearing
XRDY (AL case) and ARDY (NACK case) flags. XRDY or ARDY interrupt will be
fired again (in parallel with omap_i2c_xfer_msg). Interrupt handler will
commit 66b9298878742f08cb6e79b7c7d5632d782fd1e1 (i2c: omap: switch over
to do {} while loop) changed the interrupt handler to abort transfers
in case interrupt serviced 100 times but commit's comment states that
No functional changes otherwise..
Also, original commit could report status 0 (no
Hi,
On Fri, Nov 14, 2014 at 04:47:02PM -0600, George McCollister wrote:
Felipe,
Thank you for your reply.
no problem
+ vbat: fixedregulator@0 {
+ compatible = regulator-fixed;
+ regulator-name = vbat;
+ regulator-min-microvolt = 500;
+
On Sat, Nov 15, 2014 at 05:20:51AM +0400, Alexander Kochetkov wrote:
commit 1d7afc95946487945cc7f5019b41255b72224b70 (i2c: omap: ack IRQ in parts)
changed the interrupt handler to complete transfers without clearing
XRDY (AL case) and ARDY (NACK case) flags. XRDY or ARDY interrupt will be
Add si4713 node to the N900 device tree file.
Signed-off-by: Sebastian Reichel s...@kernel.org
---
arch/arm/boot/dts/omap3-n900.dts | 10 ++
1 file changed, 10 insertions(+)
diff --git a/arch/arm/boot/dts/omap3-n900.dts b/arch/arm/boot/dts/omap3-n900.dts
index 9b0494a..81c99f3 100644
Hi,
On Sat, Nov 15, 2014 at 05:20:52AM +0400, Alexander Kochetkov wrote:
commit 66b9298878742f08cb6e79b7c7d5632d782fd1e1 (i2c: omap: switch over
to do {} while loop) changed the interrupt handler to abort transfers
in case interrupt serviced 100 times but commit's comment states that
No
This adds support for the N900's battery to the
Nokia N900 DTS file.
Signed-off-by: Sebastian Reichel s...@kernel.org
---
arch/arm/boot/dts/omap3-n900.dts | 6 ++
1 file changed, 6 insertions(+)
diff --git a/arch/arm/boot/dts/omap3-n900.dts b/arch/arm/boot/dts/omap3-n900.dts
index
Hi Felipe,
Initially you made the change (66b9298878742f08cb6e79b7c7d5632d782fd1e1):
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/i2c/busses/i2c-omap.c?id=66b9298878742f08cb6e79b7c7d5632d782fd1e1
dev_dbg(dev-dev, IRQ (ISR = 0x%04x)\n, stat);
Assuming this is really correct (I haven't tested), you need to add:
To help understanding logic, I'd like to provide event traces (with the patch
applied):
See i2c-omap.c dc418f6e6a8f5021ccf9e9c0957eefae3737168d as a reference.
Hi,
(please, never top-post)
On Sat, Nov 15, 2014 at 05:37:41AM +0300, Alexander Kochetkov wrote:
Hi Felipe,
Initially you made the change (66b9298878742f08cb6e79b7c7d5632d782fd1e1):
Hi again,
On Fri, Nov 14, 2014 at 09:47:56PM -0600, Felipe Balbi wrote:
how ? This is an interesting bug which deserves further explanation.
Look at the loops above, and at the omap_i2c_complete_cmd:
static inline void
omap_i2c_complete_cmd(struct omap_i2c_dev *dev, u16 err)
{
Hello again.
(please, never top-post)
Sorry.
Sorry for the inaccurate presentation of ideas. I am not a native English
speaker.
First about patches:
[PATCH 1/2] and [PATCH 2/2] - intended to solve two independent problems.
They were sent as series, In the future, try not to do so, In order
72 matches
Mail list logo
