mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Suman Anna <s-anna@ti.com>
To: Sekhar Nori <nsekhar@ti.com>
Cc: Bartosz Golaszewski <bgolaszewski@baylibre.com>,
	David Lechner <david@lechnology.com>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ARM: davinci_all_defconfig: enable CMA options
Date: Thu, 21 Sep 2017 10:11:41 -0500	[thread overview]
Message-ID: <52fd708b-8497-8d5d-262b-f78ecf068d87@ti.com> (raw)
In-Reply-To: <758ebb8d-cdf5-4cdc-253b-b1eb8e2f7c61@ti.com>

On 09/21/2017 09:43 AM, Sekhar Nori wrote:
> On Wednesday 20 September 2017 11:31 PM, Suman Anna wrote:
>> Enable the CMA and DMA_CMA Kconfig options by default for
>> Davinci platforms. Davinci remoteproc driver is one of the
>> modules that depends on these options, and this allows the
>> driver to be made visible for selection with menuconfig.
>>
>> Signed-off-by: Suman Anna <s-anna@ti.com>
>> ---
>> Hi Sekhar,
>>
>> Here's the patch that enables CMA as per your request. Patch based
>> on your v4.15/defconfig branch.
> 
> Applied! I guess you will be sending another patch enabling the
> remoteproc driver itself?

Thanks. Well, one always needs a firmware image in their filesystem
without which enabling the driver is meaningless (it would fail). So was
not planning to enable it by default.

regards
Suman

  reply	other threads:[~2017-09-21 15:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-20 18:01 Suman Anna
2017-09-21 14:43 ` Sekhar Nori
2017-09-21 15:11   ` Suman Anna [this message]
2017-09-22  9:12     ` Sekhar Nori
2017-09-22 16:24       ` Suman Anna
2017-09-22 16:43         ` David Lechner
2017-09-26  9:56           ` Sekhar Nori
2017-09-26 16:28             ` David Lechner
2017-09-26  9:50         ` Sekhar Nori

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=52fd708b-8497-8d5d-262b-f78ecf068d87@ti.com \
    --to=s-anna@ti.com \
    --cc=bgolaszewski@baylibre.com \
    --cc=david@lechnology.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nsekhar@ti.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
all inboxes | Powered by JetHome®