GitLab

this patches removes unneccessary calls to yenta_init()/ti_set_zv() in
ti1250_init() as the called ti113x_init() already does this..

[ GregKH has already done this is USB and PCI core. ]

From: "Warren A. Layton" <zeevon@debian.org>

Based on a request from Matthew Wilcox, convert instances of
pci_dev->slot_name to use pci_name() instead:

  "In order to support PCI Domains, we have to stop using slot_name.
   It's related to driver model transition too since pci_dev->slot_name
   was redundant with pci_dev->dev.bus_id.  So I introduced the inline
   function pci_name().  Now there's about 300-400 places in the tree
   that're using slot_name which need to be converted to use pci_name().
   once that's done, we can remove the slot_name pointer in pci_dev and
   save a (void *) per pci_dev."

(Taral)

Fixes up drivers/input/* drivers/isdn/* drivers/media/*
drivers/mtd/* drivers/parisc/* drivers/pci/* drivers/parport/*
drivers/scsi/* and drivers/serial/*

Also apply the right fix to the yenta hang problem

pcmcia_socket_dev_suspend() should be called with SUSPEND_SAVE_STATE
if the level is unknown.

This patch updates the sh-specific hd64465 pcmcia driver for the new API, as
well as fixing up some other issues (such as remap_page_range() abuse -- we
remap through P3 area instead) which caused it not to compile. Changes by
Dominik Brodowski and myself.

Switching the PCMCIA interrupts from serial PCI interrupts to parallel
PCI interrupts causes machines to hang solid.  If we leave such setups
well alone, and only change the interrupt mode of parallel PCI systems
between PCI+ISA and PCI only.

from 2.4-ac - it seems to cause hangs for people.

From: Russell King <rmk@arm.linux.org.uk>

Interrupts can sometimes occur before the socket thread is started.

From: Daniel Ritz <daniel.ritz@gmx.ch>

init_socket() enables interrupts, and the interrupt handler does a wakeup.
Let's initialise that waitqueue head before turning on the interrupts.

Rename the strangely named "ss_entry" structure to "ops".

Don't hide calls to the socket driver by "shorthand functions"

We were calling wake_up on an uninitialised wait queue.  Oops.
Fix this by ignoring events from the socket driver if we know that
the pcmcia thread is not running.

Since the cs.c pcmcia core has a per-socket thread, we don't need each
socket driver having a work queue and associated complexity.

Therefore, remove this complexity and allow the socket drivers to call
pcmcia_parse_events directly from their interrupt or timer handlers.

Remove register_callback methods.  Instead, allow socket drivers
pass their events directly into cs.c via pcmcia_parse_events().

Add work-around for i82365-based socket drivers to the core PCMCIA
code.  Since insert processing is not a time critical event, we can
afford to delay (by sleeping) these for everyone.

Get/Put module when we insert and remove a card.  This avoids a
potential deadlock when socket drivers are unloaded, and we have
a cardbus card known to the system.

Move ->owner field from socket operations to pcmcia_socket.  (This
change is mainly for the SA11xx drivers, which use a core driver
for the chip, and a separate module for all the machine specific
bits.)

This is an update of the AMD Alchemy support for 2.5.

(This is way behind what we have for 2.4 but forward porting is non-trivial
and work in progress.)

Stumbled over this patch within 2.4.21-ac. Depends on the ti113x.h
burst mode patch sent earlier.

Linus Torvalds wrote:
> Here's a patch that apparently improves throughput on Texas
> Instrument 1520 controllers a lot by enabling memory bursting.
> Apparently to the point that without this you can't even do
> things like 802.11g without starting to drop data.

Done. Also cleaned up the "Override Table" a bit.

It was using a non-existent socket[] index and not doing it for all
sockets.

Some socket hardware appears to "bounce" when a card is inserted - we
seem to receive more than one SS_DETECT event.  Unfortunately, this
causes us to initialise, setup the socket, and create the necessary
devices multiple times.

Fix this by ignoring card insertion events when we already know that
there is a card in the socket.

We must always allocate windows below 1MB when a socket driver
indicates that it does not have "page registers".  Handle this
case in rsrc_mgr.c within find_mem_region rather than each use
of find_mem_region().

Remove the racy check_mem_resource() function.  Instead, claim
the region while we check it, passing a resource structure to
the core validation functions.

The overwhelming majority of Linux users are using modular PCMCIA,
and loading the "yenta_socket" module.  2.5.71 unfortunately changed
the name to "yenta" when pci_socket.c was combined with yenta.c.
Rename yenta.[ch] to yenta_socket.[ch] for compatibility.

Although no such oops has been reported, removing a socket driver
while a file under /sysfs/class/pcmcia_socket/pcmcia_socket* is
held open by user space could potentially cause an oops.

Plug this by preventing pcmcia_unregister_socket from returning
until all references by sysfs to the pcmcia socket have been dropped.

Patch from Daniel Ritz

rmmod yenta produces the following oops:
Unable to handle kernel paging request at virtual address d084781e
EIP is at yenta_config_init+0x18f/0x1e0 [yenta]
Process pccardd (pid: 2618, threadinfo=c3236000 task=c988ae60)

Update sa11xx_core.c for Dominik's previous patch.

Remove the inquire_socket callback by moving the (static) capability
information to the top-level of struct pcmcia_socket.

Move the creation of /proc/pccard to ds.c so that ds.c is the only
file that needs to include linux/proc_fs.h any longer.

Remove the proc_setup callback. The drivers can use CLASS_DEVICE_ATTR
instead. Example: i82365.c.

A "\n" was at the end of the device name, sorry.

Rename the socket_info_t inside tcic.c to struct tcic_socket. At one
time there were at least five different "socket_info_t" within cardmgr
/ linux/drivers/pcmcia. Let's get rid of all of them to avoid
confusion in future.

Rename the socket_info_t inside tcic.c to struct i82365_socket. At one
time there were at least five different "socket_info_t" within cardmgr
/ linux/drivers/pcmcia. Let's get rid of all of them to avoid
confusion in future.

The i82365 doesn't work unless CONFIG_ISA is set -- see this from
i82365_init:

...

    sockets = 0;

#ifdef CONFIG_ISA
    isa_probe();
#endif

    if (sockets == 0) {
        printk("not found.\n");
        driver_unregister(&i82365_driver);
        return -ENODEV;
    }

...

So, remove all instances of CONFIG_ISA from i82365.c and add a
dependency to the Kconfig file.

Get rid of the

typedef struct pcmcia_socket socket_info_t;

by replacing all remaining usages of cs_internal's socket_info_t with
struct pcmcia_socket.