From: gregory.clement@bootlin•com (Gregory CLEMENT)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH 0/3] crypto: inside-secure: improve clock management
Date: Fri, 23 Mar 2018 17:30:46 +0100 [thread overview]
Message-ID: <874ll6wy89.fsf@bootlin.com> (raw)
In-Reply-To: <20180323160149.GC2186@gondor.apana.org.au> (Herbert Xu's message of "Sat, 24 Mar 2018 00:01:49 +0800")
Hi Herbert,
On sam., mars 24 2018, Herbert Xu <herbert@gondor•apana.org.au> wrote:
> On Tue, Mar 13, 2018 at 05:48:39PM +0100, Gregory CLEMENT wrote:
>> Hi,
>>
>> This short series fixes the way the clocks are used for the SafeXcel
>> EIP-197 controller embedded in the Marvell Armada 7K/8K SoCs. On these
>> SoCs a second one is needed in order to clock the registers. It was
>> not noticed until now because we relied on the bootloader and also
>> because the clock driver was wrong.
>>
>> Thanks to this fix, it would be possible to fix the clock driver
>> without introducing a regression.
>>
>> While I was working on the clocks I found a bug in the clock
>> management which was fixed with the first patch and should be applied
>> to v4.16.
>
> I haven't applied it to the crypto 4.16 tree because your other
> patches depend on it and I don't think the issue doesn't seem to
> be that severe.
>
> In future it would help if you can avoid such dependencies if you
> wish the patches to go in as soon as possible.
Yes sure. And I agree with you, the issue is not that severe, so it can
wait for 4.17.
>
>> The second patch is a small improvement which is aim for v4.17 as well
>> as the last patch.
>>
>> Thanks,
>>
>> Gregory
>>
>> Gregory CLEMENT (3):
>> crypto: inside-secure - fix clock management
>> crypto: inside-secure - improve clock initialization
>> crypto: inside-secure - fix clock resource by adding a register clock
>>
>> .../bindings/crypto/inside-secure-safexcel.txt | 6 ++-
>> drivers/crypto/inside-secure/safexcel.c | 47 +++++++++++++++-------
>> drivers/crypto/inside-secure/safexcel.h | 1 +
>> 3 files changed, 38 insertions(+), 16 deletions(-)
>
> All applied. Thanks.
Thanks
> --
> Email: Herbert Xu <herbert@gondor•apana.org.au>
> Home Page: http://gondor.apana.org.au/~herbert/
> PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
--
Gregory Clement, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
http://bootlin.com
prev parent reply other threads:[~2018-03-23 16:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-13 16:48 [PATCH 0/3] crypto: inside-secure: improve clock management Gregory CLEMENT
2018-03-13 16:48 ` [PATCH 1/3] crypto: inside-secure - fix " Gregory CLEMENT
2018-03-13 16:48 ` [PATCH 2/3] crypto: inside-secure - improve clock initialization Gregory CLEMENT
2018-03-13 16:48 ` [PATCH 3/3] crypto: inside-secure - fix clock resource by adding a register clock Gregory CLEMENT
2018-03-23 16:01 ` [PATCH 0/3] crypto: inside-secure: improve clock management Herbert Xu
2018-03-23 16:30 ` Gregory CLEMENT [this message]
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=874ll6wy89.fsf@bootlin.com \
--to=gregory.clement@bootlin$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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