From: Jonathan Cameron <jic23@kernel.org>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: "linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
Giuseppe Barba <giuseppe.barba@st.com>,
Denis Ciocca <denis.ciocca@st.com>
Subject: Re: [PATCH 1/2] iio: st_sensors: support active-low interrupts
Date: Sun, 15 Nov 2015 17:46:32 +0000 [thread overview]
Message-ID: <5648C4F8.5020603@kernel.org> (raw)
In-Reply-To: <CACRpkdYi9t_NBjWfBf4qr3XMx7zA62UkBRO-VF1fCUjuX48K_A@mail.gmail.com>
On 15/11/15 16:26, Linus Walleij wrote:
> On Sun, Nov 15, 2015 at 11:31 AM, Jonathan Cameron <jic23@kernel.org> wrote:
>
>>> This patch requires the previously sent patch to switch the
>>> driver to request_any_context_irq().
>>
>> Really requires or will create some fuzz without it? Looks like
>> the latter so if we end up discussing that one for a while
>> I might reorder. Mind you early in this cycle anyway so
>> no rush on this one!
>
> I can put all three patches in a series and put this before that
> patch, no problem.
Might be wise as we can get this one sorted anyway whilst seeing
if we can get some input on the other one from others...
>
>> p.s. If anyone fancies adding support for the venerable
>> lis3l02dq as well so we can kill off my ancient driver
>> in staging that would be great! (I know I should do it
>> myself probably but I can always hope someone else will
>> get there first ;)
>
> They are all so similar that I could probably code up
> support from the datasheet.
>
> However I have no hardware to test on...
>
> Who submitted that driver in the first place?
<tries to look innocent>... That would be me ;)
Back at the dawn of time for IIO - this was one of our original
drivers (the sca3000 was to and that's still in staging too -
that one is a seriously odd beast).
Technically I still have a board with one lis3l02dq on it
somewhere around, but I haven't booted it in a few years and
it has darned silly connectors so wiring it up to something else
would be 'interesting'. Not to mention, if I recall correctly
this chip only gives level interrupts and the board only
has edge triggered ones. Were some nasty games to discover
if new data had turned up whilst you were reading the old stuff.
I'm almost tempted to drop the driver entirely on the basis
the only boards I know ever had one have been unavailable for
a long time and I'm the maintainer of those anyway and given
complete lack of patches for the last 5 years may have the only
ones that even work (probably) any more...
I can always bring it back up if I ever actually make the board
boot again.
p.s. Now it will turn out there are hundreds of people using
intel research stargate 2 imb400 sensor boards....
(they were also compatible and sold by CrossBow for their
imote 2 boards but those went all .net for no apparent reason.
It was interesting hardware. The camera board for instance
had no pull ups on the i2c bus so the tinyos driver that was
the only documentation effectively simply never read back or
checked for acks from the sensor. Gives you an idea of the
fun. Still these were very small boards that well predated
the gumstix etc.
Ah, the glory days when I regularly fired up actual hardware!
Jonathan
>
> Yours,
> Linus Walleij
> --
> To unsubscribe from this list: send the line "unsubscribe linux-iio" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2015-11-15 17:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-13 20:18 [PATCH 1/2] iio: st_sensors: support active-low interrupts Linus Walleij
2015-11-15 10:31 ` Jonathan Cameron
2015-11-15 16:26 ` Linus Walleij
2015-11-15 17:46 ` Jonathan Cameron [this message]
2015-11-16 6:02 ` Denis Ciocca
2015-11-16 8:29 ` Linus Walleij
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=5648C4F8.5020603@kernel.org \
--to=jic23@kernel.org \
--cc=denis.ciocca@st.com \
--cc=giuseppe.barba@st.com \
--cc=linus.walleij@linaro.org \
--cc=linux-iio@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