From: Jarkko Nikula <jarkko.nikula@linux.intel.com>
To: Jean Delvare <jdelvare@suse.de>, Linux I2C <linux-i2c@vger.kernel.org>
Cc: Heiner Kallweit <hkallweit1@gmail.com>
Subject: Re: [PATCH 2/2] i2c: i801: Add support for the Process Call command
Date: Wed, 2 Mar 2022 16:12:52 +0200 [thread overview]
Message-ID: <580a47c1-6a2a-2703-b6ce-1705a0467cf4@linux.intel.com> (raw)
In-Reply-To: <20220301173937.636a21ce@endymion.delvare>
On 3/1/22 18:39, Jean Delvare wrote:
> The Process Call command is implemented by the hardware since the very
> first Intel 82801 chipset, and trivial to support. Oscar Romero
> Matamala from the Georgia Institute of Technology told me it is needed
> for an experiment his team is working on at the moment, so let's just
> add support for it.
>
> Signed-off-by: Jean Delvare <jdelvare@suse.de>
> ---
> Disclaimer: untested code. I don't have any device at hand which
> supports the Process Call command so I just can't test it. If anyone
> has a chance, please test. If not, I hope Oscar will be able to test it
> soon.
>
> drivers/i2c/busses/i2c-i801.c | 12 +++++++++++-
> 1 file changed, 11 insertions(+), 1 deletion(-)
>
As far as I can see this follows how it is depicted in the specification.
Reviewed-by: Jarkko Nikula <jarkko.nikula@linux.intel.com>
next prev parent reply other threads:[~2022-03-02 14:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-01 16:28 [PATCH 1/2] i2c: i801: Drop useless masking in i801_access Jean Delvare
2022-03-01 16:39 ` [PATCH 2/2] i2c: i801: Add support for the Process Call command Jean Delvare
2022-03-02 14:12 ` Jarkko Nikula [this message]
2022-03-02 13:54 ` [PATCH 1/2] i2c: i801: Drop useless masking in i801_access Jarkko Nikula
2022-03-02 21:12 ` Wolfram Sang
2022-03-02 21:13 ` Wolfram Sang
2022-03-03 16:41 ` Jean Delvare
2022-03-03 18:22 ` 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=580a47c1-6a2a-2703-b6ce-1705a0467cf4@linux.intel.com \
--to=jarkko.nikula@linux.intel.com \
--cc=hkallweit1@gmail.com \
--cc=jdelvare@suse.de \
--cc=linux-i2c@vger.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