All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jacek Anaszewski <j.anaszewski@samsung.com>
To: "Michał Kępień" <kernel@kempniu.pl>
Cc: "Richard Purdie" <rpurdie@rpsys.net>,
	"Matthew Garrett" <mjg59@srcf.ucam.org>,
	"Pali Rohár" <pali.rohar@gmail.com>,
	"Darren Hart" <dvhart@infradead.org>,
	"Bob Rodgers" <Robert_Rodgers@dell.com>,
	"Louis Davis" <Louis_Davis@dell.com>,
	"Jim Dailey" <Jim_Dailey@dell.com>,
	"Alex Hung" <alex.hung@canonical.com>,
	linux-leds@vger.kernel.org, platform-driver-x86@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: Moving drivers/leds/dell-led.c to drivers/platform/x86
Date: Wed, 15 Jun 2016 12:10:20 +0200	[thread overview]
Message-ID: <5761298C.9030005@samsung.com> (raw)
In-Reply-To: <20160613134942.GA2824@eudyptula.hq.kempniu.pl>

Hi Michał,

I have no objections.

Best regards,
Jacek Anaszewski

On 06/13/2016 03:49 PM, Michał Kępień wrote:
> Hi everyone,
>
> Back in January [1], while working on the dell-smbios module, I
> suggested that the code present in drivers/leds/dell-led.c could be
> moved to drivers/platform/x86 for coherency.  I decided to revisit that
> idea.
>
> dell-led consists of two major parts:
>
>    - the part handling an "Activity LED" present in Dell Latitude 2100
>      netbooks, introduced in 72dcd8d; it registers a LED device and uses
>      a special WMI interface to control its state,
>
>    - the part exposing a "microphone mute LED interface", introduced in
>      db6d8cc; this interface is used by sound/pci/hda/dell_wmi_helper.c;
>      while the original implementation also used a WMI interface, it was
>      changed to use dell-smbios in cf0d7ea and 0c41a08.
>
> I believe both parts could (and should) be moved to drivers/platform/x86
> as drivers/platform/x86/dell-laptop.c already handles a bunch of LEDs
> and drivers/leds/dell-led.c is the only dell-smbios user outside of
> drivers/platform/x86.
>
> My question to you, the maintainers of the relevant drivers and
> subsystems, is whether you would like to see such a move happen.  I have
> prepared a draft patch series which:
>
>    - moves the "microphone mute LED interface" to dell-laptop.c,
>      effectively causing sound/pci/hda/dell_wmi_helper.c to depend on
>      CONFIG_DELL_LAPTOP instead of CONFIG_LEDS_DELL_NETBOOKS,
>
>    - moves the "Activity LED" part to a new file, tentatively called
>      drivers/platform/x86/dell-wmi-led.c.
>
> Merging the "Activity LED" part with drivers/platform/x86/dell-wmi.c is
> not really clean because dell-wmi handles a different GUID, which AFAIK
> is not related in any way to the GUID used by dell-led.
>
> So, before I spam *three* subsystem mailing lists with a bunch of
> patches, I would love to hear from the maintainers of both drivers/leds
> and drivers/platform/x86 whether there are any arguments against such a
> move.  Meanwhile, I will keep polishing the patch series and if there is
> no strong disagreement from any party involved, I will post the series
> next week or so, so that we can discuss code and not just ideas.
>
> As a side note, if anyone reading this has access to a Dell device which
> has an "Activity LED" and/or a "microphone mute LED" currently supported
> by dell-led, I would love to hear from you as I do not have the hardware
> needed to practically test the patch series I am working on.
>
> Looking forward to hearing from you,
>
> [1] https://www.spinics.net/lists/platform-driver-x86/msg08143.html
>

      parent reply	other threads:[~2016-06-15 10:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-13 13:49 Moving drivers/leds/dell-led.c to drivers/platform/x86 Michał Kępień
2016-06-15  8:05 ` Pali Rohár
2016-06-15 10:10 ` Jacek Anaszewski [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=5761298C.9030005@samsung.com \
    --to=j.anaszewski@samsung.com \
    --cc=Jim_Dailey@dell.com \
    --cc=Louis_Davis@dell.com \
    --cc=Robert_Rodgers@dell.com \
    --cc=alex.hung@canonical.com \
    --cc=dvhart@infradead.org \
    --cc=kernel@kempniu.pl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-leds@vger.kernel.org \
    --cc=mjg59@srcf.ucam.org \
    --cc=pali.rohar@gmail.com \
    --cc=platform-driver-x86@vger.kernel.org \
    --cc=rpurdie@rpsys.net \
    /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.