[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160314223022.GB22360@jcartwri.amer.corp.natinst.com>
Date: Mon, 14 Mar 2016 17:30:22 -0500
From: Josh Cartwright <joshc@...com>
To: Greg KH <gregkh@...uxfoundation.org>
Cc: Kyle Roeschley <kyle.roeschley@...com>, arnd@...db.de,
linux-kernel@...r.kernel.org, jeff.westfahl@...com,
nathan.sullivan@...com, xander.huff@...com,
Lee Jones <lee.jones@...aro.org>
Subject: Re: [PATCH 1/2] misc: add nirtfeatures driver
On Mon, Mar 14, 2016 at 03:05:59PM -0700, Greg KH wrote:
> On Mon, Mar 14, 2016 at 04:54:32PM -0500, Kyle Roeschley wrote:
> > From: Jeff Westfahl <jeff.westfahl@...com>
> >
> > This driver introduces support for hardware features of National
> > Instruments real-time controllers. This is an ACPI device that exposes
> > LEDs, switches, and watchdogs.
>
> If it's an acpi driver, why not put it in drivers/acpi?
For the same reason we don't move all drivers for devices-on-a-PCI-bus
into drivers/pci?
Drivers typically exist in the sourcetree with other drivers which
implement similar functionality, which works great for devices with
clear functional boundaries (GPIO controller drivers in drivers/gpio,
led drivers in drivers/leds, etc. etc.); but for devices which are a
hodgepodge of functionality, there isn't really a good fit anywhere
except maybe in misc or mfd.
We could move it to mfd, but drivers in drivers/mfd which don't make use
of MFD_CORE seems equally strange (although, I suppose there is
precedent). Maybe Lee has some thoughts.
Josh
Download attachment "signature.asc" of type "application/pgp-signature" (474 bytes)
Powered by blists - more mailing lists