[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <82ef9505-f8ae-36d0-fdeb-9bfc92aec557@amd.com>
Date: Thu, 6 Apr 2023 06:58:07 -0500
From: Mario Limonciello <mario.limonciello@....com>
To: Wolfram Sang <wsa@...nel.org>,
Herbert Xu <herbert@...dor.apana.org.au>,
Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
Mika Westerberg <mika.westerberg@...ux.intel.com>,
Jan Dabros <jsd@...ihalf.com>, linux-crypto@...r.kernel.org,
linux-i2c@...r.kernel.org, Held Felix <Felix.Held@....com>,
linux-kernel@...r.kernel.org,
Mark Hasemeyer <markhas@...omium.org>,
Grzegorz Bernacki <gjb@...ihalf.com>
Subject: Re: [PATCH v8 0/6] Use CCP driver to handle PSP I2C arbitration
On 4/6/23 01:42, Wolfram Sang wrote:
> On Mon, Apr 03, 2023 at 01:32:09PM -0500, Mario Limonciello wrote:
>> 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.
> How should this go upstream, i.e. are there dependencies? Shall I pick
> the I2C patches or is it better if all goes via the crypto tree?
>
IMO it's better to go through the crypto tree. There are dependencies
in the crypto part from the earlier series that was merged.
Powered by blists - more mailing lists