From: Jonathan Cameron <jic23@kernel.org>
To: Brian Masney <masneyb@onstation.org>
Cc: devel@driverdev.osuosl.org, lars@metafoo.de,
linux-iio@vger.kernel.org, gregkh@linuxfoundation.org,
linux-kernel@vger.kernel.org, Jon.Brenner@ams.com,
pmeerw@pmeerw.net, knaack.h@gmx.de
Subject: Re: [PATCH 10/12] staging: iio: tsl2x7x: make logging consistent and correct newlines
Date: Sat, 10 Mar 2018 14:52:40 +0000 [thread overview]
Message-ID: <20180310145240.40cac123@archlinux> (raw)
In-Reply-To: <20180304014942.18727-11-masneyb@onstation.org>
On Sat, 3 Mar 2018 20:49:40 -0500
Brian Masney <masneyb@onstation.org> wrote:
> This patch updates all of the logging commands so that they are
> consistent with the other messages, includes __func__ in the message,
> and all of the messages include newlines.
>
> This patch also removes some debug log messages from tsl2x7x_prox_cal().
>
> Signed-off-by: Brian Masney <masneyb@onstation.org>
Hmm. I nearly fixed this one up but there are a few too many elements I don't
agree with.
> ---
> drivers/staging/iio/light/tsl2x7x.c | 58 ++++++++++++++++++++-----------------
> 1 file changed, 31 insertions(+), 27 deletions(-)
>
> diff --git a/drivers/staging/iio/light/tsl2x7x.c b/drivers/staging/iio/light/tsl2x7x.c
> index da7a4e025083..fb91c46c8747 100644
> --- a/drivers/staging/iio/light/tsl2x7x.c
> +++ b/drivers/staging/iio/light/tsl2x7x.c
> @@ -378,7 +378,8 @@ static int tsl2x7x_get_lux(struct iio_dev *indio_dev)
> ret = i2c_smbus_read_byte_data(chip->client, reg);
> if (ret < 0) {
> dev_err(&chip->client->dev,
> - "failed to read. err=%x\n", ret);
> + "%s: failed to read from register %x: %d\n",
> + __func__, reg, ret);
> goto out_unlock;
> }
>
> @@ -424,7 +425,9 @@ static int tsl2x7x_get_lux(struct iio_dev *indio_dev)
>
> /* note: lux is 31 bit max at this point */
> if (ch1lux > ch0lux) {
> - dev_dbg(&chip->client->dev, "ch1lux > ch0lux-return last value\n");
> + dev_dbg(&chip->client->dev,
> + "%s: ch1lux > ch0lux; returning last value\n",
> + __func__);
> ret = chip->als_cur_info.lux;
> goto out_unlock;
> }
> @@ -600,7 +603,8 @@ static int tsl2x7x_als_calibrate(struct iio_dev *indio_dev)
>
> chip->settings.als_gain_trim = ret;
> dev_info(&chip->client->dev,
> - "%s als_calibrate completed\n", chip->client->name);
> + "%s: %s ALS calibration successfully completed\n",
> + __func__, chip->client->name);
I'm happy with having function name in errors, but it's just noise in info
prints.
Mind you this dev_info should go or become dev_dbg - it is superflous
detail to put in the kernel logs.
>
> return ret;
> }
> @@ -644,7 +648,8 @@ static int tsl2x7x_chip_on(struct iio_dev *indio_dev)
> /* and make sure we're not already on */
> if (chip->tsl2x7x_chip_status == TSL2X7X_CHIP_WORKING) {
> /* if forcing a register update - turn off, then on */
> - dev_info(&chip->client->dev, "device is already enabled\n");
> + dev_info(&chip->client->dev, "%s: device is already enabled\n",
> + __func__);
Again noise. dev_dbg or drop entirely as it doesn't need to be logged.
> return -EINVAL;
> }
>
> @@ -681,12 +686,14 @@ static int tsl2x7x_chip_on(struct iio_dev *indio_dev)
> */
> for (i = 0, dev_reg = chip->tsl2x7x_config;
> i < TSL2X7X_MAX_CONFIG_REG; i++) {
> - ret = i2c_smbus_write_byte_data(chip->client,
> - TSL2X7X_CMD_REG + i,
> + int reg = TSL2X7X_CMD_REG + i;
> +
> + ret = i2c_smbus_write_byte_data(chip->client, reg,
> *dev_reg++);
> if (ret < 0) {
> dev_err(&chip->client->dev,
> - "failed on write to reg %d.\n", i);
> + "%s: failed to write to register %x: %d\n",
> + __func__, reg, ret);
> return ret;
> }
> }
> @@ -708,7 +715,8 @@ static int tsl2x7x_chip_on(struct iio_dev *indio_dev)
> chip->tsl2x7x_chip_status = TSL2X7X_CHIP_WORKING;
>
> if (chip->settings.interrupts_en != 0) {
> - dev_info(&chip->client->dev, "Setting Up Interrupt(s)\n");
> + dev_info(&chip->client->dev, "%s: Setting up interrupt(s)\n",
> + __func__);
>
> reg_val = TSL2X7X_CNTL_PWR_ON | TSL2X7X_CNTL_ADC_ENBL;
> if (chip->settings.interrupts_en == 0x20 ||
> @@ -819,8 +827,8 @@ static int tsl2x7x_prox_cal(struct iio_dev *indio_dev)
>
> if (chip->settings.prox_max_samples_cal > MAX_SAMPLES_CAL) {
> dev_err(&chip->client->dev,
> - "max prox samples cal is too big: %d\n",
> - chip->settings.prox_max_samples_cal);
> + "%s: prox_max_samples_cal %d is too big\n",
> + __func__, chip->settings.prox_max_samples_cal);
> chip->settings.prox_max_samples_cal = MAX_SAMPLES_CAL;
> }
>
> @@ -845,8 +853,6 @@ static int tsl2x7x_prox_cal(struct iio_dev *indio_dev)
> if (ret < 0)
> return ret;
> prox_history[i] = chip->prox_data;
> - dev_info(&chip->client->dev, "2 i=%d prox data= %d\n",
> - i, chip->prox_data);
> }
>
> ret = tsl2x7x_chip_off(indio_dev);
> @@ -857,12 +863,6 @@ static int tsl2x7x_prox_cal(struct iio_dev *indio_dev)
> chip->settings.prox_max_samples_cal, cal);
> chip->settings.prox_thres_high = (cal->max << 1) - cal->mean;
>
> - dev_info(&chip->client->dev, " cal min=%d mean=%d max=%d\n",
> - cal->min, cal->mean, cal->max);
> - dev_info(&chip->client->dev,
> - "%s proximity threshold set to %d\n",
> - chip->client->name, chip->settings.prox_thres_high);
> -
> /* back to the way they were */
> chip->settings.interrupts_en = tmp_irq_settings;
> if (current_state == TSL2X7X_CHIP_WORKING) {
> @@ -1000,12 +1000,14 @@ static ssize_t in_illuminance0_lux_table_store(struct device *dev,
> n = value[0];
> if ((n % 3) || n < 6 ||
> n > ((ARRAY_SIZE(chip->tsl2x7x_device_lux) - 1) * 3)) {
> - dev_info(dev, "LUX TABLE INPUT ERROR 1 Value[0]=%d\n", n);
> + dev_info(dev, "%s: lux table input error 1. n=%d\n",
> + __func__, n);
> return -EINVAL;
> }
>
> if ((value[(n - 2)] | value[(n - 1)] | value[n]) != 0) {
> - dev_info(dev, "LUX TABLE INPUT ERROR 2 Value[0]=%d\n", n);
> + dev_info(dev, "%s: lux table input error 2. n=%d\n",
> + __func__, n);
dev_dbg or drop it.
> return -EINVAL;
> }
>
> @@ -1150,14 +1152,14 @@ static int tsl2x7x_write_event_value(struct iio_dev *indio_dev,
> chip->settings.persistence &= 0xF0;
> chip->settings.persistence |=
> (filter_delay & 0x0F);
> - dev_info(&chip->client->dev, "%s: ALS persistence = %d",
> + dev_info(&chip->client->dev, "%s: ALS persistence = %d\n",
> __func__, filter_delay);
Again, dev_dbg at the most - or drop it.
> } else {
> chip->settings.persistence &= 0x0F;
> chip->settings.persistence |=
> ((filter_delay << 4) & 0xF0);
> dev_info(&chip->client->dev,
> - "%s: Proximity persistence = %d",
> + "%s: Proximity persistence = %d\n",
> __func__, filter_delay);
> }
> ret = 0;
> @@ -1372,7 +1374,7 @@ static int tsl2x7x_write_raw(struct iio_dev *indio_dev,
> chip->settings.als_time =
> TSL2X7X_MAX_TIMER_CNT - (val2 / TSL2X7X_MIN_ITIME);
>
> - dev_info(&chip->client->dev, "%s: als time = %d",
> + dev_info(&chip->client->dev, "%s: als time = %d\n",
> __func__, chip->settings.als_time);
Drop it.
> break;
> default:
> @@ -1738,8 +1740,9 @@ static int tsl2x7x_probe(struct i2c_client *clientp,
>
> ret = i2c_smbus_write_byte(clientp, TSL2X7X_CMD_REG | TSL2X7X_CNTRL);
> if (ret < 0) {
> - dev_err(&clientp->dev, "write to cmd reg failed. err = %d\n",
> - ret);
> + dev_err(&clientp->dev,
> + "%s: Failed to write to CMD register: %d\n",
> + __func__, ret);
> return ret;
> }
>
> @@ -1773,7 +1776,7 @@ static int tsl2x7x_probe(struct i2c_client *clientp,
> indio_dev);
> if (ret) {
> dev_err(&clientp->dev,
> - "%s: irq request failed", __func__);
> + "%s: IRQ request failed\n", __func__);
> return ret;
> }
> }
> @@ -1790,7 +1793,8 @@ static int tsl2x7x_probe(struct i2c_client *clientp,
> return ret;
> }
>
> - dev_info(&clientp->dev, "%s Light sensor found.\n", id->name);
> + dev_info(&clientp->dev, "%s: %s Light sensor found.\n", __func__,
> + id->name);
Again, unnecessary logging. Definitely doesn't also want the function name.
People 'might' care about whether the sensor is found, but not which function
it is in.
Jonathan
>
> return 0;
> }
_______________________________________________
devel mailing list
devel@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
next prev parent reply other threads:[~2018-03-10 14:52 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-04 1:49 [PATCH 00/12] staging cleanups Brian Masney
2018-03-04 1:49 ` [PATCH 01/12] staging: iio: tsl2x7x: remove power functions from tsl2X7X_platform_data Brian Masney
2018-03-10 14:20 ` Jonathan Cameron
2018-03-04 1:49 ` [PATCH 02/12] staging: iio: tsl2x7x: add common function for clearing interrupts Brian Masney
2018-03-10 14:27 ` Jonathan Cameron
2018-03-04 1:49 ` [PATCH 03/12] staging: iio: tsl2x7x: add common function for reading chip status Brian Masney
2018-03-10 14:34 ` Jonathan Cameron
2018-03-04 1:49 ` [PATCH 04/12] staging: iio: tsl2x7x: add common function for writing to the control register Brian Masney
2018-03-10 14:36 ` Jonathan Cameron
2018-03-04 1:49 ` [PATCH 05/12] staging: iio: tsl2x7x: convert mutex_trylock() to mutex_lock() Brian Masney
2018-03-10 14:39 ` Jonathan Cameron
2018-03-04 1:49 ` [PATCH 06/12] staging: iio: tsl2x7x: correctly return errors in tsl2x7x_get_prox() Brian Masney
2018-03-10 14:42 ` Jonathan Cameron
2018-03-04 1:49 ` [PATCH 07/12] staging: iio: tsl2x7x: correct 'Avoid CamelCase' warning from checkpatch Brian Masney
2018-03-10 14:43 ` Jonathan Cameron
2018-03-04 1:49 ` [PATCH 08/12] staging: iio: tsl2x7x: add error handling to tsl2x7x_prox_cal() Brian Masney
2018-03-10 14:44 ` Jonathan Cameron
2018-03-04 1:49 ` [PATCH 09/12] staging: iio: tsl2x7x: add missing error checks Brian Masney
2018-03-10 14:45 ` Jonathan Cameron
2018-03-04 1:49 ` [PATCH 10/12] staging: iio: tsl2x7x: make logging consistent and correct newlines Brian Masney
2018-03-10 14:52 ` Jonathan Cameron [this message]
2018-03-11 13:45 ` Jonathan Cameron
2018-03-04 1:49 ` [PATCH 11/12] staging: iio: tsl2x7x: remove unnecessary sysfs attribute Brian Masney
2018-03-10 14:54 ` Jonathan Cameron
2018-03-04 1:49 ` [PATCH 12/12] staging: iio: tsl2x7x: make proximity sensor function correctly Brian Masney
2018-03-10 14:56 ` 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=20180310145240.40cac123@archlinux \
--to=jic23@kernel.org \
--cc=Jon.Brenner@ams.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masneyb@onstation.org \
--cc=pmeerw@pmeerw.net \
/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