From: Keerthy <j-keerthy-l0cyMroinI0@public.gmane.org>
To: Tony Lindgren <tony-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
Cc: devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
t-kristo-l0cyMroinI0@public.gmane.org,
robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org
Subject: Re: [PATCH] ARM: dts: DRA76-EVM: Set powerhold property for tps65917
Date: Thu, 30 Nov 2017 09:44:22 +0530 [thread overview]
Message-ID: <84542ce8-6e36-59a6-224c-b51c05d9866e@ti.com> (raw)
In-Reply-To: <20171026141707.GE21504-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
On Thursday 26 October 2017 07:47 PM, Tony Lindgren wrote:
> * Keerthy <j-keerthy-l0cyMroinI0@public.gmane.org> [171025 23:31]:
>>
>>
>> On Wednesday 25 October 2017 10:22 PM, Tony Lindgren wrote:
>>> * Keerthy <j-keerthy-l0cyMroinI0@public.gmane.org> [171024 01:46]:
>>>> Set powerhold property for tps65917
>>>>
>>>> Signed-off-by: Keerthy <j-keerthy-l0cyMroinI0@public.gmane.org>
>>>
>>> Is this safe to merge separately before the driver changes?
>>
>> This needs to wait till [1] is merged. I should have mentioned this.
>>
>> I will ping on this as soon as the dependent patch is merged.
>
> OK thanks will untag this patch from my inbox for now then.
Tony,
The dependent driver patch [1] is pulled by Lee Jones.
So this patch is okay to be applied.
[1] https://patchwork.kernel.org/patch/10023635/
- Keerthy
>
> Regards,
>
> Tony
>
>> [1] https://marc.info/?l=linux-omap&m=150883331614239&w=2
>>
>> Thanks,
>> Keerthy
>>
>>>
>>> Regards,
>>>
>>> Tony
>>>
>>>> ---
>>>> arch/arm/boot/dts/dra76-evm.dts | 1 +
>>>> 1 file changed, 1 insertion(+)
>>>>
>>>> diff --git a/arch/arm/boot/dts/dra76-evm.dts b/arch/arm/boot/dts/dra76-evm.dts
>>>> index b024a65..f64aab4 100644
>>>> --- a/arch/arm/boot/dts/dra76-evm.dts
>>>> +++ b/arch/arm/boot/dts/dra76-evm.dts
>>>> @@ -148,6 +148,7 @@
>>>> compatible = "ti,tps65917";
>>>> reg = <0x58>;
>>>> ti,system-power-controller;
>>>> + ti,palmas-override-powerhold;
>>>> interrupt-controller;
>>>> #interrupt-cells = <2>;
>>>>
>>>> --
>>>> 1.9.1
>>>>
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2017-11-30 4:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-24 8:44 [PATCH] ARM: dts: DRA76-EVM: Set powerhold property for tps65917 Keerthy
[not found] ` <1508834648-28715-1-git-send-email-j-keerthy-l0cyMroinI0@public.gmane.org>
2017-10-25 16:52 ` Tony Lindgren
[not found] ` <20171025165219.GO4394-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
2017-10-26 6:29 ` Keerthy
[not found] ` <30907da7-a80c-4718-dd9a-17cb22669eb5-l0cyMroinI0@public.gmane.org>
2017-10-26 14:17 ` Tony Lindgren
[not found] ` <20171026141707.GE21504-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
2017-11-30 4:14 ` Keerthy [this message]
[not found] ` <84542ce8-6e36-59a6-224c-b51c05d9866e-l0cyMroinI0@public.gmane.org>
2017-12-11 16:43 ` Tony Lindgren
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=84542ce8-6e36-59a6-224c-b51c05d9866e@ti.com \
--to=j-keerthy-l0cymroini0@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=t-kristo-l0cyMroinI0@public.gmane.org \
--cc=tony-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.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;
as well as URLs for NNTP newsgroup(s).