From: Tony Lindgren <tony@atomide.com>
To: Kevin Hilman <khilman@deeprootsystems.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] UART regs: add OMAP wakeup-enable register
Date: Thu, 21 May 2009 10:46:20 -0700 [thread overview]
Message-ID: <20090521174620.GN8308@atomide.com> (raw)
In-Reply-To: <1242925798-29672-1-git-send-email-khilman@deeprootsystems.com>
* Kevin Hilman <khilman@deeprootsystems.com> [090521 10:10]:
> Add the wakeup enable register to the list of OMAP-specific UART
> registers. This is to support forthcoming OMAP PM enhancements which
> use the wakeup feature of the OMAP's 8250-based UART.
>
> Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
> ---
> The MAINTAINERS file lists the 8250 driver as orphaned, and posts to
> linux-serial go unanswered. How should this go upstream?
I suggest you merge this into your omap PM queue and we'll merge it
with that.
Tony
> include/linux/serial_reg.h | 1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)
>
> diff --git a/include/linux/serial_reg.h b/include/linux/serial_reg.h
> index 96c0d93..850db2e 100644
> --- a/include/linux/serial_reg.h
> +++ b/include/linux/serial_reg.h
> @@ -323,6 +323,7 @@
> #define UART_OMAP_MVER 0x14 /* Module version register */
> #define UART_OMAP_SYSC 0x15 /* System configuration register */
> #define UART_OMAP_SYSS 0x16 /* System status register */
> +#define UART_OMAP_WER 0x17 /* Wake-up enable register */
>
> #endif /* _LINUX_SERIAL_REG_H */
>
> --
> 1.6.2.2
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2009-05-21 17:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-21 17:09 [PATCH] UART regs: add OMAP wakeup-enable register Kevin Hilman
2009-05-21 17:46 ` Tony Lindgren [this message]
2009-05-21 17:59 ` Kevin Hilman
2009-05-21 19:37 ` Alan Cox
2009-05-22 15:13 ` Kevin Hilman
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=20090521174620.GN8308@atomide.com \
--to=tony@atomide.com \
--cc=khilman@deeprootsystems.com \
--cc=linux-kernel@vger.kernel.org \
/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.