From: Ian Abbott <abbotti@mev.co.uk>
To: Hartley Sweeten <HartleyS@visionengravers.com>,
"driverdev-devel@linuxdriverproject.org"
<driverdev-devel@linuxdriverproject.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/5] staging: comedi: split bus support into separate modules
Date: Fri, 31 Oct 2014 22:53:39 +0000 [thread overview]
Message-ID: <545412F3.60502@mev.co.uk> (raw)
In-Reply-To: <DC148C5AA1CEBA4E87973D432B1C2D882601B051@P3PWEX4MB008.ex4.secureserver.net>
On 31/10/14 22:18, Hartley Sweeten wrote:
> On Friday, October 31, 2014 3:09 PM, Ian Abbott wrote:
>> On 31/10/14 18:19, Hartley Sweeten wrote:
>>> On Friday, October 31, 2014 10:48 AM, Ian Abbott wrote:
>>>> The Comedi core module doesn't need support for PCI, USB or PCMCIA.
>>>> Only the low-level Comedi drivers need it. Split the support for these
>>>> bus types out of the core "comedi" module and into new modules,
>>>> "comedi_pci", "comedi_usb", and "comedi_pcmcia".
>>>>
>>>> 1) staging: comedi: comedidev.h: remove dummy PCI support functions
>>>> 2) staging: comedi: comedidev.h: remove some #ifdefs
>>>> 3) staging: comedi: split out PCMCIA support into new module
>>>> 4) staging: comedi: split out USB support into new module
>>>> 5) staging: comedi: split out PCI support into new module
>>>
>>> Ian,
>>>
>>> Is this really necessary?
>>>
>>> The pci, usb, and pcmcia support is already conditionally compiled in.
>>> The support does get added to the main comedi module instead of
>>> as separate modules but that shouldn't be a problem.
>>
>> Well a lot of potentially unused module space could get pulled in if
>> using a stock distro kernel. For example, the USB dependencies amount to
>> over 200k. Not so bad for the others, especially PCI where the code is
>> built in anyway.
>
> But its only pulled in if the user selected the usb, pci, and/or pcmcia
> comedi drivers. And if they selected any of those options they will
> need the that code anyway.
Yes, if the user configured and compiled the kernel his or herself. I
was more concerned with using distro kernel binaries.
> Splitting the bus specific code out of the comdi core module doesn't
> lower the total module space used it just spreads it from one to possibly
> four modules. And it increases the module dependancies for all the
> usb, pci, and pcmcia comedi drivers.
Yes, you might have to load one more module to load the modules for a
particular card, but modprobe can take care of that. It's only a pain if
you're loading the modules individually. On the other hand, to load the
"comedi_test.ko" module using insmod on a desktop PC on Debian for
example (assuming the USB modules are already loaded), you'd first have
to load the "pcmcia_core" and "pcmcia" modules before the "comedi" and
"comedi_test" modules. But with the PCMCIA support separated out, you'd
just have to load the "comedi" and "comedi_test" modules.
> To be clear, I'm not against this series I just want to make sure it's worth
> applying.
I like the idea of the core comedi module being separated from all the
various buses. And other buses can be added easily without pulling extra
dependencies into the core (e.g. for platform or spi devices).
--
-=( Ian Abbott @ MEV Ltd. E-mail: <abbotti@mev.co.uk> )=-
-=( Web: http://www.mev.co.uk/ )=-
next prev parent reply other threads:[~2014-10-31 22:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-31 17:47 [PATCH 0/5] staging: comedi: split bus support into separate modules Ian Abbott
2014-10-31 17:47 ` [PATCH 1/5] staging: comedi: comedidev.h: remove dummy PCI support functions Ian Abbott
2014-10-31 17:47 ` [PATCH 2/5] staging: comedi: comedidev.h: remove some #ifdefs Ian Abbott
2014-10-31 17:47 ` [PATCH 3/5] staging: comedi: split out PCMCIA support into new module Ian Abbott
2014-10-31 17:47 ` [PATCH 4/5] staging: comedi: split out USB " Ian Abbott
2014-10-31 17:47 ` [PATCH 5/5] staging: comedi: split out PCI " Ian Abbott
2014-10-31 18:19 ` [PATCH 0/5] staging: comedi: split bus support into separate modules Hartley Sweeten
2014-10-31 22:08 ` Ian Abbott
2014-10-31 22:18 ` Hartley Sweeten
2014-10-31 22:53 ` Ian Abbott [this message]
2014-10-31 23:00 ` Ian Abbott
2014-11-05 22:50 ` Greg Kroah-Hartman
2014-11-05 23:13 ` Hartley Sweeten
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=545412F3.60502@mev.co.uk \
--to=abbotti@mev.co.uk \
--cc=HartleyS@visionengravers.com \
--cc=driverdev-devel@linuxdriverproject.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.