From: Vitaly Wool <vitalhome@rbcmail.ru>
To: Russell King <rmk+lkml@arm.linux.org.uk>
Cc: linux-kernel@vger.kernel.org,
Grigory Tolstolytkin <gtolstolytkin@dev.rtsoft.ru>
Subject: Re: [PATCH] custom PM support for 8250
Date: Wed, 31 Aug 2005 15:40:46 +0400 [thread overview]
Message-ID: <4315973E.7040103@rbcmail.ru> (raw)
In-Reply-To: <20050831122622.B1118@flint.arm.linux.org.uk>
Yes, that's also something I was thinking of, but I wasn't sure enough
in this radical change :)
Anyway, I do agree that this way looks better than the current one.
So, if you don't object against other changes (say, the suggested
approach to set uart->pm), I can proceed with the changes you suggest
and work it out to the new patch. ;)
Best regards,
Vitaly
Russell King wrote:
>On Wed, Aug 31, 2005 at 03:10:09PM +0400, Vitaly Wool wrote:
>
>
>>please find the patch that allows passing the pointer to custom power
>>management routine (via platform_device) to 8250 serial driver.
>>Please note that the interface to the outer world (i. e. exported
>>functions) remained the same.
>>
>>
>
>I'd rather change the structure passed via the platform device to
>something like:
>
>struct platform_serial_data {
> void (*pm)(struct uart_port *port, unsigned int state, unsigned int old);
> int nr_ports;
> struct plat_serial8250_port *ports;
>};
>
>which also eliminates the empty plat_serial8250_port terminator from
>all the serial8250 platform devices (which appears to have caused some
>folk problems.)
>
>It does mean that a set of 8250 ports (grouped by each platform device)
>have a common power management method - which seems a logical restriction.
>
>
>
next prev parent reply other threads:[~2005-08-31 11:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-31 11:10 [PATCH] custom PM support for 8250 Vitaly Wool
2005-08-31 11:20 ` Vitaly Wool
2005-08-31 11:26 ` Russell King
2005-08-31 11:40 ` Vitaly Wool [this message]
2005-09-05 9:59 ` Grigory Tolstolytkin
2005-09-06 6:22 ` Vitaly Wool
2005-09-01 16:16 ` Pavel Machek
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=4315973E.7040103@rbcmail.ru \
--to=vitalhome@rbcmail.ru \
--cc=gtolstolytkin@dev.rtsoft.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk+lkml@arm.linux.org.uk \
/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.