On 12/28/2015 09:18 AM, Dave Young wrote:
> On 12/27/15 at 03:38pm, Dave Young wrote:
>> Here is what I get when I test kdump on Beagle bone black:
>>
>> Added a printk line at the begin of function omap_gpio_rmw:
>> printk("## %lx, %x, %x\n", base, reg, mask);
>>
>> Any hints how to fix
On 12/27/2015 07:14 PM, Uri Mashiach wrote:
> Hello Grygorii,
>
> On 12/24/2015 06:32 PM, Grygorii Strashko wrote:
>> On 12/24/2015 05:35 PM, Uri Mashiach wrote:
>>> The power function uses a consumer regulator access to update the WiFi
>>> enable GPIO value.
&g
for ARM TWD and Global timers.
Signed-off-by: Grygorii Strashko <grygorii.stras...@ti.com>
---
arch/arm/boot/dts/am4372.dtsi | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/arm/boot/dts/am4372.dtsi b/arch/arm/boot/dts/am4372.dtsi
index de8791a..dfa1a29 100644
--- a/ar
declaration for pixcir_ts@5c node
in am437x-gp-evm.dts.
Signed-off-by: Grygorii Strashko <grygorii.stras...@ti.com>
---
arch/arm/boot/dts/am437x-gp-evm.dts | 4 +---
arch/arm/boot/dts/am43x-epos-evm.dts | 2 +-
2 files changed, 2 insertions(+), 4 deletions(-)
diff --git a/arch/arm/boot/dts/
On 12/24/2015 05:35 PM, Uri Mashiach wrote:
> Add DT support for the wl1271 SPI WiFi.
>
> Add documentation file for the wl1271 SPI WiFi.
>
> Signed-off-by: Uri Mashiach
> Acked-by: Igor Grinberg
> ---
> v1 -> v2: update interrupt
On 12/24/2015 05:35 PM, Uri Mashiach wrote:
The power function uses a consumer regulator access to update the WiFi
enable GPIO value.
Signed-off-by: Uri Mashiach
---
v1 -> v2: oops fix was removed to a separate fix.
drivers/net/wireless/ti/wlcore/spi.c | 37
On 12/23/2015 10:35 AM, Uri Mashiach wrote:
> The power function uses a consumer regulator access to update the WiFi
> enable GPIO value.
>
> Fix the below Oops when trying to modprobe wlcore_spi.
> The oops occurs because the wl1271_power_{off,on}()
> function doesn't check the power() function
On 12/23/2015 10:35 AM, Uri Mashiach wrote:
> Add DT support for the wl1271 SPI WiFi.
>
> Add documentation file for the wl1271 SPI WiFi.
>
> Signed-off-by: Uri Mashiach
> Acked-by: Igor Grinberg
> ---
>
On 12/17/2015 12:48 PM, Jon Hunter wrote:
> Some IRQ chips, such as GPIO controllers or secondary level interrupt
> controllers, may require require additional runtime power management
> control to ensure they are accessible. For such IRQ chips, it makes sense
> to enable the IRQ chip when
Hi All,
On 11/30/2015 08:25 PM, Grygorii Strashko wrote:
> Now the System stall is observed on TI AM437x based board
> (am437x-gp-evm) during resuming from System suspend when ARM Global
> timer is selected as clocksource device (CPUIdle not enabled) - SysRq are
> working,
> b
]
http://lists.infradead.org/pipermail/linux-arm-kernel/2015-August/363989.html
[2] http://www.spinics.net/lists/linux-omap/msg123940.html
Felipe Balbi (1):
arm: omap2: AM43xx: select ARM TWD timer
Grygorii Strashko (1):
ARM: OMAP: am43xx: enable GENERIC_CLOCKEVENTS_BROADCAST
arch/arm/mach
GENERIC_CLOCKEVENTS_BROADCAST option for
AM43XX SoCs always and add empty tick_broadcast() function
implementation - no need to send any IPI on UP. After this change
timer1 will be selected as broadcast timer the same way as for SMP,
and CPUIdle will work properly.
Signed-off-by: Grygorii Strashko
fe to enable
it unconditionally]
Signed-off-by: Grygorii Strashko <grygorii.stras...@ti.com>
---
v1: http://www.spinics.net/lists/arm-kernel/msg459649.html
arch/arm/mach-omap2/Kconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/mach-omap2/Kconfig b/arch/arm/mach-omap2/Kconfig
inde
On 12/11/2015 06:57 PM, Sebastian Andrzej Siewior wrote:
* Grygorii Strashko | 2015-10-15 19:33:43 [+0300]:
Hi Thomas,
On 10/13/2015 09:33 PM, Thomas Gleixner wrote:
Grygorii,
On Tue, 13 Oct 2015, Grygorii Strashko wrote:
I'd very appreciate for any advice of how to better proceed
:
omap2_gptimer_clocksource_init
->BUG_ON(res);
This happens because clk_dev alias "sys_clkin_ck" is not registered.
Hence, fix it by adding missing "sys_clkin_ck" clk_dev aliases
definitions for omap5 and dra7.
Cc: Tero Kristo <t-kri...@ti.com>
Cc: Tony Lindgren <t...@atom
rg>
Cc: Alexandre Courbot <gnu...@gmail.com>
Cc: Simon Horman <ho...@verge.net.au>
Cc: Pratyush Anand <pratyush.an...@gmail.com>
Cc: Michal Simek <michal.si...@xilinx.com>
Cc: "Sören Brinkmann" <soren.brinkm...@xilinx.com>
Cc: Sebastian Andrzej Siewi
On 12/09/2015 05:24 PM, Bjorn Helgaas wrote:
On Tue, Dec 08, 2015 at 10:05:56AM +0100, Sebastian Andrzej Siewior wrote:
* Bjorn Helgaas | 2015-12-04 12:46:19 [-0600]:
The backtrace might be OK (maybe slightly overkill), but all the
stack addresses are certainly irrelevant and distracting. We
Hi Tony, Felipe, Tero,
On 12/03/2015 08:04 PM, Grygorii Strashko wrote:
On 12/03/2015 06:35 PM, Tony Lindgren wrote:
* Grygorii Strashko <grygorii.stras...@ti.com> [151130 07:58]:
ARM TWD and Global timer are clocked by PERIPHCLK which is MPU_CLK/2.
But now they are clocked by dpll_mpu
On 12/03/2015 11:37 PM, Tony Lindgren wrote:
* Grygorii Strashko <grygorii.stras...@ti.com> [151203 10:36]:
I think, this patch should not break our wake-up functionality.
It will just change the moment when pcs_irq_handler() will be called:
before this change:
- suspend
On 12/04/2015 12:54 PM, Sudeep Holla wrote:
> Hi Grygorii,
>
> On 04/12/15 10:44, Grygorii Strashko wrote:
>> On 12/03/2015 11:37 PM, Tony Lindgren wrote:
>
> [...]
>
>>> And these both need to be applied together when we have a fix for the
>>>
On 12/04/2015 05:35 PM, Tony Lindgren wrote:
> * Grygorii Strashko <grygorii.stras...@ti.com> [151204 02:45]:
>> On 12/03/2015 11:37 PM, Tony Lindgren wrote:
>>> * Grygorii Strashko <grygorii.stras...@ti.com> [151203 10:36]:
>>>>
>>>> I think,
On 12/04/2015 05:44 PM, Sudeep Holla wrote:
>
>
> On 04/12/15 15:40, Tony Lindgren wrote:
>> * Tony Lindgren [151203 13:41]:
>>> * Sudeep Holla [151203 11:00]:
I have added irq_set_irq_wake(pcs_soc->irq, state) in pcs_irq_set_wake
which
On 12/04/2015 06:11 PM, Sudeep Holla wrote:
>
>
> On 04/12/15 15:59, Grygorii Strashko wrote:
>>
>> Sorry, I can't test it right now :(
>> Potential fix below:
>
> I had posted similar patch a while ago which Tony rejected.
> I might have made a mistake
On 12/04/2015 08:46 PM, Bjorn Helgaas wrote:
> Hi Grygorii,
>
> On Fri, Nov 20, 2015 at 03:59:26PM +0200, Grygorii Strashko wrote:
>> On -RT, TI DRA7 PCIe driver always produces below backtrace when the
>> first PCI interrupt is triggered:
>>
>> [
On 12/03/2015 06:00 PM, Tony Lindgren wrote:
> * Tony Lindgren [151130 08:29]:
>> We want to be able to probe a few selected device drivers before hwmod
>> code populates the clocks in omap_hwmod_setup_all(). This allows us to
>> convert most of the clock drivers into regular
On 12/03/2015 06:35 PM, Tony Lindgren wrote:
> * Grygorii Strashko <grygorii.stras...@ti.com> [151130 07:58]:
>> ARM TWD and Global timer are clocked by PERIPHCLK which is MPU_CLK/2.
>> But now they are clocked by dpll_mpu_m2_ck == MPU_CLK and, as result.
>>
On 12/02/2015 01:38 AM, Tony Lindgren wrote:
> Hi all,
>
> Here are some fixes for v4.5 merge window to get dm814x-evm booting.
> While hp t410 boots based on the bootloader clocks, dm814x-evm needs
> more things configured. Especially the clock dts entries were all
> wrong and just happened to
On 12/03/2015 06:37 PM, Tony Lindgren wrote:
> * Tony Lindgren [151203 08:34]:
>>
>> It seems we should apply this as a fix unless somebody has better ideas.
>
> Actually I think the fix for now is "[4.4-rc][PATCH v2] ARM: dts: am4372: fix
> clock source for arm twd and global
On 12/03/2015 08:13 PM, Tony Lindgren wrote:
> * Linus Walleij [151201 06:07]:
>> On Fri, Nov 27, 2015 at 6:21 PM, Sudeep Holla wrote:
>>
>>> From: Sudeep Holla
>>>
>>> The IRQF_NO_SUSPEND flag is used to identify the
On 12/03/2015 06:41 PM, Tony Lindgren wrote:
> * Grygorii Strashko <grygorii.stras...@ti.com> [151203 08:35]:
>> On 12/03/2015 06:00 PM, Tony Lindgren wrote:
>>> * Tony Lindgren <t...@atomide.com> [151130 08:29]:
>>>> We want to be able to probe a few sele
On 12/01/2015 06:07 PM, Tony Lindgren wrote:
* Grygorii Strashko <grygorii.stras...@ti.com> [151201 07:09]:
On 11/30/2015 06:28 PM, Tony Lindgren wrote:
We should be able to make this into an early_platform_device and just
have it depend on the source clock muxes. See the omap in
Hi Tony,
On 11/30/2015 06:28 PM, Tony Lindgren wrote:
> * Grygorii Strashko <grygorii.stras...@ti.com> [151127 12:11]:
>> On 11/20/2015 08:21 PM, Felipe Balbi wrote:
>>> Grygorii Strashko <grygorii.stras...@ti.com> writes:
>>>> Since system clocksour
lipe Balbi <ba...@ti.com>
> Cc: Grygorii Strashko <grygorii.stras...@ti.com>
> Cc: Paul Walmsley <p...@pwsan.com>
> Cc: Tero Kristo <t-kri...@ti.com>
> Signed-off-by: Tony Lindgren <t...@atomide.com>
> ---
> arch/arm/mach-omap2/timer.c | 46
>
ot;fixed-factor-clock") and use
it for clocking ARM TWD and Global timer (same way as on OMAP4).
Cc: Tony Lindgren <t...@atomide.com>
Cc: Felipe Balbi <ba...@ti.com>
Cc: Tero Kristo <t-kri...@ti.com>
Fixes:commit 8cbd4c2f6a99 ("arm: boot: dts: am4372: add ARM time
On 11/30/2015 07:27 PM, Lucas Stach wrote:
> Am Montag, den 16.11.2015, 14:24 +0200 schrieb Grygorii Strashko:
>> On 11/16/2015 01:25 PM, Lucas Stach wrote:
>>> omap_interconnect_sync() is the only user of the SRAM scratch area
>>> allocated in the omap4_sram_init init
;john.stu...@linaro.org>
Cc: Felipe Balbi <ba...@ti.com>
Cc: Tony Lindgren <t...@atomide.com>
Cc: Marc Zyngier <marc.zyng...@arm.com>
Reviewed-by: Santosh Shilimkar <ssant...@kernel.org>
Signed-off-by: Grygorii Strashko <grygorii.stras...@ti.com>
---
Changes in v4:
- c
On 11/30/2015 02:29 AM, santosh.shilim...@oracle.com wrote:
On 11/27/15 11:47 AM, Grygorii Strashko wrote:
Now the System stall is observed on TI AM437x based board
(am437x-gp-evm) during resuming from System suspend when ARM Global
timer is selected as clocksource device (CPUIdle not enabled
On 11/30/2015 10:25 AM, Tero Kristo wrote:
On 11/27/2015 09:44 PM, Grygorii Strashko wrote:
ARM TWD and Global timer are clocked by PERIPHCLK which is MPU_CLK/2.
But now they are clocked by dpll_mpu_m2_ck == MPU_CLK and, as result.
Timekeeping core misbehaves. For example, execution of command
On 11/30/2015 03:32 PM, Tero Kristo wrote:
> On 11/30/2015 01:53 PM, Grygorii Strashko wrote:
>> On 11/30/2015 10:25 AM, Tero Kristo wrote:
>>> On 11/27/2015 09:44 PM, Grygorii Strashko wrote:
>>>> ARM TWD and Global timer are clocked by PERIPHCLK which is MPU_CLK/2.
;
Cc: Felipe Balbi <ba...@ti.com>
Cc: Tony Lindgren <t...@atomide.com>
Cc: Santosh Shilimkar <ssant...@kernel.org>
Cc: Marc Zyngier <marc.zyng...@arm.com>
Signed-off-by: Grygorii Strashko <grygorii.stras...@ti.com>
---
Changes in v3:
- dropped all DT specific code
C
ot;fixed-factor-clock") and use
it for clocking ARM TWD and Global timer (same way as on OMAP4).
Cc: Tony Lindgren <t...@atomide.com>
Cc: Felipe Balbi <ba...@ti.com>
Cc: Tero Kristo <t-kri...@ti.com>
Fixes:commit 8cbd4c2f6a99 ("arm: boot: dts: am4372: add ARM time
Hi Felipe,
On 11/20/2015 08:21 PM, Felipe Balbi wrote:
> Grygorii Strashko <grygorii.stras...@ti.com> writes:
>> Since system clocksource is finally selected by Clocksource core at
>> fs_initcall stage during boot there are no reasons to initialize
>> ti_32k_timer
Enable REGULATOR_FIXED_VOLTAGE for all OMAP2+ platforms
otherwise system can't boot from SD-card when kernel is
built for single SoC (for example, with CONFIG_SOC_DRA7XX=y only).
It's also required for almost all TI SoC's platforms.
Signed-off-by: Grygorii Strashko <grygorii.stras...@ti.
On 11/25/2015 10:57 PM, Tony Lindgren wrote:
* Grygorii Strashko <grygorii.stras...@ti.com> [151125 12:26]:
On 11/25/2015 08:25 PM, Tony Lindgren wrote:
* Grygorii Strashko <grygorii.stras...@ti.com> [151105 08:45]:
Enable REGULATOR_FIXED_VOLTAGE otherwise system can't boot from
On 11/25/2015 08:25 PM, Tony Lindgren wrote:
> * Grygorii Strashko <grygorii.stras...@ti.com> [151105 08:45]:
>> Enable REGULATOR_FIXED_VOLTAGE otherwise system can't boot from
>> SD-card when kernel is buit with CONFIG_SOC_DRA7XX=y only.
>>
>> It's also requi
assumption. And recommended fix for
this issue is to request dra7xx_pcie_msi IRQ with IRQF_NO_THREAD flag.
[1] https://lkml.org/lkml/2015/11/3/660
Cc: Thomas Gleixner <t...@linutronix.de>
Cc: Sebastian Andrzej Siewior <bige...@linutronix.de>
Signed-off-by: Grygorii Strashko <
t;t...@atomide.com>
Cc: Santosh Shilimkar <ssant...@kernel.org>
Signed-off-by: Grygorii Strashko <grygorii.stras...@ti.com>
---
Changes in v2:
- suspend/resume simplified: nothing is stored any more and
ARM GT just re-enabled
Link on v1:
https://lkml.org/lkml/2015/11/13/456
t;)
Reported-by: Aaro Koskinen <aaro.koski...@iki.fi>
Signed-off-by: Grygorii Strashko <grygorii.stras...@ti.com>
---
drivers/gpio/gpio-omap.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/drivers/gpio/gpio-omap.c b/drivers/gpio/gpio-omap.c
index 56d2d02..f7fbb46 100644
--- a/d
to DT.
Cc: Tony Lindgren <t...@atomide.com>
Cc: Felipe Balbi <ba...@ti.com>
Signed-off-by: Grygorii Strashko <grygorii.stras...@ti.com>
---
arch/arm/mach-omap2/timer.c| 16 +++
drivers/clocksource/timer-ti-32k.c | 58 --
2
Hi Santosh,
On 11/20/2015 07:23 PM, santosh shilimkar wrote:
> + Thomas, Marc
>
> On 11/20/2015 5:57 AM, Grygorii Strashko wrote:
>> Now the System stall is observed on TI AM437x based board
>> (am437x-gp-evm) during resuming from System suspend when ARM Global
On 11/20/2015 09:09 PM, John Stultz wrote:
> On Fri, Nov 20, 2015 at 10:35 AM, Grygorii Strashko
> <grygorii.stras...@ti.com> wrote:
>> Hi Santosh,
>>
>> On 11/20/2015 07:23 PM, santosh shilimkar wrote:
>>> + Thomas, Marc
>>>
>>> On 11/20/2
On 11/20/2015 08:52 PM, santosh shilimkar wrote:
> On 11/20/2015 10:46 AM, Marc Zyngier wrote:
>> On 20/11/15 18:35, Grygorii Strashko wrote:
>>> Hi Santosh,
>>>
>>> On 11/20/2015 07:23 PM, santosh shilimkar wrote:
>>>> + Thomas, Marc
>>
On 11/20/2015 09:32 PM, John Stultz wrote:
> On Fri, Nov 20, 2015 at 11:28 AM, Grygorii Strashko
> <grygorii.stras...@ti.com> wrote:
>> On 11/20/2015 09:09 PM, John Stultz wrote:
>>> On Fri, Nov 20, 2015 at 10:35 AM, Grygorii Strashko
>>> <grygorii.
On 11/18/2015 08:31 PM, Aaro Koskinen wrote:
> Hi,
>
> On Wed, Nov 18, 2015 at 02:58:38PM +0200, Grygorii Strashko wrote:
>> On 11/17/2015 11:42 PM, Aaro Koskinen wrote:
>>> Amstrad E3 computer (OMAP1) boot crashes early
Hi Mark,
On 11/18/2015 04:15 PM, Mark Rutland wrote:
> On Wed, Nov 18, 2015 at 04:01:55PM +0200, Grygorii Strashko wrote:
>> Keep ARM TWD and Global timer's nodes disabled by default - if someone
>> would like to use them then those nodes have to be enabled explicitly
&
Hi Aaro,
On 11/17/2015 11:42 PM, Aaro Koskinen wrote:
Amstrad E3 computer (OMAP1) boot crashes early with v4.4-rc1. Bisected to:
450fa54cfd66e3dda6eda26256637ee8928af12a is the first bad commit
commit 450fa54cfd66e3dda6eda26256637ee8928af12a
Author: Grygorii Strashko
On 11/13/2015 06:39 PM, santosh shilimkar wrote:
> On 11/13/2015 5:07 AM, Mason wrote:
>> On 13/11/2015 13:48, Grygorii Strashko wrote:
>>> On 11/12/2015 08:06 PM, Felipe Balbi wrote:
>>>> Make sure to tell the kernel that AM437x has
>>>> TWD and glob
g>
Signed-off-by: Grygorii Strashko <grygorii.stras...@ti.com>
---
arch/arm/boot/dts/am4372.dtsi | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arm/boot/dts/am4372.dtsi b/arch/arm/boot/dts/am4372.dtsi
index d83ff9c..11376e3 100644
--- a/arch/arm/boot/dts/am4372.dtsi
+++ b
On 11/16/2015 01:25 PM, Lucas Stach wrote:
> omap_interconnect_sync() is the only user of the SRAM scratch area
> allocated in the omap4_sram_init initcall. The interconnect sync is
> used exclusively in the OMAP4 specific WFI implementation, so there
> is no point in allocating the SRAM scratch
SyS_write) from [] (ret_fast_syscall+0x0/0x54)
CPU1: smp_ops.cpu_die() returned, trying to resuscitate
Cc: Tero Kristo <t-kri...@ti.com>
Signed-off-by: Grygorii Strashko <grygorii.stras...@ti.com>
---
arch/arm/mach-omap2/omap-smp.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletion
On 11/13/2015 06:43 PM, Felipe Balbi wrote:
>
> Hi,
>
> Grygorii Strashko <grygorii.stras...@ti.com> writes:
>> Now the System stall is observed on TI AM437x based board
>> (am437x-gp-evm) during resuming from System suspend when ARM Global
>> timer is se
On 11/13/2015 02:48 PM, Grygorii Strashko wrote:
> On 11/12/2015 08:06 PM, Felipe Balbi wrote:
>> Make sure to tell the kernel that AM437x has
>> TWD and global timers.
>>
>> Signed-off-by: Felipe Balbi <ba...@ti.com>
>> ---
>>
>> Hi Tony,
&
lt;t...@atomide.com>
Signed-off-by: Grygorii Strashko <grygorii.stras...@ti.com>
---
drivers/clocksource/arm_global_timer.c | 23 +++
1 file changed, 23 insertions(+)
diff --git a/drivers/clocksource/arm_global_timer.c
b/drivers/clocksource/arm_global_timer.c
ind
Hi Felipe,
On 11/13/2015 08:59 PM, Grygorii Strashko wrote:
> On 11/13/2015 08:32 PM, Felipe Balbi wrote:
>> Grygorii Strashko <grygorii.stras...@ti.com> writes:
>>> On 11/13/2015 08:15 PM, Felipe Balbi wrote:
>>>> Grygorii Strashko <grygorii.stras...@ti.co
On 11/13/2015 07:40 PM, Felipe Balbi wrote:
Hi,
Grygorii Strashko <grygorii.stras...@ti.com> writes:
On 11/13/2015 06:43 PM, Felipe Balbi wrote:
Hi,
Grygorii Strashko <grygorii.stras...@ti.com> writes:
Now the System stall is observed on TI AM437x based board
(am437x-gp
On 11/13/2015 08:15 PM, Felipe Balbi wrote:
Hi,
Grygorii Strashko <grygorii.stras...@ti.com> writes:
On 11/13/2015 07:40 PM, Felipe Balbi wrote:
Hi,
Grygorii Strashko <grygorii.stras...@ti.com> writes:
On 11/13/2015 06:43 PM, Felipe Balbi wrote:
Hi,
Grygorii Strashko <
On 11/13/2015 08:32 PM, Felipe Balbi wrote:
>
> Hi,
>
> Grygorii Strashko <grygorii.stras...@ti.com> writes:
>> On 11/13/2015 08:15 PM, Felipe Balbi wrote:
>>>
>>> Hi,
>>>
>>> Grygorii Strashko <grygorii.stras...@ti.com> write
On 11/12/2015 11:19 AM, Sebastian Andrzej Siewior wrote:
> On 11/06/2015 08:59 PM, Grygorii Strashko wrote:
>> Hi Sebastian,
>
> Hi Grygorii,
>
>> - IRQF_NO_THREAD is the first considered option for such kind of issues.
>>But: Now in LKML there are ~60 occurr
On 11/12/2015 08:06 PM, Felipe Balbi wrote:
> Make sure to tell the kernel that AM437x has
> TWD and global timers.
>
> Signed-off-by: Felipe Balbi
> ---
>
> Hi Tony,
>
> now that all dependencies are in place, we can
> finally enable twd and global_timer for AM437x.
>
I'd
On 11/12/2015 08:09 PM, Felipe Balbi wrote:
Hi,
Grygorii Strashko <grygorii.stras...@ti.com> writes:
On 11/12/2015 07:50 PM, Felipe Balbi wrote:
According to TRM, debounce is measured in periods of
the functional clock of the GPIO IP. This means that
What TRM? link pls.
http://www.
On 11/12/2015 07:50 PM, Felipe Balbi wrote:
> According to TRM, debounce is measured in periods of
> the functional clock of the GPIO IP. This means that
What TRM? link pls.
http://www.ti.com/lit/ug/spruhl7d/spruhl7d.pdf
28.4.1.24 GPIO_DEBOUNCINGTIME Register (offset = 154h) [reset = 0h]
The
>
Fixes: e509bd7da149 ("genirq: Allow migration of chained interrupts..")
Signed-off-by: Grygorii Strashko <grygorii.stras...@ti.com>
---
kernel/irq/internals.h | 5 +
kernel/irq/pm.c| 3 ++-
kernel/irq/proc.c | 2 +-
3 files changed, 8 insertions(+), 2 deleti
On 11/06/2015 12:15 AM, Aaro Koskinen wrote:
We cannot put the HW RNG to idle using a timer because we cannot disable
clocks from atomic context. Use a delayed work instead.
Fixes a warning with CONFIG_DEBUG_MUTEXES on Nokia N900 during boot.
Reported-by: Sebastian Reichel
Hi Sebastian,
On 11/06/2015 10:53 AM, Sebastian Andrzej Siewior wrote:
> On 11/05/2015 07:43 PM, Grygorii Strashko wrote:
>> diff --git a/drivers/pci/host/pci-dra7xx.c b/drivers/pci/host/pci-dra7xx.c
>> index 6589e7e..31460f4 100644
>> --- a/drivers/pci/host/pci-dra7xx.c
>
Enable REGULATOR_FIXED_VOLTAGE otherwise system can't boot from
SD-card when kernel is buit with CONFIG_SOC_DRA7XX=y only.
It's also required for almost all other TI SoC's platforms.
Signed-off-by: Grygorii Strashko <grygorii.stras...@ti.com>
---
arch/arm/configs/omap2plus_defconfig |
assumption. And recommended fix for
this issue is to request dra7xx_pcie_msi IRQ with IRQF_NO_THREAD flag.
[1] https://lkml.org/lkml/2015/11/3/660
Cc: Thomas Gleixner <t...@linutronix.de>
Cc: Sebastian Andrzej Siewior <bige...@linutronix.de>
Signed-off-by: Grygorii Strashko <
On 11/02/2015 05:20 PM, Felipe Balbi wrote:
> Grygorii Strashko <grygorii.stras...@ti.com> writes:
>
>> On 10/29/2015 03:57 PM, Felipe Balbi wrote:
>>> there's no need to call pm_runtime_get_sync()
>>> followed by pm_runtime_put(). We should, instea
On 10/29/2015 03:57 PM, Felipe Balbi wrote:
there's no need to call pm_runtime_get_sync()
followed by pm_runtime_put(). We should, instead,
just call pm_runtime_put_sync() and pm_runtime_disable().
Sry, but why do we need to call pm_runtime_put[_sync]() here?
My be just pm_runtime_disable()
On 11/02/2015 06:06 PM, Felipe Balbi wrote:
>
> hi,
>
> Grygorii Strashko <grygorii.stras...@ti.com> writes:
>> On 11/02/2015 05:20 PM, Felipe Balbi wrote:
>>> Grygorii Strashko <grygorii.stras...@ti.com> writes:
>>>
>>>> On 10/29/2015
On 10/26/2015 03:58 PM, Adam Ford wrote:
Gigi,
I am working on modifying the DTS and DTSI files for the LogicPD Torpedo which
Tony added in Kernel 4.2
There was a flurry of activity earlier this year regarding device tree bindings
for the shared transport and using the Bluetooth with it as
MUSB omap2430 interface as the
>> runtime PM for the parent device needs the child initialized to access
>> the MUSB hardware registers.
>>
>> Let's delay the enabling of PM runtime for the parent until the child
>> has been properly initialized as suggested in an earlier
On 10/23/2015 02:01 AM, Tony Lindgren wrote:
* Tony Lindgren [151022 11:03]:
* Tony Lindgren [151021 16:44]:
Hi all,
I noticed a regresssino in v4.3-rc series to day with MUSB gadgets
and DMA. Doing a git bisect between v4.2..v4.3-rc1 on it pointed to:
There is no reasons to probe cpsw from late_initcall level
and it's not recommended. Hence, use module_platform_driver()
to register and probe cpsw driver from module_init() level.
Cc: Tony Lindgren <t...@atomide.com>
Acked-by: Mugunthan V N <mugunthan...@ti.com>
Signed-off-by: Grygo
On 10/01/2015 10:20 PM, Grygorii Strashko wrote:
TI's mux and divider clock drivers do not require locking and they do
not initialize internal spinlocks. This code was occasionally
copy-posted from generic mux/divider drivers. So remove it.
Cc: Tony Lindgren <t...@atomide.com>
Cc: Sekha
Hi Thomas,
On 10/13/2015 09:33 PM, Thomas Gleixner wrote:
Grygorii,
On Tue, 13 Oct 2015, Grygorii Strashko wrote:
I'd very appreciate for any advice of how to better proceed with your request.
- I can try to apply and re-send only patches marked by '*'
- I can prepare branch with all
Hi Thomas,
On 10/12/2015 10:52 AM, Thomas Gleixner wrote:
> Grygorii,
>
> can you please provide a patch set against 4.1-RT? That stuff rejects
> left and right.
>
This is really not easy thing to do :( and I don't know how to do it the best
way.
This patches are based on top of big set of
On 10/12/2015 04:12 PM, Ladislav Michl wrote:
> On Fri, Oct 09, 2015 at 11:45:17AM +0200, Rolf Peukert wrote:
>> On 09.10.2015 02:54, Ladislav Michl wrote:
>>> Hi there!
>>>
>>> on custom AM37x board running 2.6.37 this was enough to enable gpio 67:
>>> echo 71 > /sys/class/gpio/export
>>> echo
undefined!
This patch exports the handle_bad_irq symbol in order to
allow the use in modules.
Thanks for fixing it and sorry for the mess.
Tested-by: Grygorii Strashko <grygorii.stras...@ti.com>
Signed-off-by: Arnd Bergmann <a...@arndb.de>
Fixes: 450fa54cfd66 ("gpio: omap:
On 10/02/2015 03:17 PM, Linus Walleij wrote:
On Fri, Sep 25, 2015 at 12:28 PM, Grygorii Strashko
<grygorii.stras...@ti.com> wrote:
This patch converts TI OMAP GPIO driver to use generic irq handler
instead of chained IRQ handler. This way OMAP GPIO driver will be
compatible with RT
TI's mux and divider clock drivers do not require locking and they do
not initialize internal spinlocks. This code was occasionally
copy-posted from generic mux/divider drivers. So remove it.
Cc: Tony Lindgren <t...@atomide.com>
Cc: Sekhar Nori <nsek...@ti.com>
Signed-off-by: Grygo
.
Tested-by: Tony Lindgren <t...@atomide.com>
Tested-by: Austin Schuh <aus...@peloton-tech.com>
Signed-off-by: Grygorii Strashko <grygorii.stras...@ti.com>
---
drivers/gpio/gpio-omap.c | 25 +++--
1 file changed, 15 insertions(+), 10 deletions(-)
diff --git
dev_err(dev,
1194 "can't get irq resource ret=%d\n",
bank->irq);
1195 return bank->irq;
1196 }
Fixes: commit 89d18e3af8b9: "gpio: omap: switch to use platform_get_irq"
Signed-off-by: Grygorii Strashko
<aus...@peloton-tech.com>
Signed-off-by: Grygorii Strashko <grygorii.stras...@ti.com>
---
drivers/gpio/gpio-omap.c | 55
1 file changed, 27 insertions(+), 28 deletions(-)
diff --git a/drivers/gpio/gpio-omap.c b/drivers/gpio/gpio-omap.c
i
gpio functionality tested on:
dra7-evm, BeagleBone(white), am43xx-gpevm, am437x-sk
Manually tested on dra7-evm including suspend/resume and wakeup.
Links on RFC:
https://lkml.org/lkml/2015/8/18/161
https://lkml.org/lkml/2015/8/18/162
Grygorii Strashko (2):
gpio: omap: move pm runtime
Hi Tony,
On 08/27/2015 08:20 AM, Grygorii Strashko wrote:
This series enables support for leds and gpio-keys which
is available on dra7-evm. It also adds pcf8575 gpio expander (i2c1 addr 20)
Grygorii Strashko (3):
ARM: dts: dra7-evm: add pcf8575 gpio expander (i2c1 addr 20)
ARM: dts
On 09/24/2015 03:28 PM, Linus Walleij wrote:
On Tue, Aug 18, 2015 at 4:10 AM, Grygorii Strashko
<grygorii.stras...@ti.com> wrote:
The PM runtime API can't be used in atomic contex on -RT even if
it's configured as irqsafe. As result, below error report can
be seen when PM runtime API
+Cc: Austin, Philipp
On 08/26/2015 10:53 AM, Linus Walleij wrote:
On Tue, Aug 18, 2015 at 1:10 PM, Grygorii Strashko
<grygorii.stras...@ti.com> wrote:
This patch series contains set of trivial fixes and improvements, and also
patches which fixes wrong APIs usage in atomic context as f
On 09/03/2015 08:31 PM, Tony Lindgren wrote:
If gpio-omap probe fails with -EPROBE_DEFER, the GPIO numbering
keeps increasing. Only increase the gpio count if gpiochip_add()
was successful as otherwise the numbers will increase for each
probe attempt.
Cc: Grygorii Strashko <grygorii.st
On 09/01/2015 12:14 AM, Tony Lindgren wrote:
> * Tony Lindgren [150831 14:02]:
>>
>> And I must have tested next-20150827 instead of next-20150828. Or
>> else it does not happen on every boot. In any case, I'm now getting
>> the following on next-20150831 most of the time:
>>
>>
On 09/01/2015 05:50 PM, Tony Lindgren wrote:
* Grygorii Strashko <grygorii.stras...@ti.com> [150901 07:36]:
On 09/01/2015 12:14 AM, Tony Lindgren wrote:
* Tony Lindgren <t...@atomide.com> [150831 14:02]:
And I must have tested next-20150827 instead of next-20150828. Or
1 - 100 of 319 matches
Mail list logo