From: Alan Cox <alan@linux.intel.com>
To: Jamie Iles <jamie@jamieiles.com>
Cc: Ralf Baechle <ralf@linux-mips.org>,
linux-serial@vger.kernel.org, Greg Kroah-Hartman <gregkh@suse.de>,
linux-mips@linux-mips.org, Marc St-Jean <bluezzer@gmail.com>,
Shane McDonald <mcdonald.shane@gmail.com>,
Anoop P A <anoop.pa@gmail.com>
Subject: Re: [PATCH] tty: 8250: handle USR for DesignWare 8250 with correct accessors
Date: Fri, 10 Jun 2011 14:57:24 +0100 [thread overview]
Message-ID: <20110610145724.1e0c0983@bob.linux.org.uk> (raw)
In-Reply-To: <20110610075426.GM3711@pulham.picochip.com>
> I found this series from Alan
> (http://www.spinics.net/lists/linux-serial/msg03484.html) which looks
> like it would do the job if we added the extra irq callback. Ideally
> we just remove both of the UPIO_DWAPB and UPIO_DWAPB32 and let the
> platform specify the ops.
I've not yet had time to go back and revisit those patches and debug
them so they actually work but as and when someone gets time I think
it's the right basic path to follow, and the irq callback looks
sensible too.
Ultimately yes I'd also like to see all board specific ops banished
from 8250.c
next prev parent reply other threads:[~2011-06-10 13:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-09 10:48 [PATCH] tty: 8250: handle USR for DesignWare 8250 with correct accessors Jamie Iles
2011-06-10 3:58 ` Ralf Baechle
2011-06-10 7:54 ` Jamie Iles
2011-06-10 13:57 ` Alan Cox [this message]
2011-06-13 9:19 ` Jamie Iles
2011-06-13 9:29 ` Alan Cox
2011-06-10 18:58 ` Shane McDonald
2011-06-14 15:33 ` Shane McDonald
2011-06-15 8:49 ` Jamie Iles
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=20110610145724.1e0c0983@bob.linux.org.uk \
--to=alan@linux.intel.com \
--cc=anoop.pa@gmail.com \
--cc=bluezzer@gmail.com \
--cc=gregkh@suse.de \
--cc=jamie@jamieiles.com \
--cc=linux-mips@linux-mips.org \
--cc=linux-serial@vger.kernel.org \
--cc=mcdonald.shane@gmail.com \
--cc=ralf@linux-mips.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;
as well as URLs for NNTP newsgroup(s).