public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 2/2] omap changes to make dm816x usable
Date: Mon, 26 Jan 2015 20:30:33 -0800	[thread overview]
Message-ID: <20150127043033.GK22154@quad.lixom.net> (raw)
In-Reply-To: <54c6ad94.8182440a.13ff.1604SMTPIN_ADDED_BROKEN@mx.google.com>

On Mon, Jan 26, 2015 at 01:08:19PM -0800, Tony Lindgren wrote:
> The following changes since commit 13efcb188984f69e1f97b4d9e7d3663fb782946f:
> 
>   ARM: OMAP2+: Disable omap3 PM init for ti81xx (2015-01-14 17:37:16 -0800)
> 
> are available in the git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/omap-for-v3.20/dm816x-data
> 
> for you to fetch changes up to 4d38bd1237f5bb67c3d5d183fc41db4bf4dbfb6b:
> 
>   ARM: OMAP2+: Add dm816x hwmod support (2015-01-26 09:26:32 -0800)
> 
> ----------------------------------------------------------------
> Patches to add necessary SoC related clockdomain and interconnect
> data  to make dm816x boot with basic devices. This finally gets
> dm816x into a usable shape for further work to happen after a few
> years of stalled effort of making this SoC to work with the mainline
> kernel.
> 
> As most of the devices are similar to the other omap variants, we
> get at least serial, MMC, Ethernet, I2C, EDMA, pinctrl, SPI and GPMC
> working for these SoCs with the related device tree changes.

Merged into next/soc.

Thanks,


-Olof

      parent reply	other threads:[~2015-01-27  4:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-26 21:08 [GIT PULL 1/2] omap non-urgent fixes for v3.20, part 2 Tony Lindgren
2015-01-26 21:08 ` [GIT PULL 2/2] omap changes to make dm816x usable Tony Lindgren
     [not found] ` <54c6ad94.8182440a.13ff.1604SMTPIN_ADDED_BROKEN@mx.google.com>
2015-01-27  4:30   ` Olof Johansson [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=20150127043033.GK22154@quad.lixom.net \
    --to=olof@lixom.net \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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