From: Tony Lindgren <tony@atomide.com> To: Tero Kristo <t-kristo@ti.com>, Stephen Boyd <swboyd@chromium.org> Cc: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org Subject: Re: [PATCH 0/5] ARM: dts: omap4+: Add PRM nodes for reset support Date: Thu, 10 Oct 2019 07:31:33 -0700 [thread overview] Message-ID: <20191010143133.GW5610@atomide.com> (raw) In-Reply-To: <20191010082108.15448-1-t-kristo@ti.com> * Tero Kristo <t-kristo@ti.com> [191010 01:21]: > Hi Tony, > > This series adds the OMAP PRM nodes for reset support for am3, am4, > omap4, omap5 and dra7 SoCs. The driver support has been queued up by > Santosh [1]. OK planning on applying these into omap-for-v5.5/prm on top of Santosh's immutable branch. But I'm wondering if we should also have an immutable branch for the clkctrl changes that I can merge in too? Then with the prm driver changes, clkctrl changes and these, we have things working for applying some rstctrl using device patches like the old am335x sgx ti-sysc patch? Regards, Tony > [1] https://patchwork.kernel.org/cover/11179573/
WARNING: multiple messages have this Message-ID (diff)
From: Tony Lindgren <tony@atomide.com> To: Tero Kristo <t-kristo@ti.com>, Stephen Boyd <swboyd@chromium.org> Cc: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org Subject: Re: [PATCH 0/5] ARM: dts: omap4+: Add PRM nodes for reset support Date: Thu, 10 Oct 2019 07:31:33 -0700 [thread overview] Message-ID: <20191010143133.GW5610@atomide.com> (raw) In-Reply-To: <20191010082108.15448-1-t-kristo@ti.com> * Tero Kristo <t-kristo@ti.com> [191010 01:21]: > Hi Tony, > > This series adds the OMAP PRM nodes for reset support for am3, am4, > omap4, omap5 and dra7 SoCs. The driver support has been queued up by > Santosh [1]. OK planning on applying these into omap-for-v5.5/prm on top of Santosh's immutable branch. But I'm wondering if we should also have an immutable branch for the clkctrl changes that I can merge in too? Then with the prm driver changes, clkctrl changes and these, we have things working for applying some rstctrl using device patches like the old am335x sgx ti-sysc patch? Regards, Tony > [1] https://patchwork.kernel.org/cover/11179573/ _______________________________________________ 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-10-10 14:31 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-10-10 8:21 [PATCH 0/5] ARM: dts: omap4+: Add PRM nodes for reset support Tero Kristo 2019-10-10 8:21 ` Tero Kristo 2019-10-10 8:21 ` [PATCH 1/5] ARM: dts: dra7: add PRM nodes Tero Kristo 2019-10-10 8:21 ` Tero Kristo 2019-10-10 8:21 ` [PATCH 2/5] ARM: dts: omap4: " Tero Kristo 2019-10-10 8:21 ` Tero Kristo 2019-10-10 8:21 ` [PATCH 3/5] ARM: dts: am33xx: Add PRM data Tero Kristo 2019-10-10 8:21 ` Tero Kristo 2019-10-10 8:21 ` [PATCH 4/5] ARM: dts: am43xx: " Tero Kristo 2019-10-10 8:21 ` Tero Kristo 2019-10-10 8:21 ` [PATCH 5/5] ARM: dts: omap5: " Tero Kristo 2019-10-10 8:21 ` Tero Kristo 2019-10-10 14:31 ` Tony Lindgren [this message] 2019-10-10 14:31 ` [PATCH 0/5] ARM: dts: omap4+: Add PRM nodes for reset support 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=20191010143133.GW5610@atomide.com \ --to=tony@atomide.com \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-omap@vger.kernel.org \ --cc=swboyd@chromium.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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.