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. > 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. -- Email: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx> Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
