From: Stephen Boyd <sboyd@kernel.org>
To: Tero Kristo <t-kristo@ti.com>,
linux-clk@vger.kernel.org, mturquette@baylibre.com
Cc: linux-omap@vger.kernel.org, tony@atomide.com, s-anna@ti.com
Subject: Re: [PATCH 0/3] clk: ti: couple of fixes towards 5.4
Date: Wed, 07 Aug 2019 15:25:13 -0700 [thread overview]
Message-ID: <20190807222514.059A0214C6@mail.kernel.org> (raw)
In-Reply-To: <1565183079-27798-1-git-send-email-t-kristo@ti.com>
Quoting Tero Kristo (2019-08-07 06:04:36)
> Hi,
>
> Here are some TI clock fixes which can be queued for 5.4. These are
> needed for getting remoteproc functionality working properly, as these
> depend on reset handling also and timing out with clocks is bad for
> them. The timer clock alias fix is needed for the same, as remoteprocs
> depend on certain HW timers for their functionality.
>
Looks ok to me. Are you going to add Fixes tags to any? Should I expect
a PR or you want me to pick them up directly?
next prev parent reply other threads:[~2019-08-07 22:25 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-07 13:04 [PATCH 0/3] clk: ti: couple of fixes towards 5.4 Tero Kristo
2019-08-07 13:04 ` [PATCH 1/3] clk: ti: clkctrl: add support for polling clock status for enable only Tero Kristo
2019-08-07 22:43 ` Suman Anna
2019-08-19 9:13 ` Tero Kristo
2019-08-19 21:07 ` Suman Anna
2019-08-20 8:17 ` Tero Kristo
2019-08-07 13:04 ` [PATCH 2/3] clk: ti: dra7xx: remove idlest polling from disabling ipu/dsp clocks Tero Kristo
2019-08-07 22:50 ` Suman Anna
2019-08-19 9:19 ` Tero Kristo
2019-08-19 21:11 ` Suman Anna
2019-08-07 13:04 ` [PATCH 3/3] clk: ti: dra7xx: add timer_sys_ck clock alias Tero Kristo
2019-08-07 22:56 ` Suman Anna
2019-08-19 21:14 ` Suman Anna
2019-08-23 18:16 ` Tero Kristo
2019-08-26 22:26 ` Suman Anna
2019-08-27 5:57 ` Tero Kristo
2019-08-07 22:25 ` Stephen Boyd [this message]
2019-08-19 9:17 ` [PATCH 0/3] clk: ti: couple of fixes towards 5.4 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=20190807222514.059A0214C6@mail.kernel.org \
--to=sboyd@kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=s-anna@ti.com \
--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 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.