From: Kishon Vijay Abraham I <kishon@ti.com>
To: Peter Robinson <pbrobinson@gmail.com>, Tony Lindgren <tony@atomide.com>
Cc: Grygorii Strashko <grygorii.strashko@ti.com>,
mark.rutland@arm.com, devicetree@vger.kernel.org,
linux@arm.linux.org.uk, pawel.moll@arm.com,
ijc+devicetree@hellion.org.uk, nsekhar@ti.com,
linux-kernel@vger.kernel.org, t-kristo@ti.com,
robh+dt@kernel.org, bcousson@baylibre.com, galak@codeaurora.org,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/4] omap: Fix broken pbias device creation
Date: Fri, 7 Aug 2015 19:55:43 +0530 [thread overview]
Message-ID: <55C4BFE7.2070302@ti.com> (raw)
In-Reply-To: <CALeDE9OBjESdkXhkAEVj1L-XKJ1yoFg8rkHvcJ_Uj_RXOC-yUQ@mail.gmail.com>
Hi Peter,
On Friday 07 August 2015 05:18 PM, Peter Robinson wrote:
> On Wed, Aug 5, 2015 at 11:00 AM, Tony Lindgren <tony@atomide.com> wrote:
>> * Grygorii Strashko <grygorii.strashko@ti.com> [150729 02:01]:
>>> On 07/27/2015 03:16 PM, Kishon Vijay Abraham I wrote:
>>>> pbias device creation got broken once SCM cleanup got merged.
>>>> This patch series re-enables device creation by adding
>>>> "simple-bus" in the compatible property of the syscon
>>>> dt node.
>>>>
>>>> validated this series in DRA72, OMAP4 PANDA and OMAP5 UEVM
>>>> boards.
>>>>
>>>> Kishon Vijay Abraham I (4):
>>>> ARM: dts: omap24xx: Fix broken pbias device creation
>>>> ARM: dts: OMAP4: Fix broken pbias device creation
>>>> ARM: dts: OMAP5: Fix broken pbias device creation
>>>> ARM: dts: dra7: Fix broken pbias device creation
>>>>
>>>> arch/arm/boot/dts/dra7.dtsi | 2 +-
>>>> arch/arm/boot/dts/omap2430.dtsi | 3 ++-
>>>> arch/arm/boot/dts/omap4.dtsi | 3 ++-
>>>> arch/arm/boot/dts/omap5.dtsi | 3 ++-
>>>> 4 files changed, 7 insertions(+), 4 deletions(-)
>>>>
>>>
>>> For dra7-evm:
>>> Tested-by: Grygorii Strashko <grygorii.strashko@ti.com>
>>
>> Applying all into omap-for-v4.2fixes-v2 thanks.
>
> Do we need the same for am33xx.dtsi too given commit e3bc5358e097 ?
PBIAS is not present in am33xx.
Thanks
Kishon
prev parent reply other threads:[~2015-08-07 14:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-27 12:16 [PATCH 0/4] omap: Fix broken pbias device creation Kishon Vijay Abraham I
2015-07-27 12:16 ` [PATCH 2/4] ARM: dts: OMAP4: " Kishon Vijay Abraham I
2015-07-27 12:16 ` [PATCH 3/4] ARM: dts: OMAP5: " Kishon Vijay Abraham I
2015-07-27 12:16 ` [PATCH 4/4] ARM: dts: dra7: " Kishon Vijay Abraham I
[not found] ` <1437999401-3519-1-git-send-email-kishon-l0cyMroinI0@public.gmane.org>
2015-07-27 12:16 ` [RFT PATCH 1/4] ARM: dts: omap24xx: " Kishon Vijay Abraham I
2015-07-29 8:57 ` [PATCH 0/4] omap: " Grygorii Strashko
2015-08-05 10:00 ` Tony Lindgren
[not found] ` <20150805100009.GY16878-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
2015-08-07 11:48 ` Peter Robinson
2015-08-07 14:25 ` Kishon Vijay Abraham I [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=55C4BFE7.2070302@ti.com \
--to=kishon@ti.com \
--cc=bcousson@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=grygorii.strashko@ti.com \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mark.rutland@arm.com \
--cc=nsekhar@ti.com \
--cc=pawel.moll@arm.com \
--cc=pbrobinson@gmail.com \
--cc=robh+dt@kernel.org \
--cc=t-kristo@ti.com \
--cc=tony@atomide.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).