From: Jonathan Cameron <jic23@kernel.org>
To: Vasileios Amoiridis <vassilisamir@gmail.com>
Cc: lars@metafoo.de, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, andriy.shevchenko@linux.intel.com,
anshulusr@gmail.com, gustavograzs@gmail.com,
linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 06/13] iio: chemical: bme680: Fix indentation and unnecessary spaces
Date: Sun, 27 Oct 2024 10:08:41 +0000 [thread overview]
Message-ID: <20241027100841.46cafdb2@jic23-huawei> (raw)
In-Reply-To: <20241021195316.58911-7-vassilisamir@gmail.com>
On Mon, 21 Oct 2024 21:53:09 +0200
Vasileios Amoiridis <vassilisamir@gmail.com> wrote:
> Fix indentation issues, line breaking and unnecessary spaces
> reported by checkpatch.pl.
>
> Signed-off-by: Vasileios Amoiridis <vassilisamir@gmail.com>
> ---
> drivers/iio/chemical/bme680_core.c | 21 +++++++++------------
> 1 file changed, 9 insertions(+), 12 deletions(-)
>
> diff --git a/drivers/iio/chemical/bme680_core.c b/drivers/iio/chemical/bme680_core.c
> index 2ff85e29bfc1..2ad427f5deb4 100644
> --- a/drivers/iio/chemical/bme680_core.c
> +++ b/drivers/iio/chemical/bme680_core.c
> @@ -229,7 +229,7 @@ static int bme680_read_calib(struct bme680_data *data,
> calib->res_heat_val = data->bme680_cal_buf_3[RES_HEAT_VAL];
>
> calib->res_heat_range = FIELD_GET(BME680_RHRANGE_MASK,
> - data->bme680_cal_buf_3[RES_HEAT_RANGE]);
> + data->bme680_cal_buf_3[RES_HEAT_RANGE]);
>
> calib->range_sw_err = FIELD_GET(BME680_RSERROR_MASK,
> data->bme680_cal_buf_3[RANGE_SW_ERR]);
> @@ -450,12 +450,12 @@ static u32 bme680_compensate_gas(struct bme680_data *data, u16 gas_res_adc,
> 2147483647u, 2126008810u, 2147483647u, 2147483647u
> };
>
> - var1 = ((1340 + (5 * (s64) calib->range_sw_err)) *
> - ((s64)lookup_table[gas_range])) >> 16;
> + var1 = ((1340LL + (5 * calib->range_sw_err)) *
> + (lookup_table[gas_range])) >> 16;
Everything other than this one is straight forward and requires
checking types of range_sw_err is less than 32 bit for example.
For cleanup I'd normally avoid these subtle cases.
An extra type case or two does little harm to readability.
Anyhow, with that in mind I've applied anyway.
> var2 = ((gas_res_adc << 15) - 16777216) + var1;
> var3 = ((125000 << (15 - gas_range)) * var1) >> 9;
> var3 += (var2 >> 1);
> - calc_gas_res = div64_s64(var3, (s64) var2);
> + calc_gas_res = div64_s64(var3, (s64)var2);
>
> return calc_gas_res;
> }
> @@ -473,7 +473,7 @@ static u8 bme680_calc_heater_res(struct bme680_data *data, u16 temp)
> if (temp > 400) /* Cap temperature */
> temp = 400;
>
> - var1 = (((s32) BME680_AMB_TEMP * calib->par_gh3) / 1000) * 256;
> + var1 = (((s32)BME680_AMB_TEMP * calib->par_gh3) / 1000) * 256;
> var2 = (calib->par_gh1 + 784) * (((((calib->par_gh2 + 154009) *
> temp * 5) / 100)
> + 3276800) / 10);
> @@ -569,9 +569,8 @@ static int bme680_chip_config(struct bme680_data *data)
> int ret;
> u8 osrs;
>
> - osrs = FIELD_PREP(
> - BME680_OSRS_HUMIDITY_MASK,
> - bme680_oversampling_to_reg(data->oversampling_humid));
> + osrs = FIELD_PREP(BME680_OSRS_HUMIDITY_MASK,
> + bme680_oversampling_to_reg(data->oversampling_humid));
> /*
> * Highly recommended to set oversampling of humidity before
> * temperature/pressure oversampling.
> @@ -585,8 +584,7 @@ static int bme680_chip_config(struct bme680_data *data)
>
> /* IIR filter settings */
> ret = regmap_update_bits(data->regmap, BME680_REG_CONFIG,
> - BME680_FILTER_MASK,
> - BME680_FILTER_COEFF_VAL);
> + BME680_FILTER_MASK, BME680_FILTER_COEFF_VAL);
> if (ret < 0) {
> dev_err(dev, "failed to write config register\n");
> return ret;
> @@ -885,8 +883,7 @@ int bme680_core_probe(struct device *dev, struct regmap *regmap,
> data->heater_temp = 320; /* degree Celsius */
> data->heater_dur = 150; /* milliseconds */
>
> - ret = regmap_write(regmap, BME680_REG_SOFT_RESET,
> - BME680_CMD_SOFTRESET);
> + ret = regmap_write(regmap, BME680_REG_SOFT_RESET, BME680_CMD_SOFTRESET);
> if (ret < 0)
> return dev_err_probe(dev, ret, "Failed to reset chip\n");
>
next prev parent reply other threads:[~2024-10-27 10:08 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-21 19:53 [PATCH v2 00/13]: chemical: bme680: 2nd set of cleanup Vasileios Amoiridis
2024-10-21 19:53 ` [PATCH v2 01/13] iio: chemical: bme680: Fix missing header Vasileios Amoiridis
2024-10-21 20:13 ` Greg KH
2024-10-27 9:48 ` Jonathan Cameron
2024-10-21 19:53 ` [PATCH v2 02/13] iio: chemical: bme680: optimize startup time Vasileios Amoiridis
2024-10-27 9:53 ` Jonathan Cameron
2024-10-21 19:53 ` [PATCH v2 03/13] iio: chemical: bme680: avoid using camel case Vasileios Amoiridis
2024-10-27 9:54 ` Jonathan Cameron
2024-10-21 19:53 ` [PATCH v2 04/13] iio: chemical: bme680: refactorize set_mode() mode Vasileios Amoiridis
2024-10-27 9:56 ` Jonathan Cameron
2024-10-27 9:59 ` Jonathan Cameron
2024-10-29 23:28 ` Vasileios Amoiridis
2024-10-21 19:53 ` [PATCH v2 05/13] iio: chemical: bme680: move to fsleep() Vasileios Amoiridis
2024-10-27 10:01 ` Jonathan Cameron
2024-10-21 19:53 ` [PATCH v2 06/13] iio: chemical: bme680: Fix indentation and unnecessary spaces Vasileios Amoiridis
2024-10-27 10:08 ` Jonathan Cameron [this message]
2024-10-27 10:10 ` Jonathan Cameron
2024-10-21 19:53 ` [PATCH v2 07/13] iio: chemical: bme680: generalize read_*() functions Vasileios Amoiridis
2024-10-27 10:11 ` Jonathan Cameron
2024-10-21 19:53 ` [PATCH v2 08/13] iio: chemical: bme680: Add SCALE and RAW channels Vasileios Amoiridis
2024-10-27 10:12 ` Jonathan Cameron
2024-10-21 19:53 ` [PATCH v2 09/13] iio: chemical: bme680: Add triggered buffer support Vasileios Amoiridis
2024-10-27 10:18 ` Jonathan Cameron
2024-10-21 19:53 ` [PATCH v2 10/13] iio: chemical: bme680: Add support for preheat current Vasileios Amoiridis
2024-10-21 19:53 ` [PATCH v2 11/13] dt-bindings: iio: add binding for BME680 driver Vasileios Amoiridis
2024-10-21 21:22 ` Rob Herring (Arm)
2024-10-22 13:41 ` Rob Herring
2024-10-22 17:24 ` Jonathan Cameron
2024-10-21 19:53 ` [PATCH v2 12/13] iio: chemical: bme680: add regulators Vasileios Amoiridis
2024-10-21 19:53 ` [PATCH v2 13/13] iio: chemical: bme680: add power management Vasileios Amoiridis
2024-10-27 10:30 ` Jonathan Cameron
2024-10-30 0:24 ` Vasileios Amoiridis
2024-10-30 20:35 ` Jonathan Cameron
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=20241027100841.46cafdb2@jic23-huawei \
--to=jic23@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=anshulusr@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gustavograzs@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=vassilisamir@gmail.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;
as well as URLs for NNTP newsgroup(s).