From: Alan Cox <alan@linux.intel.com>
To: Jamie Iles <jamie@jamieiles.com>
Cc: linux-serial@vger.kernel.org,
devicetree-discuss@lists.ozlabs.org,
Grant Likely <grant.likely@secretlab.ca>
Subject: Re: [PATCH 2/2] tty: of_serial: support for 32 bit accesses
Date: Wed, 15 Jun 2011 13:54:19 +0100 [thread overview]
Message-ID: <20110615135419.52c5ee06@bob.linux.org.uk> (raw)
In-Reply-To: <1308142199-17972-2-git-send-email-jamie@jamieiles.com>
On Wed, 15 Jun 2011 13:49:59 +0100
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.
>
> Cc: Alan Cox <alan@linux.intel.com>
Acked-by: Alan Cox <alan@linux.intel.com>
next prev parent reply other threads:[~2011-06-15 12:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-15 12:49 [PATCH 1/2] dt: document the of_serial bindings Jamie Iles
2011-06-15 12:49 ` [PATCH 2/2] tty: of_serial: support for 32 bit accesses Jamie Iles
2011-06-15 12:54 ` Alan Cox [this message]
2011-06-15 13:27 ` Grant Likely
2011-06-15 14: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=20110615135419.52c5ee06@bob.linux.org.uk \
--to=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).