mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Samuel Ortiz <sameo@linux.intel.com>
To: Steve Twiss <stwiss.opensource@diasemi.com>
Cc: Mark Brown <broonie@kernel.org>,
	Philipp Zabel <p.zabel@pengutronix.de>,
	Lee Jones <lee.jones@linaro.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: DA9063 driver development
Date: Fri, 6 Sep 2013 13:08:18 +0200	[thread overview]
Message-ID: <20130906110818.GA3696@zurbaran> (raw)
In-Reply-To: <6ED8E3B22081A4459DAC7699F3695FB732FD0B57@SW-EX-MBX02.diasemi.com>

Hi Steve,

See my answers below:

On Fri, Sep 06, 2013 at 10:47:58AM +0000, Steve Twiss wrote:
> 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?
Unfortunately it's too late for that. I sent a pull request to Linus
with this driver included, so I expect it to hit Linus' tree anytime
soon.
That means that it will be part of the 3.12-rc1 release. The good news
here is that we have about 8 weeks to modify it to match your recent
development, before 3.12 is released.
I would really prefer to modify the now existing driver and improve it,
rather than revert it.

Cheers,
Samuel.





> Regards,
> Steve Twiss
> 

-- 
Intel Open Source Technology Centre
http://oss.intel.com/

  parent reply	other threads:[~2013-09-06 11:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-06 10:47 Steve Twiss
2013-09-06 10:50 ` David Dajun Chen
2013-09-06 11:08 ` Samuel Ortiz [this message]
2013-09-06 11:20 ` Mark Brown

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20130906110818.GA3696@zurbaran \
    --to=sameo@linux.intel.com \
    --cc=broonie@kernel.org \
    --cc=lee.jones@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=p.zabel@pengutronix.de \
    --cc=stwiss.opensource@diasemi.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®