From: Russell King <rmk@arm.linux.org.uk>
To: Linux Kernel List <linux-kernel@vger.kernel.org>
Cc: linux-pcmcia@lists.infradead.org
Subject: [CFT] Clean up yenta_socket
Date: Sun, 17 Aug 2003 15:34:35 +0100 [thread overview]
Message-ID: <20030817153435.A24478@flint.arm.linux.org.uk> (raw)
Patch set:
http://patches.arm.linux.org.uk/pcmcia/yenta-20030817*
The tar file contains all patches.
This is a patch set aimed to cleaning up the yenta controller quirks,
working around some of the warts which have appeared (eg, overwriting
of yenta_operations init pointer.) and adding better power management
support.
Unfortunately, since my laptop continues to have an argument with the
2.6 kernel APM, I am unable to properly test the suspend/hibernate/resume
functionality.
yenta-20030817-1-zv.diff
Use #defined constants for TI ZV initialisation
yenta-20030817-2-override.diff
Clean up yenta overrides - move the quirks to the main
PCI ID table, and list the quirks by type.
yenta-20030817-3-sockinit.diff
Move socket initialisation to the quirk table.
yenta-20030817-4-pm.diff
Add per-quirk power management (to aid saving/restoring
controller specific state.) Also, add proper pci state
saving/restoring. Note that Cardbus bridges have to
save and restore at least 0x48 bytes of configuration
space, not 0x40. WIBNI pci_save_state/pci_restore_state
took "start, length" parameters...
yenta-20030817-5-pm2.diff
Remove PM restore from socket initialisation; less reason
for socket initialisation to vary between controller types
now. In fact, we could very well get rid of much of the
TI-specific socket initialisation quirk handling, since
TI realised that they should be more compatible with other
implementations in later versions of their bridges.
yenta-20030817-6-init.diff
Move re-initialisation from the socket init/resume paths to
where it belongs - the main initialisation path.
yenta-20030817-7-quirks.diff
Move more controllers to the more advanced quirks.
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
next reply other threads:[~2003-08-17 14:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-17 14:34 Russell King [this message]
2003-08-19 2:31 ` [CFT] Clean up yenta_socket Thomas Molina
2003-08-19 11:42 ` Russell King
2003-08-19 21:43 ` Thomas Molina
-- strict thread matches above, loose matches on Subject: below --
2003-08-17 16:02 Daniel Ritz
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=20030817153435.A24478@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pcmcia@lists.infradead.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