qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: BALATON Zoltan <balaton@eik.bme.hu>
Cc: qemu-devel@nongnu.org, Aurelien Jarno <aurelien@aurel32.net>,
	"Michael S . Tsirkin" <mst@redhat.com>
Subject: Re: [PATCH-for-9.1 v4 1/2] hw/pci-host/gt64120: Set PCI base address register write mask
Date: Fri, 2 Aug 2024 23:30:19 +0200	[thread overview]
Message-ID: <20a598c0-fb47-438e-a292-d92b134fd7c9@linaro.org> (raw)
In-Reply-To: <0319cc95-fb5b-d904-4043-00384ac9df4e@eik.bme.hu>

On 2/8/24 21:21, BALATON Zoltan wrote:
> On Fri, 2 Aug 2024, Philippe Mathieu-Daudé wrote:
>> When booting Linux we see:
>>
>>  PCI host bridge to bus 0000:00
>>  pci_bus 0000:00: root bus resource [mem 0x10000000-0x17ffffff]
>>  pci_bus 0000:00: root bus resource [io  0x1000-0x1fffff]
>>  pci_bus 0000:00: No busn resource found for root bus, will use [bus 
>> 00-ff]
>>  pci 0000:00:00.0: [11ab:4620] type 00 class 0x060000
>>  pci 0000:00:00.0: [Firmware Bug]: reg 0x14: invalid BAR (can't size)
>>  pci 0000:00:00.0: [Firmware Bug]: reg 0x18: invalid BAR (can't size)
>>  pci 0000:00:00.0: [Firmware Bug]: reg 0x1c: invalid BAR (can't size)
>>  pci 0000:00:00.0: [Firmware Bug]: reg 0x20: invalid BAR (can't size)
>>  pci 0000:00:00.0: [Firmware Bug]: reg 0x24: invalid BAR (can't size)
>>
>> This is due to missing base address register write mask.
>> Add it to get:
>>
>>  PCI host bridge to bus 0000:00
>>  pci_bus 0000:00: root bus resource [mem 0x10000000-0x17ffffff]
>>  pci_bus 0000:00: root bus resource [io  0x1000-0x1fffff]
>>  pci_bus 0000:00: No busn resource found for root bus, will use [bus 
>> 00-ff]
>>  pci 0000:00:00.0: [11ab:4620] type 00 class 0x060000
>>  pci 0000:00:00.0: reg 0x10: [mem 0x00000000-0x00000fff pref]
>>  pci 0000:00:00.0: reg 0x14: [mem 0x01000000-0x01000fff pref]
>>  pci 0000:00:00.0: reg 0x18: [mem 0x1c000000-0x1c000fff]
>>  pci 0000:00:00.0: reg 0x1c: [mem 0x1f000000-0x1f000fff]
>>  pci 0000:00:00.0: reg 0x20: [mem 0x1be00000-0x1be00fff]
>>  pci 0000:00:00.0: reg 0x24: [io  0x14000000-0x14000fff]
>>
>> Since this device is only used by MIPS machines which aren't
>> versioned, we don't need to update migration compat machinery.
>>
>> Mention the datasheet referenced. Remove the "Malta assumptions
>> ahead" comment since the reset values from the datasheet are used.
>>
>> Signed-off-by: Philippe Mathieu-Daudé <philmd@linaro.org>
>> ---
>> hw/pci-host/gt64120.c | 14 +++++++++++++-
>> 1 file changed, 13 insertions(+), 1 deletion(-)


>> static void gt64120_pci_realize(PCIDevice *d, Error **errp)
>> {
>> -    /* FIXME: Malta specific hw assumptions ahead */
>> +    /* Values from chapter 17.16 "PCI Configuration" */
>> +
>>     pci_set_word(d->config + PCI_COMMAND, 0);
>>     pci_set_word(d->config + PCI_STATUS,
>>                  PCI_STATUS_FAST_BACK | PCI_STATUS_DEVSEL_MEDIUM);
>>     pci_config_set_prog_interface(d->config, 0);
>> +
>> +    pci_set_long(d->wmask + PCI_BASE_ADDRESS_0, 0xfffff009);
>> +    pci_set_long(d->wmask + PCI_BASE_ADDRESS_1, 0xfffff009);
>> +    pci_set_long(d->wmask + PCI_BASE_ADDRESS_2, 0xfffff009);
>> +    pci_set_long(d->wmask + PCI_BASE_ADDRESS_3, 0xfffff009);
>> +    pci_set_long(d->wmask + PCI_BASE_ADDRESS_4, 0xfffff009);
> 
> Documentation says bit 0 is read only 0 for these? Why mask ending with 
> 9 not 8? Also prefetch bit 3 is read only 0 for the last one BAR4.

Oops indeed, and also Type/Prefetch for BAR5; updated as:

pci_set_long(d->wmask + PCI_BASE_ADDRESS_0, 0xfffff008); /* SCS[1:0] */
pci_set_long(d->wmask + PCI_BASE_ADDRESS_1, 0xfffff008); /* SCS[3:2] */
pci_set_long(d->wmask + PCI_BASE_ADDRESS_2, 0xfffff008); /* CS[2:0] */
pci_set_long(d->wmask + PCI_BASE_ADDRESS_3, 0xfffff008); /* CS[3], BootCS */
pci_set_long(d->wmask + PCI_BASE_ADDRESS_4, 0xfffff000); /* ISD MMIO */
pci_set_long(d->wmask + PCI_BASE_ADDRESS_5, 0xfffff001); /* ISD I/O */

> Otherwise:
> 
> Reviewed-by: BALATON Zoltan <balaton@eik.bme.hu>

Thanks!

Phil.


  reply	other threads:[~2024-08-02 21:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-02 17:10 [PATCH-for-9.1 v4 0/2] hw/pci-host/gt64120: Set PCI base address register write mask Philippe Mathieu-Daudé
2024-08-02 17:10 ` [PATCH-for-9.1 v4 1/2] " Philippe Mathieu-Daudé
2024-08-02 19:21   ` BALATON Zoltan
2024-08-02 21:30     ` Philippe Mathieu-Daudé [this message]
2024-08-02 17:10 ` [PATCH-for-9.1 v4 2/2] hw/pci-host/gt64120: Reset config registers during RESET phase Philippe Mathieu-Daudé

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=20a598c0-fb47-438e-a292-d92b134fd7c9@linaro.org \
    --to=philmd@linaro.org \
    --cc=aurelien@aurel32.net \
    --cc=balaton@eik.bme.hu \
    --cc=mst@redhat.com \
    --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).