2002-03-23 15:49:15 +00:00
|
|
|
# $FreeBSD$
|
|
|
|
|
|
2017-07-31 22:26:30 +00:00
|
|
|
SUBDIR = \
|
2019-08-05 15:56:44 +00:00
|
|
|
ads111x \
|
2017-07-31 22:26:30 +00:00
|
|
|
controllers \
|
|
|
|
|
cyapa \
|
2017-07-31 22:32:11 +00:00
|
|
|
ds1307 \
|
Add a new driver, ds13rtc, that handles all DS13xx series i2c RTC chips.
This driver supports only basic timekeeping functionality. It completely
replaces the ds133x driver. It can also replace the ds1374 driver, but that
will take a few other changes in MIPS code and config, and will be committed
separately. It does NOT replace the existing ds1307 driver, which provides
access to some of the extended features on the 1307 chip, such as controlling
the square wave output signal. If both ds1307 and ds13rtc drivers are
present, the ds1307 driver will outbid and win control of the device.
This driver can be configured with FDT data, or by using hints on non-FDT
systems. In addition to the standard hints for i2c devices, it requires
a "chiptype" string of the form "dallas,ds13xx" where 'xx' is the chip id
(i.e., the same format as FDT compat strings).
2017-08-13 21:02:40 +00:00
|
|
|
ds13rtc \
|
2018-03-06 02:30:34 +00:00
|
|
|
ds1672 \
|
2017-07-31 22:32:11 +00:00
|
|
|
ds3231 \
|
2017-09-17 22:58:13 +00:00
|
|
|
icee \
|
2017-07-31 22:26:30 +00:00
|
|
|
if_ic \
|
|
|
|
|
iic \
|
|
|
|
|
iicbb \
|
|
|
|
|
iicbus \
|
|
|
|
|
iicsmb \
|
|
|
|
|
isl \
|
2017-08-01 04:16:52 +00:00
|
|
|
isl12xx \
|
2018-02-22 23:18:46 +00:00
|
|
|
jedec_dimm \
|
Add support for i2c bus mux hardware.
An i2c bus can be divided into segments which can be selectively connected
and disconnected from the main bus. This is usually done to enable using
multiple slave devices having the same address, by isolating the devices
onto separate bus segments, only one of which is connected to the main bus
at once.
There are several types of i2c bus muxes, which break down into two general
categories...
- Muxes which are themselves i2c slaves. These devices respond to i2c
commands on their upstream bus, and based on those commands, connect
various downstream buses to the upstream. In newbus terms, they are both
a child of an iicbus and the parent of one or more iicbus instances.
- Muxes which are not i2c devices themselves. Such devices are part of the
i2c bus electrically, but in newbus terms their parent is some other
bus. The association with the upstream bus must be established by
separate metadata (such as FDT data).
In both cases, the mux driver has one or more iicbus child instances
representing the downstream buses. The mux driver implements the iicbus_if
interface, as if it were an iichb host bridge/i2c controller driver. It
services the IO requests sent to it by forwarding them to the iicbus
instance representing the upstream bus, after electrically connecting the
upstream bus to the downstream bus that hosts the i2c slave device which
made the IO request.
The net effect is automatic mux switching which is transparent to slaves on
the downstream buses. They just do i2c IO they way they normally do, and the
bus is electrically connected for the duration of the IO and then idled when
it is complete.
The existing iicbus_if callback() method is enhanced so that the parameter
passed to it can be a struct which contains a device_t for the requesting
bus and slave devices. This change is done by adding a flag that indicates
the extra values are present, and making the flags field the first field of
a new args struct. If the flag is set, the iichb or mux driver can recast
the pointer-to-flags into a pointer-to-struct and access the extra
fields. Thus abi compatibility with older drivers is retained (but a mux
cannot exist on the bus with the older iicbus driver in use.)
A new set of core support routines exists in iicbus.c. This code will help
implement mux drivers for any type of mux hardware by supplying all the
boilerplate code that forwards IO requests upstream. It also has code for
parsing metadata and instantiating the child iicbus instances based on it.
Two new hardware mux drivers are added. The ltc430x driver supports the
LTC4305/4306 mux chips which are controlled via i2c commands. The
iic_gpiomux driver supports any mux hardware which is controlled by
manipulating the state of one or more gpio pins. Test Plan
Tested locally using a variety of mux'd bus configurations involving both
ltc4305 and a homebrew gpio-controlled mux. Tested configurations included
cascaded muxes (unlikely in the real world, but useful to prove that 'it all
just works' in terms of the automatic switching and upstream forwarding of
IO requests).
2020-01-02 17:51:49 +00:00
|
|
|
mux \
|
2017-07-31 22:32:11 +00:00
|
|
|
nxprtc \
|
2018-03-04 21:06:21 +00:00
|
|
|
rtc8583 \
|
2017-08-14 00:00:24 +00:00
|
|
|
s35390a \
|
2017-07-31 22:26:30 +00:00
|
|
|
smb \
|
|
|
|
|
smbus \
|
2002-03-23 15:49:15 +00:00
|
|
|
|
|
|
|
|
.include <bsd.subdir.mk>
|
