devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: santosh shilimkar <santosh.shilimkar-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
To: Franklin S Cooper Jr <fcooper-l0cyMroinI0@public.gmane.org>,
	nm-l0cyMroinI0@public.gmane.org,
	devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
	ssantosh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org
Subject: Re: [PATCH 0/3] Add initial support for TI's K2G SOC
Date: Tue, 2 Feb 2016 15:59:36 -0800	[thread overview]
Message-ID: <56B142E8.4090301@oracle.com> (raw)
In-Reply-To: <1454455517-7360-1-git-send-email-fcooper-l0cyMroinI0@public.gmane.org>

On 2/2/2016 3:25 PM, Franklin S Cooper Jr wrote:
> This patchset provides initial support for K2G the latest addition to Texas
> Instruments Keystone 2 product family. These patches are built on top of
> the latest 4.5-rc2 commit.
>
> K2G is a A15 + C66x DSP processor built to address the needs of industrial
> communication and control, automotive and performance audio applications.
>
> Supported peripherals include MMC,USB2.0,DCAN,DSS,McASP and PCIe SS.
>
> The technical reference manual for K2G can be found here:
> http://www.ti.com/lit/ug/spruhy8/spruhy8.pdf
>
> This patchset provides the ability to boot K2G's general purpose evm using
> a ramfs filesystem.
>
> Additional patches will follow this series that will add support for new
> drivers that will enable additional peripherals and features
>
> K2G Bootlog on 4.5-rc2:
> http://pastebin.ubuntu.com/14861580/
>
Quick scan of the series looks fine to me. I will wait for others to
come back for a week or so and then add to 4.6 queue.

Thanks for the series !!

Reagrds,
Santosh
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2016-02-02 23:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-02 23:25 [PATCH 0/3] Add initial support for TI's K2G SOC Franklin S Cooper Jr
     [not found] ` <1454455517-7360-1-git-send-email-fcooper-l0cyMroinI0@public.gmane.org>
2016-02-02 23:25   ` [PATCH 1/3] ARM: keystone: Create new binding for K2G SoC Franklin S Cooper Jr
     [not found]     ` <1454455517-7360-2-git-send-email-fcooper-l0cyMroinI0@public.gmane.org>
2016-02-08 16:11       ` Rob Herring
2016-02-02 23:25   ` [PATCH 2/3] ARM: dts: keystone: Add Initial DT support for TI K2G SoC family Franklin S Cooper Jr
2016-02-02 23:25   ` [PATCH 3/3] ARM: dts: keystone: Add minimum support for K2G evm Franklin S Cooper Jr
2016-02-02 23:59   ` santosh shilimkar [this message]
     [not found]     ` <56B142E8.4090301-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2016-02-05 18:42       ` [PATCH 0/3] Add initial support for TI's K2G SOC santosh shilimkar

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=56B142E8.4090301@oracle.com \
    --to=santosh.shilimkar-qhclzuegtsvqt0dzr+alfa@public.gmane.org \
    --cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=fcooper-l0cyMroinI0@public.gmane.org \
    --cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
    --cc=nm-l0cyMroinI0@public.gmane.org \
    --cc=ssantosh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.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;
as well as URLs for NNTP newsgroup(s).