mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sekhar Nori <nsekhar@ti.com>
To: Suman Anna <s-anna@ti.com>, Kevin Hilman <khilman@kernel.org>
Cc: <linux-arm-kernel@lists.infradead.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/3] ARM: davinci: da8xx: Create DSP device only when assigned memory
Date: Mon, 22 May 2017 14:49:29 +0530	[thread overview]
Message-ID: <ebf2a3e7-4d21-00a8-f6d7-6461ef3e0ec6@ti.com> (raw)
In-Reply-To: <6c37a43e-78d4-3fa4-21ca-3c94ad83cbe4@ti.com>

On Thursday 18 May 2017 09:29 PM, Suman Anna wrote:
> Hi Sekhar,
> 
> On 05/18/2017 01:10 AM, Sekhar Nori wrote:
>> On Wednesday 17 May 2017 03:43 AM, Suman Anna wrote:
>>> The DSP device on Davinci platforms does not have an MMU and requires
>>> specific DDR memory to boot. This memory is reserved using the rproc_mem
>>> kernel boot parameter and is assigned to the device on non-DT boots.
>>> The remoteproc core uses the DMA API and so will fall back to assigning
>>> random memory if this memory is not assigned to the device, but the DSP
>>> remote processor boot will not be successful in such cases. So, check
>>> that memory has been reserved and assigned to the device specifically
>>> before even creating the DSP device.
>>>
>>> Signed-off-by: Suman Anna <s-anna@ti.com>
>>> ---
>>>  arch/arm/mach-davinci/devices-da8xx.c | 10 ++++++++++
>>>  1 file changed, 10 insertions(+)
>>>
>>> diff --git a/arch/arm/mach-davinci/devices-da8xx.c b/arch/arm/mach-davinci/devices-da8xx.c
>>> index 7cf529ffbe5a..1ccf52e49886 100644
>>> --- a/arch/arm/mach-davinci/devices-da8xx.c
>>> +++ b/arch/arm/mach-davinci/devices-da8xx.c
>>> @@ -814,6 +814,8 @@ static struct platform_device da8xx_dsp = {
>>>  	.resource	= da8xx_rproc_resources,
>>>  };
>>>  
>>> +static bool rproc_mem_inited __initdata;
>>> +
>>>  #if IS_ENABLED(CONFIG_DA8XX_REMOTEPROC)
>>>  
>>>  static phys_addr_t rproc_base __initdata;
>>> @@ -852,6 +854,8 @@ void __init da8xx_rproc_reserve_cma(void)
>>>  	ret = dma_declare_contiguous(&da8xx_dsp.dev, rproc_size, rproc_base, 0);
>>>  	if (ret)
>>>  		pr_err("%s: dma_declare_contiguous failed %d\n", __func__, ret);
>>> +	else
>>> +		rproc_mem_inited = true;
>>>  }
>>>  
>>>  #else
>>> @@ -866,6 +870,12 @@ int __init da8xx_register_rproc(void)
>>>  {
>>>  	int ret;
>>>  
>>> +	if (!rproc_mem_inited) {
>>> +		pr_warn("%s: memory not reserved for DSP, not registering DSP device\n",
>>> +			__func__);
>>
>> We now have a warning and an error if dma_declare_contiguous() fails. I
>> like this message better. So can you replace the existing error message
>> with this text instead ?
> 
> Hmm, this trace is not just covering the dma_declare_contiguous failure.
> There can be two different errors in da8xx_rproc_reserve_cma, and this

I seem to have missed that part. I now applied this series to v4.13/soc.
I don't have a branch in linux-next. So, it may be a while before it
ends up there. But I do merge all the patches I apply to master branch
of my tree.

Thanks,
Sekhar

  reply	other threads:[~2017-05-22  9:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-16 22:13 [PATCH 0/3] Davinci DSP remoteproc device improvements Suman Anna
2017-05-16 22:13 ` [PATCH 1/3] ARM: davinci: da8xx: Create DSP device only when assigned memory Suman Anna
2017-05-18  6:10   ` Sekhar Nori
2017-05-18 15:59     ` Suman Anna
2017-05-22  9:19       ` Sekhar Nori [this message]
2017-05-16 22:13 ` [PATCH 2/3] ARM: davinci: da8xx: Add names to DSP IOMEM resources Suman Anna
2017-05-16 22:13 ` [PATCH 3/3] ARM: davinci: da8xx: Add DSP internal RAM memories as " Suman Anna

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=ebf2a3e7-4d21-00a8-f6d7-6461ef3e0ec6@ti.com \
    --to=nsekhar@ti.com \
    --cc=khilman@kernel.org \
    --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®