linux-kernel - RE: DA9063 driver development

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: <A0A72D937C18F64E89EDAB73B0232777BAF39D2F@SW-EX-MBX02.diasemi.com>
Date:	Fri, 6 Sep 2013 10:50:18 +0000
From:	David Dajun Chen <david.chen@...semi.com>
To:	Steve Twiss <stwiss.opensource@...semi.com>,
	Mark Brown <broonie@...nel.org>,
	Philipp Zabel <p.zabel@...gutronix.de>
CC:	Lee Jones <lee.jones@...aro.org>,
	Samuel Ortiz <sameo@...ux.intel.com>,
	LKML <linux-kernel@...r.kernel.org>
Subject: RE: DA9063 driver development

Could copy me the mfd.c file of da9063 in the lkml?

-----Original Message-----
From: Steve Twiss
Sent: 06 September 2013 11:48
To: Mark Brown; Philipp Zabel
Cc: Lee Jones; Samuel Ortiz; LKML
Subject: DA9063 driver development

Hello,

I am late into the discussion about the DA9063 driver because I missed the e-mail thread around 24th July
(https://lkml.org/lkml/2013/7/24/460)
so I only recently noticed that a DA9063 driver from Philipp Zabel had been submitted and accepted to linux-next.

I also noted that this driver was using a previous patch-set as its baseline; sent by Krystian Garbaciak over a year ago. Given that this original patch-set was not accepted, and the production of the DA9063 chip has advanced since the last submission, we were holding off the final DA9063 driver until later.

As I discussed earlier in https://lkml.org/lkml/2013/6/28/170 I was in the process of getting this driver ready for submission to the kernel.

It is well understood that any early submission of our driver to the community (around v3.6) meant that this sort of external driver development could happen without any further input from Dialog. However, this driver:

- is based on something that is a year old and now out of date;
- it cannot support the most recent mass-production release of DA9063 silicon;

Is it possible to remove this driver from linux-next so these issues can be resolved by Dialog?

Regards,
Steve Twiss

Legal Disclaimer: This e-mail communication (and any attachment/s) is confidential and contains proprietary information, some or all of which may be legally privileged. It is intended solely for the use of the individual or entity to which it is addressed. Access to this email by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful.

Please consider the environment before printing this e-mail

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