qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Henrique Barboza <danielhb413@gmail.com>
To: "Cédric Le Goater" <clg@kaod.org>,
	qemu-ppc@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [PATCH 2/5] ppc/pnv: Remove PHB4 reset handler
Date: Wed, 22 Dec 2021 15:12:23 -0300	[thread overview]
Message-ID: <5f81a641-20ed-0ff3-5845-71edc7908eb2@gmail.com> (raw)
In-Reply-To: <20211222063817.1541058-3-clg@kaod.org>



On 12/22/21 03:38, Cédric Le Goater wrote:
> The PHB4 reset handler was preparing ground for PHB5 to set
> appropriately the device id. We don't need it for the PHB4 since the
> device id is already set in the root port complex. PH5 will introduce
> its own.
> 
> "device-id" property is now useless. It should be removed.
> 
> Signed-off-by: Cédric Le Goater <clg@kaod.org>
> ---

Reviewed-by: Daniel Henrique Barboza <danielhb413@gmail.com>

>   hw/pci-host/pnv_phb4.c | 13 -------------
>   1 file changed, 13 deletions(-)
> 
> diff --git a/hw/pci-host/pnv_phb4.c b/hw/pci-host/pnv_phb4.c
> index 40b793201a34..4caf03310fab 100644
> --- a/hw/pci-host/pnv_phb4.c
> +++ b/hw/pci-host/pnv_phb4.c
> @@ -1229,18 +1229,6 @@ static void pnv_phb4_realize(DeviceState *dev, Error **errp)
>       phb->qirqs = qemu_allocate_irqs(xive_source_set_irq, xsrc, xsrc->nr_irqs);
>   }
>   
> -static void pnv_phb4_reset(DeviceState *dev)
> -{
> -    PnvPHB4 *phb = PNV_PHB4(dev);
> -    PCIDevice *root_dev = PCI_DEVICE(&phb->root);
> -
> -    /*
> -     * Configure PCI device id at reset using a property.
> -     */
> -    pci_config_set_vendor_id(root_dev->config, PCI_VENDOR_ID_IBM);
> -    pci_config_set_device_id(root_dev->config, phb->device_id);
> -}
> -
>   static const char *pnv_phb4_root_bus_path(PCIHostState *host_bridge,
>                                             PCIBus *rootbus)
>   {
> @@ -1290,7 +1278,6 @@ static void pnv_phb4_class_init(ObjectClass *klass, void *data)
>       device_class_set_props(dc, pnv_phb4_properties);
>       set_bit(DEVICE_CATEGORY_BRIDGE, dc->categories);
>       dc->user_creatable  = false;
> -    dc->reset           = pnv_phb4_reset;
>   
>       xfc->notify         = pnv_phb4_xive_notify;
>   }
> 


  reply	other threads:[~2021-12-22 18:16 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-22  6:38 [PATCH 0/5] ppc/pnv: Preliminary cleanups before user created PHBs Cédric Le Goater
2021-12-22  6:38 ` [PATCH 1/5] ppc/pnv: Change the maximum of PHB3 devices for Power8NVL Cédric Le Goater
2021-12-22 18:11   ` Daniel Henrique Barboza
2021-12-22  6:38 ` [PATCH 2/5] ppc/pnv: Remove PHB4 reset handler Cédric Le Goater
2021-12-22 18:12   ` Daniel Henrique Barboza [this message]
2021-12-22  6:38 ` [PATCH 3/5] ppc/pnv: Remove the PHB4 "device-id" property Cédric Le Goater
2021-12-22 18:12   ` Daniel Henrique Barboza
2021-12-22  6:38 ` [PATCH 4/5] ppc/pnv: Attach PHB3 root port device when defaults are enabled Cédric Le Goater
2021-12-22 18:13   ` Daniel Henrique Barboza
2021-12-22  6:38 ` [PATCH 5/5] ppc/pnv: Attach PHB4 " Cédric Le Goater
2021-12-22 18:13   ` Daniel Henrique Barboza
2021-12-22 18:16 ` [PATCH 0/5] ppc/pnv: Preliminary cleanups before user created PHBs Daniel Henrique Barboza
2022-01-04  7:43 ` Cédric Le Goater

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=5f81a641-20ed-0ff3-5845-71edc7908eb2@gmail.com \
    --to=danielhb413@gmail.com \
    --cc=clg@kaod.org \
    --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).