From: Michael Williamson <michael.williamson@criticallink.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: davinci-linux-open-source@linux.davincidsp.com,
linux-arm-kernel@lists.infradead.org,
khilman@deeprootsystems.com, linux-serial@vger.kernel.org,
gregkh@suse.de, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] serial: Provide capability to disable modem status interrupts in 8250 driver
Date: Tue, 04 Jan 2011 09:10:50 -0500 [thread overview]
Message-ID: <4D232A6A.1030307@criticallink.com> (raw)
In-Reply-To: <20110104135621.56a4770e@lxorguk.ukuu.org.uk>
On 1/4/2011 8:56 AM, Alan Cox wrote:
>> This patch was tested using a MityDSP-L138F platform having a UART CTS pin
>> connected to a clock signal (and configured, via pinmux, as a clock input
>> for another peripheral function).
>
> Please hide such horrors in your platform code. We are trying todrive all
> the quirks stuff we can out of the core code.
>
> Instead provide your own I/O methods when registering the port and mask
> the appropriate bogus bits in the register.
>
Got it. Thanks for the guidance.
-Mike
prev parent reply other threads:[~2011-01-04 14:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-04 13:51 [PATCH 1/2] serial: Provide capability to disable modem status interrupts in 8250 driver Michael Williamson
2011-01-04 13:51 ` [PATCH 2/2] davinci: Disable modem status (CTS) interrupts on UART1 Michael Williamson
2011-01-04 13:56 ` [PATCH 1/2] serial: Provide capability to disable modem status interrupts in 8250 driver Alan Cox
2011-01-04 14:10 ` Michael Williamson [this message]
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=4D232A6A.1030307@criticallink.com \
--to=michael.williamson@criticallink.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=davinci-linux-open-source@linux.davincidsp.com \
--cc=gregkh@suse.de \
--cc=khilman@deeprootsystems.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@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