public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Jacek Anaszewski <j.anaszewski@samsung•com>
To: Stewart Smith <stewart@linux•vnet.ibm.com>
Cc: Jacek Anaszewski <j.anaszewski81@gmail•com>,
	cooloney@gmail•com, rpurdie@rpsys•net,
	linuxppc-dev@lists•ozlabs.org, linux-leds@vger•kernel.org,
	khandual@linux•vnet.ibm.com
Subject: Re: [PATCH v2 2/2] leds/powernv: Add driver for PowerNV platform
Date: Tue, 28 Apr 2015 11:10:08 +0200	[thread overview]
Message-ID: <553F4E70.3020604@samsung.com> (raw)
In-Reply-To: <m3zj5slovt.fsf@oc8180480414.ibm.com>

On 04/28/2015 08:59 AM, Stewart Smith wrote:
> Jacek Anaszewski <j.anaszewski81@gmail•com> writes:
>> Is the DT node we are discussing used by some other drivers than the
>> LED class driver? Or is it required in this form by other components of
>> your platform?
>
> OS kernels are the chief consumers, Linux being the overwhelmingly major
> one here.
>
> But this is what firmware currently produces.
>
> Changing the DT representation at this stage is perhaps *possible*
> without creating a bunch of pain (I'd have to audit a bunch of things to
> see if we have GA shipping systems with this functionality for instance,
> and then evaluate the impact to partners and our various labs) which is
> a lot of work I don't particularly want to do and is well below urgent
> item 248 on my TODO list, especially for what seems to be largely a
> cosmetic suggestion?
>
> That being said, more and better review of things we're putting in the
> device tree in firmware is probably a good thing. After all, once we
> release we do kind of have to live with it essentially forever. If
> people are able to aid in that kind of code review, I'd be most welcome
> to hear it.
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-leds" in
> the body of a message to majordomo@vger•kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>

As we agreed with Ben - DT bindings are platform specific and they will
have to be acked by powerpc maintainers. I have only DT related
experience from ARM based platforms, but it seems not to be applicable
to powerpc.

-- 
Best Regards,
Jacek Anaszewski

  reply	other threads:[~2015-04-28  9:10 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-22 21:45 [PATCH v2 2/2] leds/powernv: Add driver for PowerNV platform Jacek Anaszewski
2015-04-23  5:25 ` Vasant Hegde
2015-04-23 14:13   ` Jacek Anaszewski
2015-04-24  4:18     ` Stewart Smith
2015-04-24 10:16       ` Jacek Anaszewski
2015-04-28  6:59         ` Stewart Smith
2015-04-28  9:10           ` Jacek Anaszewski [this message]
2015-04-24  5:30     ` Vasant Hegde
2015-04-24 10:15       ` Jacek Anaszewski
2015-04-26 22:08         ` Benjamin Herrenschmidt
2015-04-27 11:15         ` Jacek Anaszewski
2015-04-26 22:07     ` Benjamin Herrenschmidt
2015-04-27  7:24       ` Jacek Anaszewski
2015-04-27  9:53         ` Benjamin Herrenschmidt
2015-04-27 11:15           ` Jacek Anaszewski
2015-04-27 13:47             ` Vasant Hegde
2015-04-28 11:06               ` Vasant Hegde
  -- strict thread matches above, loose matches on Subject: below --
2015-03-20 11:02 [PATCH v2 0/2] LED interface " Vasant Hegde
2015-03-20 11:04 ` [PATCH v2 2/2] leds/powernv: Add driver " Vasant Hegde
2015-03-25  5:21   ` Benjamin Herrenschmidt
2015-04-14  5:40     ` Vasant Hegde
2015-04-14 15:20   ` Jacek Anaszewski
2015-04-15  6:26     ` Vasant Hegde
     [not found]       ` <552E2480.9060102@samsung.com>
2015-04-15 10:15         ` Vasant Hegde
     [not found]           ` <552E63D2.4070209@samsung.com>
2015-04-16  6:52             ` Vasant Hegde
2015-04-16  8:51               ` Jacek Anaszewski
2015-04-16 10:26                 ` Vasant Hegde
2015-04-16 11:34                   ` Jacek Anaszewski
2015-04-20  7:29                     ` Jacek Anaszewski
2015-04-20 11:45           ` Jacek Anaszewski
2015-04-20 12:34             ` Vasant Hegde
2015-04-20 15:20               ` Jacek Anaszewski
2015-04-20 15:53                 ` Vasant Hegde
2015-04-15 18:50     ` Stewart Smith
2015-04-16  5:07       ` Vasant Hegde
2015-04-21 23:03         ` Stewart Smith

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=553F4E70.3020604@samsung.com \
    --to=j.anaszewski@samsung$(echo .)com \
    --cc=cooloney@gmail$(echo .)com \
    --cc=j.anaszewski81@gmail$(echo .)com \
    --cc=khandual@linux$(echo .)vnet.ibm.com \
    --cc=linux-leds@vger$(echo .)kernel.org \
    --cc=linuxppc-dev@lists$(echo .)ozlabs.org \
    --cc=rpurdie@rpsys$(echo .)net \
    --cc=stewart@linux$(echo .)vnet.ibm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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