From: Jarkko Nikula <jarkko.nikula@linux.intel.com>
To: "Mario Limonciello" <mario.limonciello@amd.com>,
"Jan Dąbroś" <jsd@semihalf.com>,
"Grzegorz Bernacki" <gjb@semihalf.com>,
"Mark Hasemeyer" <markhas@chromium.org>,
"Andy Shevchenko" <andriy.shevchenko@linux.intel.com>,
"Mika Westerberg" <mika.westerberg@linux.intel.com>
Cc: Felix Held <Felix.Held@amd.com>,
linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v7 6/6] i2c: designware: Add doorbell support for Mendocino
Date: Fri, 31 Mar 2023 14:55:53 +0300 [thread overview]
Message-ID: <b6d72005-5c5e-2716-1e6c-5d4e2ce3e60a@linux.intel.com> (raw)
In-Reply-To: <20230329220753.7741-7-mario.limonciello@amd.com>
On 3/30/23 01:07, Mario Limonciello wrote:
> Mendocino and later platform don't use the platform feature mailbox for
> communication for I2C arbitration, they rely upon ringing a doorbell.
>
> Detect the platform by the device ID of the root port and choose the
> appropriate method.
>
> Link: https://lore.kernel.org/linux-i2c/20220916131854.687371-3-jsd@semihalf.com/
> Signed-off-by: Mario Limonciello <mario.limonciello@amd.com>
> ---
> v6->v7:
> * Add missing pci_dev_put()
> * s/mendocino/doorbell/
> v5->v6:
> * Handle Mendocino busy code like Cezanne
> v4->v5:
> * Poll for busy
> * Rename to mendocino
> * Add explicit dependency on PCI
> v3->v4:
> * Adjust to use PCI device ID and function pointers instead
> v2->v3:
> * Use CPU ID rather than ACPI ID, this will be pushed to a later patch
> v1->v2:
> * New patch
> ---
> drivers/i2c/busses/Kconfig | 1 +
> drivers/i2c/busses/i2c-designware-amdpsp.c | 26 +++++++++++++++++++++-
> 2 files changed, 26 insertions(+), 1 deletion(-)
>
Acked-by: Jarkko Nikula <jarkko.nikula@linux.intel.com>
next prev parent reply other threads:[~2023-03-31 11:56 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-29 22:07 [PATCH v7 0/6] Use CCP driver to handle PSP I2C arbitration Mario Limonciello
2023-03-29 22:07 ` [PATCH v7 1/6] crypto: ccp: Drop extra doorbell checks Mario Limonciello
2023-03-31 19:28 ` Mark Hasemeyer
2023-03-29 22:07 ` [PATCH v7 2/6] crypto: ccp: Bump up doorbell debug message to error Mario Limonciello
2023-03-29 22:07 ` [PATCH v7 3/6] crypto: ccp: Return doorbell status code as an argument Mario Limonciello
2023-03-31 19:29 ` Mark Hasemeyer
2023-03-29 22:07 ` [PATCH v7 4/6] crypto: ccp: Use lower 8 bytes to communicate with doorbell command register Mario Limonciello
2023-03-31 19:31 ` Mark Hasemeyer
2023-03-29 22:07 ` [PATCH v7 5/6] i2c: designware: Use PCI PSP driver for communication Mario Limonciello
2023-03-31 11:53 ` Jarkko Nikula
2023-03-31 12:03 ` Jan Dąbroś
2023-03-31 14:13 ` Limonciello, Mario
2023-03-31 19:32 ` Mark Hasemeyer
2023-04-01 7:39 ` kernel test robot
2023-03-29 22:07 ` [PATCH v7 6/6] i2c: designware: Add doorbell support for Mendocino Mario Limonciello
2023-03-31 11:55 ` Jarkko Nikula [this message]
2023-03-31 19:33 ` Mark Hasemeyer
2023-04-01 19:38 ` kernel test robot
2023-03-31 19:34 ` [PATCH v7 0/6] Use CCP driver to handle PSP I2C arbitration Mark Hasemeyer
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=b6d72005-5c5e-2716-1e6c-5d4e2ce3e60a@linux.intel.com \
--to=jarkko.nikula@linux.intel.com \
--cc=Felix.Held@amd.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=gjb@semihalf.com \
--cc=jsd@semihalf.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=markhas@chromium.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