linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: linux-omap@vger.kernel.org
Cc: Tero Kristo <t-kristo@ti.com>, Paul Walmsley <paul@pwsan.com>,
	linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/7] omap changes to allocate struct omap_hwmod dynamically
Date: Mon, 25 Mar 2019 11:38:12 -0700	[thread overview]
Message-ID: <20190325183819.15400-1-tony@atomide.com> (raw)

Hi all,

With ti-sysc interconnect target module, and clkctrl clock driver,
we can start allocating struct omap_hwmod dynamically from dts and
configure devices at module_init time. Here's a series of changes
to prepare the hwmod code for that.

Note that we also still need related changes to the ti-sysc
interconnect target module driver that I'll post separately.

Regards,

Tony


Tony Lindgren (7):
  ARM: OMAP2+: Fix potentially uninitialized return value for
    _setup_reset()
  ARM: OMAP2+: Make interconnect target module allocation functions
    static
  ARM: OMAP2+: Prepare class allocation for dynamically allocated
    modules
  ARM: OMAP2+: Define _HWMOD_STATE_DEFAULT and use it
  ARM: OMAP2+: Allocate struct omap_hwmod based on dts data
  ARM: OMAP2+: Remove hwmod .rev data and use local SoC checks instead
  ARM: OMAP2+: Handle reset quirks for dynamically allocated modules

 arch/arm/mach-omap2/common.h                  |   9 +
 arch/arm/mach-omap2/i2c.c                     |  11 +-
 arch/arm/mach-omap2/io.c                      |   7 +-
 arch/arm/mach-omap2/omap_hwmod.c              | 200 +++++++++++++++---
 arch/arm/mach-omap2/omap_hwmod.h              |   8 +-
 arch/arm/mach-omap2/omap_hwmod_2420_data.c    |   1 -
 arch/arm/mach-omap2/omap_hwmod_2430_data.c    |   1 -
 .../mach-omap2/omap_hwmod_2xxx_ipblock_data.c |   1 -
 .../omap_hwmod_33xx_43xx_ipblock_data.c       |   2 -
 arch/arm/mach-omap2/omap_hwmod_3xxx_data.c    |   4 -
 arch/arm/mach-omap2/omap_hwmod_44xx_data.c    |   3 -
 arch/arm/mach-omap2/omap_hwmod_54xx_data.c    |   2 -
 arch/arm/mach-omap2/omap_hwmod_7xx_data.c     |   7 +-
 arch/arm/mach-omap2/omap_hwmod_81xx_data.c    |   1 -
 arch/arm/mach-omap2/sr_device.c               |   5 +-
 15 files changed, 198 insertions(+), 64 deletions(-)

-- 
2.21.0

             reply	other threads:[~2019-03-25 18:38 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-25 18:38 Tony Lindgren [this message]
2019-03-25 18:38 ` [PATCH 1/7] ARM: OMAP2+: Fix potentially uninitialized return value for _setup_reset() Tony Lindgren
2019-03-25 18:38 ` [PATCH 2/7] ARM: OMAP2+: Make interconnect target module allocation functions static Tony Lindgren
2019-03-25 18:38 ` [PATCH 3/7] ARM: OMAP2+: Prepare class allocation for dynamically allocated modules Tony Lindgren
2019-03-25 18:38 ` [PATCH 4/7] ARM: OMAP2+: Define _HWMOD_STATE_DEFAULT and use it Tony Lindgren
2019-03-25 18:38 ` [PATCH 5/7] ARM: OMAP2+: Allocate struct omap_hwmod based on dts data Tony Lindgren
2019-03-25 18:38 ` [PATCH 6/7] ARM: OMAP2+: Remove hwmod .rev data and use local SoC checks instead Tony Lindgren
2019-03-25 18:38 ` [PATCH 7/7] ARM: OMAP2+: Handle reset quirks for dynamically allocated modules Tony Lindgren
2019-03-26 15:36   ` Tony Lindgren
2019-03-28  0:28   ` Sebastian Reichel
2019-04-01 14:58     ` 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=20190325183819.15400-1-tony@atomide.com \
    --to=tony@atomide.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=paul@pwsan.com \
    --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).