lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHp75Ve8oLeT=-_t96i_ctcmnM4kEPHD0cBjBroJTnYxwczBmw@mail.gmail.com>
Date:	Fri, 12 Jul 2013 14:29:16 +0300
From:	Andy Shevchenko <andy.shevchenko@...il.com>
To:	Wolfram Sang <wsa@...-dreams.de>
Cc:	Mark Brown <broonie@...nel.org>, Bin Gao <bin.gao@...ux.intel.com>,
	linux-i2c@...r.kernel.org,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Laurent Pinchart <laurent.pinchart@...asonboard.com>
Subject: Re: i2c: introduce i2c helper i2c_find_client_by_name()

On Fri, Jul 12, 2013 at 2:00 PM, Wolfram Sang <wsa@...-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.

--
With Best Regards,
Andy Shevchenko
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