From: Jarkko Nikula <jarkko.nikula@linux.intel.com>
To: ende.tan@starfivetech.com, linux-i2c@vger.kernel.org
Cc: andriy.shevchenko@linux.intel.com,
mika.westerberg@linux.intel.com, jsd@semihalf.com,
andi.shyti@kernel.org, linux-kernel@vger.kernel.org,
leyfoon.tan@starfivetech.com, endeneer@gmail.com
Subject: Re: [v2,1/1] i2c: designware: Add SMBus Quick Command support
Date: Mon, 14 Apr 2025 17:16:23 +0300 [thread overview]
Message-ID: <7b619cf2-8f50-4f6e-9a5f-cce9112a99b3@linux.intel.com> (raw)
In-Reply-To: <20250412093414.39351-1-ende.tan@starfivetech.com>
Hi
On 4/12/25 12:34 PM, ende.tan@starfivetech.com wrote:
> From: Tan En De <ende.tan@starfivetech.com>
>
> Add support for SMBus Quick Read and Quick Write commands.
>
> Signed-off-by: Tan En De <ende.tan@starfivetech.com>
> ---
> v1 -> v2: Removed redundant check of tx_limit and rx_limit
> ---
> drivers/i2c/busses/i2c-designware-core.h | 4 ++++
> drivers/i2c/busses/i2c-designware-master.c | 18 +++++++++++++++++-
> 2 files changed, 21 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/i2c/busses/i2c-designware-core.h b/drivers/i2c/busses/i2c-designware-core.h
> index 347843b4f5dd..91f17181ece1 100644
> --- a/drivers/i2c/busses/i2c-designware-core.h
> +++ b/drivers/i2c/busses/i2c-designware-core.h
> @@ -40,6 +40,8 @@
>
> #define DW_IC_DATA_CMD_DAT GENMASK(7, 0)
> #define DW_IC_DATA_CMD_FIRST_DATA_BYTE BIT(11)
> +#define DW_IC_DATA_CMD_STOP BIT(9)
> +#define DW_IC_DATA_CMD_CMD BIT(8)
>
If you like these defines would be nice to have in another patch before
this and convert i2c-designware-master.c to use them instead of 0x100,
BIT(9) and BIT(10) in existing code. Makes code more uniform together
with your change.
I'm not demanding it but wanted to give you idea if you like to do some
additional cleanups to the code :-)
next prev parent reply other threads:[~2025-04-14 14:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-12 9:34 ende.tan
2025-04-14 6:55 ` Andy Shevchenko
2025-04-14 8:43 ` Wolfram Sang
2025-04-14 9:02 ` Wolfram Sang
2025-04-14 9:18 ` Jarkko Nikula
2025-04-14 14:16 ` Jarkko Nikula [this message]
2025-04-20 3:44 ` EnDe Tan
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=7b619cf2-8f50-4f6e-9a5f-cce9112a99b3@linux.intel.com \
--to=jarkko.nikula@linux.intel.com \
--cc=andi.shyti@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=ende.tan@starfivetech.com \
--cc=endeneer@gmail.com \
--cc=jsd@semihalf.com \
--cc=leyfoon.tan@starfivetech.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.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
Powered by JetHome