public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Nuno Sá" <noname.nuno@gmail.com>
To: David Lechner <dlechner@baylibre.com>,
	"Miclaus, Antoniu" <Antoniu.Miclaus@analog.com>,
	"jic23@kernel.org" <jic23@kernel.org>,
	 "robh@kernel.org" <robh@kernel.org>,
	"conor+dt@kernel.org" <conor+dt@kernel.org>,
	 "linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-pwm@vger.kernel.org" <linux-pwm@vger.kernel.org>
Subject: Re: [PATCH v10 8/8] iio: adc: ad4851: add ad485x driver
Date: Tue, 21 Jan 2025 10:24:33 +0000	[thread overview]
Message-ID: <70975c6682e4eed4ede3d751830813290e6fee80.camel@gmail.com> (raw)
In-Reply-To: <c424cedb-5b45-43c0-897b-dec83918d658@baylibre.com>

On Mon, 2025-01-20 at 11:37 -0600, David Lechner wrote:
> On 1/20/25 6:37 AM, Miclaus, Antoniu wrote:
> > > > +		}
> > > > +		channels++;
> > > > +
> > > > +		st->bipolar_ch[reg] = fwnode_property_read_bool(child,
> > > "bipolar");
> > > > +
> > > > +		if (st->bipolar_ch[reg]) {
> > > > +			channels->scan_type.sign = 's';
> > > > +		} else {
> > > > +			ret = regmap_write(st->regmap,
> > > AD4851_REG_CHX_SOFTSPAN(reg),
> > > > +					   AD4851_SOFTSPAN_0V_40V);
> > > > +			if (ret)
> > > > +				return ret;
> > > > +		}
> > > > +	}
> > > > +
> > > > +	*ad4851_channels = channels;
> > > 
> > > At this point, channels is pointing to memory we didn't allocate (because
> > > of
> > > channels++). As in the previous review, I suggest we just get rid of the
> > > output
> > > parameter since indio_dev->channels already has the correct pointer.
> > > 
> > > It's less chance for mistakes like this and avoids needing to provide an
> > > unused
> > > arg in ad4857_parse_channels().
> > 
> > Hmm, how can I then do the assignments in `ad4858_parse_channels` ?
> > 
> > drivers/iio/adc/ad4851.c:1055:42: error: assignment of member
> > ‘has_ext_scan_type’ in read-only object
> >  1055 |   indio_dev->channels->has_ext_scan_type = 1;
> >       |                                          ^
> > drivers/iio/adc/ad4851.c:1057:39: error: assignment of member
> > ‘ext_scan_type’ in read-only object
> >  1057 |    indio_dev->channels->ext_scan_type = ad4851_scan_type_20_b;
> >       |                                       ^
> > drivers/iio/adc/ad4851.c:1058:43: error: assignment of member
> > ‘num_ext_scan_type’ in read-only object
> >  1058 |    indio_dev->channels->num_ext_scan_type =
> > ARRAY_SIZE(ad4851_scan_type_20_b);
> >       |                                           ^
> > drivers/iio/adc/ad4851.c:1061:39: error: assignment of member
> > ‘ext_scan_type’ in read-only object
> >  1061 |    indio_dev->channels->ext_scan_type = ad4851_scan_type_20_u;
> >       |                                       ^
> > drivers/iio/adc/ad4851.c:1062:43: error: assignment of member
> > ‘num_ext_scan_type’ in read-only object
> >  1062 |    indio_dev->channels->num_ext_scan_type =
> > ARRAY_SIZE(ad4851_scan_type_20_u);
> >       |                                           ^
> 
> I would be tempted to just not have a second loop of
> 
> 	device_for_each_child_node_scoped(dev, child)
> 
> in ad4858_parse_channels() and instead do everything in
> ad4851_parse_channels()
> and just pass a boolean parameter to conditionally handle the difference
> between the two types of chips.
> 
> Or you use a cast to remove the const qualifier.
> 
> 	ad4851_channels = (struct iio_chan_spec *)indio_dev->channels;

Hmm a bit nasty IMO :).

But up to you both anyways...

- Nuno Sá 

  reply	other threads:[~2025-01-21 10:24 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-17 13:06 [PATCH v10 0/8] Add support for AD485x DAS Family Antoniu Miclaus
2025-01-17 13:06 ` [PATCH v10 1/8] iio: backend: add API for interface get Antoniu Miclaus
2025-01-17 16:08   ` Nuno Sá
2025-01-17 13:06 ` [PATCH v10 2/8] iio: backend: add support for data size set Antoniu Miclaus
2025-01-17 16:09   ` Nuno Sá
2025-01-17 13:06 ` [PATCH v10 3/8] iio: backend: add API for oversampling Antoniu Miclaus
2025-01-17 16:17   ` Nuno Sá
2025-01-18 16:42     ` Jonathan Cameron
2025-01-17 13:06 ` [PATCH v10 4/8] iio: adc: adi-axi-adc: add interface type Antoniu Miclaus
2025-01-17 16:18   ` Nuno Sá
2025-01-17 13:06 ` [PATCH v10 5/8] iio: adc: adi-axi-adc: set data format Antoniu Miclaus
2025-01-17 16:20   ` Nuno Sá
2025-01-17 17:50     ` David Lechner
2025-01-18 14:47       ` Nuno Sá
2025-01-17 13:07 ` [PATCH v10 6/8] iio: adc: adi-axi-adc: add oversampling Antoniu Miclaus
2025-01-17 16:22   ` Nuno Sá
2025-01-17 13:07 ` [PATCH v10 7/8] dt-bindings: iio: adc: add ad4851 Antoniu Miclaus
2025-01-17 13:07 ` [PATCH v10 8/8] iio: adc: ad4851: add ad485x driver Antoniu Miclaus
2025-01-17 21:45   ` David Lechner
2025-01-18 16:57     ` Jonathan Cameron
2025-01-18 17:09       ` David Lechner
2025-01-18 17:41         ` Jonathan Cameron
2025-01-20 12:37     ` Miclaus, Antoniu
2025-01-20 17:37       ` David Lechner
2025-01-21 10:24         ` Nuno Sá [this message]
2025-01-18 15:10   ` Nuno Sá
2025-01-18 17:37     ` David Lechner
2025-01-20  9:44       ` Nuno Sá

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=70975c6682e4eed4ede3d751830813290e6fee80.camel@gmail.com \
    --to=noname.nuno@gmail.com \
    --cc=Antoniu.Miclaus@analog.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dlechner@baylibre.com \
    --cc=jic23@kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pwm@vger.kernel.org \
    --cc=robh@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