From: Jonathan Cameron <jic23@kernel.org>
To: Fabrice Gasnier <fabrice.gasnier@st.com>
Cc: Benjamin Gaignard <benjamin.gaignard@linaro.org>,
William Breathitt Gray <vilhelm.gray@gmail.com>,
Patrick Havelange <patrick.havelange@essensium.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
<devicetree@vger.kernel.org>,
Lars-Peter Clausen <lars@metafoo.de>,
Benjamin GAIGNARD <benjamin.gaignard@st.com>,
<linux-iio@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
Hartmut Knaack <knaack.h@gmx.de>,
Andrew Morton <akpm@linux-foundation.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: New IIO/counter driver
Date: Sat, 12 Jan 2019 17:51:59 +0000 [thread overview]
Message-ID: <20190112175159.3dac7a70@archlinux> (raw)
In-Reply-To: <8b2bb569-a6e0-25ec-740d-48083b30fe60@st.com>
On Tue, 8 Jan 2019 12:01:57 +0100
Fabrice Gasnier <fabrice.gasnier@st.com> wrote:
> On 1/8/19 11:57 AM, Benjamin Gaignard wrote:
> > Le mar. 8 janv. 2019 à 01:46, William Breathitt Gray
> > <vilhelm.gray@gmail.com> a écrit :
> >>
> >> On Mon, Jan 07, 2019 at 02:45:37PM +0100, Patrick Havelange wrote:
> >>> Hello,
> >>>
> >>> I'm in the process of adding a new IIO/counter driver, however I also saw
> >>> that there was a work in progress to have a separate counter subsystem (
> >>> https://marc.info/?l=linux-iio&m=153974167727206 ). But it seems there is
> >>> no recent progress on it.
> >>> What is the state of those patches ? Is it still interesting to develop the
> >>> driver as an IIO/counter , or should I use already that new subsystem ?
> >>>
> >>> Best Regards,
> >>>
> >>> Patrick Havelange.
> >>
> >> Hello,
> >>
> >> I am still open to merging this patchset and maintaining the Counter
> >> subsystem. However, I took the lack of response for my latest
> >> submission to indicate a loss of interest in this patchset's approach.
> >> If there are still people who want this, I can rebase and resend this
> >> patchset for submission; the past few versions have primarily been code
> >> clarity and documentation changes so I believe the core design itself is
> >> somewhat stable now.
> >>
> >> Just let me know how best to proceed and I shall be happy to oblige --
> >> whether to continue maintaining this patchset or to drop this design in
> >> favor of improving the existing IIO Counter code in the kernel.
> >>
> >> I'll CC those from the patchset submission to keep them in the loop.
> >
> > I confirm that I still interested to get those patches merged.
> >
> > Regards,
> > Benjamin
> Hi,
>
> Same for me,
In a more abstract fashion (I don't have any hardware of this type!)
I'm still keen for the counter subsystem to go in. Hopefully, if
Greg or anyone else wants to take a detailed look they will have time
this cycle to do so.
I was pretty happy with the last version I read through. There will
always be things to improved, but as long a we are happy with
the userspace inteface, the little things can happen later.
Jonathan
>
> Regards,
> Fabrice
> >>
> >> Sincerely,
> >>
> >> William Breathitt Gray
> >>
> >> _______________________________________________
> >> linux-arm-kernel mailing list
> >> linux-arm-kernel@lists.infradead.org
> >> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
> >
> >
> >
prev parent reply other threads:[~2019-01-12 17:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAKKE0ZHmODzhvjPNJFVgT2cF_F=f2kNKr5K_CGP+0XgA5XZokw@mail.gmail.com>
2019-01-07 13:55 ` New IIO/counter driver Patrick Havelange
2019-01-08 0:46 ` William Breathitt Gray
2019-01-08 10:57 ` Benjamin Gaignard
2019-01-08 11:01 ` Fabrice Gasnier
2019-01-12 17:51 ` 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=20190112175159.3dac7a70@archlinux \
--to=jic23@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=benjamin.gaignard@linaro.org \
--cc=benjamin.gaignard@st.com \
--cc=devicetree@vger.kernel.org \
--cc=fabrice.gasnier@st.com \
--cc=gregkh@linuxfoundation.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patrick.havelange@essensium.com \
--cc=pmeerw@pmeerw.net \
--cc=vilhelm.gray@gmail.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;
as well as URLs for NNTP newsgroup(s).