2005-01-06 01:43:34 +00:00
|
|
|
#-
|
1999-11-28 21:11:13 +00:00
|
|
|
# Copyright (c) 1999 M. Warner Losh.
|
|
|
|
# All rights reserved.
|
|
|
|
#
|
|
|
|
# Redistribution and use in source and binary forms, with or without
|
|
|
|
# modification, are permitted provided that the following conditions
|
|
|
|
# are met:
|
|
|
|
# 1. Redistributions of source code must retain the above copyright
|
|
|
|
# notice, this list of conditions and the following disclaimer.
|
|
|
|
# 2. Redistributions in binary form must reproduce the above copyright
|
|
|
|
# notice, this list of conditions and the following disclaimer in the
|
|
|
|
# documentation and/or other materials provided with the distribution.
|
|
|
|
#
|
|
|
|
# THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND
|
|
|
|
# ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
|
|
|
|
# IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
|
|
|
|
# ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE
|
|
|
|
# FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
|
|
|
|
# DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
|
|
|
|
# OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
|
|
|
|
# HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
|
|
|
|
# LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
|
|
|
|
# OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
|
|
|
|
# SUCH DAMAGE.
|
|
|
|
#
|
|
|
|
# $FreeBSD$
|
|
|
|
#
|
|
|
|
|
2000-04-16 06:04:13 +00:00
|
|
|
#include <sys/bus.h>
|
2004-05-28 02:23:10 +00:00
|
|
|
#include <machine/bus.h>
|
2002-05-30 17:38:00 +00:00
|
|
|
#include <dev/pccard/pccardvar.h>
|
2000-04-16 06:04:13 +00:00
|
|
|
|
1999-11-28 21:11:13 +00:00
|
|
|
INTERFACE card;
|
|
|
|
|
|
|
|
#
|
|
|
|
# Companion interface for pccard. We need to set attributes for memory
|
|
|
|
# and i/o port mappings (as well as other types of attributes) that have
|
|
|
|
# a well defined meaning inside the pccard/cardbus system. The bus
|
|
|
|
# methods are inadequate for this because this must be done at the time the
|
|
|
|
# resources are set for the device, which predates their activation. Also,
|
|
|
|
# the driver activating the resources doesn't necessarily know or need to know
|
|
|
|
# these attributes.
|
|
|
|
#
|
2000-04-13 06:42:58 +00:00
|
|
|
METHOD int set_res_flags {
|
1999-11-28 21:11:13 +00:00
|
|
|
device_t dev;
|
|
|
|
device_t child;
|
2000-04-13 06:42:58 +00:00
|
|
|
int restype;
|
2000-03-26 07:01:52 +00:00
|
|
|
int rid;
|
2000-04-13 06:42:58 +00:00
|
|
|
u_long value;
|
1999-11-28 21:11:13 +00:00
|
|
|
};
|
|
|
|
|
2000-04-13 06:42:58 +00:00
|
|
|
METHOD int get_res_flags {
|
1999-11-28 21:11:13 +00:00
|
|
|
device_t dev;
|
|
|
|
device_t child;
|
2000-04-13 06:42:58 +00:00
|
|
|
int restype;
|
1999-11-28 21:11:13 +00:00
|
|
|
int rid;
|
2000-04-13 06:42:58 +00:00
|
|
|
u_long *value;
|
1999-11-28 21:11:13 +00:00
|
|
|
};
|
2000-04-13 06:42:58 +00:00
|
|
|
|
2000-06-18 05:02:09 +00:00
|
|
|
#
|
|
|
|
# Sets the memory offset of the pccard bridge's window into attribute
|
|
|
|
# or common memory space.
|
|
|
|
#
|
2000-04-13 06:42:58 +00:00
|
|
|
METHOD int set_memory_offset {
|
|
|
|
device_t dev;
|
|
|
|
device_t child;
|
2001-08-26 23:56:49 +00:00
|
|
|
int rid;
|
2005-01-24 06:48:26 +00:00
|
|
|
uint32_t cardaddr;
|
|
|
|
uint32_t *deltap;
|
2000-04-13 06:42:58 +00:00
|
|
|
}
|
|
|
|
|
2000-08-11 15:51:51 +00:00
|
|
|
METHOD int get_memory_offset {
|
|
|
|
device_t dev;
|
|
|
|
device_t child;
|
2001-08-26 23:56:49 +00:00
|
|
|
int rid;
|
2005-01-24 06:48:26 +00:00
|
|
|
uint32_t *offset;
|
2000-08-11 15:51:51 +00:00
|
|
|
}
|
|
|
|
|
2000-06-18 05:02:09 +00:00
|
|
|
#
|
|
|
|
# pccard bridges call this method to initate the attachment of a card
|
|
|
|
#
|
2000-04-13 06:42:58 +00:00
|
|
|
METHOD int attach_card {
|
|
|
|
device_t dev;
|
|
|
|
}
|
|
|
|
|
2000-06-18 05:02:09 +00:00
|
|
|
#
|
|
|
|
# pccard bridges call this to detach a card.
|
|
|
|
#
|
2000-04-13 06:42:58 +00:00
|
|
|
METHOD int detach_card {
|
|
|
|
device_t dev;
|
2000-11-28 15:50:13 +00:00
|
|
|
}
|
|
|
|
|
2002-07-17 05:20:43 +00:00
|
|
|
#
|
|
|
|
# Find "dev" in the passed table of devices. Return it or NULL.
|
|
|
|
#
|
2009-02-05 19:39:07 +00:00
|
|
|
METHOD const struct pccard_product * do_product_lookup {
|
2002-05-30 17:38:00 +00:00
|
|
|
device_t bus;
|
|
|
|
device_t dev;
|
|
|
|
const struct pccard_product *tab;
|
|
|
|
size_t ent_size;
|
|
|
|
pccard_product_match_fn matchfn;
|
|
|
|
}
|
2002-07-17 05:20:43 +00:00
|
|
|
|
Add a much-requested feature: The ability for pccard attachments to
scan the CIS for interesting tuples. 95% of what can be obtained from
the CIS is harvested by the pccard layer and presented to the user in
standard function calls. However, there are special needs at times
where the standard stuff doesn't suffice. This is for those special
cases.
CARD_SCAN_CIS(device_get_parent(dev), function, argp)
scans the CIS of the card, passing each tuple to function with
the tuple and argp as its arguments. Returning 0 continues the scan,
while returning 1 terminates the scan. The value of the last
invocation of function is returned from this function.
int (*pccard_scan_t)(struct pccard_tuple *tuple, void *argp)
function called for each tuple. Elements of the CIS tuple can be
read with pccard_tuple_read_{1,2,3,4,n}(). You are reading
the actual tuple memory each time, in case your card has
registers in the CIS.
# I suppose these things should be documented in pccard(4) or something like
# that.
# I plan on unifying cardbus CIS support in a similar way.
Approved by: re (scottl)
2005-07-01 03:40:28 +00:00
|
|
|
#
|
|
|
|
# Scanning function for accessing the CIS of a card in its driver.
|
|
|
|
#
|
|
|
|
METHOD int cis_scan {
|
|
|
|
device_t bus;
|
2005-09-13 17:56:36 +00:00
|
|
|
device_t dev;
|
Add a much-requested feature: The ability for pccard attachments to
scan the CIS for interesting tuples. 95% of what can be obtained from
the CIS is harvested by the pccard layer and presented to the user in
standard function calls. However, there are special needs at times
where the standard stuff doesn't suffice. This is for those special
cases.
CARD_SCAN_CIS(device_get_parent(dev), function, argp)
scans the CIS of the card, passing each tuple to function with
the tuple and argp as its arguments. Returning 0 continues the scan,
while returning 1 terminates the scan. The value of the last
invocation of function is returned from this function.
int (*pccard_scan_t)(struct pccard_tuple *tuple, void *argp)
function called for each tuple. Elements of the CIS tuple can be
read with pccard_tuple_read_{1,2,3,4,n}(). You are reading
the actual tuple memory each time, in case your card has
registers in the CIS.
# I suppose these things should be documented in pccard(4) or something like
# that.
# I plan on unifying cardbus CIS support in a similar way.
Approved by: re (scottl)
2005-07-01 03:40:28 +00:00
|
|
|
pccard_scan_t fnp;
|
|
|
|
void *argp;
|
|
|
|
};
|
2005-09-13 17:56:36 +00:00
|
|
|
|
|
|
|
#
|
|
|
|
# Convenience function to read attribute memory.
|
|
|
|
#
|
|
|
|
METHOD int attr_read {
|
|
|
|
device_t bus;
|
|
|
|
device_t dev;
|
|
|
|
uint32_t offset;
|
|
|
|
uint8_t *val;
|
|
|
|
}
|
|
|
|
|
|
|
|
#
|
|
|
|
# Convenience function to write attribute memory.
|
|
|
|
#
|
|
|
|
METHOD int attr_write {
|
|
|
|
device_t bus;
|
|
|
|
device_t dev;
|
|
|
|
uint32_t offset;
|
|
|
|
uint8_t val;
|
|
|
|
}
|
|
|
|
|
|
|
|
#
|
|
|
|
# Read the CCR register
|
|
|
|
#
|
|
|
|
METHOD int ccr_read {
|
|
|
|
device_t bus;
|
|
|
|
device_t dev;
|
|
|
|
uint32_t offset;
|
|
|
|
uint8_t *val;
|
|
|
|
}
|
|
|
|
|
|
|
|
#
|
|
|
|
# Write the CCR register
|
|
|
|
#
|
|
|
|
METHOD int ccr_write {
|
|
|
|
device_t bus;
|
|
|
|
device_t dev;
|
|
|
|
uint32_t offset;
|
|
|
|
uint8_t val;
|
|
|
|
}
|