From: Varun Wadekar <vwadekar@nvidia.com>
To: Stephen Warren <swarren@nvidia.com>
Cc: "herbert@gondor.hengli.com.au" <herbert@gondor.hengli.com.au>,
"davem@davemloft.net" <davem@davemloft.net>,
"linux-crypto@vger.kernel.org" <linux-crypto@vger.kernel.org>,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>
Subject: Re: [PATCH] crypto: driver for tegra AES hardware
Date: Sat, 5 Nov 2011 16:14:51 +0530 [thread overview]
Message-ID: <4EB513A3.5080608@nvidia.com> (raw)
In-Reply-To: <4EB4EFC0.1060702@nvidia.com>
>>> + /* Initialize the vde clock */
>>> + dd->aes_clk = clk_get(dev, "vde");
>> That clock doesn't exist in the mainline kernel; "bsev" exists for device
>> "tegra-aes"...
>>
> We need to use the "vde" clock. I will submit a patch to add the "vde"
> clock. "bsev" might not be needed at the moment.
Just checked and we have "vde" as a duplicate clock for "tegra-aes"
next prev parent reply other threads:[~2011-11-05 10:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-04 11:14 [PATCH] crypto: driver for tegra AES hardware vwadekar-DDmLM1+adcrQT0dZR+AlfA
[not found] ` <1320405256-29374-1-git-send-email-vwadekar-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2011-11-04 13:54 ` Henning Heinold
2011-11-04 13:54 ` Henning Heinold
[not found] ` <20111104135436.GA29112-/JE64I/RTDPrEm6qDNUMlj7Snszu6STo@public.gmane.org>
2011-11-05 7:28 ` Varun Wadekar
2011-11-04 21:21 ` Stephen Warren
2011-11-04 21:21 ` Stephen Warren
[not found] ` <74CDBE0F657A3D45AFBB94109FB122FF173F9A4E83-C7FfzLzN0UxDw2glCA4ptUEOCMrvLtNR@public.gmane.org>
2011-11-05 8:11 ` Varun Wadekar
2011-11-05 10:44 ` Varun Wadekar [this message]
[not found] ` <4EB4EFC0.1060702-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2011-11-07 17:52 ` Stephen Warren
2011-11-05 1:22 ` Kim Phillips
2011-11-05 1:22 ` Kim Phillips
[not found] ` <20111104202202.882b4d84473ba616cacda7d7-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
2011-11-05 10:30 ` Varun Wadekar
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=4EB513A3.5080608@nvidia.com \
--to=vwadekar@nvidia.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.hengli.com.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=swarren@nvidia.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.