From: York Sun <yorksun@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH V5] mpc85xx: inhibit qman and bman portals by default
Date: Tue, 16 Dec 2014 09:19:42 -0800 [thread overview]
Message-ID: <549069AE.20106@freescale.com> (raw)
In-Reply-To: <1418068441-28799-1-git-send-email-Jeffrey.Ladouceur@freescale.com>
On 12/08/2014 11:54 AM, Jeffrey Ladouceur wrote:
> Not all portals might be managed and therefore visible.
> Set the isdr register so that the corresponding isr register
> won't be set. This is required when supporting power management.
>
> Signed-off-by: Jeffrey Ladouceur <Jeffrey.Ladouceur@freescale.com>
> ---
> The following dependent patches should be applied first:
> http://patchwork.ozlabs.org/patch/403532
> http://patchwork.ozlabs.org/patch/403533
> http://patchwork.ozlabs.org/patch/403540
> http://patchwork.ozlabs.org/patch/403534
> http://patchwork.ozlabs.org/patch/403535
> http://patchwork.ozlabs.org/patch/403538
> http://patchwork.ozlabs.org/patch/403536
> http://patchwork.ozlabs.org/patch/403539
>
> Changes in v5:
> - Qman portals also require their isdr register to be set in order to support
> power management (sleep, deepsleep). Otherwise QMan will appear to not be idle
> if all portals are not managed by the OS.
>
> Changes in v4:
> - The assertion that reading from portal reserved memory would return zero
> is incorrect. Therefore modify code to depend on specified number of
> portals in board config file
>
> Changes in v3:
> - Update subject title to be consistent
> Changes in v2:
> - Removed P1023RDS as it is no longer supported.
>
Applied to u-boot-mpc85xx master, awaiting upstream.
York
prev parent reply other threads:[~2014-12-16 17:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-08 19:54 [U-Boot] [PATCH V5] mpc85xx: inhibit qman and bman portals by default Jeffrey Ladouceur
2014-12-16 17:19 ` York Sun [this message]
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=549069AE.20106@freescale.com \
--to=yorksun@freescale.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