public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Ilias Apalodimas <ilias.apalodimas@linaro.org>
To: Heinrich Schuchardt <heinrich.schuchardt@canonical.com>
Cc: u-boot@lists.denx.de
Subject: Re: [PATCH 1/1] doc: documentation of EFI driver binding protocol
Date: Wed, 5 Oct 2022 10:05:01 +0300	[thread overview]
Message-ID: <Yz0snYxmEH0HsDFc@hades> (raw)
In-Reply-To: <20221004163034.154292-1-heinrich.schuchardt@canonical.com>

Hi Heinrich, 

On Tue, Oct 04, 2022 at 06:30:34PM +0200, Heinrich Schuchardt wrote:
> * Convert code comments in include/efi_driver.h to Sphinx style.
> * Add include/efi_driver.h to the HTML documentation.
> 
> Signed-off-by: Heinrich Schuchardt <heinrich.schuchardt@canonical.com>
> ---
>  doc/api/efi.rst      |  6 ++++++
>  include/efi_driver.h | 19 ++++++++++++-------
>  2 files changed, 18 insertions(+), 7 deletions(-)
> 
> diff --git a/doc/api/efi.rst b/doc/api/efi.rst
> index 2b96783828..43d6f936fb 100644
> --- a/doc/api/efi.rst
> +++ b/doc/api/efi.rst
> @@ -172,6 +172,12 @@ Firmware management protocol
>  .. kernel-doc:: lib/efi_loader/efi_firmware.c
>     :internal:
>  
> +Driver binding protocol
> +~~~~~~~~~~~~~~~~~~~~~~~
> +
> +.. kernel-doc:: include/efi_driver.h
> +   :internal:
> +
>  Unit testing
>  ------------
>  
> diff --git a/include/efi_driver.h b/include/efi_driver.h
> index dc0c1c7ac0..de38abe83b 100644
> --- a/include/efi_driver.h
> +++ b/include/efi_driver.h
> @@ -1,6 +1,6 @@
>  /* SPDX-License-Identifier: GPL-2.0+ */
>  /*
> - *  EFI application loader
> + *  Internal structures for the EFI driver binding protocol
>   *
>   *  Copyright (c) 2017 Heinrich Schuchardt
>   */
> @@ -10,16 +10,16 @@
>  
>  #include <efi_loader.h>
>  
> -/*
> - * Operations supported by an EFI driver with respect to the EFI uclass
> +/**
> + * struct efi_driver_ops - operations support by an EFI driver
>   *
> - * @protocol		The GUID of the protocol which is consumed by the
> + * @protocol:		The GUID of the protocol which is consumed by the
>   *			driver. This GUID is used by the EFI uclass in the
>   *			supports() and start() methods of the
>   *			EFI_DRIVER_BINDING_PROTOCOL.
> - * @child_protocol	Protocol supported by the child handles generated by
> + * @child_protocol:	Protocol supported by the child handles generated by
>   *			the EFI driver.
> - * @bind		Function called by the EFI uclass to attach the
> + * @bind:		Function called by the EFI uclass to attach the
>   *			driver to EFI driver to a handle.
>   */
>  struct efi_driver_ops {
> @@ -28,8 +28,13 @@ struct efi_driver_ops {
>  	efi_status_t (*bind)(efi_handle_t handle, void *interface);
>  };
>  
> -/*
> +/**
> + * struct efi_driver_binding_extended_protocol - extended driver binding protocol
> + *
>   * This structure adds internal fields to the driver binding protocol.
> + *
> + * @bp:		driver binding protocol
> + * @ops:	operations supported by the driver
>   */
>  struct efi_driver_binding_extended_protocol {
>  	struct efi_driver_binding_protocol bp;
> -- 
> 2.37.2
> 

Reviewed-by: Ilias Apalodimas <ilias.apalodimas@linaro.org>

      reply	other threads:[~2022-10-05  7:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-04 16:30 [PATCH 1/1] doc: documentation of EFI driver binding protocol Heinrich Schuchardt
2022-10-05  7:05 ` Ilias Apalodimas [this message]

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=Yz0snYxmEH0HsDFc@hades \
    --to=ilias.apalodimas@linaro.org \
    --cc=heinrich.schuchardt@canonical.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