From: grant.likely@secretlab.ca (Grant Likely)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/3] serial/imx: add device tree support
Date: Tue, 21 Jun 2011 13:13:50 -0600 [thread overview]
Message-ID: <BANLkTim4vunTm1176MRw3pqRZnunu4=9jg@mail.gmail.com> (raw)
In-Reply-To: <20110621135558.GB9228@S2101-09.ap.freescale.net>
On Tue, Jun 21, 2011 at 7:55 AM, Shawn Guo <shawn.guo@freescale.com> wrote:
> Hi Grant,
>
> I just gave a try to use aliases node for identify the device index.
> Please take a look and let me know if it's what you expect.
Thanks Shawn. This is definitely on track. Comments below...
>
> On Sun, Jun 19, 2011 at 03:30:02PM +0800, Shawn Guo wrote:
> [...]
>> > >
>> > > +#ifdef CONFIG_OF
>> > > +static int serial_imx_probe_dt(struct imx_port *sport,
>> > > + ? ? ? ? struct platform_device *pdev)
>> > > +{
>> > > + struct device_node *node = pdev->dev.of_node;
>> > > + const __be32 *line;
>> > > +
>> > > + if (!node)
>> > > + ? ? ? ? return -ENODEV;
>> > > +
>> > > + line = of_get_property(node, "id", NULL);
>> > > + if (!line)
>> > > + ? ? ? ? return -ENODEV;
>> > > +
>> > > + sport->port.line = be32_to_cpup(line) - 1;
>> >
>> > Hmmm, I really would like to be rid of this. ?Instead, if uarts must
>> > be enumerated, the driver should look for a /aliases/uart* property
>> > that matches the of_node. ?Doing it that way is already established in
>> > the OpenFirmware documentation, and it ensures there are no overlaps
>> > in the global namespace.
>> >
>>
>> I just gave one more try to avoid using 'aliases', and you gave a
>> 'no' again. ?Now, I know how hard you are on this. ?Okay, I start
>> thinking about your suggestion seriously :)
>>
>> > We do need some infrastructure to make that easier though. ?Would you
>> > have time to help put that together?
>> >
>> Ok, I will give it a try.
>>
>
> diff --git a/arch/arm/boot/dts/imx51-babbage.dts b/arch/arm/boot/dts/imx51-babbage.dts
> index da0381a..f4a5c3c 100644
> --- a/arch/arm/boot/dts/imx51-babbage.dts
> +++ b/arch/arm/boot/dts/imx51-babbage.dts
> @@ -18,6 +18,12 @@
> ? ? ? ?compatible = "fsl,imx51-babbage", "fsl,imx51";
> ? ? ? ?interrupt-parent = <&tzic>;
>
> + ? ? ? aliases {
> + ? ? ? ? ? ? ? serial0 = &uart0;
> + ? ? ? ? ? ? ? serial1 = &uart1;
> + ? ? ? ? ? ? ? serial2 = &uart2;
> + ? ? ? };
> +
Hmmm. David Gibson had tossed out an idea of automatically generating
aliases from labels. It may be time to revisit that idea.
David, perhaps using this format for a label should turn it into an
alias (prefix label with an asterisk):
*thealias: i2c at 12340000 { /*...*/ };
.... although that approach gets *really* hairy when considering that
different boards will want different enumeration. How would one
override an automatic alias defined by an included .dts file?
> ? ? ? ?chosen {
> ? ? ? ? ? ? ? ?bootargs = "console=ttymxc0,115200 root=/dev/mmcblk0p3 rootwait";
> ? ? ? ?};
> @@ -47,29 +53,29 @@
> ? ? ? ? ? ? ? ? ? ? ? ?reg = <0x70000000 0x40000>;
> ? ? ? ? ? ? ? ? ? ? ? ?ranges;
>
> - ? ? ? ? ? ? ? ? ? ? ? uart at 7000c000 {
> + ? ? ? ? ? ? ? ? ? ? ? uart2: uart at 7000c000 {
> ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?compatible = "fsl,imx51-uart", "fsl,imx21-uart";
> ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?reg = <0x7000c000 0x4000>;
> ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?interrupts = <33>;
> ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?id = <3>;
> - ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? fsl,has-rts-cts;
> + ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? fsl,uart-has-rtscts;
> ? ? ? ? ? ? ? ? ? ? ? ?};
> ? ? ? ? ? ? ? ?};
>
> - ? ? ? ? ? ? ? uart at 73fbc000 {
> + ? ? ? ? ? ? ? uart0: uart at 73fbc000 {
> ? ? ? ? ? ? ? ? ? ? ? ?compatible = "fsl,imx51-uart", "fsl,imx21-uart";
> ? ? ? ? ? ? ? ? ? ? ? ?reg = <0x73fbc000 0x4000>;
> ? ? ? ? ? ? ? ? ? ? ? ?interrupts = <31>;
> ? ? ? ? ? ? ? ? ? ? ? ?id = <1>;
> - ? ? ? ? ? ? ? ? ? ? ? fsl,has-rts-cts;
> + ? ? ? ? ? ? ? ? ? ? ? fsl,uart-has-rtscts;
> ? ? ? ? ? ? ? ?};
>
> - ? ? ? ? ? ? ? uart at 73fc0000 {
> + ? ? ? ? ? ? ? uart1: uart at 73fc0000 {
> ? ? ? ? ? ? ? ? ? ? ? ?compatible = "fsl,imx51-uart", "fsl,imx21-uart";
> ? ? ? ? ? ? ? ? ? ? ? ?reg = <0x73fc0000 0x4000>;
> ? ? ? ? ? ? ? ? ? ? ? ?interrupts = <32>;
> ? ? ? ? ? ? ? ? ? ? ? ?id = <2>;
> - ? ? ? ? ? ? ? ? ? ? ? fsl,has-rts-cts;
> + ? ? ? ? ? ? ? ? ? ? ? fsl,uart-has-rtscts;
> ? ? ? ? ? ? ? ?};
> ? ? ? ?};
>
> diff --git a/drivers/of/base.c b/drivers/of/base.c
> index 632ebae..13df5d2 100644
> --- a/drivers/of/base.c
> +++ b/drivers/of/base.c
> @@ -737,6 +737,37 @@ err0:
> ?EXPORT_SYMBOL(of_parse_phandles_with_args);
>
> ?/**
> + * ? ? of_get_device_index - Get device index by looking up "aliases" node
> + * ? ? @np: ? ?Pointer to device node that asks for device index
> + * ? ? @name: ?The device alias without index number
> + *
> + * ? ? Returns the device index if find it, else returns -ENODEV.
> + */
> +int of_get_device_index(struct device_node *np, const char *alias)
> +{
> + ? ? ? struct device_node *aliases = of_find_node_by_name(NULL, "aliases");
> + ? ? ? struct property *prop;
> + ? ? ? char name[32];
> + ? ? ? int index = 0;
> +
> + ? ? ? if (!aliases)
> + ? ? ? ? ? ? ? return -ENODEV;
> +
> + ? ? ? while (1) {
> + ? ? ? ? ? ? ? snprintf(name, sizeof(name), "%s%d", alias, index);
> + ? ? ? ? ? ? ? prop = of_find_property(aliases, name, NULL);
> + ? ? ? ? ? ? ? if (!prop)
> + ? ? ? ? ? ? ? ? ? ? ? return -ENODEV;
> + ? ? ? ? ? ? ? if (np == of_find_node_by_path(prop->value))
> + ? ? ? ? ? ? ? ? ? ? ? break;
> + ? ? ? ? ? ? ? index++;
> + ? ? ? }
Rather than parsing the alias strings everytime, it would probably be
better to preprocess all the properties in the aliases node and create
a lookup table of alias->node references that can be walked quickly
and trivially.
Also, when obtaining an enumeration for a device, you'll need to be
careful about what number gets returned. If the node doesn't match a
given alias, but aliases do exist for other devices of like type, then
you need to be careful not to assign a number already assigned to
another device via an alias (this of course assumes the driver
supports dynamics enumeration, which many drivers will). It would be
\> +
> + ? ? ? return index;
> +}
> +EXPORT_SYMBOL(of_get_device_index);
> +
> +/**
> ?* prom_add_property - Add a property to a node
> ?*/
> ?int prom_add_property(struct device_node *np, struct property *prop)
> diff --git a/drivers/tty/serial/imx.c b/drivers/tty/serial/imx.c
> index da436e0..852668f 100644
> --- a/drivers/tty/serial/imx.c
> +++ b/drivers/tty/serial/imx.c
> @@ -1271,18 +1271,18 @@ static int serial_imx_probe_dt(struct imx_port *sport,
> ? ? ? ?struct device_node *node = pdev->dev.of_node;
> ? ? ? ?const struct of_device_id *of_id =
> ? ? ? ? ? ? ? ? ? ? ? ?of_match_device(imx_uart_dt_ids, &pdev->dev);
> - ? ? ? const __be32 *line;
> + ? ? ? int line;
>
> ? ? ? ?if (!node)
> ? ? ? ? ? ? ? ?return -ENODEV;
>
> - ? ? ? line = of_get_property(node, "id", NULL);
> - ? ? ? if (!line)
> + ? ? ? line = of_get_device_index(node, "serial");
> + ? ? ? if (IS_ERR_VALUE(line))
> ? ? ? ? ? ? ? ?return -ENODEV;
Personally, it an alias isn't present, then I'd dynamically assign a port id.
>
> - ? ? ? sport->port.line = be32_to_cpup(line) - 1;
> + ? ? ? sport->port.line = line;
>
> - ? ? ? if (of_get_property(node, "fsl,has-rts-cts", NULL))
> + ? ? ? if (of_get_property(node, "fsl,uart-has-rtscts", NULL))
> ? ? ? ? ? ? ? ?sport->have_rtscts = 1;
>
> ? ? ? ?if (of_get_property(node, "fsl,irda-mode", NULL))
> diff --git a/include/linux/of.h b/include/linux/of.h
> index bfc0ed1..3153752 100644
> --- a/include/linux/of.h
> +++ b/include/linux/of.h
> @@ -213,6 +213,8 @@ extern int of_parse_phandles_with_args(struct device_node *np,
> ? ? ? ?const char *list_name, const char *cells_name, int index,
> ? ? ? ?struct device_node **out_node, const void **out_args);
>
> +extern int of_get_device_index(struct device_node *np, const char *alias);
> +
> ?extern int of_machine_is_compatible(const char *compat);
>
> ?extern int prom_add_property(struct device_node* np, struct property* prop);
>
> --
> Regards,
> Shawn
>
>
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
next prev parent reply other threads:[~2011-06-21 19:13 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-18 15:19 [PATCH 0/3] Add basic device support for imx51 babbage Shawn Guo
2011-06-18 15:19 ` [PATCH 1/3] serial/imx: add device tree support Shawn Guo
2011-06-18 16:19 ` Grant Likely
2011-06-19 7:02 ` Wolfram Sang
2011-06-19 7:30 ` Shawn Guo
2011-06-19 15:05 ` Grant Likely
2011-06-19 15:15 ` Rob Herring
2011-06-19 18:44 ` Grant Likely
2011-06-21 13:55 ` Shawn Guo
2011-06-21 18:32 ` Mitch Bradley
2011-06-21 18:42 ` Grant Likely
2011-06-21 18:53 ` Russell King - ARM Linux
2011-06-21 19:02 ` Grant Likely
2011-06-21 19:04 ` Mitch Bradley
2011-06-21 19:13 ` Grant Likely [this message]
2011-06-21 19:35 ` Mitch Bradley
2011-06-21 19:38 ` Grant Likely
2011-06-21 22:08 ` Mitch Bradley
2011-06-21 22:33 ` Grant Likely
2011-06-21 22:52 ` Segher Boessenkool
2011-06-21 22:58 ` Grant Likely
2011-06-22 15:33 ` Shawn Guo
2011-06-22 15:52 ` Grant Likely
2011-06-23 0:12 ` Shawn Guo
2011-06-23 3:35 ` Grant Likely
2011-06-23 18:38 ` Shawn Guo
2011-06-23 23:11 ` Grant Likely
2011-06-24 3:49 ` Shawn Guo
2011-06-24 4:05 ` Grant Likely
2011-06-18 16:21 ` Arnd Bergmann
2011-06-18 16:26 ` Grant Likely
2011-06-18 18:11 ` Arnd Bergmann
2011-06-19 7:41 ` Shawn Guo
2011-06-19 7:40 ` Shawn Guo
2011-06-18 15:19 ` [PATCH 2/3] net/fec: " Shawn Guo
2011-06-18 16:22 ` Grant Likely
2011-06-19 7:46 ` Shawn Guo
2011-06-18 18:27 ` Arnd Bergmann
2011-06-19 0:24 ` Grant Likely
2011-06-19 7:55 ` Shawn Guo
2011-06-19 11:39 ` Greg Ungerer
2011-06-19 12:11 ` Arnd Bergmann
2011-06-19 15:09 ` Rob Herring
2011-06-19 18:43 ` Grant Likely
2011-06-20 0:05 ` Greg Ungerer
2011-06-18 15:19 ` [PATCH 3/3] ARM: mx5: add basic device tree support for imx51 babbage Shawn Guo
2011-06-18 16:24 ` Grant Likely
2011-06-18 16:29 ` [PATCH 0/3] Add basic device " 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='BANLkTim4vunTm1176MRw3pqRZnunu4=9jg@mail.gmail.com' \
--to=grant.likely@secretlab.ca \
--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).