From: Grant Likely <grant.likely@linaro.org>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Darren Hart <darren.hart@intel.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Aaron Lu <aaron.lu@intel.com>, Arnd Bergmann <arnd@arndb.de>,
devicetree@vger.kernel.org,
Linus Walleij <linus.walleij@linaro.org>,
Alexandre Courbot <gnurou@gmail.com>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Bryan Wu <cooloney@gmail.com>
Subject: Re: [PATCH v6 04/12] misc: at25: Make use of device property API
Date: Tue, 04 Nov 2014 14:18:26 +0000 [thread overview]
Message-ID: <20141104141826.36F8AC408F6@trevor.secretlab.ca> (raw)
In-Reply-To: <5019278.RtDq7RlWqt@vostro.rjw.lan>
On Tue, 21 Oct 2014 23:19:56 +0200
, "Rafael J. Wysocki" <rjw@rjwysocki.net>
wrote:
> From: Mika Westerberg <mika.westerberg@linux.intel.com>
>
> Make use of device property API in this driver so that both DT and ACPI
> based systems can use this driver.
>
> Signed-off-by: Mika Westerberg <mika.westerberg@linux.intel.com>
> Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
> ---
> drivers/misc/eeprom/at25.c | 34 +++++++++++++---------------------
> 1 file changed, 13 insertions(+), 21 deletions(-)
>
> Index: linux-pm/drivers/misc/eeprom/at25.c
> ===================================================================
> --- linux-pm.orig/drivers/misc/eeprom/at25.c
> +++ linux-pm/drivers/misc/eeprom/at25.c
> @@ -18,7 +18,7 @@
>
> #include <linux/spi/spi.h>
> #include <linux/spi/eeprom.h>
> -#include <linux/of.h>
> +#include <linux/property.h>
>
> /*
> * NOTE: this is an *EEPROM* driver. The vagaries of product naming
> @@ -301,35 +301,33 @@ static ssize_t at25_mem_write(struct mem
>
> /*-------------------------------------------------------------------------*/
>
> -static int at25_np_to_chip(struct device *dev,
> - struct device_node *np,
> - struct spi_eeprom *chip)
> +static int at25_fw_to_chip(struct device *dev, struct spi_eeprom *chip)
> {
> u32 val;
>
> memset(chip, 0, sizeof(*chip));
> - strncpy(chip->name, np->name, sizeof(chip->name));
> + strncpy(chip->name, "at25", sizeof(chip->name));
This line changes behaviour of the driver. It's possibly not a problem,
but it should be commented on and whether any due diligance has been
done to make sure it there isn't anything that depends on it.
Otherwise:
Acked-by: Grant Likely <grant.likely@linaro.org>
>
> - if (of_property_read_u32(np, "size", &val) == 0 ||
> - of_property_read_u32(np, "at25,byte-len", &val) == 0) {
> + if (device_property_read_u32(dev, "size", &val) == 0 ||
> + device_property_read_u32(dev, "at25,byte-len", &val) == 0) {
> chip->byte_len = val;
> } else {
> dev_err(dev, "Error: missing \"size\" property\n");
> return -ENODEV;
> }
>
> - if (of_property_read_u32(np, "pagesize", &val) == 0 ||
> - of_property_read_u32(np, "at25,page-size", &val) == 0) {
> + if (device_property_read_u32(dev, "pagesize", &val) == 0 ||
> + device_property_read_u32(dev, "at25,page-size", &val) == 0) {
> chip->page_size = (u16)val;
> } else {
> dev_err(dev, "Error: missing \"pagesize\" property\n");
> return -ENODEV;
> }
>
> - if (of_property_read_u32(np, "at25,addr-mode", &val) == 0) {
> + if (device_property_read_u32(dev, "at25,addr-mode", &val) == 0) {
> chip->flags = (u16)val;
> } else {
> - if (of_property_read_u32(np, "address-width", &val)) {
> + if (device_property_read_u32(dev, "address-width", &val)) {
> dev_err(dev,
> "Error: missing \"address-width\" property\n");
> return -ENODEV;
> @@ -350,7 +348,7 @@ static int at25_np_to_chip(struct device
> val);
> return -ENODEV;
> }
> - if (of_find_property(np, "read-only", NULL))
> + if (device_property_present(dev, "read-only"))
> chip->flags |= EE_READONLY;
> }
> return 0;
> @@ -360,21 +358,15 @@ static int at25_probe(struct spi_device
> {
> struct at25_data *at25 = NULL;
> struct spi_eeprom chip;
> - struct device_node *np = spi->dev.of_node;
> int err;
> int sr;
> int addrlen;
>
> /* Chip description */
> if (!spi->dev.platform_data) {
> - if (np) {
> - err = at25_np_to_chip(&spi->dev, np, &chip);
> - if (err)
> - return err;
> - } else {
> - dev_err(&spi->dev, "Error: no chip description\n");
> - return -ENODEV;
> - }
> + err = at25_fw_to_chip(&spi->dev, &chip);
> + if (err)
> + return err;
> } else
> chip = *(struct spi_eeprom *)spi->dev.platform_data;
>
>
next prev parent reply other threads:[~2014-11-04 14:18 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-21 21:08 [PATCH v6 00/12] Add ACPI _DSD and unified device properties support Rafael J. Wysocki
2014-10-21 21:09 ` [PATCH v6 01/12] ACPI: Add support for device specific properties Rafael J. Wysocki
2014-10-21 21:15 ` [PATCH v6 02/12] Driver core: Unified device properties interface for platform firmware Rafael J. Wysocki
2014-11-03 15:40 ` Grant Likely
2014-11-03 22:04 ` Rafael J. Wysocki
[not found] ` <3645687.BsyGDrJDrU-sKB8Sp2ER+y1GS7QM15AGw@public.gmane.org>
2014-11-04 17:01 ` Grant Likely
[not found] ` <CACxGe6uv0TmoZivL3ESw+oRW-OjqakLP4KBnDrwJXzQ2ku8ZLA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-11-04 21:29 ` Rafael J. Wysocki
2014-11-04 15:51 ` Grant Likely
[not found] ` <20141104155112.6FC67C423D0-WNowdnHR2B42iJbIjFUEsiwD8/FfD2ys@public.gmane.org>
2014-11-04 16:20 ` Rafael J. Wysocki
[not found] ` <2127128.VT1Iq03xz1-sKB8Sp2ER+y1GS7QM15AGw@public.gmane.org>
2014-11-04 16:38 ` [Update][PATCH " Rafael J. Wysocki
2014-10-21 21:19 ` [PATCH v6 03/12] ACPI: Allow drivers to match using Device Tree compatible property Rafael J. Wysocki
2014-10-21 21:19 ` [PATCH v6 04/12] misc: at25: Make use of device property API Rafael J. Wysocki
2014-11-04 14:18 ` Grant Likely [this message]
[not found] ` <20141104141826.36F8AC408F6-WNowdnHR2B42iJbIjFUEsiwD8/FfD2ys@public.gmane.org>
2014-11-04 14:38 ` Mika Westerberg
2014-11-04 15:04 ` Grant Likely
2014-11-04 16:19 ` Rafael J. Wysocki
[not found] ` <4645043.WOkgNMSUuO-sKB8Sp2ER+y1GS7QM15AGw@public.gmane.org>
2014-11-04 16:07 ` Mika Westerberg
2014-10-21 21:20 ` [PATCH v6 05/12] gpio / ACPI: Add support for _DSD device properties Rafael J. Wysocki
2014-10-21 21:21 ` [PATCH v6 06/12] gpio: sch: Consolidate core and resume banks Rafael J. Wysocki
2014-10-21 21:21 ` [PATCH v6 07/12] leds: leds-gpio: Add support for GPIO descriptors Rafael J. Wysocki
2014-10-21 21:22 ` [PATCH v6 08/12] input: gpio_keys_polled: " Rafael J. Wysocki
2014-10-21 21:29 ` [PATCH v6 09/12] Driver core: Unified interface for firmware node properties Rafael J. Wysocki
2014-11-04 16:43 ` [Update][PATCH " Rafael J. Wysocki
2014-10-21 21:33 ` [PATCH v6 10/12] gpio: Support for unified device properties interface Rafael J. Wysocki
2014-10-21 21:35 ` [PATCH v6 11/12] leds: leds-gpio: Make use of device property API Rafael J. Wysocki
2014-10-21 21:37 ` [PATCH v6 12/12] input: gpio_keys_polled: " Rafael J. Wysocki
2014-10-24 22:10 ` [PATCH v6 00/12] Add ACPI _DSD and unified device properties support Rafael J. Wysocki
2014-11-04 15:49 ` Grant Likely
2014-11-04 16:20 ` Rafael J. Wysocki
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=20141104141826.36F8AC408F6@trevor.secretlab.ca \
--to=grant.likely@linaro.org \
--cc=aaron.lu@intel.com \
--cc=arnd@arndb.de \
--cc=cooloney@gmail.com \
--cc=darren.hart@intel.com \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=gnurou@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linus.walleij@linaro.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=rjw@rjwysocki.net \
/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