From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: ende.tan@starfivetech.com
Cc: linux-i2c@vger.kernel.org, jarkko.nikula@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 09:55:16 +0300 [thread overview]
Message-ID: <Z_yxVJVc69ljaDZe@smile.fi.intel.com> (raw)
In-Reply-To: <20250412093414.39351-1-ende.tan@starfivetech.com>
On Sat, Apr 12, 2025 at 05:34:14PM +0800, ende.tan@starfivetech.com wrote:
> From: Tan En De <ende.tan@starfivetech.com>
>
> Add support for SMBus Quick Read and Quick Write commands.
it's interesting how you made a versioning. Just run
`git format-patch -v<X>...` where <X> is the number of version you want,
it will make it properly in the Subject.
...
> + /* i2c-core-smbus.c: Only I2C_SMBUS_QUICK has msg[0].len = 0 */
Please, remove filenames from the code, better to refer to the actual functions
as func(). This helps also to grep for all usages in case of renaming.
...
> + /* i2c-core-smbus.c: Only I2C_SMBUS_QUICK has msg[0].len = 0 */
Ditto.
...
> + regmap_write(
> + dev->map, DW_IC_DATA_CMD,
Something wrong with the indentation. And you have plenty of room on the
previous line.
> + *buf | DW_IC_DATA_CMD_STOP |
> + ((msgs[dev->msg_write_idx].flags & I2C_M_RD) ?
> + DW_IC_DATA_CMD_CMD : 0)
> + );
...
> - dev->functionality = I2C_FUNC_10BIT_ADDR | DW_IC_DEFAULT_FUNCTIONALITY;
> + dev->functionality = I2C_FUNC_10BIT_ADDR |
> + I2C_FUNC_SMBUS_QUICK |
> + DW_IC_DEFAULT_FUNCTIONALITY;
Ditto.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2025-04-14 6:55 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 [this message]
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
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=Z_yxVJVc69ljaDZe@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=andi.shyti@kernel.org \
--cc=ende.tan@starfivetech.com \
--cc=endeneer@gmail.com \
--cc=jarkko.nikula@linux.intel.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