From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: "Thomas Gleixner" <tglx@linutronix.de>,
linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-aspeed@lists.ozlabs.org,
linux-rpi-kernel@lists.infradead.org, linux-mips@vger.kernel.org,
linux-tegra@vger.kernel.org, "Jiri Slaby" <jirislaby@kernel.org>,
"Joel Stanley" <joel@jms.id.au>,
"Andrew Jeffery" <andrew@codeconstruct.com.au>,
"Florian Fainelli" <florian.fainelli@broadcom.com>,
"Broadcom internal kernel review list"
<bcm-kernel-feedback-list@broadcom.com>,
"Ray Jui" <rjui@broadcom.com>,
"Scott Branden" <sbranden@broadcom.com>,
"Al Cooper" <alcooperx@gmail.com>,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
"Paul Cercueil" <paul@crapouillou.net>,
"Vladimir Zapolskiy" <vz@mleia.com>,
"Thierry Reding" <thierry.reding@gmail.com>,
"Jonathan Hunter" <jonathanh@nvidia.com>,
"Kunihiko Hayashi" <hayashi.kunihiko@socionext.com>,
"Masami Hiramatsu" <mhiramat@kernel.org>
Subject: Re: [PATCH v2 03/14] serial: port: Introduce a common helper to read properties
Date: Sat, 2 Mar 2024 21:58:53 +0100 [thread overview]
Message-ID: <2024030259-playback-starlit-a472@gregkh> (raw)
In-Reply-To: <20240226142514.1485246-4-andriy.shevchenko@linux.intel.com>
On Mon, Feb 26, 2024 at 04:19:19PM +0200, Andy Shevchenko wrote:
> Several serial drivers want to read the same or similar set of
> the port properties. Make a common helper for them.
>
> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> ---
> drivers/tty/serial/serial_port.c | 134 +++++++++++++++++++++++++++++++
> include/linux/serial_core.h | 1 +
> 2 files changed, 135 insertions(+)
>
> diff --git a/drivers/tty/serial/serial_port.c b/drivers/tty/serial/serial_port.c
> index 88975a4df306..ecc980e9dba6 100644
> --- a/drivers/tty/serial/serial_port.c
> +++ b/drivers/tty/serial/serial_port.c
> @@ -8,7 +8,10 @@
>
> #include <linux/device.h>
> #include <linux/module.h>
> +#include <linux/of.h>
> +#include <linux/platform_device.h>
> #include <linux/pm_runtime.h>
> +#include <linux/property.h>
> #include <linux/serial_core.h>
> #include <linux/spinlock.h>
>
> @@ -82,6 +85,137 @@ void uart_remove_one_port(struct uart_driver *drv, struct uart_port *port)
> }
> EXPORT_SYMBOL(uart_remove_one_port);
>
> +/**
> + * uart_read_port_properties - read firmware properties of the given UART port
I like, but:
> + * @port: corresponding port
> + * @use_defaults: apply defaults (when %true) or validate the values (when %false)
Using random booleans in a function is horrid. Every time you see the
function call, or want to call it, you need to go and look up what the
boolean is and means.
Make 2 public functions here, one that does it with use_defaults=true
and one =false and then have them both call this one static function,
that way the function names themselves are easy to read and understand
and maintain over time.
thanks,
greg k-h
> + *
> + * The following device properties are supported:
> + * - clock-frequency (optional)
> + * - fifo-size (optional)
> + * - no-loopback-test (optional)
> + * - reg-shift (defaults may apply)
> + * - reg-offset (value may be validated)
> + * - reg-io-width (defaults may apply or value may be validated)
> + * - interrupts (OF only)
> + * - serial [alias ID] (OF only)
> + *
> + * If the port->dev is of struct platform_device type the interrupt line
> + * will be retrieved via platform_get_irq() call against that device.
> + * Otherwise it will be assigned by fwnode_irq_get() call. In both cases
> + * the index 0 of the resource is used.
> + *
> + * The caller is responsible to initialize the following fields of the @port
> + * ->dev (must be valid)
> + * ->flags
> + * ->mapbase
> + * ->mapsize
> + * ->regshift (if @use_defaults is false)
> + * before calling this function. Alternatively the above mentioned fields
> + * may be zeroed, in such case the only ones, that have associated properties
> + * found, will be set to the respective values.
> + *
> + * If no error happened, the ->irq, ->mapbase, ->mapsize will be altered.
> + * The ->iotype is always altered.
> + *
> + * When @use_defaults is true and the respective property is not found
> + * the following values will be applied:
> + * ->regshift = 0
> + * In this case IRQ must be provided, otherwise an error will be returned.
> + *
> + * When @use_defaults is false and the respective property is found
> + * the following values will be validated:
> + * - reg-io-width (->iotype)
> + * - reg-offset (->mapsize against ->mapbase)
> + *
> + * Returns: 0 on success or negative errno on failure
> + */
> +int uart_read_port_properties(struct uart_port *port, bool use_defaults)
> +{
> + struct device *dev = port->dev;
> + u32 value;
> + int ret;
> +
> + /* Read optional UART functional clock frequency */
> + device_property_read_u32(dev, "clock-frequency", &port->uartclk);
> +
> + /* Read the registers alignment (default: 8-bit) */
> + ret = device_property_read_u32(dev, "reg-shift", &value);
> + if (ret)
> + port->regshift = use_defaults ? 0 : port->regshift;
> + else
> + port->regshift = value;
> +
> + /* Read the registers I/O access type (default: MMIO 8-bit) */
> + ret = device_property_read_u32(dev, "reg-io-width", &value);
> + if (ret) {
> + port->iotype = UPIO_MEM;
> + } else {
> + switch (value) {
> + case 1:
> + port->iotype = UPIO_MEM;
> + break;
> + case 2:
> + port->iotype = UPIO_MEM16;
> + break;
> + case 4:
> + port->iotype = device_is_big_endian(dev) ? UPIO_MEM32BE : UPIO_MEM32;
> + break;
> + default:
> + if (!use_defaults) {
> + dev_err(dev, "Unsupported reg-io-width (%u)\n", value);
> + return -EINVAL;
> + }
> + port->iotype = UPIO_UNKNOWN;
> + break;
> + }
> + }
> +
> + /* Read the address mapping base offset (default: no offset) */
> + ret = device_property_read_u32(dev, "reg-offset", &value);
> + if (ret)
> + value = 0;
> +
> + /* Check for shifted address mapping overflow */
> + if (!use_defaults && port->mapsize < value) {
> + dev_err(dev, "reg-offset %u exceeds region size %pa\n", value, &port->mapsize);
> + return -EINVAL;
> + }
> +
> + port->mapbase += value;
> + port->mapsize -= value;
> +
> + /* Read optional FIFO size */
> + device_property_read_u32(dev, "fifo-size", &port->fifosize);
> +
> + if (device_property_read_bool(dev, "no-loopback-test"))
> + port->flags |= UPF_SKIP_TEST;
> +
> + /* Get index of serial line, if found in DT aliases */
> + ret = of_alias_get_id(dev_of_node(dev), "serial");
> + if (ret >= 0)
> + port->line = ret;
> +
> + if (dev_is_platform(dev))
> + ret = platform_get_irq(to_platform_device(dev), 0);
> + else
> + ret = fwnode_irq_get(dev_fwnode(dev), 0);
> + if (ret == -EPROBE_DEFER)
> + return ret;
> + if (ret > 0)
> + port->irq = ret;
> + else if (use_defaults)
> + /* By default IRQ support is mandatory */
> + return ret;
> + else
> + port->irq = 0;
> +
> + port->flags |= UPF_SHARE_IRQ;
> +
> + return 0;
> +}
> +EXPORT_SYMBOL(uart_read_port_properties);
EXPORT_SYMBOL_GPL()? I have to ask :)
thanks,
greg k-h
next prev parent reply other threads:[~2024-03-02 20:58 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-26 14:19 [PATCH v2 00/14] serial: Add a helper to parse device properties and more Andy Shevchenko
2024-02-26 14:19 ` [PATCH v2 01/14] serial: core: Move struct uart_port::quirks closer to possible values Andy Shevchenko
2024-02-26 14:19 ` [PATCH v2 02/14] serial: core: Add UPIO_UNKNOWN constant for unknown port type Andy Shevchenko
2024-02-26 14:19 ` [PATCH v2 03/14] serial: port: Introduce a common helper to read properties Andy Shevchenko
2024-03-02 20:58 ` Greg Kroah-Hartman [this message]
2024-03-04 11:09 ` Andy Shevchenko
2024-02-26 14:19 ` [PATCH v2 04/14] serial: 8250_aspeed_vuart: Switch to use uart_read_port_properties() Andy Shevchenko
2024-02-26 14:19 ` [PATCH v2 05/14] serial: 8250_bcm2835aux: " Andy Shevchenko
2024-02-26 18:23 ` Florian Fainelli
2024-02-26 14:19 ` [PATCH v2 06/14] serial: 8250_bcm7271: " Andy Shevchenko
2024-02-26 18:23 ` Florian Fainelli
2024-02-26 14:19 ` [PATCH v2 07/14] serial: 8250_dw: " Andy Shevchenko
2024-02-26 14:19 ` [PATCH v2 08/14] serial: 8250_ingenic: " Andy Shevchenko
2024-02-26 14:19 ` [PATCH v2 09/14] serial: 8250_lpc18xx: " Andy Shevchenko
2024-02-26 14:19 ` [PATCH v2 10/14] serial: 8250_of: " Andy Shevchenko
2024-02-26 18:24 ` Florian Fainelli
2024-02-27 14:55 ` Andy Shevchenko
2024-02-26 14:19 ` [PATCH v2 11/14] serial: 8250_omap: " Andy Shevchenko
2024-02-26 14:19 ` [PATCH v2 12/14] serial: 8250_pxa: " Andy Shevchenko
2024-02-26 14:19 ` [PATCH v2 13/14] serial: 8250_tegra: " Andy Shevchenko
2024-02-26 14:19 ` [PATCH v2 14/14] serial: 8250_uniphier: " Andy Shevchenko
2024-02-27 9:43 ` Kunihiko Hayashi
2024-02-27 14:55 ` Andy Shevchenko
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=2024030259-playback-starlit-a472@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=alcooperx@gmail.com \
--cc=andrew@codeconstruct.com.au \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=florian.fainelli@broadcom.com \
--cc=hayashi.kunihiko@socionext.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=jirislaby@kernel.org \
--cc=joel@jms.id.au \
--cc=jonathanh@nvidia.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=linux-serial@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=paul@crapouillou.net \
--cc=rjui@broadcom.com \
--cc=sbranden@broadcom.com \
--cc=tglx@linutronix.de \
--cc=thierry.reding@gmail.com \
--cc=vz@mleia.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;
as well as URLs for NNTP newsgroup(s).