From: Tony Lindgren <tony@atomide.com>
To: Tero Kristo <t-kristo@ti.com>
Cc: devicetree@vger.kernel.org, linux-omap@vger.kernel.org,
robh+dt@kernel.org, p.zabel@pengutronix.de, ssantosh@kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCHv5 00/10] soc: ti: add OMAP PRM driver (for reset)
Date: Fri, 20 Sep 2019 07:28:49 -0700 [thread overview]
Message-ID: <20190920142849.GS5610@atomide.com> (raw)
In-Reply-To: <20190912113916.20093-1-t-kristo@ti.com>
* Tero Kristo <t-kristo@ti.com> [190912 04:39]:
> Hi,
>
> V5 of the series, re-sent the whole series as one patch was dropped.
> Changes compared to v3/v4:
>
> - removed dependency towards clock driver (patch #5 was completely
> dropped compared to v3/v4)
> - dropped clocks property from dt binding
> - re-added the pdata patch which was accidentally dropped out (it has
> dependency towards this series.)
>
> The new implementation (without clock driver dependency) relies on the
> bus driver to sequence events properly, otherwise some timeouts will
> occur either at clock driver or reset driver end.
With the two updated patches seems like we're done with this
series?
If so, I suggest either Santosh or me sets up an immutable
branch against v5.3 or v5.4-rc1 that we all can merge in.
I will need it for the related dts changes at least.
Regards,
Tony
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-09-20 14:29 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-12 11:39 [PATCHv5 00/10] soc: ti: add OMAP PRM driver (for reset) Tero Kristo
2019-09-12 11:39 ` [PATCHv5 01/10] dt-bindings: omap: add new binding for PRM instances Tero Kristo
2019-09-17 17:48 ` Rob Herring
2019-09-19 12:30 ` [PATCHv6 " Tero Kristo
2019-09-19 19:54 ` Rob Herring
2019-09-20 14:26 ` Tony Lindgren
2019-09-12 11:39 ` [PATCHv5 02/10] soc: ti: add initial PRM driver with reset control support Tero Kristo
2019-09-12 11:39 ` [PATCHv5 03/10] soc: ti: omap-prm: poll for reset complete during de-assert Tero Kristo
2019-09-12 11:39 ` [PATCHv5 04/10] soc: ti: omap-prm: add support for denying idle for reset clockdomain Tero Kristo
2019-09-12 11:39 ` [PATCHv5 05/10] soc: ti: omap-prm: add omap4 PRM data Tero Kristo
2019-09-12 11:39 ` [PATCHv5 06/10] soc: ti: omap-prm: add data for am33xx Tero Kristo
2019-09-12 11:39 ` [PATCHv5 07/10] soc: ti: omap-prm: add dra7 PRM data Tero Kristo
2019-09-12 11:39 ` [PATCHv5 08/10] soc: ti: omap-prm: add am4 " Tero Kristo
2019-09-12 11:39 ` [PATCHv5 09/10] soc: ti: omap-prm: add omap5 " Tero Kristo
2019-09-12 11:39 ` [PATCHv5 10/10] ARM: OMAP2+: pdata-quirks: add PRM data for reset support Tero Kristo
2019-09-12 17:09 ` Tony Lindgren
2019-09-12 20:09 ` Tero Kristo
2019-09-19 12:32 ` [PATCHv6 " Tero Kristo
2019-09-20 14:26 ` Tony Lindgren
2019-09-20 14:28 ` Tony Lindgren [this message]
2019-09-20 19:19 ` [PATCHv5 00/10] soc: ti: add OMAP PRM driver (for reset) santosh.shilimkar
2019-09-23 17:47 ` 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=20190920142849.GS5610@atomide.com \
--to=tony@atomide.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=robh+dt@kernel.org \
--cc=ssantosh@kernel.org \
--cc=t-kristo@ti.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).