All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tero Kristo <t-kristo@ti.com>
To: <linux-clk@vger.kernel.org>, <linux-omap@vger.kernel.org>,
	<sboyd@kernel.org>, <mturquette@baylibre.com>
Cc: <tony@atomide.com>
Subject: [PATCH 0/6] clk: ti: a few OMAP clock fixes
Date: Thu, 4 Apr 2019 11:11:01 +0300	[thread overview]
Message-ID: <1554365467-1325-1-git-send-email-t-kristo@ti.com> (raw)

Hi,

These patches fix a few issues with OMAP clock driver suite. They could
be merged as fixes, or just be postponed until next merge window. Depends
on the preference from Stephen / Tony really.

Fixes done:
- dropped CLK_IS_BASIC from mach-omap2 (Tony, can you ack patch #2? Depends
  on patch #1 so can't be merged standalone.)
- prevent non-existent clocks registering on both the cutdown SoCs (dra71)
  and HS devices

-Tero

--
Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki. Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki

             reply	other threads:[~2019-04-04  8:12 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-04  8:11 Tero Kristo [this message]
2019-04-04  8:11 ` [PATCH 1/6] clk: ti: export the omap2_clk_is_hw_omap call Tero Kristo
2019-04-25 18:15   ` Stephen Boyd
2019-04-04  8:11 ` [PATCH 2/6] ARM: omap2+: hwmod: drop CLK_IS_BASIC flag usage Tero Kristo
2019-04-04 14:06   ` Tony Lindgren
2019-04-25 18:15   ` Stephen Boyd
2019-04-04  8:11 ` [PATCH 3/6] clk: ti: dra7x: prevent non-existing clkctrl clocks from registering Tero Kristo
2019-04-25 18:15   ` Stephen Boyd
2019-04-04  8:11 ` [PATCH 4/6] clk: ti: dra7: disable the RNG and TIMER12 clkctrl clocks on HS devices Tero Kristo
2019-04-25 18:15   ` Stephen Boyd
2019-04-04  8:11 ` [PATCH 5/6] clk: ti: am33xx: drop idlest polling from gfx clkctrl clock Tero Kristo
2019-04-04 14:06   ` Tony Lindgren
2019-04-08  5:45     ` Tero Kristo
2019-04-25 17:51       ` Stephen Boyd
2019-04-25 17:56         ` Tony Lindgren
2019-04-04  8:11 ` [PATCH 6/6] clk: ti: am43xx: " 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=1554365467-1325-1-git-send-email-t-kristo@ti.com \
    --to=t-kristo@ti.com \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=sboyd@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 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.