From: Petre Rodan <petre.rodan@subdimension.ro>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: linux-kernel@vger.kernel.org, linux-iio@vger.kernel.org,
Jonathan Cameron <jic23@kernel.org>,
Lars-Peter Clausen <lars@metafoo.de>,
Angel Iglesias <ang.iglesiasg@gmail.com>,
Matti Vaittinen <mazziesaccount@gmail.com>,
Andreas Klinger <ak@it-klinger.de>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>
Subject: Re: [PATCH v6 2/2] iio: pressure: driver for Honeywell HSC/SSC series
Date: Wed, 29 Nov 2023 21:12:52 +0200 [thread overview]
Message-ID: <ZWeNNMfqKquDYI9X@sunspire> (raw)
In-Reply-To: <ZWdzz7VzCW5ctend@smile.fi.intel.com>
hello!
On Wed, Nov 29, 2023 at 07:24:31PM +0200, Andy Shevchenko wrote:
> On Wed, Nov 29, 2023 at 07:04:12PM +0200, Petre Rodan wrote:
> > Adds driver for digital Honeywell TruStability HSC and SSC series
> > pressure and temperature sensors.
> > Communication is one way. The sensor only requires 4 bytes worth of
> > clock pulses on both i2c and spi in order to push the data out.
> > The i2c address is hardcoded and depends on the part number.
> > There is no additional GPIO control.
>
> ...
>
> > v6: modifications based on Andy's review
> > - use str_has_prefix(), match_string() instead of strncmp()
>
> And why not using the respective property API for that case where
> match_string() is used?
I'm lost again.
437: ret = device_property_read_string(dev, "honeywell,pressure-triplet",
&triplet);
[..]
455: ret = match_string(hsc_triplet_variants, HSC_VARIANTS_MAX,
triplet);
if (ret < 0)
return dev_err_probe(dev, -EINVAL,
"honeywell,pressure-triplet is invalid\n");
hsc->pmin = hsc_range_config[ret].pmin;
hsc->pmax = hsc_range_config[ret].pmax;
triplet is got via device_property_read_string(), is there some other property
function I should be using?
> I'm also a bit tired to repeat about:
> - capitalization and punctuation in the multi-line comments;
> - broken indentation is some cases.
sorry about that. I removed all comments you complained about.
just to simplify the process.
> Otherwise it's a good stuff, I leave it now to Jonathan.
>
> ...
>
> > + tmp = div_s64(((s64)(hsc->pmax - hsc->pmin)) * MICRO,
> > + hsc->outmax - hsc->outmin);
> > + hsc->p_scale = div_s64_rem(tmp, NANO, &hsc->p_scale_dec);
> > + tmp = div_s64(((s64)hsc->pmin * (s64)(hsc->outmax - hsc->outmin)) *
> > + MICRO, hsc->pmax - hsc->pmin);
>
> Why not put MICRO on the previous line?
oh well, from the review I understood you were asking for the replacement of
NANO with MICRO on the previous instruction and it did not make much sense ( units
are in pascal and we need a kilopascal output to userland)
now I understood it's an indentation request. however moving MICRO will cross
the 80 column rule. but if there will be yet another modification request I'll move it.
cheers,
peter
>
> --
> With Best Regards,
> Andy Shevchenko
>
>
--
petre rodan
next prev parent reply other threads:[~2023-11-29 19:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-29 17:04 [PATCH v6 1/2] dt-bindings: iio: pressure: add honeywell,hsc030 Petre Rodan
2023-11-29 17:04 ` [PATCH v6 2/2] iio: pressure: driver for Honeywell HSC/SSC series Petre Rodan
2023-11-29 17:24 ` Andy Shevchenko
2023-11-29 19:12 ` Petre Rodan [this message]
2023-11-30 13:33 ` Andy Shevchenko
2023-12-02 16:06 ` Petre Rodan
2023-12-04 12:57 ` Andy Shevchenko
2023-12-04 19:59 ` Petre Rodan
2023-12-04 12:17 ` Jonathan Cameron
2023-11-30 8:31 ` [PATCH v6 1/2] dt-bindings: iio: pressure: add honeywell,hsc030 Krzysztof Kozlowski
2023-11-30 9:36 ` Petre Rodan
2023-11-30 12:04 ` Krzysztof Kozlowski
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=ZWeNNMfqKquDYI9X@sunspire \
--to=petre.rodan@subdimension.ro \
--cc=ak@it-klinger.de \
--cc=andriy.shevchenko@linux.intel.com \
--cc=ang.iglesiasg@gmail.com \
--cc=jic23@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mazziesaccount@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.