From: Bjorn Helgaas <bjorn.helgaas@hp.com>
To: John Keller <jpk@sgi.com>
Cc: linux-ia64@vger.kernel.org, linux-acpi@vger.kernel.org
Subject: Re: [PATCH] RESEND - SN: Add initial ACPI support
Date: Thu, 26 Jan 2006 17:20:45 +0000 [thread overview]
Message-ID: <200601261020.45802.bjorn.helgaas@hp.com> (raw)
In-Reply-To: <20060123160003.30149.60885.sendpatchset@attica.americas.sgi.com>
On Monday 23 January 2006 09:00, John Keller wrote:
> +obj-$(CONFIG_IA64_SGI_SN2) += acpi-ext.o
Just FYI, this code is moving into drivers/acpi soon. Robert Moore
might have made a trivial interface change when he integrated it into
the ACPI CA. No big deal, basically acpi-ext.c was arch-independent
and we moved it to generic code.
> + * sn_fixup_ionodes() - This routine initializes the HUB data strcuture for
s/strcuture/structure/
> /*
> - * sn_pci_controller_fixup() - This routine sets up a bus's resources
> - * consistent with the Linux PCI abstraction layer.
> + * sn_common_bus_fixup()
> */
Nit: A comment that merely restates the function name is useless.
Actually, it's worse than useless because it takes up space and
requires maintenance.
> +void sn_pci_controller_fixup(int segment, int busnum, struct pci_bus *bus)
This function looks very much like pci_acpi_scan_root(). Is this the
old, non-ACPI path?
> + printk(KERN_INFO "ACPI DSDT OEM Rev 0x%x\n",
> + acpi_gbl_DSDT->oem_revision);
Doesn't ACPI print something like this for you already? (I think it's
KERN_DEBUG now, so usually not on the console, but still in dmesg.)
> +static int __init
> +sn_io_fixup(void)
> +{
> + struct pci_bus *bus;
> + struct pci_dev *pci_dev = NULL;
> + extern void sn_init_cpei_timer(void);
> +#ifdef CONFIG_PROC_FS
> + extern void register_sn_procfs(void);
> +#endif
> +
> + if (!ia64_platform_is("sn2") || IS_RUNNING_ON_FAKE_PROM())
> + return 0;
> +
> + /* Exit if running with old PROM without ACPI support */
> + if (!SN_ACPI_BASE_SUPPORT())
> + return 0;
> +
> + sn_irq_lh_init();
> + INIT_LIST_HEAD(&sn_sysdata_list);
> + sn_init_cpei_timer();
Seems like a weird place to call sn_init_cpei_timer(). I guess I
have no idea what the CPEI stuff is, but it looks like it *could*
report platform errors other than PCI. And you probably want to
call it even if you don't have ACPI support, don't you?
> +
> +#ifdef CONFIG_PROC_FS
> + register_sn_procfs();
> +#endif
> +
> + /*
> + * Generic Linux PCI Layer has created the pci_bus and pci_dev
> + * structures - time for us to add our SN Platform specific
> + * information.
> + */
> +
> + bus = NULL;
> + while ((bus = pci_find_next_bus(bus)) != NULL)
> + sn_pci_bus_fixup(bus);
> +
> + while ((pci_dev > + pci_find_device(PCI_ANY_ID, PCI_ANY_ID, pci_dev)) != NULL) {
> + sn_pci_fixup_slot(pci_dev);
> + }
You're doing these fixups with an fs_initcall(). I think they should
be done by hooking into pcibios_fixup_bus() (maybe we need a new platform
vector or optional function pointer there; I think PPC has something
like that already). The initcall scheme won't work if you hot-plug
things.
Bjorn
next prev parent reply other threads:[~2006-01-26 17:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-15 18:23 [PATCH] RESEND - SN: Add initial ACPI support John Keller
2006-01-15 20:41 ` Prarit Bhargava
2006-01-16 8:21 ` Jes Sorensen
2006-01-23 16:00 ` John Keller
2006-01-26 17:20 ` Bjorn Helgaas [this message]
2006-01-26 23:04 ` John Keller
2006-01-27 13:54 ` John Keller
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=200601261020.45802.bjorn.helgaas@hp.com \
--to=bjorn.helgaas@hp.com \
--cc=jpk@sgi.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-ia64@vger.kernel.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