From: Jonathan Cameron <jic23@kernel.org>
To: Ryan Mallon <rmallon@gmail.com>
Cc: Alexander Sverdlin <alexander.sverdlin@gmail.com>,
linux-iio@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
Hartley Sweeten <hsweeten@visionengravers.com>,
Hartmut Knaack <knaack.h@gmx.de>,
Lars-Peter Clausen <lars@metafoo.de>,
Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v4 0/5] iio: ADC driver for EP93xx SoC
Date: Sat, 3 Jun 2017 10:14:53 +0100 [thread overview]
Message-ID: <20170603101453.6b44b85a@kernel.org> (raw)
In-Reply-To: <5921F894.90809@gmail.com>
On Mon, 22 May 2017 06:29:08 +1000
Ryan Mallon <rmallon@gmail.com> wrote:
> On 22/05/17 00:03, Jonathan Cameron wrote:
> > On 17/05/17 18:13, Alexander Sverdlin wrote:
> >> This series prepares the necessary infrastructure for ADC platform
> >> device on
> >> Cirrus Logic EP93xx family of SoCs and adds the driver for ADC device
> >> using
> >> IIO subsystem.
> > Hartley, Ryan,
> >
> > How do you want to handle taking this series forward.
> > Clearly we have a few arch specific bits and then the driver which
> > is dependent on some of them.
>
> I no longer maintain an ep93xx tree because the architecture gets very
> few patches now. Patches should go via the arm-soc tree, which is
> maintained by (I believe) Arnd and Olaf.
>
> >
> > I'm happy to take the lot through the IIO tree, but will be wanting
> > a few acks.
>
> Sure, the series looks fine to me. For the ep93xx specific bits:
>
> Acked-by: Ryan Mallon <rmallon@gmail.com>
>
> > I'm interested to note how few implementations there are of clk_get_parent
> > in tree. Any comments on that little bit of the code would be
> > particularly welcome.
>
> The ep93xx architecture is old and obsolete. Because of this, and the
> relatively few number of people developing for it and with hardware to
> test, it hasn't gotten upgraded to some of the more modern kernel apis
> like the common clock framework.
>
> It probably isn't too difficult to move ep93xx to the common clock
> framework, but it is a separate change and I don't think Alexander
> should have to do it as a prerequisite to getting this adc support merged.
Agreed entirely!
Alexander, would you mind reposting the whole series, with
the linux-arm-kernel@lists.infrared.org cc'd.
I've cc'd it to this email to provide a bit of background to
the maintainers, but please add a note to the cover letter
highlighting what Ryan has covered here.
Thanks,
Jonathan
>
> ~Ryan
WARNING: multiple messages have this Message-ID (diff)
From: jic23@kernel.org (Jonathan Cameron)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 0/5] iio: ADC driver for EP93xx SoC
Date: Sat, 3 Jun 2017 10:14:53 +0100 [thread overview]
Message-ID: <20170603101453.6b44b85a@kernel.org> (raw)
In-Reply-To: <5921F894.90809@gmail.com>
On Mon, 22 May 2017 06:29:08 +1000
Ryan Mallon <rmallon@gmail.com> wrote:
> On 22/05/17 00:03, Jonathan Cameron wrote:
> > On 17/05/17 18:13, Alexander Sverdlin wrote:
> >> This series prepares the necessary infrastructure for ADC platform
> >> device on
> >> Cirrus Logic EP93xx family of SoCs and adds the driver for ADC device
> >> using
> >> IIO subsystem.
> > Hartley, Ryan,
> >
> > How do you want to handle taking this series forward.
> > Clearly we have a few arch specific bits and then the driver which
> > is dependent on some of them.
>
> I no longer maintain an ep93xx tree because the architecture gets very
> few patches now. Patches should go via the arm-soc tree, which is
> maintained by (I believe) Arnd and Olaf.
>
> >
> > I'm happy to take the lot through the IIO tree, but will be wanting
> > a few acks.
>
> Sure, the series looks fine to me. For the ep93xx specific bits:
>
> Acked-by: Ryan Mallon <rmallon@gmail.com>
>
> > I'm interested to note how few implementations there are of clk_get_parent
> > in tree. Any comments on that little bit of the code would be
> > particularly welcome.
>
> The ep93xx architecture is old and obsolete. Because of this, and the
> relatively few number of people developing for it and with hardware to
> test, it hasn't gotten upgraded to some of the more modern kernel apis
> like the common clock framework.
>
> It probably isn't too difficult to move ep93xx to the common clock
> framework, but it is a separate change and I don't think Alexander
> should have to do it as a prerequisite to getting this adc support merged.
Agreed entirely!
Alexander, would you mind reposting the whole series, with
the linux-arm-kernel at lists.infrared.org cc'd.
I've cc'd it to this email to provide a bit of background to
the maintainers, but please add a note to the cover letter
highlighting what Ryan has covered here.
Thanks,
Jonathan
>
> ~Ryan
next prev parent reply other threads:[~2017-06-03 9:14 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-17 17:13 [PATCH v4 0/5] iio: ADC driver for EP93xx SoC Alexander Sverdlin
2017-05-17 17:13 ` Alexander Sverdlin
2017-05-17 17:13 ` [PATCH v4 1/5] clk: ep93xx: Implement clk_get_parent() Alexander Sverdlin
2017-05-17 17:13 ` Alexander Sverdlin
2017-05-17 17:13 ` [PATCH v4 2/5] clk: ep93xx: Add ADC clock Alexander Sverdlin
2017-05-17 17:13 ` Alexander Sverdlin
2017-05-17 17:13 ` [PATCH v4 3/5] ep93xx: Add ADC platform device support to core Alexander Sverdlin
2017-05-17 17:13 ` Alexander Sverdlin
2017-05-17 17:13 ` [PATCH v4 4/5] edb93xx: Add ADC platform device Alexander Sverdlin
2017-05-17 17:13 ` Alexander Sverdlin
2017-05-17 17:13 ` [PATCH v4 5/5] iio: adc: New driver for Cirrus Logic EP93xx ADC Alexander Sverdlin
2017-05-17 17:13 ` Alexander Sverdlin
2017-05-21 14:03 ` [PATCH v4 0/5] iio: ADC driver for EP93xx SoC Jonathan Cameron
2017-05-21 14:03 ` Jonathan Cameron
2017-05-21 20:29 ` Ryan Mallon
2017-05-21 20:29 ` Ryan Mallon
2017-05-22 5:41 ` Alexander Sverdlin
2017-05-22 6:51 ` Ryan Mallon
2017-06-03 9:14 ` Jonathan Cameron [this message]
2017-06-03 9:14 ` 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=20170603101453.6b44b85a@kernel.org \
--to=jic23@kernel.org \
--cc=alexander.sverdlin@gmail.com \
--cc=hsweeten@visionengravers.com \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-iio@vger.kernel.org \
--cc=pmeerw@pmeerw.net \
--cc=rmallon@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 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.