mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jiri Pirko <jiri@resnulli.us>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org, davem@davemloft.net,
	mchehab@kernel.org, jikos@kernel.org
Subject: Re: [patch 0/2] add actuators support
Date: Mon, 17 Jul 2017 18:48:36 +0200	[thread overview]
Message-ID: <20170717164836.GB1920@nanopsycho.orion> (raw)
In-Reply-To: <20170717164006.GB11246@kroah.com>

Mon, Jul 17, 2017 at 06:40:06PM CEST, gregkh@linuxfoundation.org wrote:
>On Mon, Jul 17, 2017 at 06:34:58PM +0200, Jiri Pirko wrote:
>> Mon, Jul 17, 2017 at 06:28:38PM CEST, gregkh@linuxfoundation.org wrote:
>> >On Mon, Jul 17, 2017 at 06:19:12PM +0200, Jiri Pirko wrote:
>> >> From: Jiri Pirko <jiri@mellanox.com>
>> >> 
>> >> I am owner of height adjustable desk and naturally, as it has an USB
>> >> interface, I need to controll it from my computer. Started to think
>> >> about what would be the best way, I realized that I need to introduce
>> >> a new driver class in kernel. The reason is a need to have one API
>> >> for all possible kinds of actuator devices (USB, I2C, gpio, etc).
>> >
>> >Why does this have to be a kernel driver at all?  Your USB driver should
>> >really just be a simple userspace application (use libusb to have it
>> >work on all operating systems.)
>> 
>> Yeah, I was thinking about it as well. To have some kind of single
>> purpose app like sispmctl (control of surge protector). But that would
>> limit you only for this specific device. And for multiple devices you
>> would have to have multiple apps.
>> 
>> So it seems to me like a suitable solution to have this as a driver
>> class.
>
>For USB devices, especially ones as simple as this, we don't want them
>to have kernel drivers.  It's just overkill.
>
>And never create a class if you only have one type of device, otherwise
>you don't know if you really have it properly defined or not.  3 is a
>good number to start with.

You are making it hard for me :) Have to find other 2 then. And I thought
that this spare time quest is coming to an end... 


>
>sorry,
>
>greg k-h

      reply	other threads:[~2017-07-17 16:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-17 16:19 Jiri Pirko
2017-07-17 16:19 ` [patch 1/2] add support for generic actuator devices Jiri Pirko
2017-07-17 16:19 ` [patch 2/2] actuator: introduce Linak USB2LIN cable support Jiri Pirko
2017-07-17 16:28 ` [patch 0/2] add actuators support Greg KH
2017-07-17 16:34   ` Jiri Pirko
2017-07-17 16:40     ` Greg KH
2017-07-17 16:48       ` Jiri Pirko [this message]

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=20170717164836.GB1920@nanopsycho.orion \
    --to=jiri@resnulli.us \
    --cc=davem@davemloft.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=jikos@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchehab@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®