From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Alexandre Courbot <gnurou@gmail.com>,
linux-gpio@vger.kernel.org, Hans de Goede <hdegoede@redhat.com>,
linux-kernel@vger.kernel.org,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Jarkko Nikula <jarkko.nikula@linux.intel.com>,
linux-acpi@vger.kernel.org, Irina Tirdea <irina.tirdea@intel.com>,
Bastien Nocera <hadess@hadess.net>
Subject: Re: [PATCH v1 4/8] gpio: acpi: Even more tighten up ACPI GPIO lookups
Date: Thu, 23 Mar 2017 13:12:41 -0700 [thread overview]
Message-ID: <20170323201241.GB2502@dtor-ws> (raw)
In-Reply-To: <20170323194618.26548-5-andriy.shevchenko@linux.intel.com>
On Thu, Mar 23, 2017 at 09:46:14PM +0200, Andy Shevchenko wrote:
> The commit 10cf4899f8af ("gpiolib: tighten up ACPI legacy gpio lookups")
> prevents to getting same resource twice if the driver asks twice using same
s/same/different/
> connection ID.
>
> But the whole idea of fallback might bring some problems. Imagine the case when
> we have two versions of BIOS/hardware where in one _DSD is introduced along
> with GPIO resources, but the other one uses just plain GPIO resource for
> another purpose
>
> Case 1:
>
> Device (DEVX)
> {
> ...
> Name (_CRS, ResourceTemplate ()
> {
> GpioIo (Exclusive, PullUp, 0, 0, IoRestrictionInputOnly,
> "\\_SB.GPO0", 0, ResourceConsumer) {15}
> })
> Name (_DSD, Package ()
> {
> ToUUID("daffd814-6eba-4d8c-8a91-bc9bbf4aa301"),
> Package ()
> {
> Package () {"some-gpios", Package() {^DEVX, 0, 0, 0 }},
> }
> })
> }
>
> Case 2:
>
> Device (DEVX)
> {
> ...
> Name (_CRS, ResourceTemplate ()
> {
> GpioIo (Exclusive, PullUp, 0, 0, IoRestrictionInputOnly,
> "\\_SB.GPO0", 0, ResourceConsumer) {27}
> })
> }
>
> To prevent the possible misconfiguration tighten up even more ACPI GPIO lookups
> for case without connection ID provided.
I wonder if this will break Goodix. Irina, Bastien?
>
> In the past the issue had been triggered by "use mctrl_gpio helpers" series
> [1,2].
>
> Besides above, removal of the main logic of acpi_can_fallback_to_crs()
> eliminates a potential memory leak when the same device has been unbound and
> bound again.
Where? We'll reuse lookup table as ACPI device is still the same.
>
> [1] commit 4ef03d328769 ("tty/serial/8250: use mctrl_gpio helpers")
> [2] https://patchwork.kernel.org/patch/9283745/
>
> Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>
> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> ---
> drivers/gpio/gpiolib-acpi.c | 36 +-----------------------------------
> 1 file changed, 1 insertion(+), 35 deletions(-)
>
> diff --git a/drivers/gpio/gpiolib-acpi.c b/drivers/gpio/gpiolib-acpi.c
> index 21e4930ca2db..e516b7a0cc50 100644
> --- a/drivers/gpio/gpiolib-acpi.c
> +++ b/drivers/gpio/gpiolib-acpi.c
> @@ -1121,45 +1121,11 @@ int acpi_gpio_count(struct device *dev, const char *con_id)
> return count ? count : -ENOENT;
> }
>
> -struct acpi_crs_lookup {
> - struct list_head node;
> - struct acpi_device *adev;
> - const char *con_id;
> -};
> -
> -static DEFINE_MUTEX(acpi_crs_lookup_lock);
> -static LIST_HEAD(acpi_crs_lookup_list);
> -
> bool acpi_can_fallback_to_crs(struct acpi_device *adev, const char *con_id)
> {
> - struct acpi_crs_lookup *l, *lookup = NULL;
> -
> /* Never allow fallback if the device has properties */
> if (adev->data.properties || adev->driver_gpios)
> return false;
>
> - mutex_lock(&acpi_crs_lookup_lock);
> -
> - list_for_each_entry(l, &acpi_crs_lookup_list, node) {
> - if (l->adev == adev) {
> - lookup = l;
> - break;
> - }
> - }
> -
> - if (!lookup) {
> - lookup = kmalloc(sizeof(*lookup), GFP_KERNEL);
> - if (lookup) {
> - lookup->adev = adev;
> - lookup->con_id = kstrdup(con_id, GFP_KERNEL);
> - list_add_tail(&lookup->node, &acpi_crs_lookup_list);
> - }
> - }
> -
> - mutex_unlock(&acpi_crs_lookup_lock);
> -
> - return lookup &&
> - ((!lookup->con_id && !con_id) ||
> - (lookup->con_id && con_id &&
> - strcmp(lookup->con_id, con_id) == 0));
> + return con_id == NULL;
> }
> --
> 2.11.0
>
--
Dmitry
next prev parent reply other threads:[~2017-03-23 20:12 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-23 19:46 [PATCH v1 0/8] gpio: acpi: Make it working Andy Shevchenko
2017-03-23 19:46 ` [PATCH v1 1/8] gpiolib: Export gpiod_configure_flags() to internal users Andy Shevchenko
2017-03-23 19:46 ` [PATCH v1 2/8] gpio: acpi: Align acpi_find_gpio() with DT version Andy Shevchenko
2017-03-23 20:13 ` Dmitry Torokhov
2017-03-23 19:46 ` [PATCH v1 3/8] gpio: acpi: Do sanity check for GpioInt in acpi_find_gpio() Andy Shevchenko
2017-03-23 20:19 ` Dmitry Torokhov
2017-03-23 19:46 ` [PATCH v1 4/8] gpio: acpi: Even more tighten up ACPI GPIO lookups Andy Shevchenko
2017-03-23 20:12 ` Dmitry Torokhov [this message]
2017-03-24 10:46 ` Bastien Nocera
2017-03-28 16:31 ` Andy Shevchenko
2017-03-29 7:04 ` Dmitry Torokhov
2017-03-23 19:46 ` [PATCH v1 5/8] gpio: acpi: Synchronize acpi_find_gpio() and acpi_gpio_count() Andy Shevchenko
2017-03-24 15:55 ` Mika Westerberg
2017-03-23 19:46 ` [PATCH v1 6/8] gpio: acpi: Explain how to get GPIO descriptors in ACPI case Andy Shevchenko
2017-03-23 20:28 ` Dmitry Torokhov
2017-03-28 16:39 ` Andy Shevchenko
2017-03-29 7:12 ` Dmitry Torokhov
2017-03-29 15:04 ` Andy Shevchenko
2017-04-04 16:11 ` Andy Shevchenko
2017-04-04 17:31 ` Dmitry Torokhov
2017-04-04 17:59 ` Andy Shevchenko
2017-04-04 18:21 ` Dmitry Torokhov
2017-03-23 19:46 ` [PATCH v1 7/8] gpio: acpi: Factor out acpi_gpio_to_gpiod_flags() helper Andy Shevchenko
2017-03-23 19:46 ` [PATCH v1 8/8] gpio: acpi: Override GPIO initialization flags Andy Shevchenko
2017-03-24 13:48 ` [PATCH v1 0/8] gpio: acpi: Make it working Jarkko Nikula
2017-03-24 16:01 ` Mika Westerberg
2017-03-28 13:24 ` Linus Walleij
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=20170323201241.GB2502@dtor-ws \
--to=dmitry.torokhov@gmail.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=gnurou@gmail.com \
--cc=hadess@hadess.net \
--cc=hdegoede@redhat.com \
--cc=irina.tirdea@intel.com \
--cc=jarkko.nikula@linux.intel.com \
--cc=linus.walleij@linaro.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
/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).