public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Nishanth Menon <nm@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 2/3] remoteproc: Introduce a sandbox dummy driver
Date: Tue, 25 Aug 2015 10:47:00 -0500	[thread overview]
Message-ID: <55DC8DF4.308@ti.com> (raw)
In-Reply-To: <CAPnjgZ253Q+fGm9x6uVSkYbz6d=7p8jG9A7X3jcic5zjiXuziQ@mail.gmail.com>

On 08/25/2015 12:04 AM, Simon Glass wrote:
[...]
>> +# Please keep the configuration alphabetically sorted.
>> +config DM_TESTPROC_SANDBOX
> 
> Should this be REMOTEPROC_SANDBOX?

Yep - will do.

>> diff --git a/drivers/remoteproc/sandbox_testproc.c b/drivers/remoteproc/sandbox_testproc.c
>> new file mode 100644
>> index 000000000000..e942f66fc2dc
>> --- /dev/null
>> +++ b/drivers/remoteproc/sandbox_testproc.c
>> @@ -0,0 +1,243 @@
>> +/*
>> + * (C) Copyright 2015
>> + * Texas Instruments Incorporated - http://www.ti.com/
>> + * SPDX-License-Identifier:    GPL-2.0+
>> + */
>> +#define pr_fmt(fmt) "%s: " fmt, __func__
^^

>> +#include <common.h>
>> +#include <dm.h>
>> +#include <errno.h>
>> +#include <remoteproc.h>

[...]

>> +
>> +static int sandbox_testproc_is_running(struct udevice *dev)
>> +{
>> +       struct dm_rproc_uclass_pdata *uc_pdata;
>> +       struct sandbox_test_devdata *ddata;
>> +       int ret = 1;
>> +
>> +       uc_pdata = dev_get_uclass_platdata(dev);
>> +       ddata = dev_get_priv(dev);
>> +
>> +       if (ddata->current_state == sb_running)
>> +               ret = 0;
>> +       debug("%s: called(%d)\n", uc_pdata->name, ret);
> 
> should that say "is_running called" / do you need __func__?

pr_fmt (at the start of the file) should take care of it.

[...]

>> +U_BOOT_DRIVER(sandbox_testproc) = {
>> +       /* *INDENT-OFF* */
> 
> What is that for? ^^

trying to keep indent sane - will drop.


Thanks once again for the review.


-- 
Regards,
Nishanth Menon

  reply	other threads:[~2015-08-25 15:47 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-24 17:28 [U-Boot] [PATCH 0/3] drivers/sandbox: Introduce a simplified remoteproc framework Nishanth Menon
2015-08-24 17:28 ` [U-Boot] [PATCH 1/3] drivers: " Nishanth Menon
2015-08-25  5:04   ` Simon Glass
2015-08-25 15:44     ` Nishanth Menon
2015-08-26  2:26       ` Simon Glass
     [not found]         ` <CAGo_u6pb_BSzT0fXZ7uxoqEM1RzwKKL3dXq0wyrphAB80Yf-Nw@mail.gmail.com>
2015-08-27 15:49           ` Simon Glass
2015-08-27 15:54             ` Nishanth Menon
2015-08-24 17:28 ` [U-Boot] [PATCH 2/3] remoteproc: Introduce a sandbox dummy driver Nishanth Menon
2015-08-25  5:04   ` Simon Glass
2015-08-25 15:47     ` Nishanth Menon [this message]
2015-08-24 17:28 ` [U-Boot] [PATCH 3/3] sandbox: Introduce dummy remoteproc nodes Nishanth Menon
2015-08-25  5:04   ` Simon Glass
2015-08-25 15:47     ` Nishanth Menon
2015-08-25  5:04 ` [U-Boot] [PATCH 0/3] drivers/sandbox: Introduce a simplified remoteproc framework Simon Glass
2015-08-25 15:48   ` Nishanth Menon

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=55DC8DF4.308@ti.com \
    --to=nm@ti.com \
    --cc=u-boot@lists.denx.de \
    /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