linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tero Kristo <t-kristo@ti.com>
To: linux-omap@vger.kernel.org, tony@atomide.com, paul@pwsan.com
Cc: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/5] ARM: OMAP2+: hwmod/clk related fixes
Date: Thu, 30 Jun 2016 16:14:58 +0300	[thread overview]
Message-ID: <1467292503-4376-1-git-send-email-t-kristo@ti.com> (raw)

Hi,

These patches have been split out of the series here:

http://www.spinics.net/lists/arm-kernel/msg510985.html

Basically a few fixes to the hwmod / clk related functionality
under mach-omap2.

This split up series has been boot tested on following platforms:

  : Board           : Boot WRN version                 
 1: am335x-evm      : PASS   0 4.7.0-rc1-00005-g8238af6
 2: am335x-evmsk    : PASS   0 4.7.0-rc1-00005-g8238af6
 3: am3517-evm      : PASS   1 4.7.0-rc1-00005-g8238af6
 4: am37x-evm       : PASS   0 4.7.0-rc1-00005-g8238af6
 5: am437x-sk       : PASS   0 4.7.0-rc1-00005-g8238af6
 6: am43x-epos-evm  : PASS   0 4.7.0-rc1-00005-g8238af6
 7: am437x-gp-evm   : PASS   0 4.7.0-rc1-00005-g8238af6
 8: am57xx-evm      : PASS   3 4.7.0-rc1-00005-g8238af6
 9: omap3-beagle-xm : PASS   0 4.7.0-rc1-00005-g8238af6
10: omap3-beagle    : PASS   0 4.7.0-rc1-00005-g8238af6
11: am335x-boneblack: PASS   0 4.7.0-rc1-00005-g8238af6
12: am335x-bone     : PASS   0 4.7.0-rc1-00005-g8238af6
13: craneboard      : PASS   1 4.7.0-rc1-00005-g8238af6
14: dra72x-evm      : FAIL   3 4.7.0-rc1-00005-g8238af6
15: dra7xx-evm      : PASS   3 4.7.0-rc1-00005-g8238af6
16: ldp3430         : FAIL   0                         
17: omap3-n900      : PASS   0 4.7.0-rc1-00005-g8238af6
18: omap5-uevm      : PASS   0 4.7.0-rc1-00005-g8238af6
19: omap4-panda-es  : PASS   0 4.7.0-rc1-00005-g8238af6
20: omap4-panda     : PASS   0 4.7.0-rc1-00005-g8238af6
21: omap2430-sdp    : PASS   0 4.7.0-rc1-00005-g8238af6
22: omap3430-sdp    : PASS   0 4.7.0-rc1-00005-g8238af6
23: omap4-sdp-es23plus: PASS   0 4.7.0-rc1-00005-g8238af6
TOTAL = 23 boards, Booted Boards = 21, No Boot boards = 2

Does not generate any new boot warnings, or other visible side effects.

The two failing boards seem to be broken in the farm in general, as they
fail with any kernel.

Patches also available here:

tree: https://github.com/t-kristo/linux-pm.git
branch: 4.7-rc1-hwmod-fixes

-Tero

             reply	other threads:[~2016-06-30 13:14 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-30 13:14 Tero Kristo [this message]
2016-06-30 13:14 ` [PATCH 1/5] ARM: OMAP2+: omap_device: create clock alias purely from DT data Tero Kristo
2016-06-30 13:15 ` [PATCH 2/5] ARM: OMAP2+: hwmod: fetch main_clk based on hwmod name Tero Kristo
2016-07-04  6:54   ` Tony Lindgren
2016-07-04  9:17     ` Tero Kristo
2016-07-04 11:11     ` [PATCHv2 " Tero Kristo
2016-07-04 14:32       ` Tony Lindgren
2016-06-30 13:15 ` [PATCH 3/5] ARM: OMAP2+: timer: change order of hwmod data handling Tero Kristo
2016-06-30 13:15 ` [PATCH 4/5] ARM: OMAP2+: clockdomain: add usecounting support to autoidle APIs Tero Kristo
2016-06-30 13:15 ` [PATCH 5/5] ARM: AM33xx: fix module_wait_ready without clkctrl register 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=1467292503-4376-1-git-send-email-t-kristo@ti.com \
    --to=t-kristo@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=paul@pwsan.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 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).