linux-kernel - Re: [PATCH V2] misc : ROHM BH1780GLI Ambient light sensor Driver

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20100601135430.9c8c28df.akpm@linux-foundation.org>
Date:	Tue, 1 Jun 2010 13:54:30 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Jonathan Cameron <kernel@...23.retrosnub.co.uk>
Cc:	Hemanth V <hemanthv@...com>, linux-kernel@...r.kernel.org,
	linux-omap@...r.kernel.org, Daniel Mack <daniel@...aq.de>,
	Jonathan Cameron <jic23@....ac.uk>,
	Wolfram Sang <w.sang@...gutronix.de>
Subject: Re: [PATCH V2] misc : ROHM BH1780GLI Ambient light sensor Driver

On Tue, 01 Jun 2010 21:39:10 +0100
Jonathan Cameron <kernel@...23.retrosnub.co.uk> wrote:

> > 
> > It would be most useful if the changelog were to fully describe the
> > proposed kernel<->userspace interface.  That's the most important part
> > of the driver, because it's the only part we can never change.
> > 
> > There is a desultory effort to maintain sysfs API descriptions under
> > Documentation/ABI/.  I'd have thought that it would be appropriate to
> > document this driver's ABI in there.
> Agreed, but we get back to the debate of what we should standardise on.

I'd suggest standardising on one of the existing drivers.  That way we
have two compliant drivers and only need to change (n-2) others.  If we
pick some new standard then we need to change (n) drivers.

And we can't change the drivers, really.  They'd all end up needing to
provide two interfaces: one for the shiny-new-standard and one legacy.

> The main point of ALS before it died was exactly putting this standardization
> in place (admittedly the interface was slightly different from what we
> are proposing in IIO, but that was before Greg pointed out that sharing
> with hwmon would be a good idea!)
> 
> I have to admit I'm a little loath to spend too much time on this given
> the amount of time wasted previously (ALS).

Well, it's not a waste.  This is very important!  We appear to be
making a big mess which we can never fix up.

--
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/