On Monday 19 October 2015 08:20 PM, Tony Lindgren wrote:
> Hi,
>
> * Sekhar Nori [151019 02:51]:
>> Under some conditions, irq sorting procedure used by INTC can go wrong
>> resulting in a spurious irq getting reported.
>>
>> This condition is flagged by INTC by setting "Spurious IRQ Flag" in SIR
On Tue, Oct 20, 2015 at 01:24:13AM +0300, Aaro Koskinen wrote:
> On Mon, Oct 19, 2015 at 09:05:22PM +0100, Russell King - ARM Linux wrote:
> > On Mon, Oct 19, 2015 at 10:37:59PM +0300, Aaro Koskinen wrote:
> > > Hi,
> > >
> > > Somewhere between 4.1 .. 4.3-rc6 framebuffer on Nokia 770 stopped work
On Mon, Oct 19, 2015 at 09:05:22PM +0100, Russell King - ARM Linux wrote:
> On Mon, Oct 19, 2015 at 10:37:59PM +0300, Aaro Koskinen wrote:
> > Hi,
> >
> > Somewhere between 4.1 .. 4.3-rc6 framebuffer on Nokia 770 stopped working.
> >
> > Bisection points to:
> >
> > commit 2568999835d7797afce3dc
* Mark Rutland [151019 13:27]:
> On Mon, Oct 19, 2015 at 01:05:33PM -0700, Stephen Boyd wrote:
> > Now that __cpuinit has been removed, the __ref markings on these
> > functions are useless. Remove them. This also reduces the size of
> > the multi_v7_defconfig image:
> >
> > $ size before after
>
On Mon, Oct 19, 2015 at 01:05:33PM -0700, Stephen Boyd wrote:
> Now that __cpuinit has been removed, the __ref markings on these
> functions are useless. Remove them. This also reduces the size of
> the multi_v7_defconfig image:
>
> $ size before after
>textdata bss dec hex fil
Now that __cpuinit has been removed, the __ref markings on these
functions are useless. Remove them. This also reduces the size of
the multi_v7_defconfig image:
$ size before after
textdata bss dec hex filename
126835781470996 348904 14503478 dd4e36 before
On Mon, Oct 19, 2015 at 10:37:59PM +0300, Aaro Koskinen wrote:
> Hi,
>
> Somewhere between 4.1 .. 4.3-rc6 framebuffer on Nokia 770 stopped working.
>
> Bisection points to:
>
> commit 2568999835d7797afce3dcc3a3f368051ffcaf1f
> Author: Russell King
> Date: Mon Mar 2 15:40:29 2015 +
>
>
Hi,
Somewhere between 4.1 .. 4.3-rc6 framebuffer on Nokia 770 stopped working.
Bisection points to:
commit 2568999835d7797afce3dcc3a3f368051ffcaf1f
Author: Russell King
Date: Mon Mar 2 15:40:29 2015 +
clkdev: add clkdev_create() helper
The commit cannot be reverted cleanly from curr
* Keerthy [151014 22:14]:
> Add AM438x compatible property to identify the SoCs on epos evms.
>
> Signed-off-by: Keerthy
> ---
>
> Changes in v2:
>
> * Rebased to latest 4.3-rc5
>
> Documentation/devicetree/bindings/arm/omap/omap.txt | 5 -
> arch/arm/boot/dts/am43x-epos-evm.dts
* Roger Quadros [151014 03:48]:
> Let's keep the SSI ports disabled in the omap3.dtsi to avoid
> getting the following noise on the console for boards that don't
> use the SSI ports.
>
> "omap_ssi_port 4805a000.ssi-port: DT data is missing cawake gpio (err=-2)"
>
> As omap3-n900 uses one SSI por
* Lokesh Vutla [151019 07:03]:
>
> Since there is a big hole with in the memory space, we might also need
> to enable SPARSEMEM ?
No from what I remember that depends on section sizes and smaller
chunks of physical memory. For example, on the old Psions we had to
use DISCONTIGMEM/SPARSEMEM becau
Use the OMAP3 pinmux IOPAD macro to define the physical address instead
of the offset from the padconf address. It makes the DTS easier to read
since matches the addresses listed in the Technical Reference Manual.
Signed-off-by: Javier Martinez Canillas
---
arch/arm/boot/dts/omap3-igep0020-comm
Hello,
This series use the IOPAD pinmux macros for the remaining IGEP boards that
still used the register offset instead of the physical address using these
macros so the DTS matches what is in the Technical Reference Manual.
The changes are only cosmetic since they make the DTS easier to read bu
Use the AM33XX pinmux IOPAD macro to define the physical address instead
of the offset from the padconf address. It makes the DTS easier to read
since matches the addresses listed in the Technical Reference Manual.
Signed-off-by: Javier Martinez Canillas
---
arch/arm/boot/dts/am335x-base0033.d
Use the AM33xx pinmux IOPAD macro to define the physical address instead
of the offset from the padconf address. It makes the DTS easier to read
since matches the addresses listed in the Technical Reference Manual.
Signed-off-by: Javier Martinez Canillas
---
arch/arm/boot/dts/am335x-igep0033.dt
In order to set the currently platform dependent dmtimer
functions pointers as platform data for the pwm-omap-dmtimer
platform driver, add it to plat-omap auxdata_lookup table.
Suggested-by: Tony Lindgren
Signed-off-by: Neil Armstrong
---
arch/arm/mach-omap2/pdata-quirks.c | 23
This patch is based on an earlier patch by NeilBrown which is based on
a older patch from Grant Erickson which provided PWM devices using
the 'legacy' interface.
The pwm driver was renamed to not be confused with the OMAP4 PWM dedicated
hardware and was cleaned with the review from Thierry Reding.
Adds support for using a OMAP dual-mode timer with PWM capability
as a Linux PWM device. The driver controls the timer by using the
dmtimer API.
Add a platform_data structure for each pwm-omap-dmtimer nodes containing
the dmtimers functions in order to get driver not rely on platform
specific func
Add a function which sets the timer source from the clocks
binding on dm_timer_prepare call.
In case the clocks property is not valid, it falls back to
the set_source() with 32_KHZ clock as default.
Suggested-by: Tony Lindgren
Signed-off-by: Neil Armstrong
---
arch/arm/plat-omap/dmtimer.c | 31
Hi,
* Sekhar Nori [151019 02:51]:
> Under some conditions, irq sorting procedure used by INTC can go wrong
> resulting in a spurious irq getting reported.
>
> This condition is flagged by INTC by setting "Spurious IRQ Flag" in SIR
> register to 0x1ff. Section 6.2.5 of AM335x TRM revised Jun
* Pau Pajuel [151019 06:40]:
> Hi Tony,
> 2015-10-16 16:57 GMT+02:00 Tony Lindgren :
> > >
> > > So far I've tested that basic things work, such as serial, USB
> > > Ethernet, HDMI and WLAN.
Also mSATA works too BTW.
> I am testing your patch without succes. Which u-boot version are you using?
On Saturday 17 October 2015 12:53 AM, Tony Lindgren wrote:
> * Lokesh Vutla [151015 08:21]:
[..snip..]
>>>
>
> 8< --From c37732f6cea23d15fa357cf698833c03ce05 Mon
> Sep 17 00:00:00 2001
> Date: Fri, 16 Oct 2015 12:16:21 -0700
> Subject: [PATCH] ARM: OMAP2+: Fix oops wi
Hi,
On 10/16/2015 05:40 PM, Felipe Balbi wrote:
>> +static int omap_dm_timer_of_set_source(struct omap_dm_timer *timer)
>> +{
>> +int ret;
>> +struct clk *parent;
>> +
>> +if (unlikely(!timer))
>> +return -EINVAL;
>
> IMO, let this crash. If this happens we have bigger pro
Am Donnerstag, den 15.10.2015, 16:32 +0100 schrieb Russell King - ARM
Linux:
> On Thu, Oct 15, 2015 at 12:32:20PM +0200, Lucas Stach wrote:
> > Install a non-faulting handler just before unmasking imprecise aborts
> > and switch back to the regular one after unmasking is done.
> >
> > This catches
Am 19.10.2015 um 13:57 schrieb Lars-Peter Clausen :
> On 10/16/2015 02:53 PM, H. Nikolaus Schaller wrote:
> [...]
>> +Optional sub-nodes:
>> +ti,channel0-current-microamp: Channel 0 current in uA.
>> +Values are rounded to derive 0uA, 5uA, 15uA, 20uA.
>> +ti,channel3-current-microamp: Channel
On 10/16/2015 02:53 PM, H. Nikolaus Schaller wrote:
[...]
> +Optional sub-nodes:
> +ti,channel0-current-microamp: Channel 0 current in uA.
> + Values are rounded to derive 0uA, 5uA, 15uA, 20uA.
> +ti,channel3-current-microamp: Channel 3 current in uA.
> + Valid are rounded to derive 0uA, 10
Hi,
During N900 boot I get the trace found below. The problem can be
seen in omap3_rom_rng_idle(), which is called by a kernel timer
(=softirq). In that function you call clk_disable_unprepare(), which
must not be called from atomic context, since clk_unprepare() may
sleep.
[1.885131] ---
On Mon, 19 Oct 2015, Sekhar Nori wrote:
> + /*
> + * A spurious IRQ can result if interrupt that triggered the
> + * sorting is no longer active during the sorting (10 INTC
> + * functional clock cycles after interrupt assertion). Or a
> + * change in interrupt mask affected
Under some conditions, irq sorting procedure used by INTC can go wrong
resulting in a spurious irq getting reported.
This condition is flagged by INTC by setting "Spurious IRQ Flag" in SIR
register to 0x1ff. Section 6.2.5 of AM335x TRM revised Jun 2014
describes this.
Using IRQ number 0 for c
On 10/19/2015 09:27 AM, Heiko Schocher wrote:
>>> .../devicetree/bindings/net/can/ti_hecc-can.txt| 20 ++
>>> arch/arm/boot/dts/am3517.dtsi | 13 +++
>>> drivers/net/can/ti_hecc.c | 45
>>> +-
>>> 3 files change
Hello Marc,
Am 19.10.2015 um 08:58 schrieb Marc Kleine-Budde:
On 10/19/2015 08:39 AM, Heiko Schocher wrote:
add DT support for the ti hecc controller, used on
am3517 SoCs.
A similar patch was posted a few days ago, see
http://comments.gmane.org/gmane.linux.can/8616 and my comments.
Uh, sorr
On 17/10/15 00:25, Tony Lindgren wrote:
> * Roger Quadros [151006 04:13]:
>>
>> Fine. The updated series is now at
>>
>> g...@github.com:rogerq/linux.git
>> * [new branch] for-v4.4/gpmc-v4
>
> Looks like it produces some build errors, this with RMKs 3430 and 4430
> only .configs:
>
> drive
32 matches
Mail list logo