public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa@the-dreams.de>
To: Bin Gao <bin_gao@linux.intel.com>
Cc: Bin Gao <bin.gao@linux.intel.com>,
	Andy Shevchenko <andy.shevchenko@gmail.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: Sun, 23 Jun 2013 14:43:18 +0200	[thread overview]
Message-ID: <20130623124316.GA3025@katana> (raw)
In-Reply-To: <51C4EF85.7010607@linux.intel.com>

[-- Attachment #1: Type: text/plain, Size: 773 bytes --]


> >I also wonder about the need to unregister. I have to admit I don't know
> >much about I2C handling in v4l2. But if it requires unregistering from
> >i2c core and registering to v4l2 core, then it sounds to me like we
> >could check if there is a more fundamential cleanup needed? Deferring
> >for now, looks like an issue worth looking at, yet there are other
> >things in the queue first.
> >
> 
> Platform codes are supposed to call i2c_register_board_info() or
> i2c_new_device() to register devices, we don't want to change this.

Exactly.

> Not sure v4l2 can still take over the devices without
> unregistering/registering. Need look deeply into the v4l2 code...

That would help, I currently don't have time for that.

Thanks,

   Wolfram

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2013-06-23 12:41 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 [this message]
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
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=20130623124316.GA3025@katana \
    --to=wsa@the-dreams.de \
    --cc=andy.shevchenko@gmail.com \
    --cc=bin.gao@linux.intel.com \
    --cc=bin_gao@linux.intel.com \
    --cc=linux-i2c@vger.kernel.org \
    --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