From: Wolfram Sang <wsa@the-dreams.de>
To: Mika Westerberg <mika.westerberg@linux.intel.com>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
Stephen Warren <swarren@wwwdotorg.org>,
linux-i2c@vger.kernel.org, linux-acpi@vger.kernel.org,
linux-kernel@vger.kernel.org,
Jerry Snitselaar <jerry.snitselaar@oracle.com>
Subject: Re: [PATCH] i2c: move of helpers into the core
Date: Tue, 20 Aug 2013 16:30:43 +0200 [thread overview]
Message-ID: <20130820143043.GA2993@katana> (raw)
In-Reply-To: <20130820092813.GW4898@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1811 bytes --]
On Tue, Aug 20, 2013 at 12:28:13PM +0300, Mika Westerberg wrote:
> [Added Jerry as he found out a problem when acpi_i2c is being build as a
> module, this should solve it as well.]
>
> On Tue, Aug 20, 2013 at 01:25:27AM +0200, Rafael J. Wysocki wrote:
> > On Monday, August 19, 2013 04:56:19 PM Stephen Warren wrote:
> > > On 08/19/2013 05:04 PM, Rafael J. Wysocki wrote:
> > > > On Monday, August 19, 2013 03:19:18 PM Wolfram Sang wrote:
> > > >> I2C of helpers used to live in of_i2c.c but experience (from SPI) shows
> > > >> that it is much cleaner to have this in the core. This also removes a
> > > >> circular dependency between the helpers and the core, and so we can
> > > >> finally register child nodes in the core instead of doing this manually
> > > >> in each driver. So, fix the drivers and documentation, too.
> > > >
> > > > Perhaps we should do the analogous for ACPI then?
>
> Here is the ACPI version based on the current patch from Wolfram (there is
> a compile error because of missing dummy implementation of
> of_i2c_register_devices())
>
> From: Mika Westerberg <mika.westerberg@linux.intel.com>
> Subject: [PATCH] i2c: move ACPI helpers into the core
>
> This follows what has already been done for the DeviceTree helpers. Move
> the ACPI helpers from drivers/acpi/acpi_i2c.c to the I2C core and update
> documentation accordingly.
>
> This also solves a problem reported by Jerry Snitselaar that we can't build
> the ACPI I2C helpers as a module.
>
> Signed-off-by: Mika Westerberg <mika.westerberg@linux.intel.com>
Nice, one thing, though:
> /* create pre-declared device nodes */
> of_i2c_register_devices(adap);
> + acpi_i2c_register_devices(adap);
I prefer the if (IS_ENABLED()) solution and will use this in my V2 as
well.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-08-20 14:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1376918361-7014-1-git-send-email-wsa@the-dreams.de>
2013-08-19 17:59 ` [PATCH RESEND] i2c: move of helpers into the core Wolfram Sang
2013-08-19 18:22 ` Sylwester Nawrocki
2013-08-19 18:56 ` Wolfram Sang
2013-08-19 19:46 ` Thierry Reding
2013-08-19 21:16 ` Wolfram Sang
2013-08-19 20:10 ` Felipe Balbi
2013-08-19 22:01 ` Rob Herring
[not found] ` <3792014.HtzPVmLjnf@vostro.rjw.lan>
[not found] ` <5212A293.2030903@wwwdotorg.org>
2013-08-19 23:25 ` [PATCH] " Rafael J. Wysocki
2013-08-20 9:28 ` Mika Westerberg
2013-08-20 12:31 ` Rafael J. Wysocki
2013-08-20 14:30 ` Wolfram Sang [this message]
2013-08-21 7:54 ` Mika Westerberg
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=20130820143043.GA2993@katana \
--to=wsa@the-dreams.de \
--cc=jerry.snitselaar@oracle.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=rjw@sisk.pl \
--cc=swarren@wwwdotorg.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;
as well as URLs for NNTP newsgroup(s).