From: Alain Volmat <alain.volmat@foss.st.com>
To: Wolfram Sang <wsa@kernel.org>
Cc: <linux-i2c@vger.kernel.org>,
<linux-stm32@st-md-mailman.stormreply.com>,
<pierre-yves.mordret@foss.st.com>
Subject: Re: [PATCH] i2c: stm32f7: remove noisy and imprecise log messages
Date: Tue, 30 Nov 2021 17:25:34 +0100 [thread overview]
Message-ID: <20211130162534.GA813993@gnbcxd0016.gnb.st.com> (raw)
In-Reply-To: <20211130093816.12789-1-wsa@kernel.org>
Hi Wolfram,
On Tue, Nov 30, 2021 at 10:38:16AM +0100, Wolfram Sang wrote:
> The log messages talk about 'bus recovery' while it is not a bus
> recovery with 9 pulses but merely a controller reset. Controller resets
> are not worth log messages. The 'bus busy' message should be emitted by
> upper layers, a busy bus may be expectected in some cases.
>
> Signed-off-by: Wolfram Sang <wsa@kernel.org>
> ---
>
> Alain, do you agree? Only compile tested.
Yes I fully agree with that, thanks for doing that.
2 minor points:
- s/expectected/expected, within the commit log
- looking at this area of code again, it appears that the function stm32f7_i2c_release_bus
is ALWAYS returning 0. So it should actually be a void function. I thus
propose, if you agree with that, that I propose, and apply a patch PRIOR to your/this patch
to change that and remove the error checking of the stm32f7_i2c_release_bus function since it is useless.
Is that fine for you ?
Alain
>
> drivers/i2c/busses/i2c-stm32f7.c | 8 +-------
> 1 file changed, 1 insertion(+), 7 deletions(-)
>
> diff --git a/drivers/i2c/busses/i2c-stm32f7.c b/drivers/i2c/busses/i2c-stm32f7.c
> index b9b19a2a2ffa..e0e7d0001cbc 100644
> --- a/drivers/i2c/busses/i2c-stm32f7.c
> +++ b/drivers/i2c/busses/i2c-stm32f7.c
> @@ -832,8 +832,6 @@ static int stm32f7_i2c_release_bus(struct i2c_adapter *i2c_adap)
> {
> struct stm32f7_i2c_dev *i2c_dev = i2c_get_adapdata(i2c_adap);
>
> - dev_info(i2c_dev->dev, "Trying to recover bus\n");
> -
> stm32f7_i2c_clr_bits(i2c_dev->base + STM32F7_I2C_CR1,
> STM32F7_I2C_CR1_PE);
>
> @@ -854,13 +852,9 @@ static int stm32f7_i2c_wait_free_bus(struct stm32f7_i2c_dev *i2c_dev)
> if (!ret)
> return 0;
>
> - dev_info(i2c_dev->dev, "bus busy\n");
> -
> ret = stm32f7_i2c_release_bus(&i2c_dev->adap);
> - if (ret) {
> - dev_err(i2c_dev->dev, "Failed to recover the bus (%d)\n", ret);
> + if (ret)
> return ret;
> - }
>
> return -EBUSY;
> }
> --
> 2.30.2
>
next prev parent reply other threads:[~2021-11-30 16:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-30 9:38 [PATCH] i2c: stm32f7: remove noisy and imprecise log messages Wolfram Sang
2021-11-30 16:25 ` Alain Volmat [this message]
2021-11-30 21:41 ` Wolfram Sang
2021-12-01 10:59 ` Alain Volmat
2021-12-01 11:04 ` Wolfram Sang
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=20211130162534.GA813993@gnbcxd0016.gnb.st.com \
--to=alain.volmat@foss.st.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=pierre-yves.mordret@foss.st.com \
--cc=wsa@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