linux-kernel - 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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <6ED8E3B22081A4459DAC7699F3695FB732FD0B57@SW-EX-MBX02.diasemi.com>
Date:	Fri, 6 Sep 2013 10:47:58 +0000
From:	Steve Twiss <stwiss.opensource@...semi.com>
To:	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: 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

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