From: Jonathan Cameron <jic23@kernel.org>
To: Subhajit Ghosh <subhajit.ghosh@tweaklogic.com>
Cc: Matti Vaittinen <mazziesaccount@gmail.com>,
Matti Vaittinen <matti.vaittinen@fi.rohmeurope.com>,
Lars-Peter Clausen <lars@metafoo.de>,
Mudit Sharma <muditsharma.info@gmail.com>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] iio: gts: Simplify available scale table build
Date: Sat, 18 Jan 2025 17:17:51 +0000 [thread overview]
Message-ID: <20250118171751.4d966c98@jic23-huawei> (raw)
In-Reply-To: <20250111124224.008b826a@jic23-huawei>
On Sat, 11 Jan 2025 12:42:24 +0000
Jonathan Cameron <jic23@kernel.org> wrote:
> On Sat, 11 Jan 2025 14:47:28 +1030
> Subhajit Ghosh <subhajit.ghosh@tweaklogic.com> wrote:
>
> > On 11/1/25 00:56, Matti Vaittinen wrote:
> > > On 22/12/2024 11:24, Matti Vaittinen wrote:
> > >> On 20/12/2024 21:21, Jonathan Cameron wrote:
> > >>> On Mon, 16 Dec 2024 10:56:37 +0200
> > >>> Matti Vaittinen <mazziesaccount@gmail.com> wrote:
> > >>>
> > >>>> Make available scale building more clear. This hurts the performance
> > >>>> quite a bit by looping throgh the scales many times instead of doing
> > >>>> everything in one loop. It however simplifies logic by:
> > >>>> - decoupling the gain and scale allocations & computations
> > >>>> - keeping the temporary 'per_time_gains' table inside the
> > >>>> per_time_scales computation function.
> > >>>> - separating building the 'all scales' table in own function and doing
> > >>>> it based on the already computed per-time scales.
> > >>>>
> > >>>> Signed-off-by: Matti Vaittinen <mazziesaccount@gmail.com>
> > >>> Looks good to me, but I want to leave it on list a while before applying.
> > >>> Ideal if it gets some tested-by or other tags before I pick it up.
> > >>> As always, this is fiddly code, so the more eyes the better!
> > >>
> > >> Please, let it wait until the Christmas has passed. I got information we might be getting some testing before the year changes :)
> > >
> > > Well, the year changed and no tested-by tags emerged. I suppose my sources weren't right at this time.
> > >
> > > Yours,
> > > -- Matti
> > Hi Matti,
> >
> > Hope you had a good Christmas and new year. After my US trip, it took me some time
> > to come to terms that I have to work for a living!
> >
> > The code works fine. I tested it with apds9306 driver with stm32mp157-dk2 board.
> >
> > Tested-by: subhajit.ghosh@tweaklogic.com
> >
> > Just want to report something else which may not be related to this.
> > When I tried to cross-compile with linux-gnueabi-gcc version 12.2.0 with Linux kernel 6.1.28, I got the following errors:
> > CC [M] /home/subhajit/opensource_contributions/apds9306/apds9306_backport/./drivers/iio/industrialio-gts-helper.o
> > /tmp/ccn9UpwF.s: Assembler messages:
> > /tmp/ccn9UpwF.s:22: Error: junk at end of line, first unrecognized character is `I'
> > ...
> > ...
> >
> > I had to remove the double quotes from the macros for all symbol exports:
> > EXPORT_SYMBOL_NS_GPL(iio_gts_total_gain_to_scale, "IIO_GTS_HELPER");
> > to
> > EXPORT_SYMBOL_NS_GPL(iio_gts_total_gain_to_scale, IIO_GTS_HELPER);
> >
> > However the x86_64 native build of the mainline kernel 6.13.0-rc6 on my laptop went just fine with this patch.
> >
> > Regards,
> > Subhajit Ghosh
>
> Hi Subhajit,
>
> You've run into a tree wide change wrt to those quote that went in just after rc1 of this cycle.
> The error message is less than helpful and we've spent all cycle fixing these up :(
>
> Anyhow this is expected if backporting.
>
> Jonathan
>
Applied to the testing branch of iio.git. I'll be rebasing on rc1 once it
is available and then push this out as normal togreg branch.
Thanks
Jonathan
>
>
prev parent reply other threads:[~2025-01-18 17:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-16 8:56 [PATCH v2] iio: gts: Simplify available scale table build Matti Vaittinen
2024-12-20 19:21 ` Jonathan Cameron
2024-12-22 9:24 ` Matti Vaittinen
2025-01-10 14:26 ` Matti Vaittinen
2025-01-11 4:17 ` Subhajit Ghosh
2025-01-11 12:42 ` Jonathan Cameron
2025-01-18 17:17 ` Jonathan Cameron [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=20250118171751.4d966c98@jic23-huawei \
--to=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matti.vaittinen@fi.rohmeurope.com \
--cc=mazziesaccount@gmail.com \
--cc=muditsharma.info@gmail.com \
--cc=subhajit.ghosh@tweaklogic.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox