public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: tony@atomide•com (Tony Lindgren)
To: linux-arm-kernel@lists•infradead.org
Subject: [GIT PULL] ARM: OMAP2+: PRCM and hwmod changes for v4.3
Date: Thu, 23 Jul 2015 21:15:52 -0700	[thread overview]
Message-ID: <20150724041552.GE16878@atomide.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1507231456540.29543@utopia.booyaka.com>

* Paul Walmsley <paul@pwsan•com> [150723 08:01]:
> Hi Tony,
> 
> The following changes since commit d770e558e21961ad6cfdf0ff7df0eb5d7d4f0754:
> 
>   Linux 4.2-rc1 (2015-07-05 11:01:52 -0700)
> 
> are available in the git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/pjw/omap-pending.git tags/for-v4.3/omap-hwmod-prcm-a
> 
> for you to fetch changes up to 3b86616e3058462c340710dc7a5ac34ec8453944:
> 
>   Merge branch 'prcm-a-for-v4.3' into hwmod-prcm-for-v4.3 (2015-07-23 08:49:57 -0600)
> 
> ----------------------------------------------------------------
> ARM: OMAP2+: PRCM and hwmod changes for v4.3
> 
> This series adds:
> 
> - I/O wakeup support for AM43xx
> - register lock and unlock support to the hwmod code (needed for the RTC
>   IP blocks on some chips)
> - several fixes for sparse warnings and an unnecessary null pointer test
> - a DRA7xx clockdomain configuration workaround, to deal with some hardware
>   bugs
> 
> Basic build, boot, and PM tests are here:
> 
> http://www.pwsan.com/omap/testlogs/hwmod-prcm-for-v4.3/20150723080012/
> 
> Since I do not have an AM43xx or DRA7xx device, I can't test on those
> platforms.

Thanks pulling into omap-for-v4.3/soc.

Regards,

Tony

      reply	other threads:[~2015-07-24  4:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-23 14:58 [GIT PULL] ARM: OMAP2+: PRCM and hwmod changes for v4.3 Paul Walmsley
2015-07-24  4:15 ` Tony Lindgren [this message]

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=20150724041552.GE16878@atomide.com \
    --to=tony@atomide$(echo .)com \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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