Re: [PATCH v2] gpio/omap: fix incorrect initialization of omap_gpio_mod_init

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

On Thu, May 10, 2012 at 3:06 AM, Janusz Krzysztofik
<jkrzyszt@xxxxxxxxxxxx> wrote:
> On Mon, 7 May 2012 10:52:28 DebBarma, Tarun Kanti wrote:
>> On Sun, May 6, 2012 at 3:25 AM, Grazvydas Ignotas <notasas@xxxxxxxxx> wrote:
>> > On Mon, Apr 30, 2012 at 10:20 AM, Tarun Kanti DebBarma
>> > <tarun.kanti@xxxxxx> wrote:
>> >> Initialization of irqenable, irqstatus registers is the common
>> >> operation done in this function for all OMAP platforms, viz. OMAP1,
>> >> OMAP2+. The latter _gpio_rmw()'s which supposedly got introduced
>> >> wrongly to take care of OMAP2+ platforms were overwriting initially
>> >> programmed OMAP1 value breaking functionality on OMAP1.
>
> Hi,
> I can confirm that my other issues with GPIO on Amstrad Delta were not
> related, and this patch is still required for GPIO interrupts hardware
> being correctly initialized on OMAP1 in 3.4-rc6. You can add my
>
> Tested-by: Janusz Krzysztofik <jkrzyszt@xxxxxxxxxxxx>
>
> if you wish.
Thank you for confirming!!
--
Tarun
>
> Thanks,
> Janusz
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Arm (vger)]     [ARM Kernel]     [ARM MSM]     [Linux Tegra]     [Linux WPAN Networking]     [Linux Wireless Networking]     [Maemo Users]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux