[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <7hr08mw8u3.fsf@baylibre.com>
Date: Fri, 11 Oct 2024 15:52:52 -0700
From: Kevin Hilman <khilman@...nel.org>
To: Judith Mendez <jm@...com>, Santosh Shilimkar <ssantosh@...nel.org>,
Linus Walleij <linus.walleij@...aro.org>, Bartosz
Golaszewski <brgl@...ev.pl>
Cc: linux-omap@...r.kernel.org, linux-gpio@...r.kernel.org,
linux-kernel@...r.kernel.org, Bin Liu <b-liu@...com>,
linux-serial@...r.kernel.org, Judith Mendez <jm@...com>
Subject: Re: [PATCH RESEND 0/2] Misc OMAP GPIO/UART fixes
Judith Mendez <jm@...com> writes:
> This patch series carries some miscellaneous
> OMAP driver fixes for GPIO and UART drivers.
>
> For GPIO, add gpio_enable and gpio_disable calls
> to gpio-omap which fixes an issue where if there
> is an irq storm, serial console is unresponsive.
>
> For UART, move pm_runtime_get_sync since the
> current order of omap_8250_rx_dma_flush and
> pm_runtime_get_sync calls are set in a way that
> when omap_8250_shutdown returns, dma->rx_running
> is set and this causes issues next time the UART
> is re-opened.
Could you summarize which OMAP platforms this was tested on?
Thanks,
Kevin
Powered by blists - more mailing lists