From: Greg KH <gregkh@linuxfoundation.org>
To: Doug Kehn <rdkehn@yahoo.com>
Cc: linux-sreial@vger.kernel.org, linux-omap@vger.kernel.org,
tony@atomide.com
Subject: Re: [PATCH] tty/serial: omap: fix !wakeirq message
Date: Tue, 24 Mar 2015 00:15:18 +0100 [thread overview]
Message-ID: <20150323231518.GA1857@kroah.com> (raw)
In-Reply-To: <1427150324-12600-1-git-send-email-rdkehn@yahoo.com>
On Mon, Mar 23, 2015 at 05:38:44PM -0500, Doug Kehn wrote:
> When wakeirq is not used/enabled, "no wakeirq for uart0" is output for
> all TTY as the log message is generated before the port line is
> initialized.
>
> [ 0.802656] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
> [ 0.811700] omap_uart 44e09000.serial: no wakeirq for uart0
> [ 0.812379] 44e09000.serial: ttyO0 at MMIO 0x44e09000 (irq = 88, base_baud = 3000000) is a OMAP UART0
> [ 1.503622] console [ttyO0] enabled
> [ 1.509836] omap_uart 48022000.serial: no wakeirq for uart0
> [ 1.516118] 48022000.serial: ttyO1 at MMIO 0x48022000 (irq = 89, base_baud = 3000000) is a OMAP UART1
> [ 1.527711] omap_uart 48024000.serial: no wakeirq for uart0
> [ 1.533881] 48024000.serial: ttyO2 at MMIO 0x48024000 (irq = 90, base_baud = 3000000) is a OMAP UART2
> [ 1.545324] omap_uart 481a6000.serial: no wakeirq for uart0
> [ 1.551410] 481a6000.serial: ttyO3 at MMIO 0x481a6000 (irq = 60, base_baud = 3000000) is a OMAP UART3
> [ 1.562946] omap_uart 481a8000.serial: no wakeirq for uart0
> [ 1.569036] 481a8000.serial: ttyO4 at MMIO 0x481a8000 (irq = 61, base_baud = 3000000) is a OMAP UART4
>
> Fix by moving wakeirq check and dev_info() call to after port line
> initialization and validation.
>
> Patch is against 3.14.36.
That's really old, please make this against a "modern" kernel, like the
4.0-rc series.
thanks,
greg k-h
parent reply other threads:[~2015-03-24 9:38 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1427150324-12600-1-git-send-email-rdkehn@yahoo.com>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150323231518.GA1857@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-sreial@vger.kernel.org \
--cc=rdkehn@yahoo.com \
--cc=tony@atomide.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.