mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Lee Jones <lee.jones@linaro.org>
To: Javier Martinez Canillas <javier@osg.samsung.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] mfd: tps6105x: Add OF device ID table
Date: Wed, 15 Mar 2017 10:35:17 +0000	[thread overview]
Message-ID: <20170315103517.ro2zz55ulwabsepf@dell> (raw)
In-Reply-To: <20170221133435.25881-2-javier@osg.samsung.com>

On Tue, 21 Feb 2017, Javier Martinez Canillas wrote:

> The driver doesn't have a struct of_device_id table but supported devices
> are registered via Device Trees. This is working on the assumption that a
> I2C device registered via OF will always match a legacy I2C device ID and
> that the MODALIAS reported will always be of the form i2c:<device>.
> 
> But this could change in the future so the correct approach is to have a
> OF device ID table if the devices are registered via OF.
> 
> The compatible strings don't have a vendor prefix because that's how it's
> used currently, and changing this will be a Device Tree ABI break.
> 
> Signed-off-by: Javier Martinez Canillas <javier@osg.samsung.com>
> ---
> 
>  drivers/mfd/tps6105x.c | 8 ++++++++
>  1 file changed, 8 insertions(+)

Likewise.

> diff --git a/drivers/mfd/tps6105x.c b/drivers/mfd/tps6105x.c
> index baa12ea666fb..29f86b8eebc5 100644
> --- a/drivers/mfd/tps6105x.c
> +++ b/drivers/mfd/tps6105x.c
> @@ -173,9 +173,17 @@ static const struct i2c_device_id tps6105x_id[] = {
>  };
>  MODULE_DEVICE_TABLE(i2c, tps6105x_id);
>  
> +static const struct of_device_id tps6105x_of_match[] = {
> +	{ .compatible = "tps61050" },
> +	{ .compatible = "tps61052" },
> +	{ },
> +};
> +MODULE_DEVICE_TABLE(of, tps6105x_of_match);
> +
>  static struct i2c_driver tps6105x_driver = {
>  	.driver = {
>  		.name	= "tps6105x",
> +		.of_match_table = of_match_ptr(tps6105x_of_match),
>  	},
>  	.probe		= tps6105x_probe,
>  	.remove		= tps6105x_remove,

-- 
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog

  reply	other threads:[~2017-03-15 10:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-21 13:34 [PATCH 1/2] mfd: retu: " Javier Martinez Canillas
2017-02-21 13:34 ` [PATCH 2/2] mfd: tps6105x: " Javier Martinez Canillas
2017-03-15 10:35   ` Lee Jones [this message]
2017-03-10 13:23 ` [PATCH 1/2] mfd: retu: " Javier Martinez Canillas
2017-03-14 10:04   ` Lee Jones
2017-03-15 10:34 ` Lee Jones

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=20170315103517.ro2zz55ulwabsepf@dell \
    --to=lee.jones@linaro.org \
    --cc=javier@osg.samsung.com \
    --cc=linux-kernel@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®