public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Wolfram Sang <wsa@the-dreams.de>, Mark Brown <broonie@kernel.org>,
	Bin Gao <bin.gao@linux.intel.com>,
	linux-i2c@vger.kernel.org,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: i2c: introduce i2c helper i2c_find_client_by_name()
Date: Fri, 12 Jul 2013 13:35:51 +0200	[thread overview]
Message-ID: <4066449.W80oPjbVFF@avalon> (raw)
In-Reply-To: <CAHp75Ve8oLeT=-_t96i_ctcmnM4kEPHD0cBjBroJTnYxwczBmw@mail.gmail.com>

Hi Andy,

On Friday 12 July 2013 14:29:16 Andy Shevchenko wrote:
> On Fri, Jul 12, 2013 at 2:00 PM, Wolfram Sang <wsa@the-dreams.de> wrote:
> >> Briefly looking into ACPI tables we have and mechanisms that we can
> >> use in ACPI case, I doubt we may apply all the ideas, probably some of
> >> them, though I didn't get yet where to read about in details. What I
> >> could say now is that the patch provided by Bin Gao is definitely no
> >> go.
> > 
> > Laurent explained to me what V4L did and now does. It used to be the way
> > tha V4L drivers did register I2C slaves according to platform_data. Now,
> > with DT the slaves get instanciated earlier, so they now use notifiers
> > to know when the slaves are in place. Something like this should
> > probably be done here, too, instead of unregistering and re-registering.
> 
> Yes, seems right way to go.
> I think ACPI case can use V4L2 async API somehow, though it has its
> own event model.
> I'll talk to Sakari Ailus to sync.

Do you have any pointer to the relevant parts of the ACPI specification ?

-- 
Regards,

Laurent Pinchart


  reply	other threads:[~2013-07-12 11:35 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-06 18:33 i2c: introduce i2c helper i2c_find_client_by_name() Bin Gao
2013-06-06 20:32 ` Andy Shevchenko
2013-06-06 21:26   ` Bin Gao
2013-06-09 19:53     ` Andy Shevchenko
2013-06-11 17:11       ` Bin Gao
2013-06-14  7:29         ` Andy Shevchenko
2013-06-14 19:00           ` Bin Gao
2013-06-19 10:13             ` Wolfram Sang
2013-06-22  0:27               ` Bin Gao
2013-06-23 12:43                 ` Wolfram Sang
2013-07-05 19:55 ` Mark Brown
2013-07-12 10:54   ` Andy Shevchenko
2013-07-12 11:00     ` Wolfram Sang
2013-07-12 11:02       ` Laurent Pinchart
2013-07-12 11:29       ` Andy Shevchenko
2013-07-12 11:35         ` Laurent Pinchart [this message]
2013-07-12 11:56           ` Andy Shevchenko

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=4066449.W80oPjbVFF@avalon \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=andy.shevchenko@gmail.com \
    --cc=bin.gao@linux.intel.com \
    --cc=broonie@kernel.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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