From: Andy Shevchenko <andy@kernel.org>
To: "Nechita, Ramona" <Ramona.Nechita@analog.com>
Cc: "Jonathan Cameron" <jic23@kernel.org>,
"Lars-Peter Clausen" <lars@metafoo.de>,
"Hennerich, Michael" <Michael.Hennerich@analog.com>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Sa, Nuno" <Nuno.Sa@analog.com>,
"David Lechner" <dlechner@baylibre.com>,
"Schmitt, Marcelo" <Marcelo.Schmitt@analog.com>,
"Olivier Moysan" <olivier.moysan@foss.st.com>,
"Dumitru Ceclan" <mitrutzceclan@gmail.com>,
"Matteo Martelli" <matteomartelli3@gmail.com>,
"João Paulo Gonçalves" <joao.goncalves@toradex.com>,
"Alisa-Dariana Roman" <alisadariana@gmail.com>,
"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [PATCH v6 3/3] drivers: iio: adc: add support for ad777x family
Date: Thu, 10 Oct 2024 20:59:29 +0300 [thread overview]
Message-ID: <ZwgWAV7SQwV02ott@smile.fi.intel.com> (raw)
In-Reply-To: <DM6PR03MB4315785FB25B980264748BCBF3782@DM6PR03MB4315.namprd03.prod.outlook.com>
On Thu, Oct 10, 2024 at 02:32:49PM +0000, Nechita, Ramona wrote:
...
> >> +struct ad7779_state {
> >> + struct spi_device *spi;
> >> + const struct ad7779_chip_info *chip_info;
> >> + struct clk *mclk;
> >> + struct iio_trigger *trig;
> >> + struct completion completion;
> >> + unsigned int sampling_freq;
> >> + enum ad7779_filter filter_enabled;
> >> + /*
> >> + * DMA (thus cache coherency maintenance) requires the
> >> + * transfer buffers to live in their own cache lines.
> >> + */
> >> + struct {
> >> + u32 chans[8];
> >> + s64 timestamp;
> >
> > aligned_s64 timestamp;
> >
> >while it makes no difference in this case, this makes code aligned inside
> >the IIO subsystem.
>
> I might be missing something but I can't find the aligned_s64 data type,
> should I define it myself in the driver?
Definitely, basically the rule of thumb is to create your patches based on
the respective subsystem tree. In such a case this is IIO tree togreg branch
(in some cases testing should be used).
There is the mentioned type been introduced.
> >> + } data __aligned(IIO_DMA_MINALIGN);
> >
> >Note, this is different alignment to the above. And isn't the buffer below should have it instead?
> >
> >> + u32 spidata_tx[8];
> >> + u8 reg_rx_buf[3];
> >> + u8 reg_tx_buf[3];
> >> + u8 reset_buf[8];
> >> +};
...
> >> +static int ad7779_write_raw(struct iio_dev *indio_dev,
> >> + struct iio_chan_spec const *chan, int val, int val2,
> >> + long mask)
> >
> >long? Not unsigned long?
>
> I copied the function header directly from iio.h, shouldn't it be left as such?
Oh, this is unfortunate. It should be fixed there, indeed.
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2024-10-10 17:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-26 13:53 [PATCH v6 0/3] add support for ad777x family Ramona Alexandra Nechita
2024-09-26 13:53 ` [PATCH v6 1/3] dt-bindings: iio: adc: add a7779 doc Ramona Alexandra Nechita
2024-09-26 15:40 ` Conor Dooley
2024-09-26 13:53 ` [PATCH v6 2/3] Documentation: ABI: added filter mode doc in sysfs-bus-iio Ramona Alexandra Nechita
2024-09-26 14:12 ` Andy Shevchenko
2024-09-26 14:12 ` Andy Shevchenko
2024-09-28 17:52 ` Jonathan Cameron
2024-09-26 13:53 ` [PATCH v6 3/3] drivers: iio: adc: add support for ad777x family Ramona Alexandra Nechita
2024-09-26 14:58 ` Andy Shevchenko
2024-10-10 14:32 ` Nechita, Ramona
2024-10-10 17:45 ` Jonathan Cameron
2024-10-10 18:25 ` Andy Shevchenko
2024-10-12 10:42 ` Jonathan Cameron
2024-10-15 11:08 ` Andy Shevchenko
2024-10-10 17:59 ` Andy Shevchenko [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=ZwgWAV7SQwV02ott@smile.fi.intel.com \
--to=andy@kernel.org \
--cc=Marcelo.Schmitt@analog.com \
--cc=Michael.Hennerich@analog.com \
--cc=Nuno.Sa@analog.com \
--cc=Ramona.Nechita@analog.com \
--cc=alisadariana@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--cc=joao.goncalves@toradex.com \
--cc=krzk+dt@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matteomartelli3@gmail.com \
--cc=mitrutzceclan@gmail.com \
--cc=olivier.moysan@foss.st.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).