From: Peng Fan <van.freenix@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] arm: imx-common: introduce back usec2ticks
Date: Tue, 3 May 2016 10:32:29 +0800 [thread overview]
Message-ID: <20160503023149.GA1155@linux-7smt.suse> (raw)
In-Reply-To: <20160503020447.GM7884@bill-the-cat>
Hi Tom,
On Mon, May 02, 2016 at 10:04:47PM -0400, Tom Rini wrote:
>On Tue, May 03, 2016 at 09:17:51AM +0800, Peng Fan wrote:
>> Hi Tom,
>>
>> On Mon, May 02, 2016 at 07:41:35PM -0400, Tom Rini wrote:
>> >On Fri, Apr 29, 2016 at 09:56:09AM +0800, Peng Fan wrote:
>> >
>> >> This commit "2bb014820c49a63902103bac710bc86b5772e843"
>> >> do some clean up to use the code in lib/time.c.
>> >> But usec2ticks is still being used by security related job ring code.
>> >> Bring back the function to avoid build break.
>> >>
>> >> Signed-off-by: Peng Fan <van.freenix@gmail.com>
>> >> Cc: Stefano Babic <sbabic@denx.de>
>> >
>> >.... some option not enabled by default somewhere? I build test the
>> >world frequently..
>>
>>
>> Yeah.
>>
>> Security related options not enabled by default.
>>
>> If enabled these for i.MX6,
>> #define CONFIG_SECURE_BOOT
>> #define CONFIG_SYS_FSL_SEC_COMPAT 4 /* HAB version */
>> #define CONFIG_FSL_CAAM
>> #define CONFIG_CMD_DEKBLOB
>> #define CONFIG_SYS_FSL_SEC_LE
>>
>> Met the errors:
>>
>> drivers/crypto/fsl/jr.c:333: undefined reference to `usec2ticks'
>
>I'd like to see this stuff moved over to Kconfig and a sample config
>enabled so things don't break in the future, thanks!
Ok. Will add this support.
Will you directly pick up this patch or go through i.MX tree?
Thanks,
Peng.
>
>--
>Tom
next prev parent reply other threads:[~2016-05-03 2:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-29 1:56 [U-Boot] [PATCH] arm: imx-common: introduce back usec2ticks Peng Fan
2016-05-02 23:41 ` Tom Rini
2016-05-03 1:17 ` Peng Fan
2016-05-03 2:04 ` Tom Rini
2016-05-03 2:32 ` Peng Fan [this message]
2016-05-10 9:30 ` Peng Fan
2016-05-10 13:20 ` Stefano Babic
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=20160503023149.GA1155@linux-7smt.suse \
--to=van.freenix@gmail.com \
--cc=u-boot@lists.denx.de \
/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