From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Mika Westerberg <mika.westerberg@linux.intel.com>
Cc: "Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Hans de Goede <hdegoede@redhat.com>,
Wolfram Sang <wsa@the-dreams.de>
Subject: Re: [PATCH v2 4/4] i2c: allow specify device properties in i2c_board_info
Date: Wed, 1 Feb 2017 09:10:39 -0800 [thread overview]
Message-ID: <20170201171039.GB40045@dtor-ws> (raw)
In-Reply-To: <20170201152418.GQ17297@lahna.fi.intel.com>
On Wed, Feb 01, 2017 at 05:24:18PM +0200, Mika Westerberg wrote:
> On Tue, Jan 31, 2017 at 06:11:30PM -0800, Dmitry Torokhov wrote:
> > With many drivers converting to using generic device properties, it is
> > useful to provide array of device properties when instantiating new i2c
> > client via i2c_board_info and have them automatically added to the device
> > in question.
> >
> > Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
> > ---
> > drivers/i2c/i2c-core.c | 16 +++++++++++++++-
> > include/linux/i2c.h | 3 +++
> > 2 files changed, 18 insertions(+), 1 deletion(-)
> >
> > diff --git a/drivers/i2c/i2c-core.c b/drivers/i2c/i2c-core.c
> > index f009549f86a5..3897e78e5e9a 100644
> > --- a/drivers/i2c/i2c-core.c
> > +++ b/drivers/i2c/i2c-core.c
> > @@ -1335,15 +1335,29 @@ i2c_new_device(struct i2c_adapter *adap, struct i2c_board_info const *info)
> > client->dev.fwnode = info->fwnode;
> >
> > i2c_dev_set_name(adap, client);
> > +
> > + if (info->properties) {
> > + status = device_add_properties(&client->dev, info->properties);
>
> I don't remember anymore how it was but is the driver core supposed to
> free this automatically when the device is removed or should we deal
> this in the i2c-core instead?
>
It is done as part of device_del().
Thanks.
--
Dmitry
prev parent reply other threads:[~2017-02-01 17:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-01 2:11 [PATCH v2 0/4] Export APIs to copy device properties & more Dmitry Torokhov
2017-02-01 2:11 ` [PATCH v2 1/4] device property: export code duplicating array of property entries Dmitry Torokhov
2017-02-01 2:11 ` [PATCH v2 2/4] device property: allow to constify properties Dmitry Torokhov
2017-02-01 2:11 ` [PATCH v2 3/4] driver property: constify property arrays values Dmitry Torokhov
2017-02-01 14:42 ` Mika Westerberg
2017-02-01 17:09 ` Dmitry Torokhov
2017-02-01 2:11 ` [PATCH v2 4/4] i2c: allow specify device properties in i2c_board_info Dmitry Torokhov
2017-02-01 15:24 ` Mika Westerberg
2017-02-01 17:10 ` Dmitry Torokhov [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=20170201171039.GB40045@dtor-ws \
--to=dmitry.torokhov@gmail.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=hdegoede@redhat.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=rafael.j.wysocki@intel.com \
--cc=wsa@the-dreams.de \
/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