From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Grigory Tolstolytkin <gtolstolytkin@dev.rtsoft.ru>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 8250 serial driver and PM
Date: Wed, 31 Aug 2005 11:08:55 +0100 [thread overview]
Message-ID: <20050831110855.D26480@flint.arm.linux.org.uk> (raw)
In-Reply-To: <43134BF8.1090706@dev.rtsoft.ru>; from gtolstolytkin@dev.rtsoft.ru on Mon, Aug 29, 2005 at 09:55:04PM +0400
On Mon, Aug 29, 2005 at 09:55:04PM +0400, Grigory Tolstolytkin wrote:
> I'm working on power management support for a particular ARM based board
> and I've got a question:
> I want to add a board specific power management for standard uart driver
> (serial8250). For this purpose there is a special hook defined in
> uart_8250_port structure (drivers/serial/8250.c):
> ...
> > /*
> > * We provide a per-port pm hook.
> > */
> > void (*pm)(struct uart_port *port,
> > unsigned int state, unsigned int
> old);
> ...
>
> When driver goes into suspend/resume, serial8250_pm() function is called
> and it checks for the hook and executes it if it exists. But I didn't
> find a proper way to assign my own function to this hook.
We probably want to pass it via the platform device - which probably
means changing that interface.
> How this hook is supposed to be changed?
It's something which wasn't thought about since there were very few
people wanting to use it, and further work needed to be done (as my
first comment) to allow it to be used - which basically meant changing
the initialisation paths to allow platform devices (now done).
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 Serial core
next prev parent reply other threads:[~2005-08-31 10:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-29 17:55 8250 serial driver and PM Grigory Tolstolytkin
2005-08-31 10:08 ` Russell King [this message]
2005-08-31 10:57 ` Vitaly Wool
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=20050831110855.D26480@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=gtolstolytkin@dev.rtsoft.ru \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox