On Thu, Sep 11, 2014 at 07:01:19AM -0500, Nishanth Menon wrote:
Hi Dimtry,
On 14:13-20140910, Dmitry Torokhov wrote:
On Thu, Aug 21, 2014 at 02:01:43PM -0500, Nishanth Menon wrote:
On 08/21/2014 01:03 PM, Dmitry Torokhov wrote:
I believe I have taken care of other concerns on v2,
On Friday 12 September 2014 02:59 AM, Lennart Sorensen wrote:
I have the mac but I don't want to use both ports on the 2 port switch.
In fact in our case ethernet1 is a pru_eth interface. Can a board dts
override the alias for ethernet1 or is that a syntax error? I don't
think I tried that
On 09/11/2014 07:04 PM, Frans Klaver wrote:
On 11 September 2014 18:04:32 CEST, Sebastian Andrzej Siewior
bige...@linutronix.de wrote:
On 09/11/2014 05:11 PM, Frans Klaver wrote:
I can still reproduce it on am335x. I can get out of it as soon as
something else gets written to the console
On 11.09.2014 16:15, Ulf Hansson wrote:
On 11 September 2014 16:11, Stefan Roese s...@denx.de wrote:
From: Thorsten Einsbein thorsten.eisb...@head-acoustics.de
On the TAO3530 (OMAP3530 based) we noticed that some SD cards are not
detected reliably upon bootup (timeout). Especially the SanDisk
On 12 September 2014 00:04, Uwe Kleine-König
u.kleine-koe...@pengutronix.de wrote:
Hello,
On Thu, Sep 11, 2014 at 11:04:31PM +0200, Uwe Kleine-König wrote:
/* Mux parent lists. */
-static const char *fin_pll_p[] __initconst = {
+static const char *fin_pll_p[] __initdata = {
xxti,
Hello Ard,
On Fri, Sep 12, 2014 at 09:42:29AM +0200, Ard Biesheuvel wrote:
On 12 September 2014 00:04, Uwe Kleine-König
u.kleine-koe...@pengutronix.de wrote:
Hello,
On Thu, Sep 11, 2014 at 11:04:31PM +0200, Uwe Kleine-König wrote:
/* Mux parent lists. */
-static const char
that commit did not remove all select statements for that
symbol. These statements are useless. Remove them too.
Signed-off-by: Paul Bolle pebo...@tiscali.nl
---
Done on top of next-20140912. Tested with git grep only!
arch/arm/mach-omap2/Kconfig| 5 -
arch/arm/mach-shmobile/Kconfig | 1
Hi Ezequiel,
On 09/11/2014 04:47 PM, Ezequiel Garcia wrote:
Following the recent discussion with Roger, here's a few patches that
(hopefully) fix all the issues.
The first patches rename the OMAP NAND drivers, so they are now called
omap2_nand and omap_elm.
The last patch picks an idea
On 09/11/2014 04:47 PM, Ezequiel Garcia wrote:
Rename it to a less generic name, so the module is built with a meaningful
name instead of the previous 'omap2.ko'.
Signed-off-by: Ezequiel Garcia ezequ...@vanguardiasur.com.ar
Acked-by: Roger Quadros rog...@ti.com
---
On 09/11/2014 04:47 PM, Ezequiel Garcia wrote:
The ELM driver is only used by the OMAP NAND driver, so let's move it
to the nand/ directory. Additionally, let's rename it to a less confusing
name, so the module is built with a meaningful name, instead of the previous
'elm.ko'.
On 09/11/2014 04:47 PM, Ezequiel Garcia wrote:
This commit adds a hidden option to build the omap_elm as a module, if
omap2_nand is a module (and similarly in the built-in case).
This fixes the following build error when omap2_nand is chosen built-in,
and omap_elm is chosen as a module:
On 09/12/2014 11:40 AM, Frans Klaver wrote:
I'm not sure. I just reproduced this on a boneblack, using your uart_v9
branch.
This problem only pops-up if you use DMA. With disabled DMA you don't
see this, right?
I get the lockup both with and without DMA enabled. Here's the 8250
config I
78c5e0bb145d (PM / OPP: Remove ARCH_HAS_OPP) removed it. For
some reason that commit did not remove all select statements for that
symbol. These statements are useless. Remove them too.
Signed-off-by: Paul Bolle pebo...@tiscali.nl
---
Done on top of next-20140912. Tested with git grep only!
arch
On Fri, Sep 12, 2014 at 11:51:22AM +0200, Sebastian Andrzej Siewior wrote:
On 09/12/2014 11:40 AM, Frans Klaver wrote:
I'm not sure. I just reproduced this on a boneblack, using your uart_v9
branch.
This problem only pops-up if you use DMA. With disabled DMA you don't
see this,
---
Done on top of next-20140912. Tested with git grep only!
arch/arm/mach-omap2/Kconfig| 5 -
there can be conflict here:
https://patchwork.kernel.org/patch/4857231/
http://marc.info/?l=linux-omapm=141047815520894w=2
Thanks.
arch/arm/mach-shmobile/Kconfig | 1 -
drivers
Hi Paul, Rafael,
On Fri, Sep 12, 2014 at 12:46 PM, Paul Bolle pebo...@tiscali.nl wrote:
arch/arm/mach-shmobile/Kconfig | 1 -
drivers/devfreq/Kconfig| 1 -
Were patches submitted for these two files too? If so, we can probably
just drop my patch.
Rafael said: I've queued this up
On Fri, 2014-09-12 at 13:03 +0200, Geert Uytterhoeven wrote:
Hi Paul, Rafael,
On Fri, Sep 12, 2014 at 12:46 PM, Paul Bolle pebo...@tiscali.nl wrote:
arch/arm/mach-shmobile/Kconfig | 1 -
drivers/devfreq/Kconfig| 1 -
Were patches submitted for these two files too? If so, we
Previously, the TI clock driver initialized all the clocks hierarchically
under each separate clock provider node. Now, each clock that requires
IO access will instead check their parent node to find out which IO range
to use.
This patch allows the TI clock driver to use a few new features
of_clk_add_provider makes an internal copy of the parent_names property
while its called, thus it is no longer needed after this call and can
be freed.
Signed-off-by: Tero Kristo t-kri...@ti.com
Cc: Mike Turquette mturque...@linaro.org
Cc: Peter Ujfalusi peter.ujfal...@ti.com
---
On 12 September 2014 09:54, Roger Quadros rog...@ti.com wrote:
Hi Ezequiel,
On 09/11/2014 04:47 PM, Ezequiel Garcia wrote:
Following the recent discussion with Roger, here's a few patches that
(hopefully) fix all the issues.
The first patches rename the OMAP NAND drivers, so they are now
On 12 Sep 12:01 PM, Roger Quadros wrote:
On 09/11/2014 04:47 PM, Ezequiel Garcia wrote:
This commit adds a hidden option to build the omap_elm as a module, if
omap2_nand is a module (and similarly in the built-in case).
This fixes the following build error when omap2_nand is chosen
We are getting PRM: I/O chain clock line assertion timed out errors
on early omaps for device tree based booting. This is because we are
unconditionally calling reconfigure_io_chain while legacy booting
has omap3_has_io_chain_ctrl() checks in place in omap_hwmod.c.
For device tree based booting,
From: Rob Herring robherri...@gmail.com
Currently trying to use pstore on at least ARMs can hang as we're
mapping the peristent RAM with pgprot_noncached().
On ARMs, pgprot_noncached() will actually make the memory strongly
ordered, and as the atomic operations pstore uses are implementation
On some ARMs at least the memory can be mapped pgprot_noncached()
and still be working for atomic operations. As pointed out by
Colin Cross ccr...@android.com, in some cases you do want to use
pgprot_noncached() if the SoC supports it to see a debug printk
just before a write hanging the system.
On 10:50-20140912, Tony Lindgren wrote:
We are getting PRM: I/O chain clock line assertion timed out errors
on early omaps for device tree based booting. This is because we are
unconditionally calling reconfigure_io_chain while legacy booting
has omap3_has_io_chain_ctrl() checks in place
On 09/10/2014 11:56 AM, Nishanth Menon wrote:
On 11:04-20140910, Dave Gerlach wrote:
v3:
Fix minor issue in last patch to check for null sram_pool if no sram
phandle is given in DT.
Make all OMAP DT only platforms (am33xx, am43xx, omap4 and omap5)
use drivers/misc/sram.c driver instead of
This patch adds three new OF helper functions to use/request
locks from a hwspinlock device instantiated through a
device-tree blob.
1. The of_hwspin_lock_get_num_locks() is a common OF helper
function to read the 'hwlock-num-locks' property.
2. The of_hwspin_lock_get_base_id() is a common OF
HwSpinlock IP is present only on OMAP4 and other newer SoCs,
which are all device-tree boot only. This patch adds the
base support for parsing the DT nodes, and removes the code
dealing with the traditional platform device instantiation.
Signed-off-by: Suman Anna s-a...@ti.com
[t...@atomide.com:
This patch adds the generic common bindings used to represent
a hwlock device and use/request locks in a device-tree build.
All the platform-specific hwlock driver implementations need the
number of locks and associated base id for registering the locks
present within the device with the driver
The hwspinlock_device structure is used for registering a bank of
locks with the driver core. The structure already contains the
necessary members to identify the bank of locks. The core does not
maintain the hwspinlock_devices itself, but maintains only a radix
tree for all the registered locks.
HwSpinlock IP is present only on OMAP4 and other newer SoCs,
which are all device-tree boot only. This patch adds the
DT bindings information for OMAP hwspinlock module.
Cc: Rob Herring robh...@kernel.org
Signed-off-by: Suman Anna s-a...@ti.com
---
Hi Ohad,
This is an update to the hwspinlock dt support series. The series
is rebased onto v3.17-rc3, and addresses the review comments on the
previous v5 series. I have also split and left out the RFC patches
about the support for reserved locks (will post these as a separate
series) and return
Hi Ohad,
This series is an RFC patchset that adds the support for reserved locks
to the HwSpinlock core to restrict the dynamic hwspin_lock_request() API
from allocating reserved locks (specific locks requested by DT client
users). The patches are split away from the v5 hwspinlock/omap dt
series
The HwSpinlock core allows requesting either a specific lock or
an available normal lock. The specific locks are usually reserved
during board init time, while the normal available locks are
intended to be assigned at runtime.
This patch prepares the hwspinlock core to support this concept
of
Rearrange the code between hwspin_lock_unregister() and the underlying
hwspin_lock_unregister_single() functions so that the semantics are
similar to the _register_ functions. This change prepares the hwspinlock
driver core to support unregistration of reserved locks better.
Signed-off-by: Suman
The HwSpinlock core allows requesting either a specific lock or an
available normal lock. The specific locks are usually reserved during
board init time, while the normal available locks are intended to be
assigned at runtime for clients that do not care about a specific
lock.
The HwSpinlock core
* Sebastian Andrzej Siewior bige...@linutronix.de [140910 12:30]:
the diff of v8…v9 is small:
- rebased on top's of Greg's tty-next branch
- fixed #10 where we might have THRE interrupt enabled for longer than
needed
- re-did register setup in #10. Before this less file could freeze the
On Fri, Sep 12, 2014 at 11:32:25AM -0700, Tony Lindgren wrote:
On some ARMs at least the memory can be mapped pgprot_noncached()
and still be working for atomic operations. As pointed out by
Colin Cross ccr...@android.com, in some cases you do want to use
pgprot_noncached() if the SoC supports
38 matches
Mail list logo
