From: John Garry <john.garry@huawei.com>
To: gregkh@linuxfoundation.org, jslaby@suse.com, joel@jms.id.au,
p.zabel@pengutronix.de, arnd@arndb.de, fcooper@ti.com,
sergei.shtylyov@cogentembedded.com,
yamada.masahiro@socionext.com, khoroshilov@ispras.ru
Cc: linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org,
andriy.shevchenko@linux.intel.com, linuxarm@huawei.com
Subject: Re: [PATCH v2] serial: 8250_of: Add IO space support
Date: Tue, 8 May 2018 10:15:46 +0100 [thread overview]
Message-ID: <664f5d8a-bb9e-cb36-2360-1a905c239728@huawei.com> (raw)
In-Reply-To: <1524825366-155559-1-git-send-email-john.garry@huawei.com>
On 27/04/2018 11:36, John Garry wrote:
> Currently the 8250_of driver only supports MEM IO type
> accesses.
>
> Some development boards (Huawei D03, specifically) require
> IO space access for 8250-compatible OF driver support, so
> add it.
>
> The modification is quite simple: just set the port iotype
> and associated flags depending on the device address
> resource type.
>
> Signed-off-by: John Garry <john.garry@huawei.com>
> ---
Hi Greg,
Just a gentle reminder of this patch. I didn't see any response.
BTW, I think that this patch should still cleanly apply to your
tty-testing branch.
Thanks,
John
>
> Changes v1->v2:
> - rebase to Greg's tty-testing branch
> - use resource_type() helper
>
> diff --git a/drivers/tty/serial/8250/8250_of.c b/drivers/tty/serial/8250/8250_of.c
> index 3de8d6a..bfb37f0 100644
> --- a/drivers/tty/serial/8250/8250_of.c
> +++ b/drivers/tty/serial/8250/8250_of.c
> @@ -92,13 +92,43 @@ static int of_platform_serial_setup(struct platform_device *ofdev,
> goto err_unprepare;
> }
>
> + port->flags = UPF_SHARE_IRQ | UPF_BOOT_AUTOCONF | UPF_FIXED_PORT |
> + UPF_FIXED_TYPE;
> spin_lock_init(&port->lock);
> - port->mapbase = resource.start;
> - port->mapsize = resource_size(&resource);
>
> - /* Check for shifted address mapping */
> - if (of_property_read_u32(np, "reg-offset", &prop) == 0)
> - port->mapbase += prop;
> + if (resource_type(&resource) == IORESOURCE_IO) {
> + port->iotype = UPIO_PORT;
> + port->iobase = resource.start;
> + } else {
> + port->mapbase = resource.start;
> + port->mapsize = resource_size(&resource);
> +
> + /* Check for shifted address mapping */
> + if (of_property_read_u32(np, "reg-offset", &prop) == 0)
> + port->mapbase += prop;
> +
> + port->iotype = UPIO_MEM;
> + if (of_property_read_u32(np, "reg-io-width", &prop) == 0) {
> + switch (prop) {
> + case 1:
> + port->iotype = UPIO_MEM;
> + break;
> + case 2:
> + port->iotype = UPIO_MEM16;
> + break;
> + case 4:
> + port->iotype = of_device_is_big_endian(np) ?
> + UPIO_MEM32BE : UPIO_MEM32;
> + break;
> + default:
> + dev_warn(&ofdev->dev, "unsupported reg-io-width (%d)\n",
> + prop);
> + ret = -EINVAL;
> + goto err_dispose;
> + }
> + }
> + port->flags |= UPF_IOREMAP;
> + }
>
> /* Check for registers offset within the devices address range */
> if (of_property_read_u32(np, "reg-shift", &prop) == 0)
> @@ -114,26 +144,6 @@ static int of_platform_serial_setup(struct platform_device *ofdev,
> port->line = ret;
>
> port->irq = irq_of_parse_and_map(np, 0);
> - port->iotype = UPIO_MEM;
> - if (of_property_read_u32(np, "reg-io-width", &prop) == 0) {
> - switch (prop) {
> - case 1:
> - port->iotype = UPIO_MEM;
> - break;
> - case 2:
> - port->iotype = UPIO_MEM16;
> - break;
> - case 4:
> - port->iotype = of_device_is_big_endian(np) ?
> - UPIO_MEM32BE : UPIO_MEM32;
> - break;
> - default:
> - dev_warn(&ofdev->dev, "unsupported reg-io-width (%d)\n",
> - prop);
> - ret = -EINVAL;
> - goto err_dispose;
> - }
> - }
>
> info->rst = devm_reset_control_get_optional_shared(&ofdev->dev, NULL);
> if (IS_ERR(info->rst)) {
> @@ -147,8 +157,6 @@ static int of_platform_serial_setup(struct platform_device *ofdev,
>
> port->type = type;
> port->uartclk = clk;
> - port->flags = UPF_SHARE_IRQ | UPF_BOOT_AUTOCONF | UPF_IOREMAP
> - | UPF_FIXED_PORT | UPF_FIXED_TYPE;
> port->irqflags |= IRQF_SHARED;
>
> if (of_property_read_bool(np, "no-loopback-test"))
>
prev parent reply other threads:[~2018-05-08 9:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-27 10:36 [PATCH v2] serial: 8250_of: Add IO space support John Garry
2018-05-08 9:15 ` John Garry [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=664f5d8a-bb9e-cb36-2360-1a905c239728@huawei.com \
--to=john.garry@huawei.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=arnd@arndb.de \
--cc=fcooper@ti.com \
--cc=gregkh@linuxfoundation.org \
--cc=joel@jms.id.au \
--cc=jslaby@suse.com \
--cc=khoroshilov@ispras.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=p.zabel@pengutronix.de \
--cc=sergei.shtylyov@cogentembedded.com \
--cc=yamada.masahiro@socionext.com \
/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