From: Jonathan Cameron <jic23@cam.ac.uk>
To: "Song, Barry" <Barry.Song@analog.com>
Cc: linux-iio@vger.kernel.org, "Zhang,
Sonic" <Sonic.Zhang@analog.com>,
"Hennerich, Michael" <Michael.Hennerich@analog.com>,
Manuel Stahl <manuel.stahl@iis.fraunhofer.de>
Subject: Re: IIO driver merge plans (for next merge window)
Date: Tue, 27 Apr 2010 10:27:22 +0100 [thread overview]
Message-ID: <4BD6ADFA.4050500@cam.ac.uk> (raw)
In-Reply-To: <0F1B54C89D5F954D8535DB252AF412FA048553F4@chinexm1.ad.analog.com>
On 04/27/10 04:20, Song, Barry wrote:
> Drivers that passed debugging and testing on hardware can be pushed
> to mainline. By now, ADIS16300 and ADIS16400 drivers are on the
> list. But the problem is they are based on old abi, will you change
> codes to match new abi? If no, we can update codes after you merge
> the new abi into mainline.
Sure. I'll take a look at those and see what the best merge technique
is. Hopefully we can tack those on to the end of the abi patch series
and do it in two stages.
Jonathan
> Thanks
> Barry
>
> -----Original Message-----
> From: Jonathan Cameron [mailto:jic23@cam.ac.uk]
> Sent: Tue 4/27/2010 4:16 AM
> To: linux-iio@vger.kernel.org
> Cc: Song, Barry; Zhang, Sonic; Hennerich, Michael; Manuel Stahl
> Subject: IIO driver merge plans (for next merge window)
>
> Hi All,
>
> It is getting to that point of the kernel development cycle where we
> want to start thinking about which drivers to push out to Greg in
> plenty of time for the next merge window. If possible I'd like to
> see some of them moving over to the new abi. However, given we are
> in staging anyway, we can always merge them first and change them
> later! Obviously the question of whether the abi changes merge
> in time is down to what feedback they generate so that may further
> complicate things.
>
> I see there are loads from Analog in the blackfin tree and based on
> a quick glance at the source they are all in pretty good state. The
> only holes I can see are possibly in documentation and that is probably
> more a case of adding things to the abi docs (in my latest patch set)
> than anything else.
>
> Barry, Sonic, Michael, what are your current plans for mainlining?
> (as much as staging is mainline anyway)
>
> I see you guys have started adding ring support. How are you finding
> that element? I'm still far from sure we have gotten that bit right
> yet! I'm going to have a play with the new FIFO implementation and
> see if that provides at the very least and easier to review alternative
> to the current buffer.
>
> Would also be great to start merging DAC and DDS support from your tree and
> finally justify the output element of IIO.
>
> I know Manuel has a couple of drivers as well. Sorry to anyone I have
> forgotten. Please post your drivers!
>
> If people want assistance with moving over to the new abi, then I'm happy
> to convert drivers, but obviously would need people to test that I haven't
> broken anything in the process.
>
> With a bit of luck I'll clean up a few half written drivers I have
> and perhaps look at pulling in the other light sensors now that ALS
> has bitten the dust.
>
> Looking forward to seeing lots of drivers!
>
> Thanks,
>
> Jonathan
>
> p.s. If anyone has a chance to glance over the latest patch set, that would
> be great.
>
>
next prev parent reply other threads:[~2010-04-27 9:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-26 20:16 IIO driver merge plans (for next merge window) Jonathan Cameron
2010-04-27 3:20 ` Song, Barry
2010-04-27 9:27 ` Jonathan Cameron [this message]
2010-05-05 7:37 ` Barry Song
2010-05-05 15:20 ` Jonathan Cameron
2010-05-17 6:18 ` Zhang, Sonic
2010-05-17 7:47 ` Hennerich, Michael
2010-05-17 8:06 ` Zhang, Sonic
2010-05-17 8:08 ` Hennerich, Michael
2010-05-17 9:32 ` Jonathan Cameron
2010-05-17 9:36 ` Hennerich, Michael
2010-05-17 9:59 ` Jonathan Cameron
2010-05-17 9:44 ` Barry Song
2010-04-27 23:17 ` adis16300 to new abi Jonathan Cameron
2010-04-28 2:46 ` Barry Song
2010-05-05 20:16 ` Jonathan Cameron
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=4BD6ADFA.4050500@cam.ac.uk \
--to=jic23@cam.ac.uk \
--cc=Barry.Song@analog.com \
--cc=Michael.Hennerich@analog.com \
--cc=Sonic.Zhang@analog.com \
--cc=linux-iio@vger.kernel.org \
--cc=manuel.stahl@iis.fraunhofer.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.