qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: David Gibson <david@gibson.dropbear.id.au>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: qemu-ppc@nongnu.org,
	Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>,
	qemu-devel@nongnu.org, Alexander Graf <agraf@suse.de>
Subject: Re: [Qemu-devel] [PATCH] ppc: Fix macio ESCC legacy mapping
Date: Wed, 3 Aug 2016 09:10:46 +1000	[thread overview]
Message-ID: <20160802231046.GB27583@voom.fritz.box> (raw)
In-Reply-To: <1470129763.12584.26.camel@kernel.crashing.org>

[-- Attachment #1: Type: text/plain, Size: 2097 bytes --]

On Tue, Aug 02, 2016 at 07:22:43PM +1000, Benjamin Herrenschmidt wrote:
> The current mapping, while correct for the base ports (which is all the
> driver uses these days), is wrong for the extended registers. 
> 
> I suspect the bugs come from incorrect tables in the CHRP IO Ref document,
> I have verified the new values here match Apple's MacTech.pdf.
> 
> Note: Nothing that I know of actually uses these registers so it's not a
> huge deal, but this patch has the added advantage of adding comments to
> document what the registers are.
> 
> Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>

Applied to ppc-for-2.8, thanks.

> ---
> 
> diff --git a/hw/misc/macio/macio.c b/hw/misc/macio/macio.c
> index be03926..5d57f45 100644
> --- a/hw/misc/macio/macio.c
> +++ b/hw/misc/macio/macio.c
> @@ -89,22 +89,16 @@ static void macio_escc_legacy_setup(MacIOState *macio_state)
>      MemoryRegion *bar = &macio_state->bar;
>      int i;
>      static const int maps[] = {
> -        0x00, 0x00,
> -        0x02, 0x20,
> -        0x04, 0x10,
> -        0x06, 0x30,
> -        0x08, 0x40,
> -        0x0A, 0x50,
> -        0x60, 0x60,
> -        0x70, 0x70,
> -        0x80, 0x70,
> -        0x90, 0x80,
> -        0xA0, 0x90,
> -        0xB0, 0xA0,
> -        0xC0, 0xB0,
> -        0xD0, 0xC0,
> -        0xE0, 0xD0,
> -        0xF0, 0xE0,
> +        0x00, 0x00, /* Command B */
> +        0x02, 0x20, /* Command A */
> +        0x04, 0x10, /* Data B */
> +        0x06, 0x30, /* Data A */
> +        0x08, 0x40, /* Enhancement B */
> +        0x0A, 0x50, /* Enhancement A */
> +        0x80, 0x80, /* Recovery count */
> +        0x90, 0x90, /* Start A */
> +        0xa0, 0xa0, /* Start B */
> +        0xb0, 0xb0, /* Detect AB */
>      };
>  
>      memory_region_init(escc_legacy, OBJECT(macio_state), "escc-legacy", 256);
> 

-- 
David Gibson			| I'll have my music baroque, and my code
david AT gibson.dropbear.id.au	| minimalist, thank you.  NOT _the_ _other_
				| _way_ _around_!
http://www.ozlabs.org/~dgibson

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

      reply	other threads:[~2016-08-02 23:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-02  9:22 [Qemu-devel] [PATCH] ppc: Fix macio ESCC legacy mapping Benjamin Herrenschmidt
2016-08-02 23:10 ` David Gibson [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=20160802231046.GB27583@voom.fritz.box \
    --to=david@gibson.dropbear.id.au \
    --cc=agraf@suse.de \
    --cc=benh@kernel.crashing.org \
    --cc=mark.cave-ayland@ilande.co.uk \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@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).