From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Alexandre Courbot <gnurou@gmail.com>,
ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 2/4] ACPI / gpio: Add support for naming GPIOs
Date: Thu, 20 Oct 2016 15:14:42 +0300 [thread overview]
Message-ID: <20161020121442.GF24289@lahna.fi.intel.com> (raw)
In-Reply-To: <CACRpkdYRWdd9anAcufadb-0sWSZ3reA-K+=z5Bc0Vk9dBrG29g@mail.gmail.com>
On Thu, Oct 20, 2016 at 02:06:42PM +0200, Linus Walleij wrote:
> On Thu, Sep 29, 2016 at 3:39 PM, Mika Westerberg
> <mika.westerberg@linux.intel.com> wrote:
>
> > DT has property 'gpio-line-names' to name GPIO lines the controller has if
> > present. Use this very same property in ACPI as well to provide nice names
> > for the GPIOS.
> >
> > Signed-off-by: Mika Westerberg <mika.westerberg@linux.intel.com>
>
> Oh wait:
>
> > +static void acpi_gpiochip_set_names(struct acpi_gpio_chip *achip)
> > +{
> > + struct gpio_chip *chip = achip->chip;
> > + struct gpio_device *gdev = chip->gpiodev;
> > + const char **names;
> > + int ret, i;
> > +
> > + ret = device_property_read_string_array(chip->parent, "gpio-line-names",
> > + NULL, 0);
> > + if (ret < 0)
> > + return;
> > +
> > + if (ret != gdev->ngpio) {
> > + dev_warn(chip->parent,
> > + "names %d do not match number of GPIOs %d\n", ret,
> > + gdev->ngpio);
> > + return;
> > + }
> > +
> > + names = kcalloc(gdev->ngpio, sizeof(*names), GFP_KERNEL);
> > + if (!names)
> > + return;
> > +
> > + ret = device_property_read_string_array(chip->parent, "gpio-line-names",
> > + names, gdev->ngpio);
> > + if (ret < 0) {
> > + dev_warn(chip->parent, "Failed to read GPIO line names\n");
> > + return;
> > + }
> > +
> > + /*
> > + * It is fine to assign the name, it will be allocated as long as
> > + * the ACPI device exists.
> > + */
> > + for (i = 0; i < gdev->ngpio; i++)
> > + gdev->descs[i].name = names[i];
> > +
> > + kfree(names);
> > +}
>
> Wouldn't this entire function work just as fine on device tree?
Now that you mentioned it, yes, I think it should work with DT as well.
> So should this snippet using device_property_* be moved into
> a file like gpiolib-devprop.c+gpiolib.h signature and get used from
> both gpiolib-of.c and gpiolib-acpi.c, replacing the DT-specific
> code in gpiolib-of.c?
Works for me :)
next prev parent reply other threads:[~2016-10-20 12:14 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-29 13:39 [PATCH v2 0/4] ACPI / gpio: Updates to properties Mika Westerberg
2016-09-29 13:39 ` [PATCH v2 1/4] ACPI / property: Allow holes in reference properties Mika Westerberg
2016-10-11 20:46 ` Rafael J. Wysocki
2016-10-20 12:00 ` Linus Walleij
2016-09-29 13:39 ` [PATCH v2 2/4] ACPI / gpio: Add support for naming GPIOs Mika Westerberg
2016-10-07 17:05 ` Andy Shevchenko
2016-10-09 15:01 ` Mika Westerberg
2016-10-09 17:08 ` Andy Shevchenko
2016-10-20 12:02 ` Linus Walleij
2016-10-20 12:08 ` Mika Westerberg
2016-10-20 12:06 ` Linus Walleij
2016-10-20 12:14 ` Mika Westerberg [this message]
2016-09-29 13:39 ` [PATCH v2 3/4] ACPI / gpio: Add hogging support Mika Westerberg
2016-10-20 12:09 ` Linus Walleij
2016-10-20 12:29 ` Mika Westerberg
2016-09-29 13:39 ` [PATCH v2 4/4] ACPI / gpio: Allow holes in list of GPIOs for a device Mika Westerberg
2016-10-20 12:10 ` Linus Walleij
2016-10-07 17:10 ` [PATCH v2 0/4] ACPI / gpio: Updates to properties 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=20161020121442.GF24289@lahna.fi.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=gnurou@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).