From: gioh.kim@lge.com (Gioh Kim)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH] ARM: cache-l2x0: add setup entry for l2 in non-secure mode
Date: Mon, 19 May 2014 18:21:49 +0900 [thread overview]
Message-ID: <5379CD2D.4080300@lge.com> (raw)
In-Reply-To: <CAGsJ_4wF7_BmTrWoxAu+NMVpsuN4oxJngBW0b2-4naXtwx5g5g@mail.gmail.com>
2014-05-19 ?? 6:11, Barry Song ? ?:
> 2014-05-19 8:29 GMT+08:00 Gioh Kim <gioh.kim@lge.com>:
>>
>>
>> 2014-05-18 ?? 10:13, Barry Song ? ?:
>>
>>> 2014-05-15 13:39 GMT+08:00 Gioh Kim <gioh.kim@lge.com>:
>>>>
>>>>
>>>> Hi,
>>>>
>>>> My board is using Trustzone and running kernel is non-secure mode.
>>>> But setup function of PL310 driver is only for secure mode kernel.
>>>>
>>>> What about adding an entry for non-secure mode setup function?
>>>>
>>>> I'm sorry for my poor code but I just wanna say what I need .
>>>
>>>
>>> Gioh,
>>>
>>> i don't really understand what is the user scenarios for this, if you
>>> are running linux in non-secure mode, your security-mode codes have
>>> enabled L2, so this makes non-secure linux have no chance to execute
>>> setup at all:
>>
>>
>> My platform runs linux kernel before L2 cache activation.
>> And the L2 cache is activated when the kernel sends command to Trustzone
>> firmware.
>> At this moment L2 is not activated. Linux should send command for L2
>> activation to Trustzone at the moment.
>
> i think you can send command to trustzone firmware to enable L2 at
> first, then make your Linux l2 driver run.
Right. My platform is working like that.
Activate L2 first and run l2x0 driver.
But I think many platforms have trustzone firmware and are working like my platform.
They might need non-secure setup.
>
>
> -barry
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo at vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
WARNING: multiple messages have this Message-ID (diff)
From: Gioh Kim <gioh.kim@lge.com>
To: Barry Song <21cnbao@gmail.com>
Cc: "Russell King" <linux@arm.linux.org.uk>,
"Sebastian Hesselbarth" <sebastian.hesselbarth@gmail.com>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
LKML <linux-kernel@vger.kernel.org>,
"Barry Song" <Baohua.Song@csr.com>,
"Santosh Shilimkar" <santosh.shilimkar@ti.com>,
이건호 <gunho.lee@lge.com>, "Gi-Oh Kim" <gurugio@gmail.com>,
DL-SHA-WorkGroupLinux <workgroup.linux@csr.com>
Subject: Re: [RFC PATCH] ARM: cache-l2x0: add setup entry for l2 in non-secure mode
Date: Mon, 19 May 2014 18:21:49 +0900 [thread overview]
Message-ID: <5379CD2D.4080300@lge.com> (raw)
In-Reply-To: <CAGsJ_4wF7_BmTrWoxAu+NMVpsuN4oxJngBW0b2-4naXtwx5g5g@mail.gmail.com>
2014-05-19 오후 6:11, Barry Song 쓴 글:
> 2014-05-19 8:29 GMT+08:00 Gioh Kim <gioh.kim@lge.com>:
>>
>>
>> 2014-05-18 오후 10:13, Barry Song 쓴 글:
>>
>>> 2014-05-15 13:39 GMT+08:00 Gioh Kim <gioh.kim@lge.com>:
>>>>
>>>>
>>>> Hi,
>>>>
>>>> My board is using Trustzone and running kernel is non-secure mode.
>>>> But setup function of PL310 driver is only for secure mode kernel.
>>>>
>>>> What about adding an entry for non-secure mode setup function?
>>>>
>>>> I'm sorry for my poor code but I just wanna say what I need .
>>>
>>>
>>> Gioh,
>>>
>>> i don't really understand what is the user scenarios for this, if you
>>> are running linux in non-secure mode, your security-mode codes have
>>> enabled L2, so this makes non-secure linux have no chance to execute
>>> setup at all:
>>
>>
>> My platform runs linux kernel before L2 cache activation.
>> And the L2 cache is activated when the kernel sends command to Trustzone
>> firmware.
>> At this moment L2 is not activated. Linux should send command for L2
>> activation to Trustzone at the moment.
>
> i think you can send command to trustzone firmware to enable L2 at
> first, then make your Linux l2 driver run.
Right. My platform is working like that.
Activate L2 first and run l2x0 driver.
But I think many platforms have trustzone firmware and are working like my platform.
They might need non-secure setup.
>
>
> -barry
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
next prev parent reply other threads:[~2014-05-19 9:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-15 5:39 [RFC PATCH] ARM: cache-l2x0: add setup entry for l2 in non-secure mode Gioh Kim
2014-05-15 5:39 ` Gioh Kim
2014-05-18 13:13 ` Barry Song
2014-05-18 13:13 ` Barry Song
2014-05-19 0:29 ` Gioh Kim
2014-05-19 0:29 ` Gioh Kim
2014-05-19 9:11 ` Barry Song
2014-05-19 9:11 ` Barry Song
2014-05-19 9:21 ` Gioh Kim [this message]
2014-05-19 9:21 ` Gioh Kim
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=5379CD2D.4080300@lge.com \
--to=gioh.kim@lge.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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.