From: rnayak@ti.com (Rajendra Nayak)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/5] mfd: mc13xxx: add device tree probe support
Date: Tue, 29 Nov 2011 13:53:31 +0530 [thread overview]
Message-ID: <4ED49683.10609@ti.com> (raw)
In-Reply-To: <1322487439-27254-2-git-send-email-shawn.guo@linaro.org>
[]...
> +};
> +MODULE_DEVICE_TABLE(of, mc13xxx_dt_ids);
> +
> static int mc13xxx_probe(struct spi_device *spi)
> {
> + struct device_node *np = spi->dev.of_node;
> + const struct of_device_id *of_id;
> + struct spi_driver *sdrv = to_spi_driver(spi->dev.driver);
> struct mc13xxx *mc13xxx;
> struct mc13xxx_platform_data *pdata = dev_get_platdata(&spi->dev);
> enum mc13xxx_id id;
> int ret;
>
> - if (!pdata) {
> - dev_err(&spi->dev, "invalid platform data\n");
> - return -EINVAL;
> - }
> + of_id = of_match_device(mc13xxx_dt_ids,&spi->dev);
> + if (of_id)
> + sdrv->id_table =&mc13xxx_device_id[(enum mc13xxx_id) of_id->data];
>
> mc13xxx = kzalloc(sizeof(*mc13xxx), GFP_KERNEL);
> if (!mc13xxx)
> @@ -735,6 +787,15 @@ static int mc13xxx_probe(struct spi_device *spi)
> if (ret)
> goto err_mask;
>
> + mc13xxx->irq_gpio = of_get_named_gpio(np, "mc13xxx-irq-gpios", 0);
> + if (gpio_is_valid(mc13xxx->irq_gpio)) {
> + ret = gpio_request_one(mc13xxx->irq_gpio, GPIOF_IN,
> + "mc13xxx-irq");
> + if (ret)
> + goto err_mask;
> + spi->irq = gpio_to_irq(mc13xxx->irq_gpio);
This seems wrong, because its adding information about the irq actually
being a gpio within the driver (which was otherwise hidden by the board
files doing a gpio_to_irq()). What happens if on some device this is
actually hooked to an irq line instead of a gpio?
There should be a better way to do this using Device tree.
WARNING: multiple messages have this Message-ID (diff)
From: Rajendra Nayak <rnayak-l0cyMroinI0@public.gmane.org>
To: Shawn Guo <shawn.guo-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
Cc: "Sascha Hauer" <s.hauer-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>,
"Samuel Ortiz" <sameo-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>,
devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org,
"Mark Brown"
<broonie-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org>,
"Uwe Kleine-König"
<u.kleine-koenig-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>,
"Liam Girdwood" <lrg-l0cyMroinI0@public.gmane.org>,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: Re: [PATCH 1/5] mfd: mc13xxx: add device tree probe support
Date: Tue, 29 Nov 2011 13:53:31 +0530 [thread overview]
Message-ID: <4ED49683.10609@ti.com> (raw)
In-Reply-To: <1322487439-27254-2-git-send-email-shawn.guo-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
[]...
> +};
> +MODULE_DEVICE_TABLE(of, mc13xxx_dt_ids);
> +
> static int mc13xxx_probe(struct spi_device *spi)
> {
> + struct device_node *np = spi->dev.of_node;
> + const struct of_device_id *of_id;
> + struct spi_driver *sdrv = to_spi_driver(spi->dev.driver);
> struct mc13xxx *mc13xxx;
> struct mc13xxx_platform_data *pdata = dev_get_platdata(&spi->dev);
> enum mc13xxx_id id;
> int ret;
>
> - if (!pdata) {
> - dev_err(&spi->dev, "invalid platform data\n");
> - return -EINVAL;
> - }
> + of_id = of_match_device(mc13xxx_dt_ids,&spi->dev);
> + if (of_id)
> + sdrv->id_table =&mc13xxx_device_id[(enum mc13xxx_id) of_id->data];
>
> mc13xxx = kzalloc(sizeof(*mc13xxx), GFP_KERNEL);
> if (!mc13xxx)
> @@ -735,6 +787,15 @@ static int mc13xxx_probe(struct spi_device *spi)
> if (ret)
> goto err_mask;
>
> + mc13xxx->irq_gpio = of_get_named_gpio(np, "mc13xxx-irq-gpios", 0);
> + if (gpio_is_valid(mc13xxx->irq_gpio)) {
> + ret = gpio_request_one(mc13xxx->irq_gpio, GPIOF_IN,
> + "mc13xxx-irq");
> + if (ret)
> + goto err_mask;
> + spi->irq = gpio_to_irq(mc13xxx->irq_gpio);
This seems wrong, because its adding information about the irq actually
being a gpio within the driver (which was otherwise hidden by the board
files doing a gpio_to_irq()). What happens if on some device this is
actually hooked to an irq line instead of a gpio?
There should be a better way to do this using Device tree.
next prev parent reply other threads:[~2011-11-29 8:23 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-28 13:37 [PATCH 0/5] Add device tree support for mc13892 regulator driver Shawn Guo
2011-11-28 13:37 ` Shawn Guo
2011-11-28 13:37 ` [PATCH 1/5] mfd: mc13xxx: add device tree probe support Shawn Guo
2011-11-28 13:37 ` Shawn Guo
2011-11-29 8:23 ` Rajendra Nayak [this message]
2011-11-29 8:23 ` Rajendra Nayak
2011-11-30 8:12 ` Shawn Guo
2011-11-30 8:12 ` Shawn Guo
2011-11-28 13:37 ` [PATCH 2/5] regulator: fix label names used in device tree bindings Shawn Guo
2011-11-28 13:37 ` Shawn Guo
2011-11-28 19:02 ` Mark Brown
2011-11-28 19:02 ` Mark Brown
2011-11-29 8:25 ` Rajendra Nayak
2011-11-29 8:25 ` Rajendra Nayak
2011-11-28 13:37 ` [PATCH 3/5] regulator: pass device_node to of_get_regulator_init_data() Shawn Guo
2011-11-28 13:37 ` Shawn Guo
2011-11-28 13:34 ` Mark Brown
2011-11-28 13:34 ` Mark Brown
2011-11-28 14:03 ` Shawn Guo
2011-11-28 14:03 ` Shawn Guo
2011-11-28 13:37 ` [PATCH 4/5] regulator: mc13892: add device tree probe support Shawn Guo
2011-11-28 13:37 ` Shawn Guo
2011-11-28 13:35 ` Mark Brown
2011-11-28 13:35 ` Mark Brown
2011-11-28 14:08 ` Shawn Guo
2011-11-28 14:08 ` Shawn Guo
2011-11-28 13:37 ` [PATCH 5/5] arm/imx: add mc13892 support into imx51-babbage.dts Shawn Guo
2011-11-28 13:37 ` Shawn Guo
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=4ED49683.10609@ti.com \
--to=rnayak@ti.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.