From: Benjamin Herrenschmidt <benh@au1.ibm.com>
To: Linux Kernel list <linux-kernel@vger.kernel.org>
Cc: Len Brown <len.brown@intel.com>, Andrew Morton <akpm@osdl.org>,
Greg KH <greg@kroah.com>
Subject: [PATCH 0/2] Add dev_sysdata and use it for ACPI
Date: Thu, 09 Nov 2006 11:45:21 +1100 [thread overview]
Message-ID: <1163033121.28571.792.camel@localhost.localdomain> (raw)
As discussed on linux PCI, these 2 patches:
- Add a dev_sysdata structure to struct device whose content is arch
specific. It will allow architectures like powerpc, arm, i386, ... who
need different types of DMA ops for busses and other kind of auxilliary
data for devices in general (numa node id, firmware data, etc...) to put
them in there, without bloating all architectures. The patch adds an
empty definition for the structure to all architectures.
- As an example (patch test built but not test booted), I removed ACPI
usage of device->firmware_data, removed the firmware_data field
completely from struct device (as it was, apparently, the only user),
and instead used an "acpi_handle" field in x86 and x86_64 dev_sysdata.
I'd like to adapt my pending 2.6.20 patch set to use that instead of my
current "device_ext" thingy I've been doing, but that would mean having
an ack from Greg to merge the first patch in 2.6.20. Thus I'd like
feedback asap. The second patch is less critial, though Len is free to
take it and do whatever he wants with it :-)
Cheers,
Ben.
next reply other threads:[~2006-11-09 0:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-09 0:45 Benjamin Herrenschmidt [this message]
2006-11-09 16:04 ` [PATCH 0/2] Add dev_sysdata and use it for ACPI Cornelia Huck
2006-11-09 22:35 ` Benjamin Herrenschmidt
2006-11-10 5:48 ` Greg KH
2006-11-10 9:44 ` Benjamin Herrenschmidt
2006-11-13 5:17 ` Paul Mackerras
2006-11-13 6:07 ` Benjamin Herrenschmidt
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=1163033121.28571.792.camel@localhost.localdomain \
--to=benh@au1.ibm.com \
--cc=akpm@osdl.org \
--cc=greg@kroah.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@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