qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: Jean-Christophe DUBOIS <jcd@tribudubois.net>
Cc: QEMU Developers <qemu-devel@nongnu.org>,
	Peter Crosthwaite <crosthwaite.peter@gmail.com>
Subject: Re: [Qemu-devel] [PATCH v2 7/9] i.MX: Add i.MX6 SOC implementation.
Date: Tue, 1 Mar 2016 16:19:59 +0000	[thread overview]
Message-ID: <CAFEAcA8pRs47=AGPsgTB3ebdXoVQDR_SERZdeJ=zncS4P-7fzg@mail.gmail.com> (raw)
In-Reply-To: <56D4B8FA.4010305@tribudubois.net>

On 29 February 2016 at 21:32, Jean-Christophe DUBOIS
<jcd@tribudubois.net> wrote:
> Le 29/02/2016 22:14, Peter Maydell a écrit :
>> Is there a datasheet available for this?

> Well the SRC device is described in the i.MX6 reference manual.
>
> http://cache.nxp.com/files/32bit/doc/ref_manual/IMX6DQRM.pdf?fpsp=1&WT_TYPE=Reference%20Manuals&WT_VENDOR=FREESCALE&WT_FILE_FORMAT=pdf&WT_ASSET=Documentation&fileExt=.pdf

Thanks for the link.

> I believe it is hardware based. Now it might involve some of the functions
> of the internal ROM in the process but we cannot change this behavior in any
> way.

The datasheet is pretty clear -- registers like the SRC_GPR<n> are just
"holds some state" registers, and when the system reset controller starts
a secondary CPU it runs through some boot ROM code which reads the
GPR controlling the start address and branches to it.

This means the code you have in the SRC emulation is actually implementing
a combination of the SRC hardware and the boot ROM software. That's OK,
but we should have a comment somewhere that makes it clear that that's
what's going on.

(it is possible to implement the "jump to address as per register" as
code that runs in the guest; highbank has a variant on this. It doesn't
really seem necessary here though.)

On the "secure vs nonsecure" question, I'm not completely sure but I
think that the answer is that it will boot in secure. So we should
use the patche that adds "sabrelite_binfo.secure_boot = true;" to the
board code.

thanks
-- PMM

  reply	other threads:[~2016-03-01 16:20 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-08 22:08 [Qemu-devel] [PATCH v2 0/9] Add i.MX6 (Single/Dual/Quad) support Jean-Christophe Dubois
2016-02-08 22:08 ` [Qemu-devel] [PATCH v2 1/9] i.MX: Allow GPT timer to rollover Jean-Christophe Dubois
2016-02-16 15:19   ` Peter Maydell
2016-02-08 22:08 ` [Qemu-devel] [PATCH v2 2/9] i.MX: Rename CCM NOCLK to CLK_NONE for naming consistency Jean-Christophe Dubois
2016-02-16 15:20   ` Peter Maydell
2016-02-08 22:08 ` [Qemu-devel] [PATCH v2 3/9] i.MX: Remove CCM useless clock computation handling Jean-Christophe Dubois
2016-02-16 15:20   ` Peter Maydell
2016-02-08 22:08 ` [Qemu-devel] [PATCH v2 4/9] i.MX: Add the CLK_IPG_HIGH clock Jean-Christophe Dubois
2016-02-16 15:20   ` Peter Maydell
2016-02-08 22:08 ` [Qemu-devel] [PATCH v2 5/9] i.MX: Add i.MX6 CCM and ANALOG device Jean-Christophe Dubois
2016-02-16 15:21   ` Peter Maydell
2016-02-29 17:33   ` Peter Maydell
2016-02-29 20:15     ` Jean-Christophe DUBOIS
2016-02-08 22:08 ` [Qemu-devel] [PATCH v2 6/9] i.MX: Add i.MX6 System Reset Controller device Jean-Christophe Dubois
2016-02-16 15:35   ` Peter Maydell
2016-02-27 16:57     ` Jean-Christophe DUBOIS
2016-02-27 17:43       ` Peter Maydell
2016-02-28 12:00         ` Jean-Christophe DUBOIS
2016-02-08 22:08 ` [Qemu-devel] [PATCH v2 7/9] i.MX: Add i.MX6 SOC implementation Jean-Christophe Dubois
2016-02-16 15:31   ` Peter Maydell
2016-02-16 20:49     ` Jean-Christophe DUBOIS
2016-02-16 21:06       ` Peter Maydell
2016-02-16 21:47         ` Jean-Christophe DUBOIS
2016-02-16 21:57           ` Peter Maydell
2016-02-18 20:51             ` Jean-Christophe DUBOIS
2016-02-18 21:46               ` Peter Maydell
2016-02-19  6:32                 ` Jean-Christophe DUBOIS
2016-02-19  9:32                   ` Peter Maydell
2016-02-19 21:06                     ` Jean-Christophe DUBOIS
2016-02-20 10:55                       ` Jean-Christophe DUBOIS
2016-02-20 15:30                         ` Peter Crosthwaite
2016-02-20 18:03                           ` Jean-Christophe DUBOIS
2016-02-21  3:42                             ` Peter Crosthwaite
2016-02-21 13:42                               ` Jean-Christophe DUBOIS
2016-02-29 17:58                   ` Peter Maydell
2016-02-29 20:34                     ` Jean-Christophe DUBOIS
2016-02-29 21:14                       ` Peter Maydell
2016-02-29 21:32                         ` Jean-Christophe DUBOIS
2016-03-01 16:19                           ` Peter Maydell [this message]
2016-03-01 19:17                             ` Jean-Christophe DUBOIS
2016-02-08 22:08 ` [Qemu-devel] [PATCH v2 8/9] i.MX: Add sabrelite i.MX6 emulation Jean-Christophe Dubois
2016-02-16 15:25   ` Peter Maydell
2016-02-08 22:08 ` [Qemu-devel] [PATCH v2 9/9] i.MX: Add missing descriptions in devices Jean-Christophe Dubois
2016-02-16 15:21   ` Peter Maydell
2016-02-28 20:27 ` [Qemu-devel] [PATCH v2 0/9] Add i.MX6 (Single/Dual/Quad) support Jean-Christophe DUBOIS
2016-03-01 19:18   ` Jean-Christophe DUBOIS
2016-03-01 19:27     ` Peter Maydell

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='CAFEAcA8pRs47=AGPsgTB3ebdXoVQDR_SERZdeJ=zncS4P-7fzg@mail.gmail.com' \
    --to=peter.maydell@linaro.org \
    --cc=crosthwaite.peter@gmail.com \
    --cc=jcd@tribudubois.net \
    --cc=qemu-devel@nongnu.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 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).