linux-kernel - Re: [PATCH] staging:iio:proof of concept in kernel interface.

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: <20111014193314.GE2931@opensource.wolfsonmicro.com>
Date:	Fri, 14 Oct 2011 20:33:14 +0100
From:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
To:	Jonathan Cameron <jic23@....ac.uk>
Cc:	linux-kernel@...r.kernel.org, linux-iio@...r.kernel.org,
	zdevai@...il.com, linus.walleij@...aro.org
Subject: Re: [PATCH] staging:iio:proof of concept in kernel interface.

On Fri, Oct 14, 2011 at 04:59:28PM +0100, Jonathan Cameron wrote:

> I'm trying to work out what our equivalent of the clk finding api is.

> The best match pair to match on I can come up with is:

> part name: iio_dev.name

> dev_name of underlying hardware if specified.
> dev_name(iio_dev->dev.parent)
> This matching source can be overridden by an optional callback if we
> unique matching is achievable in some other way for the device.

For the existing APIs doing this the device used for the request is the
client device, not the providing device.  The APIs then have a mapping
table (clkdev for most of the clk APIs) which means that boards can then
assign providers to users without needing either of the drivers to know
what's going on, though of course they can be coded that way.
--
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/