From: "Nuno Sá" <noname.nuno@gmail.com>
To: "Jonathan Cameron" <jic23@kernel.org>, "Nuno Sá" <nuno.sa@analog.com>
Cc: linux-staging@lists.linux.dev, linux-iio@vger.kernel.org,
Michael Hennerich <Michael.Hennerich@analog.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Lars-Peter Clausen <lars@metafoo.de>
Subject: Re: [PATCH] staging: iio: resolver: ads1210: fix config mode
Date: Mon, 03 Apr 2023 08:54:44 +0200 [thread overview]
Message-ID: <0fc93adff7ef33857881ffa94bbd77433abab362.camel@gmail.com> (raw)
In-Reply-To: <20230401152425.2dae5505@jic23-huawei>
On Sat, 2023-04-01 at 15:24 +0100, Jonathan Cameron wrote:
> On Mon, 27 Mar 2023 16:54:14 +0200
> Nuno Sá <nuno.sa@analog.com> wrote:
>
> > As stated in the device datasheet [1], bits a0 and a1 have to be
> > set to
> > 1 for the configuration mode.
> >
> > [1]:
> > https://www.analog.com/media/en/technical-documentation/data-sheets/ad2s1210.pdf
> >
> > Fixes: b19e9ad5e2cb9 ("staging:iio:resolver:ad2s1210 general driver
> > cleanup")
> > Signed-off-by: Nuno Sá <nuno.sa@analog.com>
>
> Oops. Younger more foolish me bug (back in 2011 so I'll cut myself
> some slack)
>
> Applied to the togreg branch of iio.git (not rushing something in
> that is in staging
> and has been broken a while without anyone commenting!)
>
> I don't suppose this means you are going to get this ready to move
> out of staging?
> *looks hopeful*
>
Eeheh, Unfortunately not on the top of my list right now... But, if I
happen to find some hardware hanging around, I might eventually get
into it.
Funny enough, this was actually reported to us in one of our support
channels which means there are people actually using the driver even
being it on staging.
- Nuno Sá
prev parent reply other threads:[~2023-04-03 6:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-27 14:54 [PATCH] staging: iio: resolver: ads1210: fix config mode Nuno Sá
2023-04-01 14:24 ` Jonathan Cameron
2023-04-03 6:54 ` Nuno Sá [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=0fc93adff7ef33857881ffa94bbd77433abab362.camel@gmail.com \
--to=noname.nuno@gmail.com \
--cc=Michael.Hennerich@analog.com \
--cc=gregkh@linuxfoundation.org \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=nuno.sa@analog.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