From: Mario Limonciello <mario.limonciello@amd.com>
To: "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>,
linux-crypto@vger.kernel.org, linux-i2c@vger.kernel.org
Cc: Mario Limonciello <mario.limonciello@amd.com>,
<linux-kernel@vger.kernel.org>
Subject: [PATCH v6 0/4] Use CCP driver to handle PSP I2C arbitration
Date: Wed, 22 Mar 2023 16:02:22 -0500 [thread overview]
Message-ID: <20230322210227.464-1-mario.limonciello@amd.com> (raw)
The CCP driver now has symbols that can be used by i2c-designware-amdpsp
to handle the communication regarding i2c arbitration with the PSP for
both Cezanne and Mendocino based designs.
Utilize those symbols.
Mario Limonciello (4):
crypto: ccp: Bump up doorbell debug messages to error
crypto: ccp: Return doorbell status code as an argument
i2c: designware: Use PCI PSP driver for communication
i2c: designware: Add doorbell support for Mendocino
drivers/crypto/ccp/platform-access.c | 10 +-
drivers/i2c/busses/Kconfig | 3 +-
drivers/i2c/busses/i2c-designware-amdpsp.c | 196 +++++---------------
drivers/i2c/busses/i2c-designware-core.h | 1 -
drivers/i2c/busses/i2c-designware-platdrv.c | 1 -
include/linux/psp-platform-access.h | 5 +-
6 files changed, 58 insertions(+), 158 deletions(-)
base-commit: e6af5c0c4d32a27e04a56f29aad587e03ff427f1
--
2.34.1
next reply other threads:[~2023-03-22 21:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-22 21:02 Mario Limonciello [this message]
2023-03-22 21:02 ` [PATCH v6 3/4] i2c: designware: Use PCI PSP driver for communication Mario Limonciello
2023-03-23 13:08 ` Andy Shevchenko
2023-03-23 18:34 ` kernel test robot
2023-03-24 2:35 ` kernel test robot
2023-03-22 21:02 ` [PATCH v6 4/4] i2c: designware: Add doorbell support for Mendocino Mario Limonciello
2023-03-23 13:06 ` Andy Shevchenko
2023-03-23 13:32 ` Limonciello, Mario
2023-03-24 20:40 ` kernel test robot
2023-03-27 16:37 ` Mark Hasemeyer
2023-03-27 17:05 ` Limonciello, Mario
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=20230322210227.464-1-mario.limonciello@amd.com \
--to=mario.limonciello@amd.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=gjb@semihalf.com \
--cc=jsd@semihalf.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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