2002-03-23 15:49:15 +00:00
|
|
|
# $FreeBSD$
|
|
|
|
|
|
2018-02-18 22:54:19 +00:00
|
|
|
.PATH: ${SRCTOP}/sys/dev/iicbus
|
|
|
|
|
|
|
|
|
|
KMOD= iicbus
|
|
|
|
|
SRCS= \
|
|
|
|
|
bus_if.h \
|
|
|
|
|
device_if.h \
|
2018-02-18 22:57:04 +00:00
|
|
|
iic_recover_bus.c \
|
2018-02-18 22:54:19 +00:00
|
|
|
iicbus.c \
|
|
|
|
|
iicbus.h \
|
|
|
|
|
iicbus_if.c \
|
|
|
|
|
iicbus_if.h \
|
|
|
|
|
iiconf.c \
|
|
|
|
|
iiconf.h \
|
2018-04-01 18:22:24 +00:00
|
|
|
opt_platform.h \
|
2002-03-23 15:49:15 +00:00
|
|
|
|
2020-03-09 20:31:38 +00:00
|
|
|
.if ${MACHINE_CPUARCH} == "aarch64" || ${MACHINE_CPUARCH} == "amd64" || \
|
|
|
|
|
${MACHINE_CPUARCH} == "i386"
|
|
|
|
|
SRCS+= acpi_iicbus.c opt_acpi.h acpi_if.h
|
|
|
|
|
.endif
|
|
|
|
|
|
Instead of building ofw_iicbus as a separate module, just compile it in to
the iicbus module for FDT-based systems.
The primary motivation for this is that host controller drivers which
declare DRIVER_MODULE(ofw_iicbus, thisdriver, etc, etc) now only need a
single MODULE_DEPEND(thisdriver, ofw_iicbus) for runtime linking to resolve
all the symbols. With ofw_iicbus and iicbus in separate modules, drivers
would need to declare a MODULE_DEPEND() on both, because symbol lookup is
non-recursive through the dependency chain. Requiring a driver to have
MODULE_DEPENDS() on both amounts to requiring the drivers to understand the
kobj inheritence details of how ofw_iicbus is implemented, which seems like
something they shouldn't have to know (and could even change some day).
Also, this is somewhat analogous to how the drivers get built when compiled
into the kernel. You don't have to ask for ofw_iicbus separately, it just
gets built in along with iicbus when option FDT is in effect.
2018-02-25 18:26:50 +00:00
|
|
|
.if !empty(OPT_FDT)
|
|
|
|
|
SRCS+= ofw_iicbus.c ofw_bus_if.h
|
|
|
|
|
.endif
|
|
|
|
|
|
2002-03-23 15:49:15 +00:00
|
|
|
.include <bsd.kmod.mk>
|
