From: "santosh.shilimkar@oracle.com" <santosh.shilimkar@oracle.com>
To: Suman Anna <s-anna@ti.com>, Santosh Shilimkar <ssantosh@kernel.org>
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Sam Nelson <sam.nelson@ti.com>,
"Andrew F. Davis" <afd@ti.com>
Subject: Re: [PATCH 0/3] Add DSP DT nodes on Keystone 66AK2G platforms
Date: Sat, 12 Aug 2017 10:59:33 -0700 [thread overview]
Message-ID: <b4413170-ed35-cf6c-22e2-ce633b8b561c@oracle.com> (raw)
In-Reply-To: <20170810235245.30316-1-s-anna@ti.com>
On 8/10/17 4:52 PM, Suman Anna wrote:
> Hi Santosh,
>
> The following series adds the DT nodes for the DSP device present
> on the Keystone2 66AK2G SoC and enables them on the currently
> supported platforms.
>
> The DTS nodes for the other Keystone2 family of SoCs were posted
> previously [1] and already in your staging branches for 4.14.
> This series adds the equivalent patches for 66AK2G SoCs. K2G uses
> slightly different properties compared to other K2 SoCs. The
> binding update for K2G is in-flight [2] and already acked by Rob.
> So, I am not sure if you need to wait for that patch to show up
> on mainline to avoid checkpatch warnings on these patches due to
> the undocumented compatible on your tree.
>
> Validation done on K2G EVM and K2G ICE boards using ramdisk boot.
> Supported features are the same as the other Keystone 2 platforms.
> Patches are based on your current -next branch [3], so should apply
> fine on your 4.14 keystone_dts branch.
>
Applied !!
prev parent reply other threads:[~2017-08-12 18:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-10 23:52 Suman Anna
2017-08-10 23:52 ` [PATCH 1/3] ARM: dts: keystone-k2g: Add DSP node Suman Anna
2017-08-10 23:52 ` [PATCH 2/3] ARM: dts: keystone-k2g-evm: Add and enable DSP CMA memory pool Suman Anna
2017-08-10 23:52 ` [PATCH 3/3] ARM: dts: keystone-k2g-ice: " Suman Anna
2017-08-12 17:59 ` santosh.shilimkar [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=b4413170-ed35-cf6c-22e2-ce633b8b561c@oracle.com \
--to=santosh.shilimkar@oracle.com \
--cc=afd@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=s-anna@ti.com \
--cc=sam.nelson@ti.com \
--cc=ssantosh@kernel.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
all inboxes | Powered by JetHome®