From: Lars Poeschel <poeschel@lemonage.de>
To: devicetree@vger.kernel.org, Samuel Ortiz <sameo@linux.intel.com>,
"open list:NFC SUBSYSTEM" <linux-wireless@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>
Cc: Johan Hovold <johan@kernel.org>
Subject: [PING] [PATCH v5 1/7] nfc: pn533: i2c: "pn532" as dt compatible string
Date: Thu, 28 Feb 2019 11:48:01 +0100 [thread overview]
Message-ID: <20190228104801.GA14788@lem-wkst-02.lemonage> (raw)
In-Reply-To: <20190111161812.26325-1-poeschel@lemonage.de>
A gentle ping on this whole patch series.
Regards,
Lars
On Fri, Jan 11, 2019 at 05:18:04PM +0100, Lars Poeschel wrote:
> It is favourable to have one unified compatible string for devices that
> have multiple interfaces. So this adds simply "pn532" as the devicetree
> binding compatible string and makes a note that the old ones are
> deprecated.
>
> Cc: Johan Hovold <johan@kernel.org>
> Signed-off-by: Lars Poeschel <poeschel@lemonage.de>
> ---
> Changes in v3:
> - This patch is new in v3
>
> drivers/nfc/pn533/i2c.c | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/drivers/nfc/pn533/i2c.c b/drivers/nfc/pn533/i2c.c
> index 4389eb4c8d0b..f4eae9dd5305 100644
> --- a/drivers/nfc/pn533/i2c.c
> +++ b/drivers/nfc/pn533/i2c.c
> @@ -258,6 +258,11 @@ static int pn533_i2c_remove(struct i2c_client *client)
> }
>
> static const struct of_device_id of_pn533_i2c_match[] = {
> + { .compatible = "nxp,pn532", },
> + /*
> + * NOTE: The use of the compatibles with the trailing "...-i2c" is
> + * deprecated and will be removed.
> + */
> { .compatible = "nxp,pn533-i2c", },
> { .compatible = "nxp,pn532-i2c", },
> {},
> --
> 2.20.1
>
next prev parent reply other threads:[~2019-02-28 10:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-11 16:18 [PATCH v5 1/7] nfc: pn533: i2c: "pn532" as dt compatible string Lars Poeschel
2019-01-11 16:18 ` [PATCH v5 2/7] nfc: pn532_uart: Add NXP PN532 to devicetree docs Lars Poeschel
2019-01-15 19:59 ` Rob Herring
2019-01-24 10:02 ` Lars Poeschel
2019-01-11 16:18 ` [PATCH v5 3/7] nfc: pn533: Add dev_up/dev_down hooks to phy_ops Lars Poeschel
2019-01-11 16:18 ` [PATCH v5 4/7] nfc: pn533: Split pn533 init & nfc_register Lars Poeschel
2019-01-11 16:18 ` [PATCH v5 5/7] nfc: pn533: add UART phy driver Lars Poeschel
2019-01-11 16:18 ` [PATCH v5 6/7] nfc: pn533: Add autopoll capability Lars Poeschel
2019-01-11 16:18 ` [PATCH v5 7/7] nfc: pn532_uart: Make use of pn532 autopoll Lars Poeschel
2019-02-28 10:48 ` Lars Poeschel [this message]
2019-04-03 9:47 ` [PING 2] [PATCH v5 1/7] nfc: pn533: i2c: "pn532" as dt compatible string Lars Poeschel
2019-08-05 12:42 ` Johan Hovold
2019-08-12 7:40 ` Lars Poeschel
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=20190228104801.GA14788@lem-wkst-02.lemonage \
--to=poeschel@lemonage.de \
--cc=devicetree@vger.kernel.org \
--cc=johan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--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