From: Tero Kristo <t-kristo@ti.com>
To: <linux-omap@vger.kernel.org>, <tony@atomide.com>
Cc: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 00/10] ARM: dts: omap changes for IOMMU / reset support
Date: Wed, 28 Aug 2019 10:56:34 +0300 [thread overview]
Message-ID: <20190828075644.4493-1-t-kristo@ti.com> (raw)
Hi,
This series adds reset nodes for OMAP4+ family of SoCs, and fixes the
IOMMUs to support these also.
This series depends on the earlier posted clock series [1], PRM support
series [2], and the pdata quirks [3] and [4].
-Tero
[1] https://marc.info/?l=linux-clk&m=156697558331203&w=2
[2] https://marc.info/?l=linux-omap&m=156697680731569&w=2
[3] https://marc.info/?l=linux-omap&m=156517109506492&w=2
[4] https://marc.info/?l=linux-omap&m=156697839332083
--
Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki. Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2019-08-28 7:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-28 7:56 Tero Kristo [this message]
2019-08-28 7:56 ` [PATCH 01/10] ARM: dts: omap5: add IVA clkctrl nodes Tero Kristo
2019-08-28 7:56 ` [PATCH 02/10] ARM: dts: dra7: add PRM nodes Tero Kristo
2019-08-28 7:56 ` [PATCH 03/10] ARM: dts: omap4: " Tero Kristo
2019-08-28 7:56 ` [PATCH 04/10] ARM: dts: am33xx: Add PRM data Tero Kristo
2019-08-28 7:56 ` [PATCH 05/10] ARM: dts: am43xx: " Tero Kristo
2019-08-28 7:56 ` [PATCH 06/10] ARM: dts: omap5: " Tero Kristo
2019-08-28 7:56 ` [PATCH 07/10] ARM: dts: dra7: convert IOMMUs to use ti-sysc Tero Kristo
2019-08-28 7:56 ` [PATCH 08/10] ARM: dts: dra74x: " Tero Kristo
2019-08-28 7:56 ` [PATCH 09/10] ARM: dts: omap4: " Tero Kristo
2019-08-28 7:56 ` [PATCH 10/10] ARM: dts: omap5: " Tero Kristo
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=20190828075644.4493-1-t-kristo@ti.com \
--to=t-kristo@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--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).