From: "Cédric Le Goater" <clg@kaod.org>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: qemu-ppc@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [PATCH] ppc/pnv: Add a LPC "ranges" property
Date: Tue, 19 Nov 2019 07:43:20 +0100 [thread overview]
Message-ID: <087a43b4-a376-f593-b23f-391b3779e466@kaod.org> (raw)
In-Reply-To: <20191119004938.GG5582@umbus.fritz.box>
On 19/11/2019 01:49, David Gibson wrote:
> On Mon, Nov 18, 2019 at 10:19:08AM +0100, Cédric Le Goater wrote:
>> And fix a typo in the MEM address space definition.
>>
>> Signed-off-by: Cédric Le Goater <clg@kaod.org>
>
> Applied to ppc-for-5.0. AFAICT this is a bugfix (amongst other
> things), but I don't think pnv is widely used enough to put this into
> 4.2 during hard freeze.
yes. I am trying to fix the dtc warnings before and after OPAL runs.
C.
>> ---
>> hw/ppc/pnv_lpc.c | 14 +++++++++++++-
>> 1 file changed, 13 insertions(+), 1 deletion(-)
>>
>> diff --git a/hw/ppc/pnv_lpc.c b/hw/ppc/pnv_lpc.c
>> index fb9f93032020..c5a85c38c783 100644
>> --- a/hw/ppc/pnv_lpc.c
>> +++ b/hw/ppc/pnv_lpc.c
>> @@ -86,7 +86,7 @@ enum {
>> #define ISA_FW_SIZE 0x10000000
>> #define LPC_IO_OPB_ADDR 0xd0010000
>> #define LPC_IO_OPB_SIZE 0x00010000
>> -#define LPC_MEM_OPB_ADDR 0xe0010000
>> +#define LPC_MEM_OPB_ADDR 0xe0000000
>> #define LPC_MEM_OPB_SIZE 0x10000000
>> #define LPC_FW_OPB_ADDR 0xf0000000
>> #define LPC_FW_OPB_SIZE 0x10000000
>> @@ -143,6 +143,16 @@ int pnv_dt_lpc(PnvChip *chip, void *fdt, int root_offset)
>> cpu_to_be32(PNV9_LPCM_SIZE >> 32),
>> cpu_to_be32((uint32_t)PNV9_LPCM_SIZE),
>> };
>> + uint32_t lpc_ranges[12] = { 0, 0,
>> + cpu_to_be32(LPC_MEM_OPB_ADDR),
>> + cpu_to_be32(LPC_MEM_OPB_SIZE),
>> + cpu_to_be32(1), 0,
>> + cpu_to_be32(LPC_IO_OPB_ADDR),
>> + cpu_to_be32(LPC_IO_OPB_SIZE),
>> + cpu_to_be32(3), 0,
>> + cpu_to_be32(LPC_FW_OPB_ADDR),
>> + cpu_to_be32(LPC_FW_OPB_SIZE),
>> + };
>> uint32_t reg[2];
>>
>> /*
>> @@ -211,6 +221,8 @@ int pnv_dt_lpc(PnvChip *chip, void *fdt, int root_offset)
>> _FDT((fdt_setprop_cell(fdt, offset, "#size-cells", 1)));
>> _FDT((fdt_setprop(fdt, offset, "compatible", lpc_compat,
>> sizeof(lpc_compat))));
>> + _FDT((fdt_setprop(fdt, offset, "ranges", lpc_ranges,
>> + sizeof(lpc_ranges))));
>>
>> return 0;
>> }
>
prev parent reply other threads:[~2019-11-19 6:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-18 9:19 [PATCH] ppc/pnv: Add a LPC "ranges" property Cédric Le Goater
2019-11-19 0:49 ` David Gibson
2019-11-19 6:43 ` Cédric Le Goater [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=087a43b4-a376-f593-b23f-391b3779e466@kaod.org \
--to=clg@kaod.org \
--cc=david@gibson.dropbear.id.au \
--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).