linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Vasant Hegde <hegdevasant@linux.vnet.ibm.com>
To: Jacek Anaszewski <j.anaszewski@samsung.com>
Cc: Jacek Anaszewski <jacek.anaszewski@gmail.com>,
	linux-leds@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
	mpe@ellerman.id.au, rpurdie@rpsys.net, cooloney@gmail.com,
	khandual@linux.vnet.ibm.com, j.anaszewski81@gmail.com,
	arnd@arndb.de, stewart@linux.vnet.ibm.com,
	benh@kernel.crashing.org
Subject: Re: [PATCH v8 3/3] leds/powernv: Add driver for PowerNV platform
Date: Wed, 19 Aug 2015 17:36:27 +0530	[thread overview]
Message-ID: <55D47143.5040908@linux.vnet.ibm.com> (raw)
In-Reply-To: <55D46E5B.20203@samsung.com>

On 08/19/2015 05:24 PM, Jacek Anaszewski wrote:
> Hi Vasant,
> 
> On 07/28/2015 07:40 PM, Jacek Anaszewski wrote:
>> Vasant,
>>
>>>
>>>>
>>>> Without my core changes your driver won't work with led triggers, but
>>>> AFAIR this use case is not relevant for your LEDs? Eventually, we could
>>>> produce a patch set adding support for LED triggers if it will be clear
>>>> that LED core changes will not be merged in the upcoming merge window.
>>>
>>> IIUC current LED code doesn't allow me to sleep (without driver specific
>>> workqueue). And powernv_led_set() call will sleep. Hence I think it
>>> won't work.
>>>
>>> I did a quick test without your patch. It doesn't seems to be working.
> 

Jacek,

> Does brightness setting work properly without work queue?
> 

Sorry ...  I forgot to respond to this thread..

Yes.. It worked for me..

I have tested v9 with and without your code patchset.. In both cases its working
fine..

Sample test case :
	[root@tul176p1 leds]# cd U78C9.001.RST0027-P1-C14:identify
	
	[root@tul176p1 U78C9.001.RST0027-P1-C14:identify]# pwd
	/sys/class/leds/U78C9.001.RST0027-P1-C14:identify
	
	[root@tul176p1 U78C9.001.RST0027-P1-C14:identify]# cat brightness
	0
	
	[root@tul176p1 U78C9.001.RST0027-P1-C14:identify]# echo 1 > brightness
	[root@tul176p1 U78C9.001.RST0027-P1-C14:identify]# cat brightness
	255

-Vasant

  reply	other threads:[~2015-08-19 12:07 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-25  5:21 [PATCH v8 0/3] LED driver for PowerNV platform Vasant Hegde
2015-07-25  5:21 ` [PATCH v8 1/3] powerpc/powernv: Add OPAL interfaces for accessing and modifying system LED states Vasant Hegde
2015-07-25  5:21 ` [PATCH v8 2/3] powerpc/powernv: Create LED platform device Vasant Hegde
2015-07-25  5:21 ` [PATCH v8 3/3] leds/powernv: Add driver for PowerNV platform Vasant Hegde
2015-07-26 21:41   ` Jacek Anaszewski
2015-07-27  3:41     ` Vasant Hegde
2015-07-27  9:50       ` Jacek Anaszewski
2015-07-28 13:40         ` Vasant Hegde
2015-07-28 17:40           ` Jacek Anaszewski
2015-08-19 11:54             ` Jacek Anaszewski
2015-08-19 12:06               ` Vasant Hegde [this message]
2015-07-28  6:38       ` Jacek Anaszewski
2015-07-28 10:14         ` Benjamin Herrenschmidt
2015-07-28 11:23           ` Jacek Anaszewski
2015-08-18 10:21   ` [v8,3/3] " Michael Ellerman
2015-08-19  8:42     ` Vasant Hegde

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=55D47143.5040908@linux.vnet.ibm.com \
    --to=hegdevasant@linux.vnet.ibm.com \
    --cc=arnd@arndb.de \
    --cc=benh@kernel.crashing.org \
    --cc=cooloney@gmail.com \
    --cc=j.anaszewski81@gmail.com \
    --cc=j.anaszewski@samsung.com \
    --cc=jacek.anaszewski@gmail.com \
    --cc=khandual@linux.vnet.ibm.com \
    --cc=linux-leds@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mpe@ellerman.id.au \
    --cc=rpurdie@rpsys.net \
    --cc=stewart@linux.vnet.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).