linux-crypto.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Iaroslav Gridin <voker57@gmail.com>
To: Stanimir Varbanov <svarbanov@mm-sol.com>
Cc: herbert@gondor.apana.org.au, davem@davemloft.net,
	linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
	andy.gross@linaro.org, david.brown@linaro.org,
	linux-arm-msm@vger.kernel.org, linux-soc@vger.kernel.org
Subject: Re: [PATCH] crypto: qce: Initialize core src clock @100Mhz
Date: Wed, 7 Sep 2016 19:13:22 +0300	[thread overview]
Message-ID: <20160907161321.s6v2bkmq7tezmrwa@localhost> (raw)
In-Reply-To: <4e509050-6e8e-069c-f00d-eca9a0f3b33d@mm-sol.com>

On Wed, Sep 07, 2016 at 04:04:01PM +0300, Stanimir Varbanov wrote:
> Hi Iaroslav,
> 
> On 09/03/2016 07:45 PM, Iaroslav Gridin wrote:
> > Without that, QCE performance is about 2x less.
> 
> On which platform? The clock rates are per SoC.

Dragonboard 8074. Should clock rate be moved to its DT?

> > 
> > Signed-off-by: Iaroslav Gridin <voker57@gmail.com>
> > ---
> >  drivers/crypto/qce/core.c | 18 +++++++++++++++++-
> >  drivers/crypto/qce/core.h |  2 +-
> >  2 files changed, 18 insertions(+), 2 deletions(-)
> > 
> > diff --git a/drivers/crypto/qce/core.c b/drivers/crypto/qce/core.c
> > index 0cde513..657354c 100644
> > --- a/drivers/crypto/qce/core.c
> > +++ b/drivers/crypto/qce/core.c
> > @@ -193,6 +193,10 @@ static int qce_crypto_probe(struct platform_device *pdev)
> >  	if (ret < 0)
> >  		return ret;
> >  
> > +	qce->core_src = devm_clk_get(qce->dev, "core_src");
> > +	if (IS_ERR(qce->core_src))
> > +		return PTR_ERR(qce->core_src);
> > +
> >  	qce->core = devm_clk_get(qce->dev, "core");
> >  	if (IS_ERR(qce->core))
> >  		return PTR_ERR(qce->core);
> > @@ -205,10 +209,20 @@ static int qce_crypto_probe(struct platform_device *pdev)
> >  	if (IS_ERR(qce->bus))
> >  		return PTR_ERR(qce->bus);
> >  
> > -	ret = clk_prepare_enable(qce->core);
> > +	ret = clk_prepare_enable(qce->core_src);
> >  	if (ret)
> >  		return ret;
> >  
> > +	ret = clk_set_rate(qce->core_src, 100000000);
> 
> Could you point me from where you got this number? Also I think you
> shouldn't be requesting "core_src" it should be a parent of "core" clock
> in the clock tree. Did you tried to set rate on "core" clock?

Tried it, helps with speed as well.

  reply	other threads:[~2016-09-07 16:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-03 16:45 [PATCH] crypto: qce: Initialize core src clock @100Mhz Iaroslav Gridin
2016-09-07 12:50 ` Herbert Xu
2016-09-07 13:04 ` Stanimir Varbanov
2016-09-07 16:13   ` Iaroslav Gridin [this message]
2016-09-07 17:25   ` Iaroslav Gridin
2016-09-13  4:00 ` Bjorn Andersson

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=20160907161321.s6v2bkmq7tezmrwa@localhost \
    --to=voker57@gmail.com \
    --cc=andy.gross@linaro.org \
    --cc=davem@davemloft.net \
    --cc=david.brown@linaro.org \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-soc@vger.kernel.org \
    --cc=svarbanov@mm-sol.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;
as well as URLs for NNTP newsgroup(s).