From: Tony Lindgren <tony@atomide.com>
To: Paul Walmsley <paul@pwsan.com>
Cc: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [GIT PULL] ARM: OMAP2+: second set of hwmod changes for v4.6
Date: Tue, 1 Mar 2016 10:00:47 -0800 [thread overview]
Message-ID: <20160301180046.GY13417@atomide.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1603010958120.14948@utopia.booyaka.com>
* Paul Walmsley <paul@pwsan.com> [160301 01:59]:
> Hi Tony
>
> The following changes since commit 8fe097a3d99e22355fb8e3bcee59542bf3f46b2d:
>
> ARM: DRA7: hwmod: Add reset data for PCIe (2016-02-09 02:18: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.6/omap-hwmod-b
>
> for you to fetch changes up to 34b4182ce5fd284bff38764f8e73e2160b49d8e9:
>
> ARM: DRA7: hwmod: Add data for eDMA tpcc, tptc0, tptc1 (2016-03-01 01:55:59 -0700)
>
> ----------------------------------------------------------------
> ARM: OMAP2+: second set of hwmod changes for v4.6
>
> These patches add RTC support for the AM43xx, and add support for
> the DRA7xx eDMA controller's TPCC, TPTC0, and TPTC1 IP blocks.
> Also included is a workaround for PRCM hardreset control of the DRA7xx
> PCIe subsystem.
>
> Note that I do not have a DRA7xx board, and therefore cannot
> test any patches for that SoC family.
>
> Basic build, boot, and PM test logs can be found here:
>
> http://www.pwsan.com/omap/testlogs/omap-hwmod-b-for-v4.6/20160301021258/
Thanks pulling into omap-for-v4.6/soc.
Regards,
Tony
prev parent reply other threads:[~2016-03-01 18:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-01 9:58 [GIT PULL] ARM: OMAP2+: second set of hwmod changes for v4.6 Paul Walmsley
2016-03-01 18:00 ` 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=20160301180046.GY13417@atomide.com \
--to=tony@atomide.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.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).