All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sebastian Gottschall <s.gottschall@dd-wrt.com>
To: Julian Calaby <julian.calaby@gmail.com>, Felix Fietkau <nbd@nbd.name>
Cc: "Pavel Machek" <pavel@ucw.cz>, "Rafał Miłecki" <zajec5@gmail.com>,
	"open list:LED SUBSYSTEM" <linux-leds@vger.kernel.org>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"Kalle Valo" <kvalo@codeaurora.org>,
	ath10k@lists.infradead.org,
	"Sebastian Gottschall" <s.gottschall@newmedia-net.de>
Subject: Re: [PATCH v12] ath10k: add LED and GPIO controlling support for various chipsets
Date: Sat, 10 Mar 2018 08:56:07 +0100	[thread overview]
Message-ID: <40dc5bc3-d77e-397d-f3db-2efb70ff82ae@dd-wrt.com> (raw)
In-Reply-To: <CAGRGNgWSnObB8PomPPEGs533dmFyQQkOEsvxzyJ=BfBBcWT2Ug@mail.gmail.com>


>> taken a look at the specific code, and from my point of view the code
>> that sets up the LED (including callback) is so trivial that it's simply
>> not worth dealing with adding the leds-gpio driver to the mix.
>> It adds extra complexity and an extra dependency for no reason at all.
>> There's no extra functionality to be gained by using it.
> Stupid question: If the LED driver isn't using the GPIO subsystem
> (when enabled), what happens if the user uses the GPIO subsystem to
> fiddle with the pin the LED is connected to?

in our case here it can coexist and will not have a negative effect 
since the led will still run. (except if you reconfigure the gpio to input)
for sure it makes no sense.
but however i can block the gpio for beeing reused if the led driver 
took it. this has been made in ath9k for instance.
in ath10k i did not do it, since there is no technical requirement for it.
but that might not be the case for all gpio controllers, so there is no 
generic answer. for ath10k. harmless

Sebastian
>
> Thanks,
>

-- 
Mit freundlichen Grüssen / Regards

Sebastian Gottschall / CTO

NewMedia-NET GmbH - DD-WRT
Firmensitz:  Stubenwaldallee 21a, 64625 Bensheim
Registergericht: Amtsgericht Darmstadt, HRB 25473
Geschäftsführer: Peter Steinhäuser, Christian Scheele
http://www.dd-wrt.com
email: s.gottschall@dd-wrt.com
Tel.: +496251-582650 / Fax: +496251-5826565

WARNING: multiple messages have this Message-ID (diff)
From: Sebastian Gottschall <s.gottschall@dd-wrt.com>
To: Julian Calaby <julian.calaby@gmail.com>, Felix Fietkau <nbd@nbd.name>
Cc: "Rafał Miłecki" <zajec5@gmail.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	ath10k@lists.infradead.org,
	"open list:LED SUBSYSTEM" <linux-leds@vger.kernel.org>,
	"Pavel Machek" <pavel@ucw.cz>,
	"Sebastian Gottschall" <s.gottschall@newmedia-net.de>,
	"Kalle Valo" <kvalo@codeaurora.org>
Subject: Re: [PATCH v12] ath10k: add LED and GPIO controlling support for various chipsets
Date: Sat, 10 Mar 2018 08:56:07 +0100	[thread overview]
Message-ID: <40dc5bc3-d77e-397d-f3db-2efb70ff82ae@dd-wrt.com> (raw)
In-Reply-To: <CAGRGNgWSnObB8PomPPEGs533dmFyQQkOEsvxzyJ=BfBBcWT2Ug@mail.gmail.com>


>> taken a look at the specific code, and from my point of view the code
>> that sets up the LED (including callback) is so trivial that it's simply
>> not worth dealing with adding the leds-gpio driver to the mix.
>> It adds extra complexity and an extra dependency for no reason at all.
>> There's no extra functionality to be gained by using it.
> Stupid question: If the LED driver isn't using the GPIO subsystem
> (when enabled), what happens if the user uses the GPIO subsystem to
> fiddle with the pin the LED is connected to?

in our case here it can coexist and will not have a negative effect 
since the led will still run. (except if you reconfigure the gpio to input)
for sure it makes no sense.
but however i can block the gpio for beeing reused if the led driver 
took it. this has been made in ath9k for instance.
in ath10k i did not do it, since there is no technical requirement for it.
but that might not be the case for all gpio controllers, so there is no 
generic answer. for ath10k. harmless

Sebastian
>
> Thanks,
>

-- 
Mit freundlichen Grüssen / Regards

Sebastian Gottschall / CTO

NewMedia-NET GmbH - DD-WRT
Firmensitz:  Stubenwaldallee 21a, 64625 Bensheim
Registergericht: Amtsgericht Darmstadt, HRB 25473
Geschäftsführer: Peter Steinhäuser, Christian Scheele
http://www.dd-wrt.com
email: s.gottschall@dd-wrt.com
Tel.: +496251-582650 / Fax: +496251-5826565


