From: Grant Likely <grant.likely@secretlab.ca>
To: Jamie Iles <jamie@jamieiles.com>
Cc: 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 10:57:26 -0600 [thread overview]
Message-ID: <BANLkTin2Bs6HxOmVHzbsxdwEViy6-DBtTw@mail.gmail.com> (raw)
In-Reply-To: <1309177954-8786-2-git-send-email-jamie@jamieiles.com>
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?
g.
> ---
> .../devicetree/bindings/tty/serial/of-serial.txt | 3 +++
> drivers/tty/serial/of_serial.c | 17 +++++++++++++++++
> 2 files changed, 20 insertions(+), 0 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/tty/serial/of-serial.txt b/Documentation/devicetree/bindings/tty/serial/of-serial.txt
> index 35e53ae..93260d0 100644
> --- a/Documentation/devicetree/bindings/tty/serial/of-serial.txt
> +++ b/Documentation/devicetree/bindings/tty/serial/of-serial.txt
> @@ -21,6 +21,9 @@ Optional properties:
> - reg-shift : quantity to shift the register offsets by.
> - used-by-rtas : set to indicate that the port is in use by the OpenFirmware
> RTAS and should not be registered.
> +- io-width : the size (in bytes) of the IO accesses that should be performed
> + on the device. There are some systems that require 32-bit accesses to the
> + UART (e.g. TI davinci).
>
> Example:
>
> diff --git a/drivers/tty/serial/of_serial.c b/drivers/tty/serial/of_serial.c
> index c911b24..dfcad6f 100644
> --- a/drivers/tty/serial/of_serial.c
> +++ b/drivers/tty/serial/of_serial.c
> @@ -65,6 +65,23 @@ static int __devinit of_platform_serial_setup(struct platform_device *ofdev,
>
> port->irq = irq_of_parse_and_map(np, 0);
> port->iotype = UPIO_MEM;
> + prop = of_get_property(np, "io-width", &prop_size);
> + if (prop && (prop_size == sizeof(u32))) {
> + switch (be32_to_cpup(prop)) {
> + case 1:
> + port->iotype = UPIO_MEM;
> + break;
> + case 4:
> + port->iotype = UPIO_MEM32;
> + break;
> + default:
> + dev_warn(&ofdev->dev,
> + "unsupported io width (%d bytes)\n",
> + be32_to_cpup(prop));
> + return -EINVAL;
> + }
> + }
> +
> port->type = type;
> port->uartclk = be32_to_cpup(clk);
> port->flags = UPF_SHARE_IRQ | UPF_BOOT_AUTOCONF | UPF_IOREMAP
> --
> 1.7.4.1
>
> _______________________________________________
> devicetree-discuss mailing list
> devicetree-discuss@lists.ozlabs.org
> https://lists.ozlabs.org/listinfo/devicetree-discuss
>
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
--
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 17:03 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 [this message]
2011-06-27 18:49 ` Alan Cox
[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=BANLkTin2Bs6HxOmVHzbsxdwEViy6-DBtTw@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=alan@linux.intel.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--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).