From: marex@denx.de (Marek Vasut)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 2/3] serial: mxs-auart: Allow device tree probing
Date: Fri, 15 Jun 2012 13:49:27 +0200 [thread overview]
Message-ID: <201206151349.27261.marex@denx.de> (raw)
In-Reply-To: <1339759950-5507-2-git-send-email-festevam@gmail.com>
Dear Fabio Estevam,
> From: Fabio Estevam <fabio.estevam@freescale.com>
>
> Allow device tree probing.
>
> Cc: Grant Likely <grant.likely@secretlab.ca>
> Cc: Rob Herring <rob.herring@calxeda.com>
> Cc: Alan Cox <alan@linux.intel.com>
> Cc: <linux-serial@vger.kernel.org>
> Signed-off-by: Fabio Estevam <fabio.estevam@freescale.com>
> ---
> Changes since v1:
> - Merged patches 3 and 5 from v1 into this one
> .../bindings/tty/serial/fsl-mxs-auart.txt | 13 +++++
> drivers/tty/serial/mxs-auart.c | 55
> +++++++++++++++++++- 2 files changed, 67 insertions(+), 1 deletions(-)
> create mode 100644
> Documentation/devicetree/bindings/tty/serial/fsl-mxs-auart.txt
>
> diff --git a/Documentation/devicetree/bindings/tty/serial/fsl-mxs-auart.txt
> b/Documentation/devicetree/bindings/tty/serial/fsl-mxs-auart.txt new file
> mode 100644
> index 0000000..1b28b1c
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/tty/serial/fsl-mxs-auart.txt
> @@ -0,0 +1,13 @@
> +* Freescale MXS Application UART (AUART)
> +
> +Required properties:
> +- compatible : Should be "fsl,mxs-uart"
> +- reg : Address and length of the register set for the device
> +- interrupts : Should contain the auart interrupt
> +
> +Example:
> +auart0: serial at 8006a000 {
> + compatible = "fsl,mxs-auart";
> + reg = <0x8006a000 0x2000>;
> + interrupts = <112 70 71>;
> +};
> diff --git a/drivers/tty/serial/mxs-auart.c
> b/drivers/tty/serial/mxs-auart.c index ec56d83..21e2ce7 100644
> --- a/drivers/tty/serial/mxs-auart.c
> +++ b/drivers/tty/serial/mxs-auart.c
> @@ -33,6 +33,7 @@
> #include <linux/delay.h>
> #include <linux/io.h>
> #include <linux/pinctrl/consumer.h>
> +#include <linux/of_device.h>
>
> #include <asm/cacheflush.h>
>
> @@ -675,6 +676,44 @@ static struct uart_driver auart_driver = {
> #endif
> };
>
> +#ifdef CONFIG_OF
Isn't CONFIG_OF always enabled?
> +/*
> + * This function returns 1 if pdev isn't a device instatiated by dt, 0 if
> it + * could successfully get all information from dt or a negative errno.
> + */
> +static int serial_mxs_probe_dt(struct mxs_auart_port *s,
> + struct platform_device *pdev)
> +{
> + struct device_node *np = pdev->dev.of_node;
> + int ret;
> +
> + if (!np)
> + /* no device tree device */
> + return 1;
> +
> + ret = of_alias_get_id(np, "serial");
> + if (ret < 0) {
> + dev_err(&pdev->dev, "failed to get alias id: %d\n", ret);
> + return ret;
> + }
> + s->port.line = ret;
> +
> + return 0;
> +}
> +#else
> +static inline int serial_mxs_probe_dt(struct mxs_auart_port *s,
> + struct platform_device *pdev)
> +{
> + return 1;
> +}
> +#endif
So drop this whole ifdef stuff ...
> +
> +static void mxs_auart_probe_pdev(struct mxs_auart_port *s,
> + struct platform_device *pdev)
> +{
> + s->port.line = pdev->id < 0 ? 0 : pdev->id;
> +}
> +
> static int __devinit mxs_auart_probe(struct platform_device *pdev)
> {
> struct mxs_auart_port *s;
> @@ -689,6 +728,14 @@ static int __devinit mxs_auart_probe(struct
> platform_device *pdev) goto out;
> }
>
> + ret = serial_mxs_probe_dt(s, pdev);
> + if (ret > 0)
> + mxs_auart_probe_pdev(s, pdev);
> + else if (ret < 0) {
> + ret = -EINVAL;
> + goto out_free;
> + }
> +
> pinctrl = devm_pinctrl_get_select_default(&pdev->dev);
> if (IS_ERR(pinctrl)) {
> ret = PTR_ERR(pinctrl);
> @@ -711,7 +758,6 @@ static int __devinit mxs_auart_probe(struct
> platform_device *pdev) s->port.membase = ioremap(r->start,
> resource_size(r));
> s->port.ops = &mxs_auart_ops;
> s->port.iotype = UPIO_MEM;
> - s->port.line = pdev->id < 0 ? 0 : pdev->id;
> s->port.fifosize = 16;
> s->port.uartclk = clk_get_rate(s->clk);
> s->port.type = PORT_IMX;
> @@ -769,12 +815,19 @@ static int __devexit mxs_auart_remove(struct
> platform_device *pdev) return 0;
> }
>
> +static struct of_device_id mxs_auart_dt_ids[] = {
> + {.compatible = "fsl,mxs-auart", },
> + { /* sentinel */ }
> +};
> +MODULE_DEVICE_TABLE(of, mxs_auart_dt_ids);
> +
> static struct platform_driver mxs_auart_driver = {
> .probe = mxs_auart_probe,
> .remove = __devexit_p(mxs_auart_remove),
> .driver = {
> .name = "mxs-auart",
> .owner = THIS_MODULE,
> + .of_match_table = of_match_ptr(mxs_auart_dt_ids),
> },
> };
Best regards,
Marek Vasut
next prev parent reply other threads:[~2012-06-15 11:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-15 11:32 [PATCH v2 1/3] ARM: dts: mx28evk: Add auart0 and auart3 support Fabio Estevam
2012-06-15 11:32 ` [PATCH v2 2/3] serial: mxs-auart: Allow device tree probing Fabio Estevam
2012-06-15 11:49 ` Marek Vasut [this message]
2012-06-15 12:01 ` Fabio Estevam
2012-06-15 12:13 ` Fabio Estevam
2012-06-15 13:10 ` Shawn Guo
2012-06-15 11:32 ` [PATCH v2 3/3] ARM: mxs_defconfig: Let AUART driver be built by default Fabio Estevam
2012-06-15 11:49 ` Marek Vasut
2012-06-15 12:33 ` Shawn Guo
2012-06-15 12:50 ` Subodh Nijsure
2012-06-15 12:53 ` Marek Vasut
2012-06-15 13:13 ` Shawn Guo
2012-06-15 11:47 ` [PATCH v2 1/3] ARM: dts: mx28evk: Add auart0 and auart3 support Marek Vasut
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=201206151349.27261.marex@denx.de \
--to=marex@denx.de \
--cc=linux-arm-kernel@lists.infradead.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).