On 30 October 2014 02:47:04 CET, Brian Norris
wrote:
>On Tue, Oct 28, 2014 at 11:46:57AM +0200, Roger Quadros wrote:
>> On 10/27/2014 04:34 PM, Frans Klaver wrote:
>> > Since commit 6d178ef2fd5e ("mtd: nand: Move ELM driver and rename
>as
>> > omap_elm"), I don't have any mtd devices present on m
On Thursday 30 October 2014 04:39 AM, Rabin Vincent wrote:
> Unless I'm missing something, this patch appears to have still not been
> picked up. It would be nice if it can go in for 3.18 so that we have
> working USB on pandaboard again at least in that release.
>
> Tony, would you mind carryi
On Tue, Oct 28, 2014 at 11:46:57AM +0200, Roger Quadros wrote:
> On 10/27/2014 04:34 PM, Frans Klaver wrote:
> > Since commit 6d178ef2fd5e ("mtd: nand: Move ELM driver and rename as
> > omap_elm"), I don't have any mtd devices present on my am335x. This
> > changes the link order of the omap_elm an
Let's use the bootloader values except for the partially configured
wait-pin that does not seem to work.
Cc: Roger Quadros
Signed-off-by: Tony Lindgren
---
arch/arm/boot/dts/omap2430-sdp.dts | 28 ++--
1 file changed, 26 insertions(+), 2 deletions(-)
diff --git a/arch/a
As we still have some devices with GPMC timings missing from the
.dts files, let's make it a bit easier to use the bootloader
values and print them out.
Note that we now need to move the parsing of the device tree provided
configuration a bit earlier so we can use that for checking if anything
was
Apparently some versions of nolo don't mux the necessary GPMC
pins for the smc91x probe to work properly. Let's fix this issue
by adding mux support for GPMC to the kernel.
Note that it's unclear why the GPMC clk pin has input enabled, but
let's not touch that as in general the mux settings in nol
This board seems to be in use only for few automated
boot test system and has been booting in device tree
only mode for quite some time now.
So let's drop the board file for it.
Signed-off-by: Tony Lindgren
---
arch/arm/mach-omap2/Kconfig | 6 -
arch/arm/mach-omap2/Makefile|
This code was only used by 2430sdp, 3430sdp, and n900 development
boards.
The 2430sdp is already device tree only, and all the users of the
3430sdp and n900 development boards are already booting in device
tree mode, so we can drop the legacy smc91x support.
Cc: Roger Quadros
Signed-off-by: Tony
Now that we have timings in the .dts files for smc91x
and 8250, we can remove the device specific checks and
just print out the bootloader timings for devices that
may not have timings in the .dts files.
Cc: Roger Quadros
Signed-off-by: Tony Lindgren
---
arch/arm/mach-omap2/gpmc.c | 16
The GPMC binding is obviously very confusing as the values
are all over the place. People seem to confuse the GPMC partition
size for the chip select, and the device IO size within the GPMC
partition easily.
The ranges entry contains the GPMC partition size. And the
reg entry contains the size of
The 81xx support is known to be broken for quite some
time now because of missing patches. And it should be
using device tree based booting now anyways.
So let's just drop the board file for it.
Signed-off-by: Tony Lindgren
---
arch/arm/mach-omap2/Kconfig | 10 --
arch/arm/mach-om
There are cases where we have multiple device instances
connected to a single GPMC chip select. For example, there
are four UARTs on the Zoom debug boards that all share a
single chip select and a GPIO interrupt.
We do have support for this already in theory, but it's broken
because we're bailing
The four port serial port on the zoom debug board uses a TL16CP754C
with a single interrupt and GPMC chip select. The serial ports each
use a 8 bytes for IO registers, and are 256 bytes apart on the GPMC
line.
Let's add timings for all four ports so we can remove the GPMC
workarounds for using boo
Here are few patches to fix and clean up some GPMC issues
and remove two board files that are no longer needed.
Regards,
Tony
Tony Lindgren (10):
ARM: dts: Fix bootloader version dependencies by muxing n900 smc91x
pins
ARM: dts: Fix wrong GPMC size mappings for omaps
ARM: dts: Add smc
Hello Tony,
On Thu, Oct 30, 2014 at 12:11 AM, Aaro Koskinen wrote:
> On Wed, Oct 29, 2014 at 12:39:16PM -0700, Tony Lindgren wrote:
>> From: Tony Lindgren
>> Date: Mon, 27 Oct 2014 13:05:54 -0700
>> Subject: [PATCH] ARM: OMAP2+: Warn about deprecated legacy booting mode
>>
>> We're moving omaps
On Wed, Oct 29, 2014 at 12:39:16PM -0700, Tony Lindgren wrote:
> From: Tony Lindgren
> Date: Mon, 27 Oct 2014 13:05:54 -0700
> Subject: [PATCH] ARM: OMAP2+: Warn about deprecated legacy booting mode
>
> We're moving omaps to use device tree based booting and already have
> omap2, omap4, omap5, am
Unless I'm missing something, this patch appears to have still not been
picked up. It would be nice if it can go in for 3.18 so that we have
working USB on pandaboard again at least in that release.
Tony, would you mind carrying it as OMAP maintainer since we haven't
heard anything from Kishon (t
Hi,
On Wed, Oct 29, 2014 at 12:39:16PM -0700, Tony Lindgren wrote:
> 8< ---
> From: Tony Lindgren
> Date: Mon, 27 Oct 2014 13:05:54 -0700
> Subject: [PATCH] ARM: OMAP2+: Warn about deprecated legacy booting mode
>
> We're moving omaps to use device tree based booting and alre
On Wed, Oct 29, 2014 at 04:45:41PM -0500, Nishanth Menon wrote:
> On 12:39-20141029, Tony Lindgren wrote:
> > OK, you want me to guess? A hundred million days, or maybe ten more
> > minutes, somewhere in there, I just can't say, don't know.
>
> How about ~1 year
* Nishanth Menon [141029 14:47]:
> On 12:39-20141029, Tony Lindgren wrote:
> > * Sebastian Reichel [141029 12:01]:
> > > Hi,
> > >
> > > On Wed, Oct 29, 2014 at 08:43:03AM -0500, Nishanth Menon wrote:
> > > > On 10/28/2014 05:12 PM, Tony Lindgren
On 12:39-20141029, Tony Lindgren wrote:
> * Sebastian Reichel [141029 12:01]:
> > Hi,
> >
> > On Wed, Oct 29, 2014 at 08:43:03AM -0500, Nishanth Menon wrote:
> > > On 10/28/2014 05:12 PM, Tony Lindgren wrote:
> > > > * Aaro Koskinen [141027 16:03]:
>
On Wed 2014-10-29 16:18:46, Tomi Valkeinen wrote:
> On 29/10/14 16:09, Tony Lindgren wrote:
>
> >> omapfb reports problems, but seems to work ok:
> >>
> >> [0.990386] omapfb omapfb: cannot parse default modes
> >> [1.004791] Console: switching to colour frame buffer device 100x30
> >> [
Dear Sir
Did your website get hit by Google Penguin update on October 17th 2014? What
basically is Google Penguin Update? It is actually a code name for Google
algorithm which aims at decreasing your websites search engine rankings that
violate Googles guidelines by using black hat SEO techniq
* Sebastian Reichel [141029 12:01]:
> Hi,
>
> On Wed, Oct 29, 2014 at 08:43:03AM -0500, Nishanth Menon wrote:
> > On 10/28/2014 05:12 PM, Tony Lindgren wrote:
> > > * Aaro Koskinen [141027 16:03]:
> > >> Hi,
> > >>
> > >> On Mon, Oct 27, 2014 at 01:00:09PM -0700, Tony Lindgren wrote:
> > >>> +
>
On Wed, 29 Oct 2014 13:50:05 +0100 Johan Hovold wrote:
> On Tue, Oct 28, 2014 at 09:36:33AM +0100, Johan Hovold wrote:
> > On Mon, Oct 27, 2014 at 03:40:31PM -0700, Andrew Morton wrote:
> > > On Mon, 27 Oct 2014 09:09:28 +0100 Johan Hovold wrote:
>
> > But in general, how do you want to handle
Hi,
On Wed, Oct 29, 2014 at 08:43:03AM -0500, Nishanth Menon wrote:
> On 10/28/2014 05:12 PM, Tony Lindgren wrote:
> > * Aaro Koskinen [141027 16:03]:
> >> Hi,
> >>
> >> On Mon, Oct 27, 2014 at 01:00:09PM -0700, Tony Lindgren wrote:
> >>> +
> >>> + if (!of_have_populated_dt())
> >>> + pr_
From: Tony Lindgren
Date: Mon, 27 Oct 2014 13:25:56 -0700
> +/**
> + * of_try_set_control_gpio - configure a gpio if it exists
> + */
> +static int try_toggle_control_gpio(struct device *dev,
> +struct gpio_desc **desc,
> +const char
On Wed, Oct 29, 2014 at 08:36:41AM -0700, Guenter Roeck wrote:
> On Wed, Oct 29, 2014 at 02:35:26PM +0100, Johan Hovold wrote:
> > On Wed, Oct 29, 2014 at 06:20:40AM -0700, Guenter Roeck wrote:
> > > On 10/29/2014 05:34 AM, Johan Hovold wrote:
> > > > And what about any power-off latencies? Should
On Wed, Oct 29, 2014 at 08:25:02AM -0700, Guenter Roeck wrote:
> On Wed, Oct 29, 2014 at 02:22:44PM +0100, Johan Hovold wrote:
> > On Wed, Oct 29, 2014 at 01:10:20PM +, Russell King - ARM Linux wrote:
> > > On Wed, Oct 29, 2014 at 01:34:18PM +0100, Johan Hovold wrote:
> > > > On Tue, Oct 28, 20
On Wed, Oct 29, 2014 at 02:35:26PM +0100, Johan Hovold wrote:
> On Wed, Oct 29, 2014 at 06:20:40AM -0700, Guenter Roeck wrote:
> > On 10/29/2014 05:34 AM, Johan Hovold wrote:
> > > On Tue, Oct 28, 2014 at 03:16:10PM +, Russell King - ARM Linux wrote:
> > >> On Tue, Oct 28, 2014 at 02:12:57PM +0
On Wed, Oct 29, 2014 at 02:22:44PM +0100, Johan Hovold wrote:
> On Wed, Oct 29, 2014 at 01:10:20PM +, Russell King - ARM Linux wrote:
> > On Wed, Oct 29, 2014 at 01:34:18PM +0100, Johan Hovold wrote:
> > > On Tue, Oct 28, 2014 at 03:16:10PM +, Russell King - ARM Linux wrote:
> > > > And how
On 29/10/14 16:09, Tony Lindgren wrote:
>> omapfb reports problems, but seems to work ok:
>>
>> [0.990386] omapfb omapfb: cannot parse default modes
>> [1.004791] Console: switching to colour frame buffer device 100x30
>> [1.073150] omapfb omapfb: using display 'lcd' mode 800x480
>
>
* Roger Quadros [141029 01:51]:
> On 10/29/2014 12:23 AM, Tony Lindgren wrote:
> > * Roger Quadros [141021 05:43]:
> >> Simplify set_gpmc_timing_reg() and always print error message
> >> if the requested timing cannot be achieved due to a too fast
> >> GPMC functional clock, irrespective if wheth
* Pavel Machek [141029 01:48]:
>
> Speaking of testing:
>
> I'm not sure what is omap_l3_smx neccessary for, but it does not work.
>
> [0.223297] omap_l3_smx omap_l3_smx.0: couldn't request debug irq
> [0.223419] omap_l3_smx: probe of omap_l3_smx.0 failed with error
> -22
Hmm this shou
[ Again, please stop with the top-posting.
A: http://en.wikipedia.org/wiki/Top_post
Q: Were do I find info about this thing called top-posting?
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing? ]
On Wed, Oct 29, 2014 at 02:11:02PM +0100
On 10/28/2014 05:12 PM, Tony Lindgren wrote:
> * Aaro Koskinen [141027 16:03]:
>> Hi,
>>
>> On Mon, Oct 27, 2014 at 01:00:09PM -0700, Tony Lindgren wrote:
>>> +
>>> + if (!of_have_populated_dt())
>>> + pr_warn("WARNING: legacy booting deprecated, please update to
>>> boot with .dts\n"
On Wed, Oct 29, 2014 at 06:20:40AM -0700, Guenter Roeck wrote:
> On 10/29/2014 05:34 AM, Johan Hovold wrote:
> > On Tue, Oct 28, 2014 at 03:16:10PM +, Russell King - ARM Linux wrote:
> >> On Tue, Oct 28, 2014 at 02:12:57PM +0100, Johan Hovold wrote:
> >>> That's not what I was trying to refer t
On 10/29/2014 10:33 AM, Roger Quadros wrote:
> On 10/29/2014 01:36 PM, Frans Klaver wrote:
>> On Tue, Oct 28, 2014 at 11:46:57AM +0200, Roger Quadros wrote:
>>> On 10/27/2014 04:34 PM, Frans Klaver wrote:
Since commit 6d178ef2fd5e ("mtd: nand: Move ELM driver and rename as
omap_elm"), I
On 10/29/2014 01:36 PM, Frans Klaver wrote:
> On Tue, Oct 28, 2014 at 11:46:57AM +0200, Roger Quadros wrote:
>> On 10/27/2014 04:34 PM, Frans Klaver wrote:
>>> Since commit 6d178ef2fd5e ("mtd: nand: Move ELM driver and rename as
>>> omap_elm"), I don't have any mtd devices present on my am335x. Thi
On Wed, Oct 29, 2014 at 01:10:20PM +, Russell King - ARM Linux wrote:
> On Wed, Oct 29, 2014 at 01:34:18PM +0100, Johan Hovold wrote:
> > On Tue, Oct 28, 2014 at 03:16:10PM +, Russell King - ARM Linux wrote:
> > > And how is that different from having a set of power-off handlers, and
> > >
On 10/29/2014 05:34 AM, Johan Hovold wrote:
On Tue, Oct 28, 2014 at 03:16:10PM +, Russell King - ARM Linux wrote:
On Tue, Oct 28, 2014 at 02:12:57PM +0100, Johan Hovold wrote:
That's not what I was trying to refer to. But the patch set explicitly
allows for multiple, prioritised power-off h
This just to be sure, nothing more. I did read that you mentionned
"poweroff-source" earlier. However If I am wrong, my bad, everything
is fine.
2014-10-29 14:00 GMT+01:00 Johan Hovold :
> [ Please do not top-post. ]
>
> On Wed, Oct 29, 2014 at 01:55:49PM +0100, Romain Perier wrote:
>> Johan:. do
On Wed, Oct 29, 2014 at 01:34:18PM +0100, Johan Hovold wrote:
> On Tue, Oct 28, 2014 at 03:16:10PM +, Russell King - ARM Linux wrote:
> > And how is that different from having a set of power-off handlers, and
> > reporting when each individual one fails? Don't you want to know if
> > your prim
[ Please do not top-post. ]
On Wed, Oct 29, 2014 at 01:55:49PM +0100, Romain Perier wrote:
> Johan:. do you really plan to use this "poweroff-source" property ? As
> you proposed a renaming few days ago...
> I don't really want to waste time to propose patches to fix things
> incrementally and ren
Johan:. do you really plan to use this "poweroff-source" property ? As
you proposed a renaming few days ago...
I don't really want to waste time to propose patches to fix things
incrementally and rename it if the old one is used...
Romain
2014-10-29 13:34 GMT+01:00 Johan Hovold :
> On Tue, Oct 28
On Tue, Oct 28, 2014 at 09:36:33AM +0100, Johan Hovold wrote:
> On Mon, Oct 27, 2014 at 03:40:31PM -0700, Andrew Morton wrote:
> > On Mon, 27 Oct 2014 09:09:28 +0100 Johan Hovold wrote:
> But in general, how do you want to handle updates to a single patch in a
> series you already have in your tr
On Tue, Oct 28, 2014 at 02:18:05PM -0700, Andrew Morton wrote:
> On Tue, 28 Oct 2014 09:36:33 +0100 Johan Hovold wrote:
>
> > > But it doesn't explain *why* we want the alarm to trigger before
> > > returning.
> >
> > Should we really require every power-off handler to document arch
> > behaviou
On Tue, Oct 28, 2014 at 03:16:10PM +, Russell King - ARM Linux wrote:
> On Tue, Oct 28, 2014 at 02:12:57PM +0100, Johan Hovold wrote:
> > That's not what I was trying to refer to. But the patch set explicitly
> > allows for multiple, prioritised power-off handlers, which can power
> > off a boa
On Tue, Oct 28, 2014 at 11:46:57AM +0200, Roger Quadros wrote:
> On 10/27/2014 04:34 PM, Frans Klaver wrote:
> > Since commit 6d178ef2fd5e ("mtd: nand: Move ELM driver and rename as
> > omap_elm"), I don't have any mtd devices present on my am335x. This
> > changes the link order of the omap_elm an
From: Tomasz Figa
On Exynos SoCs it is necessary to resume operation of L2C early in
assembly code, because otherwise certain systems will crash. This patch
adds necessary code to non-secure resume handler.
Signed-off-by: Tomasz Figa
[rewrote the code accessing l2x0_saved_regs]
Sigend-off-by: M
From: Tomasz Figa
Firmware on certain boards (e.g. ODROID-U3) can leave incorrect L2C prefetch
settings configured in registers leading to crashes if L2C is enabled
without overriding them. This patch introduces bindings to enable
prefetch settings to be specified from DT and necessary support in
From: Tomasz Figa
Certain implementations of secure hypervisors (namely the one found on
Samsung Exynos-based boards) do not provide access to individual L2C
registers. This makes the .write_sec()-based interface insufficient and
provoking ugly hacks.
This patch is first step to make the driver
From: Tomasz Figa
Certain platforms (i.e. Exynos) might need to set .write_sec callback
from firmware initialization which is happenning in .init_early callback
of machine descriptor. However current code will overwrite the pointer
with whatever is present in machine descriptor, even though it ca
From: Tomasz Figa
Because certain secure hypervisor do not allow writes to individual L2C
registers, but rather expect set of parameters to be passed as argument
to secure monitor calls, there is a need to provide an interface for the
L2C driver to ask the firmware to configure the hardware accor
From: Tomasz Figa
Exynos4 SoCs equipped with an L2C-310 cache controller and running under
secure firmware require certain registers of aforementioned IP to be
accessed only from secure mode. This means that SMC calls are required
for certain register writes. To handle this, an implementation of
From: Tomasz Figa
This patch adds device tree nodes for L2 cache controller present on
Exynos4 SoCs.
Signed-off-by: Tomasz Figa
Signed-off-by: Marek Szyprowski
---
arch/arm/boot/dts/exynos4210.dtsi | 9 +
arch/arm/boot/dts/exynos4x12.dtsi | 14 ++
2 files changed, 23 inse
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 only from secure mode.
First four patches extend existing
Warning message about missing/incorrect associativity was a bit too
long, so shorten it to fit a single line.
Suggested-by: Russell King - ARM Linux
Signed-off-by: Marek Szyprowski
---
arch/arm/mm/cache-l2x0.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/arm/mm/c
On 10/29/2014 12:23 AM, Tony Lindgren wrote:
> * Roger Quadros [141021 05:43]:
>> Simplify set_gpmc_timing_reg() and always print error message
>> if the requested timing cannot be achieved due to a too fast
>> GPMC functional clock, irrespective if whether DEBUG is defined
>> or not. This should
Hi!
> > > Here's a patch that should fix the issues for built-in USB
> > > gadgets.
> > >
> > > Pavel, care to see if this gets NFSroot over USB working again
> > > for you?
> >
> > It seems to have did the trick for me. (Plus I needed to add
> >
> > +CONFIG_ARM_ATAG_DTB_COMPAT=y
> > +CONFIG_AR
60 matches
Mail list logo
