From: Michael Tretter <m.tretter@pengutronix.de>
To: Robert Hancock <robert.hancock@calian.com>
Cc: "linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
"lars@metafoo.de" <lars@metafoo.de>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"jic23@kernel.org" <jic23@kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"michal.simek@xilinx.com" <michal.simek@xilinx.com>,
"manish.narani@xilinx.com" <manish.narani@xilinx.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"anand.ashok.dumbre@xilinx.com" <anand.ashok.dumbre@xilinx.com>,
kernel@pengutronix.de
Subject: Re: [PATCH 2/4] iio: adc: xilinx-ams: Fixed missing PS channels
Date: Tue, 25 Jan 2022 09:06:34 +0100 [thread overview]
Message-ID: <20220125080634.GD25856@pengutronix.de> (raw)
In-Reply-To: <c615acdc4f0a818e070705e1f3f5d82660fb4c8a.camel@calian.com>
On Thu, 20 Jan 2022 01:09:39 +0000, Robert Hancock wrote:
> On Wed, 2022-01-19 at 19:02 -0600, Robert Hancock wrote:
> > The code forgot to increment num_channels for the PS channel inputs,
> > resulting in them not being enabled as they should.
> >
> > Fixes: d5c70627a794 ("iio: adc: Add Xilinx AMS driver")
> > Signed-off-by: Robert Hancock <robert.hancock@calian.com>
> > ---
> > drivers/iio/adc/xilinx-ams.c | 1 +
> > 1 file changed, 1 insertion(+)
> >
> > diff --git a/drivers/iio/adc/xilinx-ams.c b/drivers/iio/adc/xilinx-ams.c
> > index 8343c5f74121..b93864362dac 100644
> > --- a/drivers/iio/adc/xilinx-ams.c
> > +++ b/drivers/iio/adc/xilinx-ams.c
> > @@ -1224,6 +1224,7 @@ static int ams_init_module(struct iio_dev *indio_dev,
> >
> > /* add PS channels to iio device channels */
> > memcpy(channels, ams_ps_channels, sizeof(ams_ps_channels));
> > + num_channels = ARRAY_SIZE(ams_ps_channels);
> > } else if (fwnode_property_match_string(fwnode, "compatible",
> > "xlnx,zynqmp-ams-pl") == 0) {
> > ams->pl_base = fwnode_iomap(fwnode, 0);
>
> Looks like this is the same change just submitted by Michael Tretter ("iio:
> adc: xilinx-ams: Fix num_channels for PS channels").
Thanks for pointing me here.
Reviewed-by: Michael Tretter <m.tretter@pengutronix.de>
Michael
next prev parent reply other threads:[~2022-01-25 9:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-20 1:02 [PATCH 0/4] Xilinx AMS fixes Robert Hancock
2022-01-20 1:02 ` [PATCH 1/4] arm64: dts: zynqmp: add AMS driver to device tree Robert Hancock
2022-01-25 8:02 ` Michael Tretter
2022-01-25 9:42 ` Michal Simek
2022-01-20 1:02 ` [PATCH 2/4] iio: adc: xilinx-ams: Fixed missing PS channels Robert Hancock
2022-01-20 1:09 ` Robert Hancock
2022-01-25 8:06 ` Michael Tretter [this message]
2022-01-30 12:29 ` Jonathan Cameron
2022-01-20 1:02 ` [PATCH 3/4] iio: adc: xilinx-ams: Fixed wrong sequencer register settings Robert Hancock
2022-01-25 8:21 ` Michael Tretter
2022-01-25 16:15 ` Robert Hancock
2022-01-26 9:12 ` Michael Tretter
2022-01-30 12:31 ` Jonathan Cameron
2022-01-20 1:02 ` [PATCH 4/4] iio: adc: xilinx-ams: Fix single channel switching sequence Robert Hancock
2022-01-30 12:34 ` 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=20220125080634.GD25856@pengutronix.de \
--to=m.tretter@pengutronix.de \
--cc=anand.ashok.dumbre@xilinx.com \
--cc=devicetree@vger.kernel.org \
--cc=jic23@kernel.org \
--cc=kernel@pengutronix.de \
--cc=lars@metafoo.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-iio@vger.kernel.org \
--cc=manish.narani@xilinx.com \
--cc=michal.simek@xilinx.com \
--cc=robert.hancock@calian.com \
--cc=robh+dt@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).