From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: linux-arch@vger.kernel.org
Cc: Len Brown <len.brown@intel.com>, Andrew Morton <akpm@osdl.org>
Subject: [PATCH 0/2] Add dev_sysdata and use it for ACPI
Date: Fri, 10 Nov 2006 17:58:48 +1100 [thread overview]
Message-ID: <1163141928.4982.142.camel@localhost.localdomain> (raw)
Due to the total absence of feedback (except Cornelia who'd like to use
this for s390 too), I'm reposting them here as they affect all archs
(and Willy admitted not seeing them on lkml).
I've already rebased all of my pending 2.6.20 powerpc stuff on top of
Patch 1/2, so I hope there won't be any major objection.
Patch 2/2 is not as urgent/important, Len, it's up to you to decide
wether you want to take the approach or not, but I feel like this void *
firmware_data in struct device is now userless, so ...
1/2 - 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.
2/2 - 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 i386, x86_64 and ia64
dev_sysdata.
Cheers,
Ben.
next reply other threads:[~2006-11-10 6:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-10 6:58 Benjamin Herrenschmidt [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-11-09 0:45 [PATCH 0/2] Add dev_sysdata and use it for ACPI Benjamin Herrenschmidt
2006-11-09 16:04 ` 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=1163141928.4982.142.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=akpm@osdl.org \
--cc=len.brown@intel.com \
--cc=linux-arch@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.