From: santosh.shilimkar@oracle.com (Santosh Shilimkar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 4/4] firmware: ti_sci: Add helper apis to mange resources
Date: Wed, 10 Oct 2018 10:00:01 -0700 [thread overview]
Message-ID: <0d559577-00a6-27d2-cb9a-64b162f58691@oracle.com> (raw)
In-Reply-To: <20181006163432.z5skpgfm7oqoiuaf@akan>
10/6/2018 9:34 AM, Nishanth Menon wrote:
> On 13:08-20181006, Lokesh Vutla wrote:
>>
>>
>> On 10/6/2018 1:44 AM, Nishanth Menon wrote:
>>> NAK. Where is the binding for this? What is this decoding? Please don't
>>> decode binding without having an official binding.
>>
>> This is a helper library for the clients to get resource range from DT
>> and is not compulsory for clients to use this library to managing these
>> resources. So in my understanding DT bindings should go into the client
>> DT doc as posted here[1]. If you really insist I can add these details
>
> Thanks.. Please get the binding approved before we discuss
> implementation in driver.
>
Absolutely. Infact there is no rush to post driver patches before the
DT binding are approved. Lets stick to the usual flow.
Regards,
Santosh
prev parent reply other threads:[~2018-10-10 17:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-05 14:30 [PATCH 0/4] firmware: ti_sci: Introduce RM support Lokesh Vutla
2018-10-05 14:30 ` [PATCH 1/4] firmware: ti_sci: Add support to get TISCI handle using of_phandle Lokesh Vutla
2018-10-05 14:30 ` [PATCH 2/4] firmware: ti_sci: Add support for RM core ops Lokesh Vutla
2018-10-05 14:30 ` [PATCH 3/4] firmware: ti_sci: Add support for IRQ management Lokesh Vutla
2018-10-05 14:30 ` [PATCH 4/4] firmware: ti_sci: Add helper apis to mange resources Lokesh Vutla
2018-10-05 20:14 ` Nishanth Menon
2018-10-06 7:38 ` Lokesh Vutla
2018-10-06 16:34 ` Nishanth Menon
2018-10-10 17:00 ` Santosh Shilimkar [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=0d559577-00a6-27d2-cb9a-64b162f58691@oracle.com \
--to=santosh.shilimkar@oracle.com \
--cc=linux-arm-kernel@lists.infradead.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