linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Lauro Ramos Venancio <lauro.venancio@openbossa.org>,
	Aloisio Almeida Jr <aloisio.almeida@openbossa.org>,
	Samuel Ortiz <sameo@linux.intel.com>,
	linux-wireless@vger.kernel.org,
	Mika Westerberg <mika.westerberg@linux.intel.com>
Subject: Re: [PATCH v2 2/2] NFC: pn544: Add GPIO ACPI mapping table
Date: Fri, 10 Mar 2017 19:14:43 +0200	[thread overview]
Message-ID: <1489166083.20145.200.camel@linux.intel.com> (raw)
In-Reply-To: <20170307101521.23271-2-andriy.shevchenko@linux.intel.com>

On Tue, 2017-03-07 at 12:15 +0200, Andy Shevchenko wrote:
> In order to make GPIO ACPI library stricter prepare users of
> gpiod_get_index() to correctly behave when there no mapping is
> provided by firmware.
> 
> Here we add explicit mapping between _CRS GpioIo() resources and
> their names used in the driver.

While the first patch is correct, this one doesn't.

It missed index conversion when GPIO ACPI mapping table is present.

Please ignore both, I think I will make it similar to what I did for
st21nfca.

> 
> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> ---
> - assign mapping table only in ACPI case
>  drivers/nfc/pn544/i2c.c | 15 +++++++++++++++
>  1 file changed, 15 insertions(+)
> 
> diff --git a/drivers/nfc/pn544/i2c.c b/drivers/nfc/pn544/i2c.c
> index 2df3176205c4..bfe099f3d347 100644
> --- a/drivers/nfc/pn544/i2c.c
> +++ b/drivers/nfc/pn544/i2c.c
> @@ -874,11 +874,25 @@ static void pn544_hci_i2c_fw_work(struct
> work_struct *work)
>  	}
>  }
>  
> +static const struct acpi_gpio_params enable_gpios = { 1, 0, false };
> +static const struct acpi_gpio_params firmware_gpios = { 2, 0, false
> };
> +
> +static const struct acpi_gpio_mapping acpi_pn544_gpios[] = {
> +	{ "enable-gpios", &enable_gpios, 1 },
> +	{ "firmware-gpios", &firmware_gpios, 1 },
> +	{ },
> +};
> +
>  static int pn544_hci_i2c_acpi_request_resources(struct i2c_client
> *client)
>  {
>  	struct pn544_i2c_phy *phy = i2c_get_clientdata(client);
>  	struct gpio_desc *gpiod_en, *gpiod_fw;
>  	struct device *dev = &client->dev;
> +	int ret;
> +
> +	ret = acpi_dev_add_driver_gpios(ACPI_COMPANION(dev),
> acpi_pn544_gpios);
> +	if (ret)
> +		return ret;
>  
>  	/* Get EN GPIO from ACPI */
>  	gpiod_en = devm_gpiod_get_index(dev, "enable", 1,
> GPIOD_OUT_LOW);
> @@ -1092,6 +1106,7 @@ static int pn544_hci_i2c_remove(struct
> i2c_client *client)
>  		pdata->free_resources();
>  	}
>  
> +	acpi_dev_remove_driver_gpios(ACPI_COMPANION(&client->dev));
>  	return 0;
>  }
>  

-- 
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy

      reply	other threads:[~2017-03-10 17:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-07 10:15 [PATCH v2 1/2] NFC: pn544: Request GPIOs with proper connection IDs Andy Shevchenko
2017-03-07 10:15 ` [PATCH v2 2/2] NFC: pn544: Add GPIO ACPI mapping table Andy Shevchenko
2017-03-10 17:14   ` Andy Shevchenko [this message]

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=1489166083.20145.200.camel@linux.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=aloisio.almeida@openbossa.org \
    --cc=lauro.venancio@openbossa.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mika.westerberg@linux.intel.com \
    --cc=sameo@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).