From: Jonathan Cameron <jic23@cam.ac.uk>
To: Jonathan Kunkee <jonathan.kunkee@gmail.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
linux-kernel@vger.kernel.org, linux-iio@vger.kernel.org
Subject: Re: [RFC] Moving magnetometer HMC6352 into IIO subsystem
Date: Tue, 16 Aug 2011 09:57:00 +0100 [thread overview]
Message-ID: <4E4A30DC.4080806@cam.ac.uk> (raw)
In-Reply-To: <CAGRJchgbqqG5xOLoR4EOXBz7YcxmBc0TNsRaH138Qs5k6-e8YA@mail.gmail.com>
On 08/16/11 00:22, Jonathan Kunkee wrote:
>>> Should the HMC6352 digital compass driver be moved [...]?
>>
>> No - that would be a regression .. but read on
>
>>> [...] they should almost always land in IIO land.
>>
>> IIO is a staging project that may never go anywhere - some of us are
>> using magnetometers in product so this alone isn't an answer that works
>> right now.
>
> In my reading I failed to catch the how transient 'staging' is--I'll
> keep it mind, as I'm hoping my driver will not be so transient.
>
>>> I would be willing to work on the change as I want to submit a similar
>>> driver for the HMC6343 magnetometer/accelerometer as well.
>>
>> It would be great if it got added into the IIO subystem *as well*, and in
>> time when and if IIO goes out of staging it would then eventually replace
>> the existing drivers.
>
> This would then necessitate maintaining both chunks of code, so I think
> for now I will develop my module in drivers/misc. After it has stabilized,
> I can add both modules to IIO as well with this in mind.
>
Certainly a valid option right now. Moving things over tends to be
straight forward anyway.
IIO is hoping to make first steps out of staging shortly, but it will be a
good while before anywhere near everything moves out into the main tree
(lots of code and some of it is probably going to be controversial!)
Jonathan
prev parent reply other threads:[~2011-08-16 8:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-15 20:04 [RFC] Moving magnetometer HMC6352 into IIO subsystem Jonathan Kunkee
2011-08-15 21:07 ` Alan Cox
2011-08-15 23:22 ` Jonathan Kunkee
2011-08-16 8:57 ` Jonathan Cameron [this message]
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=4E4A30DC.4080806@cam.ac.uk \
--to=jic23@cam.ac.uk \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jonathan.kunkee@gmail.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).