From: Jonathan Cameron <jic23@kernel.org>
To: "Tinaco, Mariel" <Mariel.Tinaco@analog.com>
Cc: "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>,
Lars-Peter Clausen <lars@metafoo.de>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
"Hennerich, Michael" <Michael.Hennerich@analog.com>,
Marcelo Schmitt <marcelo.schmitt1@gmail.com>,
Dimitri Fedrau <dima.fedrau@gmail.com>,
Guenter Roeck <linux@roeck-us.net>
Subject: Re: [PATCH 2/2] iio: dac: support the ad8460 Waveform DAC
Date: Fri, 28 Jun 2024 19:45:46 +0100 [thread overview]
Message-ID: <20240628194546.2f608365@jic23-huawei> (raw)
In-Reply-To: <SJ0PR03MB62241801F72B21EEC9CDCCBD91D42@SJ0PR03MB6224.namprd03.prod.outlook.com>
> > > +};
> > > +
> > > +static int ad8460_get_powerdown_mode(struct iio_dev *indio_dev,
> > > + const struct iio_chan_spec *chan) {
> > > + return 0;
> >
> > Why have the stubs in here?
>
> Should I move the stubs to a different place in the code or remove them
> altogether since there is only a single powerdown mode available
Ah. I'd not really understood what was going on here. This is fine as
is.
> > AD8460_HVDAC_DATA_WORD_HIGH(index),
> > > + ((val >> 8) & 0xFF));
> >
> > bulk write? or do these need to be ordered?
>
> For this I used bulk read/write this way.
>
> static int ad8460_set_hvdac_word(struct ad8460_state *state,
> int index,
> int val)
> {
> u8 regvals[AD8460_DATA_BYTE_WORD_LENGTH];
regmap bulk accesses (when spi anyway) should be provided with DMA safe buffers.
Easiest way to do that is add one with __aligned(IIO_DMA_MINALIGN) to the end
of the ad8460_state structure. Possibly you'll need a lock to protect it - I haven't
checked.
>
> regvals[0] = val & 0xFF;
> regvals[1] = (val >> 8) & 0xFF;
That is an endian conversion so use appropriate endian function to fill it efficiently
and document clearly what is going on.
put_unaligned_le16()
>
> return regmap_bulk_write(state->regmap, AD8460_HVDAC_DATA_WORD_LOW(index),
> regvals, AD8460_DATA_BYTE_WORD_LENGTH);
> }
>
>
> > > +}
> > > + state->regmap = devm_regmap_init_spi(spi, &ad8460_regmap_config);
> > > + if (IS_ERR(state->regmap))
> > > + return dev_err_probe(&spi->dev, PTR_ERR(state->regmap),
> > > + "Failed to initialize regmap");
> > > +
> > > + ret = devm_iio_dmaengine_buffer_setup_ext(&spi->dev, indio_dev, "tx",
> > > +
> > IIO_BUFFER_DIRECTION_OUT);
> >
> > Ah. I take back my binding comment. I assume this is mapping some non
> > standard interface for the parallel data flow?
>
> Yes, the HDL side doesn't follow yet the standard IIO backend from which this
> driver was tested
Hmm. I'd like to see this brought inline with the other iio backend
drivers if possible.
Jonathan
next prev parent reply other threads:[~2024-06-28 18:45 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-10 6:40 [PATCH 0/2] add AD8460 DAC driver Mariel Tinaco
2024-05-10 6:40 ` [PATCH 1/2] dt-bindings: iio: dac: add docs for ad8460 Mariel Tinaco
2024-05-10 7:21 ` Rob Herring (Arm)
2024-05-10 17:28 ` David Lechner
2024-05-11 16:25 ` Jonathan Cameron
2024-05-11 18:47 ` David Lechner
2024-05-21 7:07 ` Nuno Sá
2024-06-24 4:20 ` Tinaco, Mariel
2024-05-10 6:40 ` [PATCH 2/2] iio: dac: support the ad8460 Waveform DAC Mariel Tinaco
2024-05-10 17:30 ` David Lechner
2024-05-11 16:44 ` Jonathan Cameron
2024-06-24 4:19 ` Tinaco, Mariel
2024-06-28 18:45 ` Jonathan Cameron [this message]
2024-07-08 5:17 ` Tinaco, Mariel
2024-07-08 16:05 ` Jonathan Cameron
2024-07-11 9:20 ` Nuno Sá
2024-07-11 21:31 ` David Lechner
2024-07-12 6:57 ` Nuno Sá
2024-07-13 9:57 ` Jonathan Cameron
2024-07-14 6:17 ` Nuno Sá
2024-06-24 4:56 ` Tinaco, Mariel
2024-06-28 18:51 ` Jonathan Cameron
2024-07-07 23:32 ` Tinaco, Mariel
2024-07-07 23:37 ` Tinaco, Mariel
2024-05-10 17:30 ` [PATCH 0/2] add AD8460 DAC driver David Lechner
2024-05-11 16:21 ` Jonathan Cameron
2024-06-24 4:38 ` Tinaco, Mariel
2024-06-28 18:39 ` Jonathan Cameron
2024-07-07 23:29 ` Tinaco, Mariel
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=20240628194546.2f608365@jic23-huawei \
--to=jic23@kernel.org \
--cc=Mariel.Tinaco@analog.com \
--cc=Michael.Hennerich@analog.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dima.fedrau@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=lars@metafoo.de \
--cc=lgirdwood@gmail.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=marcelo.schmitt1@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).