_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

  reply	other threads:[~2018-03-10  7:56 UTC|newest]

Thread overview: 69+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-26  8:44 [PATCH v12] ath10k: add LED and GPIO controlling support for various chipsets s.gottschall
2018-02-26  8:44 ` s.gottschall
2018-02-27 17:03 ` Steve deRosier
2018-02-27 17:03   ` Steve deRosier
2018-02-27 17:43   ` Sebastian Gottschall
2018-02-27 17:43     ` Sebastian Gottschall
2018-02-27 22:08 ` Rafał Miłecki
2018-02-27 22:08   ` Rafał Miłecki
2018-02-28  1:49   ` Sebastian Gottschall
2018-02-28  1:49     ` Sebastian Gottschall
2018-03-02  9:03     ` Pavel Machek
2018-03-02  9:03       ` Pavel Machek
2018-03-02  9:22       ` Sebastian Gottschall
2018-03-02  9:22         ` Sebastian Gottschall
2018-03-02  9:22         ` Sebastian Gottschall
2018-03-07 16:22         ` Rafał Miłecki
2018-03-07 16:22           ` Rafał Miłecki
2018-03-07 17:54           ` Sebastian Gottschall
2018-03-07 17:54             ` Sebastian Gottschall
2018-03-08  9:02             ` Pavel Machek
2018-03-08  9:02               ` Pavel Machek
2018-03-08 12:33               ` Sebastian Gottschall
2018-03-08 12:33                 ` Sebastian Gottschall
2018-03-08 14:05                 ` Pavel Machek
2018-03-08 14:05                   ` Pavel Machek
2018-03-08 14:29                   ` Kalle Valo
2018-03-08 14:29                     ` Kalle Valo
2018-03-08 14:29                     ` Kalle Valo
2018-03-08 14:43                     ` Sebastian Gottschall
2018-03-08 14:43                       ` Sebastian Gottschall
2018-03-08 14:34                   ` Sebastian Gottschall
2018-03-08 14:34                     ` Sebastian Gottschall
2018-03-08 15:04                     ` Pavel Machek
2018-03-08 15:04                       ` Pavel Machek
2018-03-08 15:04                       ` Pavel Machek
2018-03-08 15:31                       ` Sebastian Gottschall
2018-03-08 15:31                         ` Sebastian Gottschall
2018-03-08 15:46                   ` Felix Fietkau
2018-03-08 15:46                     ` Felix Fietkau
2018-03-10  7:44                     ` Julian Calaby
2018-03-10  7:44                       ` Julian Calaby
2018-03-10  7:56                       ` Sebastian Gottschall [this message]
2018-03-10  7:56                         ` Sebastian Gottschall
2018-03-12  7:53                         ` Mathias Kresin
2018-03-12  7:53                           ` Mathias Kresin
2018-03-12  7:53                           ` Mathias Kresin
2018-03-12  9:09                           ` Sebastian Gottschall
2018-03-12  9:09                             ` Sebastian Gottschall
2018-03-12  9:09                             ` Sebastian Gottschall
2018-04-05 14:44 ` Kalle Valo
2018-04-05 14:44   ` Kalle Valo
2018-04-05 18:01   ` Sebastian Gottschall
2018-04-05 18:01     ` Sebastian Gottschall
2018-04-05 20:00     ` Sebastian Gottschall
2018-04-05 20:00       ` Sebastian Gottschall
2018-04-06  8:07       ` Kalle Valo
2018-04-06  8:07         ` Kalle Valo
2018-04-06  8:10         ` Sebastian Gottschall
2018-04-06  8:10           ` Sebastian Gottschall
     [not found]       ` <1d917688-9f59-39ad-46a6-527d9e3dec03@dd-wrt.com>
2018-04-06  8:09         ` Kalle Valo
2018-04-06  8:09           ` Kalle Valo
2018-04-06  8:11           ` Sebastian Gottschall
2018-04-06  8:11             ` Sebastian Gottschall
2018-04-06  8:25             ` Kalle Valo
2018-04-06  8:25               ` Kalle Valo
     [not found]               ` <f3617290-34d5-0cca-6442-4a37c06701b1@dd-wrt.com>
2018-04-06  9:17                 ` Kalle Valo
2018-04-06  9:17                   ` Kalle Valo
2018-04-06  8:05     ` Kalle Valo
2018-04-06  8:05       ` Kalle Valo

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=40dc5bc3-d77e-397d-f3db-2efb70ff82ae@dd-wrt.com \
    --to=s.gottschall@dd-wrt.com \
    --cc=ath10k@lists.infradead.org \
    --cc=julian.calaby@gmail.com \
    --cc=kvalo@codeaurora.org \
    --cc=linux-leds@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=nbd@nbd.name \
    --cc=pavel@ucw.cz \
    --cc=s.gottschall@newmedia-net.de \
    --cc=zajec5@gmail.com \
    /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.