On 04/22/2013 09:08 PM, Tony Lindgren wrote:
* Grygorii Strashko grygorii.stras...@ti.com [130422 05:27]:
On 04/22/2013 01:24 PM, Tomi Valkeinen wrote:
On 2013-04-22 12:08, Tomi Valkeinen wrote:
On 2013-04-19 20:13, Tony Lindgren wrote:
3. DSS fails with DT booting
Works with legacy
On 04/23/2013 08:34 PM, Tony Lindgren wrote:
* Grygorii Strashko grygorii.stras...@ti.com [130423 06:25]:
Hi
There are two public discussions now related to OMAP boot and drivers
initialization issues:
Multiple issues with omap4 panda es in linux next
http://www.spinics.net/lists/linux-omap
On 04/22/2013 01:24 PM, Tomi Valkeinen wrote:
On 2013-04-22 12:08, Tomi Valkeinen wrote:
On 2013-04-19 20:13, Tony Lindgren wrote:
3. DSS fails with DT booting
Works with legacy booting but fails with DT. I'm almost certain
the DT booting was working last week or so?
This is what I now get
: Grygorii Strashko grygorii.stras...@ti.com
Signed-off-by: Sourav Poddar sourav.pod...@ti.com
---
Hi Kevin,
I have put this as an RFC, due to few comments on cover letter of
the previous version by Grygorii Strashko.
As, he has mentioned that there are Audio playback use cases which
also requires
On 04/22/2013 04:43 PM, Sourav Poddar wrote:
The driver manages no_console_suspend by preventing runtime PM
during the suspend path, which forces the console UART to stay awake.
Signed-off-by: Sourav Poddar sourav.pod...@ti.com
---
drivers/tty/serial/omap-serial.c |5 -
1 files
On 04/18/2013 10:17 PM, Sourav Poddar wrote:
Hi Kevin,
On Thursday 18 April 2013 11:53 PM, Kevin Hilman wrote:
Hi Sourav,
Sourav Poddarsourav.pod...@ti.com writes:
Hi,
This patch series contains fixes and cleanups around the issue that
the console UART should not idled on suspend while
On 04/16/2013 10:07 PM, Mike Turquette wrote:
Quoting Andrii Tseglytskyi (2013-04-16 05:40:44)
On 04/16/2013 12:53 AM, Kevin Hilman wrote:
In addition to Mike's comments (which I completely agree with), it would
be very helfpul to see how this is actually used. e.g, how the
regulators are
On 04/15/2013 07:40 PM, Mark Brown wrote:
On Mon, Apr 15, 2013 at 07:21:25PM +0300, Andrii Tseglytskyi wrote:
On 04/15/2013 06:50 PM, Mark Brown wrote:
In addition, such locking scheme allows to have access to the supplier
regulator API from inside child's (consumer) regulator API.
I've still
On 04/16/2013 10:45 AM, Peter Ujfalusi wrote:
On 04/15/2013 06:25 PM, Tony Lindgren wrote:
This fix should not be needed. It just means the real
problem is somewhere else. Pinctrl is already before the i2c
in drivers/Makefile. Maybe one of the MFD drivers has
a wrong initcall level?
FYI; I
On 04/13/2013 09:27 PM, Christoph Fritz wrote:
Hi
while testing an omap3 board with device tree support I stumbled upon a
bug which is due to wrong initialization order of twl-core and
twl-regulator (I suppose): In the boot process they get loaded way too
late so that a lot of drivers before
On 04/15/2013 01:56 PM, Christoph Fritz wrote:
On Mon, 2013-04-15 at 13:20 +0300, Grygorii Strashko wrote:
On 04/13/2013 09:27 PM, Christoph Fritz wrote:
Hi
while testing an omap3 board with device tree support I stumbled upon a
bug which is due to wrong initialization order of twl-core
?
Grygorii Strashko (1):
regulator: core: introduce regulator chain locking scheme
drivers/regulator/core.c | 134 --
include/linux/regulator/driver.h |2 +
2 files changed, 88 insertions(+), 48 deletions(-)
Regards
Grygorii Strashko
Cc: linux
: Mike Turquette mturque...@linaro.org
Cc: Nishanth Menon n...@ti.com
Cc: Tero Kristo t-kri...@ti.com
Cc: linux-omap linux-omap@vger.kernel.org
Cc: linux-arm linux-arm-ker...@lists.infradead.org
Signed-off-by: Grygorii Strashko grygorii.stras...@ti.com
---
drivers/regulator/core.c | 134
node described in
typo: an-a
device tree blob is used to identify the exact clock provided in the SoC
specific data. This is then linked back using of_clk_add_provider to the
device node to be accessible by of_clk_get.
Based on discussion contributions from Roger Quadros, Grygorii Strashko
On 04/04/2013 07:41 PM, Tony Lindgren wrote:
* Roger Quadros rog...@ti.com [130404 00:39]:
On 04/04/2013 02:42 AM, Tony Lindgren wrote:
--- a/arch/arm/mach-omap2/cclock44xx_data.c
+++ b/arch/arm/mach-omap2/cclock44xx_data.c
@@ -27,6 +27,7 @@
#include linux/clk-private.h
#include
;
regulator-max-microvolt = 145;
};
Regards,
Grygorii Strashko
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
macros from the system.
Please comment if this is an acceptable approach - at a first glance,
it seems to pave way to be capable of being replaced potentially by DT data as
well.
Grygorii Strashko (2):
ARM: OMAP2+: clock: Add omap2_clks_register API
ARM: OMAP4: clock: use omap4_clks_register
clocks set for OMAP446x SoCs
Signed-off-by: Grygorii Strashko grygorii.stras...@ti.com
---
arch/arm/mach-omap2/clock.c | 36
arch/arm/mach-omap2/clock.h |3 +++
2 files changed, 39 insertions(+)
diff --git a/arch/arm/mach-omap2/clock.c b/arch/arm/mach-omap2
,
then, it is possible to do the same.
One additional benefit seen is that the match logic can entirely be
skipped.
Signed-off-by: Grygorii Strashko grygorii.stras...@ti.com
---
arch/arm/mach-omap2/clock44xx_data.c | 40 ++
1 file changed, 21 insertions(+), 19
301 - 319 of 319 matches
Mail list logo
