From: Sekhar Nori <nsekhar@ti.com>
To: David Lechner <david@lechnology.com>, Suman Anna <s-anna@ti.com>
Cc: Bartosz Golaszewski <bgolaszewski@baylibre.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ARM: davinci_all_defconfig: enable CMA options
Date: Tue, 26 Sep 2017 15:26:19 +0530 [thread overview]
Message-ID: <b9cbe510-112e-410c-33e1-4e4749b5fcfa@ti.com> (raw)
In-Reply-To: <ba1bb5c3-a524-8ee1-6730-e61047dec440@lechnology.com>
Hi David,
On Friday 22 September 2017 10:13 PM, David Lechner wrote:
> On 09/22/2017 11:24 AM, Suman Anna wrote:
>> Hi Sekhar,
>>
>>>
>>> On Thursday 21 September 2017 08:41 PM, Suman Anna wrote:
>>>> 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.
>>>
>>> But the errors will show up only on DA850 LCDK where we have enabled the
>>> DSP by default in DT because its an important usecase there. I think it
>>> is important for users to see those errors.
>>> (besides the usual benefits of having the module enabled to catch build
>>> and runtime issues easily).
>>
>> Yeah, DSP node is enabled only for DA850 LCDK among the DT-supported
>> boards, but I believe there are boards still using legacy boot, and it
>> shows up on those platforms as well. FYI, we do not have any rpmsg
>> drivers other than the kernel sample to make real usage of a booted
>> remoteproc. Anycase, if you still prefer this to be added, I don't mind.
>>
>> regards
>> Suman
>>
>
> I am interested in using remoteproc on LEGO MINDSTORMS EV3 to implement
> I2C and UART in the PRU.
Do note that the remoteproc driver being discussed here is the DSP
remoteproc driver. TI releases have a remoteproc driver that talks to
PRUSS[1], but that has not been used to talk to PRUSS on OMAP-L138. And
AFAIK, there is no one working towards that in TI as well.
Thanks,
Sekhar
[1]
http://git.ti.com/cgit/cgit.cgi/ti-linux-kernel/ti-linux-kernel.git/tree/drivers/remoteproc/pru_rproc.c?h=ti-linux-4.9.y
next prev parent reply other threads:[~2017-09-26 9:57 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
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 [this message]
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=b9cbe510-112e-410c-33e1-4e4749b5fcfa@ti.com \
--to=nsekhar@ti.com \
--cc=bgolaszewski@baylibre.com \
--cc=david@lechnology.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=s-anna@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®