All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tabi Timur-B04825 <B04825@freescale.com>
To: "Kokoris, Ioannis" <ioannis.kokoris@siemens-enterprise.com>
Cc: "linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
	Tabi Timur-B04825 <B04825@freescale.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] P1021: set IReady in QE Microcode Upload
Date: Fri, 11 Nov 2011 16:39:21 +0000	[thread overview]
Message-ID: <4EBD4FB8.2020406@freescale.com> (raw)
In-Reply-To: <026483A88B848047A08C3F03E20822D0267B1F4A55@MCHP058A.global-ad.net>

Kokoris, Ioannis wrote:
> Hi,
>
> QE Microcode Initialization using qe_upload_microcode() does not work
> on P1021 if the IRAM-Ready register is not set after the microcode
> upload. This patch adds a definition for the "I-RAM Ready" register and
> sets it uppon microcode upload completion.

Will this code still work on other QE parts, like the MPC8323?

--=20
Timur Tabi
Linux kernel developer at Freescale=

WARNING: multiple messages have this Message-ID (diff)
From: Tabi Timur-B04825 <B04825@freescale.com>
To: "Kokoris, Ioannis" <ioannis.kokoris@siemens-enterprise.com>
Cc: Tabi Timur-B04825 <B04825@freescale.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Subject: Re: [PATCH] P1021: set IReady in QE Microcode Upload
Date: Fri, 11 Nov 2011 16:39:21 +0000	[thread overview]
Message-ID: <4EBD4FB8.2020406@freescale.com> (raw)
In-Reply-To: <026483A88B848047A08C3F03E20822D0267B1F4A55@MCHP058A.global-ad.net>

Kokoris, Ioannis wrote:
> Hi,
>
> QE Microcode Initialization using qe_upload_microcode() does not work
> on P1021 if the IRAM-Ready register is not set after the microcode
> upload. This patch adds a definition for the "I-RAM Ready" register and
> sets it uppon microcode upload completion.

Will this code still work on other QE parts, like the MPC8323?

-- 
Timur Tabi
Linux kernel developer at Freescale

  reply	other threads:[~2011-11-11 16:39 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-11 16:05 [PATCH] P1021: set IReady in QE Microcode Upload Kokoris, Ioannis
2011-11-11 16:05 ` Kokoris, Ioannis
2011-11-11 16:39 ` Tabi Timur-B04825 [this message]
2011-11-11 16:39   ` Tabi Timur-B04825
2011-11-14  8:55   ` Kokoris, Ioannis
2011-11-14  8:55     ` Kokoris, Ioannis
2011-11-16  3:02     ` Tabi Timur-B04825
2011-11-16  3:02       ` Tabi Timur-B04825
2011-11-24  7:55       ` Kumar Gala
2011-11-24  7:55         ` Kumar Gala
2011-11-24 13:57         ` Tabi Timur-B04825
2011-11-24 13:57           ` Tabi Timur-B04825
2012-03-16 15:21           ` Kumar Gala
2012-03-16 15:21             ` Kumar Gala
2012-03-16 16:07             ` Timur Tabi
2012-03-16 16:07               ` Timur Tabi
2012-06-29 19:23               ` Kumar Gala
2012-06-29 19:23                 ` Kumar Gala
2012-06-29 19:26                 ` Timur Tabi
2012-06-29 19:26                   ` Timur Tabi
2012-07-02 18:19                 ` Timur Tabi
2012-07-02 18:19                   ` Timur Tabi
2012-07-10 12:24 ` Kumar Gala
2012-07-10 12:24   ` Kumar Gala

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=4EBD4FB8.2020406@freescale.com \
    --to=b04825@freescale.com \
    --cc=ioannis.kokoris@siemens-enterprise.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.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.