linux-kernel - Re: Issue with porting i2c driver to k3.10 (iio)

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] [day] [month] [year] [list]

Date:	Sat, 06 Jul 2013 12:47:08 +0100
From:	Jonathan Cameron <jic23@...nel.org>
To:	Greg KH <gregkh@...uxfoundation.org>
CC:	Oleksandr Kravchenko <o.v.kravchenko@...ballogic.com>,
	linux-iio@...r.kernel.org, linux-kernel@...r.kernel.org,
	arnd@...db.de, jic23@....ac.uk
Subject: Re: Issue with porting i2c driver to k3.10 (iio)

On 07/04/2013 05:19 PM, Greg KH wrote:
> On Thu, Jul 04, 2013 at 04:16:43PM +0300, Oleksandr Kravchenko wrote:
>> Hi All,
>>
>> I wrote i2c driver for APDS-9300 light sensor in drivers/misc, but I have some
>> questions regarding upstreaming of it.
>> 1. It works properly in kernel-3.4, but it works very slow in kernel-3.10 (on
>> mutex and i2c operations, particulary on mutex_lock() and i2c_smbus_read_data
>> ()). Does anyone know why this issue may be occurred?
> 
> What is "slow"?  Have you run 'perf' on the driver to see where it is
> spending time?
> 
>> 2. Can I send this driver without using Industrial I/O framework?
> 
> No, why would you even want to?

Looks like a fairly standard light sensor so drivers/iio/light.

Actually very close in design to some of the TAOS parts such as those supported
by the tsl2563 driver if you want a reference driver to compare with.

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