On Mon, Feb 06, 2023 at 08:41:44AM -0700, Jeffrey Hugo wrote: > Now that we have all the components of a minimum QAIC which can boot and > run an AIC100 device, add the infrastructure that allows the QAIC driver > to be built. > > Signed-off-by: Jeffrey Hugo <quic_jhugo@xxxxxxxxxxx> > Reviewed-by: Carl Vanderlip <quic_carlv@xxxxxxxxxxx> > --- > drivers/accel/Kconfig | 1 + > drivers/accel/Makefile | 1 + > drivers/accel/qaic/Kconfig | 23 +++++++++++++++++++++++ > drivers/accel/qaic/Makefile | 13 +++++++++++++ > 4 files changed, 38 insertions(+) > create mode 100644 drivers/accel/qaic/Kconfig > create mode 100644 drivers/accel/qaic/Makefile > > diff --git a/drivers/accel/Kconfig b/drivers/accel/Kconfig > index 8348639..56d0d01 100644 > --- a/drivers/accel/Kconfig > +++ b/drivers/accel/Kconfig > @@ -25,3 +25,4 @@ menuconfig DRM_ACCEL > > source "drivers/accel/habanalabs/Kconfig" > source "drivers/accel/ivpu/Kconfig" > +source "drivers/accel/qaic/Kconfig" > diff --git a/drivers/accel/Makefile b/drivers/accel/Makefile > index 07aa77a..3cb6f14 100644 > --- a/drivers/accel/Makefile > +++ b/drivers/accel/Makefile > @@ -2,3 +2,4 @@ > > obj-y += habanalabs/ > obj-y += ivpu/ > +obj-y += qaic/ All should be changed to obj-$(CONFIG_DRM_ACCEL_DRIVER) to avoid inspecting sub-directories. I'll send patch for this. Then you can adjust accordingly for qaic. Regards Stanislaw
