All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 2/4] dm: core: Add DM_FLAG_PRE_OS_FINALIZE flag
Date: Wed, 19 Apr 2017 11:49:36 +0200	[thread overview]
Message-ID: <bcfd63e4-948d-4d4a-8e0d-40435759e456@denx.de> (raw)
In-Reply-To: <CAPnjgZ3iuDZn1izCke7s8zQ_2HsUJQQ_ZC4JQTpLF9-+Lc=MLw@mail.gmail.com>

Hi Simon,

On 09.04.2017 21:28, Simon Glass wrote:
> Hi Stefan,
>
> On 6 April 2017 at 07:29, Stefan Roese <sr@denx.de> wrote:
>> This new flag can be added to DM device drivers, which need to do some
>> final configuration before U-Boot exits and the OS (e.g. Linux) is
>> started. The remove functions of those drivers will get called at
>> this stage to do these last-stage configuration steps.
>>
>> Signed-off-by: Stefan Roese <sr@denx.de>
>> Cc: Simon Glass <sjg@chromium.org>
>> Cc: Bin Meng <bmeng.cn@gmail.com>
>> ---
>>  drivers/core/device-remove.c | 17 ++++++++++++-----
>>  include/dm/device.h          | 11 ++++++++++-
>>  2 files changed, 22 insertions(+), 6 deletions(-)
>
> Reviewed-by: Simon Glass <sjg@chromium.org>
>
> You could perhaps have a separate patch to move the code into
> flags_remove(), but I suppose it isn't important.
>
> nit below.
>
>>
>> diff --git a/drivers/core/device-remove.c b/drivers/core/device-remove.c
>> index 8b46f3343e..390be5a0d8 100644
>> --- a/drivers/core/device-remove.c
>> +++ b/drivers/core/device-remove.c
>> @@ -148,6 +148,16 @@ void device_free(struct udevice *dev)
>>         devres_release_probe(dev);
>>  }
>>
>> +static int flags_remove(uint flags, uint drv_flags)
>
> Can this be bool, and return true/false?

I'm not a big fan of bool but I've no hard feelings here. I'll change
this if you prefer it this way in v2.

>> +{
>> +       if ((flags & DM_REMOVE_NORMAL) ||
>> +           (flags & (drv_flags &
>> +                     (DM_FLAG_ACTIVE_DMA | DM_FLAG_PRE_OS_FINALIZE))))
>
> What do you think about OS_PREPARE instead? It doesn't really finalize
> the OS...

Much better, thanks. Will change in v2.

Thanks,
Stefan

  reply	other threads:[~2017-04-19  9:49 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-06 13:29 [U-Boot] [PATCH 1/4] dm: device_remove: Don't return in device_chld_remove() upon error Stefan Roese
2017-04-06 13:29 ` [U-Boot] [PATCH 2/4] dm: core: Add DM_FLAG_PRE_OS_FINALIZE flag Stefan Roese
2017-04-09 19:28   ` Simon Glass
2017-04-19  9:49     ` Stefan Roese [this message]
2017-04-06 13:29 ` [U-Boot] [PATCH 3/4] x86: bootm: Add dm_remove_devices_flags() call to bootm_announce_and_cleanup() Stefan Roese
2017-04-09 19:28   ` Simon Glass
2017-04-06 13:29 ` [U-Boot] [PATCH 4/4] spi: ich: Configure SPI BIOS parameters for Linux upon U-Boot exit Stefan Roese
2017-04-07  6:53   ` Jagan Teki
2017-04-09 19:28   ` Simon Glass
2017-04-09 19:28 ` [U-Boot] [PATCH 1/4] dm: device_remove: Don't return in device_chld_remove() upon error Simon Glass
2017-04-19  9:27   ` Stefan Roese
2017-04-24  3:38     ` Simon Glass

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=bcfd63e4-948d-4d4a-8e0d-40435759e456@denx.de \
    --to=sr@denx.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.