linux-kernel - Re: [PATCH 0/7] gpio: omap: fixes and improvements

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 7 Sep 2015 14:40:39 +0300
From:	Grygorii Strashko <grygorii.strashko@...com>
To:	Linus Walleij <linus.walleij@...aro.org>
CC:	Alexandre Courbot <gnurou@...il.com>,
	Santosh Shilimkar <ssantosh@...nel.org>,
	Kevin Hilman <khilman@...prootsystems.com>,
	Tony Lindgren <tony@...mide.com>,
	Javier Martinez Canillas <javier@...hile0.org>,
	Linux-OMAP <linux-omap@...r.kernel.org>,
	"linux-gpio@...r.kernel.org" <linux-gpio@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Philipp Schrader <philipp@...oton-tech.com>,
	Austin Schuh <austin@...oton-tech.com>
Subject: Re: [PATCH 0/7] gpio: omap: fixes and improvements

+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.strashko@...com> wrote:
>
>> This patch series contains set of trivial fixes and improvements, and also
>> patches which fixes wrong APIs usage in atomic context as for -RT as for
>> non-RT kernel. The final goal of this series is to make TI OMAP GPIO
>> driver compatible with -RT kernel as much as possible.
>>
>> Patch 1-4: trivial fixes and improvements
>> Patch 5: fixes wrong CLK clk_prepare/unprepare APIs usage in atomic contexet
>
> I've applied patches 1-5 with Santosh's ACK and Tony's Tested-by.
>
>> Patch 6(rfc): required to be compatible with -RT kernel, because PM runtime
>>   can't be used in atimic context on -RT.
>> Patch 7(rfc): 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 kernel where it will be forced thread IRQ handler
>>   while in non-RT kernel it still will be executed in HW IRQ context.
>
> Waiting for more feedback here.
>
> Yours,
> Linus Walleij
>

I've got some feedback here.
Patches were tested on to of TI -RT tree ti-rt-linux-4.1.y.



-------- Forwarded Message --------
Subject: Re: [PATCH 0/7] gpio: omap: fixes and improvements
Date: Fri, 4 Sep 2015 21:42:03 +0000
From: Austin Schuh <austin@...oton-tech.com>
To: grygorii.strashko@...com
CC: Philipp Schrader <philipp@...oton-tech.com>

Hi Grygorii,

We are running the entire patchset on top of
a7a6541db840cc4514a26fc12cc1bc94d1b9e873 from the git://
git.ti.com/ti-linux-kernel/ti-linux-kernel.git tree. I've pushed the
system pretty hard overnight and haven't seen any instability (with lockdep
enabled. We used to get splats pretty fast).

I wasn't on lkml when you sent the patchset out, so I'm not sure how to
best reply to the original thread with this info.

Tested-by: Austin Schuh <austin@...oton-tech.com>

Austin
-------- Forwarded Message --------

-- 
regards,
-grygorii
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/