From: Jonathan Cameron <jic23@kernel.org>
To: Marcus Folkesson <marcus.folkesson@gmail.com>
Cc: Kent Gustavsson <kent@minoris.se>,
Lars-Peter Clausen <lars@metafoo.de>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iio: adc: mcp3911: mask out device ID in debug prints
Date: Sat, 15 Oct 2022 16:30:56 +0100 [thread overview]
Message-ID: <20221015163056.3d1cf27e@jic23-huawei> (raw)
In-Reply-To: <20221010194654.676525-1-marcus.folkesson@gmail.com>
On Mon, 10 Oct 2022 21:46:54 +0200
Marcus Folkesson <marcus.folkesson@gmail.com> wrote:
> The Device ID should not be included when printing register.
>
> Signed-off-by: Marcus Folkesson <marcus.folkesson@gmail.com>
Whilst obviously not super important to backport, this is a fix
so I've applied it to the fixes-togreg branch of iio.git.
Thanks,
Jonathan
> ---
> drivers/iio/adc/mcp3911.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/iio/adc/mcp3911.c b/drivers/iio/adc/mcp3911.c
> index 2c1af11a621f..a71df9f3ab29 100644
> --- a/drivers/iio/adc/mcp3911.c
> +++ b/drivers/iio/adc/mcp3911.c
> @@ -59,6 +59,7 @@
>
> #define MCP3911_REG_READ(reg, id) ((((reg) << 1) | ((id) << 6) | (1 << 0)) & 0xff)
> #define MCP3911_REG_WRITE(reg, id) ((((reg) << 1) | ((id) << 6) | (0 << 0)) & 0xff)
> +#define MCP3911_REG_MASK GENMASK(4, 1)
>
> #define MCP3911_NUM_CHANNELS 2
> #define MCP3911_NUM_SCALES 6
> @@ -94,8 +95,8 @@ static int mcp3911_read(struct mcp3911 *adc, u8 reg, u32 *val, u8 len)
>
> be32_to_cpus(val);
> *val >>= ((4 - len) * 8);
> - dev_dbg(&adc->spi->dev, "reading 0x%x from register 0x%x\n", *val,
> - reg >> 1);
> + dev_dbg(&adc->spi->dev, "reading 0x%x from register 0x%lx\n", *val,
> + FIELD_GET(MCP3911_REG_MASK, reg));
> return ret;
> }
>
prev parent reply other threads:[~2022-10-15 15:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-10 19:46 [PATCH] iio: adc: mcp3911: mask out device ID in debug prints Marcus Folkesson
2022-10-15 15:30 ` 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=20221015163056.3d1cf27e@jic23-huawei \
--to=jic23@kernel.org \
--cc=kent@minoris.se \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcus.folkesson@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