From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: Jamie Iles <jamie@jamieiles.com>,
linux-serial@vger.kernel.org,
devicetree-discuss@lists.ozlabs.org,
Alan Cox <alan@linux.intel.com>
Subject: Re: [PATCHv3 2/2] tty: of_serial: support for 32 bit accesses
Date: Mon, 27 Jun 2011 19:49:09 +0100 [thread overview]
Message-ID: <20110627194909.7636eddc@pyx> (raw)
In-Reply-To: <BANLkTin2Bs6HxOmVHzbsxdwEViy6-DBtTw@mail.gmail.com>
On Mon, 27 Jun 2011 10:57:26 -0600
Grant Likely <grant.likely@secretlab.ca> wrote:
> On Mon, Jun 27, 2011 at 6:32 AM, Jamie Iles <jamie@jamieiles.com> wrote:
> > Some platforms e.g. TI Davinci require 32-bit accesses to the UARTs.
> > The of_serial driver currently registers all UARTs as UPIO_MEM. Add a
> > new attribute "io-width" to allow the port to be registered with
> > different IO width requirements.
> >
> > Acked-by: Alan Cox <alan@linux.intel.com>
> > Acked-by: Grant Likely <grant.likely@secretlab.ca>
> > Signed-off-by: Jamie Iles <jamie@jamieiles.com>
>
> Alan, who should pick this series up? Should I take it via the
> devicetree/next tree?
Please
--
To unsubscribe from this list: send the line "unsubscribe linux-serial" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-06-27 18:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-27 12:32 [PATCHv3 1/2] dt: document the of_serial bindings Jamie Iles
[not found] ` <1309177954-8786-1-git-send-email-jamie-wmLquQDDieKakBO8gow8eQ@public.gmane.org>
2011-06-27 12:32 ` [PATCHv3 2/2] tty: of_serial: support for 32 bit accesses Jamie Iles
2011-06-27 16:57 ` Grant Likely
2011-06-27 18:49 ` Alan Cox [this message]
[not found] ` <1309177954-8786-2-git-send-email-jamie-wmLquQDDieKakBO8gow8eQ@public.gmane.org>
2011-06-30 18:38 ` Grant Likely
2011-06-27 13:05 ` [PATCHv3 1/2] dt: document the of_serial bindings Arnd Bergmann
2011-06-27 19:32 ` Grant Likely
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=20110627194909.7636eddc@pyx \
--to=alan@lxorguk.ukuu.org.uk \
--cc=alan@linux.intel.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=jamie@jamieiles.com \
--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;
as well as URLs for NNTP newsgroup(s).