From: Conor Dooley <conor@kernel.org>
To: Andi Shyti <andi.shyti@kernel.org>
Cc: Mukesh Kumar Savaliya <quic_msavaliy@quicinc.com>,
linux-i2c@vger.kernel.org,
prashanth kumar burujukindi
<prashanthkumar.burujukindi@microchip.com>,
Conor Dooley <conor.dooley@microchip.com>,
Daire McNamara <daire.mcnamara@microchip.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] i2c: microchip-corei2c: add smbus support
Date: Tue, 6 May 2025 11:56:19 +0100 [thread overview]
Message-ID: <20250506-bunny-puma-996aafbf3f56@spud> (raw)
In-Reply-To: <7q4gdh3jcbnsptmdv6fywnwqta5nekof4wtut35apw5wphhkio@veeu4ogcm44h>
[-- Attachment #1: Type: text/plain, Size: 1647 bytes --]
On Mon, May 05, 2025 at 10:04:27PM +0200, Andi Shyti wrote:
> Hi,
>
> On Wed, Apr 30, 2025 at 05:06:09PM +0530, Mukesh Kumar Savaliya wrote:
> > On 4/30/2025 4:53 PM, Conor Dooley wrote:
> > > From: prashanth kumar burujukindi <prashanthkumar.burujukindi@microchip.com>
> > >
> > > In this driver the supported SMBUS commands are smbus_quick,
> > > smbus_byte, smbus_byte_data, smbus_word_data and smbus_block_data.
> > >
> > Write completely in imperative mood. something like :
> >
> > Add support for SMBUS commands in driver
> >
> > Add support for SMBUS commands: smbus_quick, smbus_byte, smbus_byte_data,
> > smbus_word_data, and smbus_block_data.
>
> yes, I agree that the original commit log is a bit lazy written :-)
I don't personally think the suggested wording makes any meaningful
difference, but I can rework it if required.
> > Also mention below limitations here .
I actually removed them from the commit message, since they're not
limitations just what was and was not tested. I can put them back too
if that's needed.
> > SMBUS block read is supported by the controller but has not been tested due
> > to lack of hardware. However, SMBUS I2C block read has been tested.
>
> Smbus i2c block has not been tested? If so, can we leave it out?
> What is the interest to keep it in?
What's the interest in adding any feature? Someone might want to use it.
We did not have a piece of hardware that uses it, so didn't do testing
of that specific command, but a customer may well want to so we included
it. Again, if you think removing it is the play, I can do that.
Cheers,
Conor.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2025-05-06 10:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-30 11:23 [PATCH v1] i2c: microchip-corei2c: add smbus support Conor Dooley
2025-04-30 11:36 ` Mukesh Kumar Savaliya
2025-05-05 20:04 ` Andi Shyti
2025-05-06 10:56 ` Conor Dooley [this message]
2025-05-06 12:04 ` Andi Shyti
2025-05-08 11:39 ` Conor Dooley
2025-05-12 23:42 ` Andi Shyti
2025-05-08 10:14 ` Andi Shyti
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=20250506-bunny-puma-996aafbf3f56@spud \
--to=conor@kernel.org \
--cc=andi.shyti@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=daire.mcnamara@microchip.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=prashanthkumar.burujukindi@microchip.com \
--cc=quic_msavaliy@quicinc.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