From: AKASHI Takahiro <takahiro.akashi@linaro.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v7 4/7] cmd: efidebug: add drivers command
Date: Fri, 22 Feb 2019 13:16:24 +0900 [thread overview]
Message-ID: <20190222041622.GP20286@linaro.org> (raw)
In-Reply-To: <cd5b001c-28a8-4b7d-2454-1506f0c90edb@gmx.de>
On Fri, Feb 22, 2019 at 04:01:52AM +0100, Heinrich Schuchardt wrote:
> On 2/22/19 1:05 AM, AKASHI Takahiro wrote:
> > On Thu, Feb 21, 2019 at 08:32:06PM +0100, Heinrich Schuchardt wrote:
> >> On 2/21/19 7:26 AM, AKASHI Takahiro wrote:
> >>> "drivers" command prints all the uefi drivers on the system.
> >>>
> >>> => efi drivers
> >>> Driver Name Image Path
> >>> ================ ==================== ====================
> >>> 000000007ef003d0 <NULL> <built-in>
> >>>
> >>> Signed-off-by: AKASHI Takahiro <takahiro.akashi@linaro.org>
> >>> ---
> >>> cmd/efidebug.c | 95 +++++++++++++++++++++++++++++++++++++++++++++++++-
> >>> 1 file changed, 94 insertions(+), 1 deletion(-)
> >>>
> >>> diff --git a/cmd/efidebug.c b/cmd/efidebug.c
> >>> index 72e0652fc3e4..04fc170867fc 100644
> >>> --- a/cmd/efidebug.c
> >>> +++ b/cmd/efidebug.c
> >>> @@ -89,6 +89,95 @@ static int do_efi_show_devices(cmd_tbl_t *cmdtp, int flag,
> >>> return CMD_RET_SUCCESS;
> >>> }
> >>>
> >>> +/**
> >>> + * efi_get_driver_handle_info() - get information of UEFI driver
> >>> + *
> >>> + * @handle: Handle of UEFI device
> >>> + * @driver_name: Driver name
> >>> + * @image_path: Pointer to text of device path
> >>> + * Return: 0 on success, -1 on failure
> >>> + *
> >>> + * Currently return no useful information as all UEFI drivers are
> >>> + * built-in..
> >>> + */
> >>> +static int efi_get_driver_handle_info(efi_handle_t handle, u16 **driver_name,
> >>> + u16 **image_path)
> >>> +{
> >>> + struct efi_handler *handler;
> >>> + struct efi_loaded_image *image;
> >>> + efi_status_t ret;
> >>> +
> >>> + /*
> >>> + * driver name
> >>> + * TODO: support EFI_COMPONENT_NAME2_PROTOCOL
> >>> + */
> >>> + *driver_name = NULL;
> >>> +
> >>> + /* image name */
> >>> + ret = efi_search_protocol(handle, &efi_guid_loaded_image, &handler);
> >>> + if (ret != EFI_SUCCESS) {
> >>> + *image_path = NULL;
> >>> + return 0;
> >>> + }
> >>> +
> >>> + image = handler->protocol_interface;
> >>> + *image_path = efi_dp_str(image->file_path);
> >>> +
> >>> + return 0;
> >>> +}
> >>> +
> >>> +/**
> >>> + * do_efi_show_drivers() - show UEFI drivers
> >>> + *
> >>> + * @cmdtp: Command table
> >>> + * @flag: Command flag
> >>> + * @argc: Number of arguments
> >>> + * @argv: Argument array
> >>> + * Return: CMD_RET_SUCCESS on success, CMD_RET_RET_FAILURE on failure
> >>> + *
> >>> + * Implement efidebug "drivers" sub-command.
> >>> + * Show all UEFI drivers and their information.
> >>> + */
> >>> +static int do_efi_show_drivers(cmd_tbl_t *cmdtp, int flag,
> >>> + int argc, char * const argv[])
> >>> +{
> >>> + efi_handle_t *handles;
> >>> + efi_uintn_t num, i;
> >>> + u16 *driver_name, *image_path_text;
> >>> + efi_status_t ret;
> >>> +
> >>> + ret = EFI_CALL(BS->locate_handle_buffer(BY_PROTOCOL,
> >>> + &efi_guid_driver_binding_protocol, NULL,
> >>> + &num, &handles));
> >>
> >> nits:
> >>
> >> scripts/checkpatch.pl is complaining:
> >> Alignment should match open parenthesis
> >>
> >> Just will have to move 'BY_PROTOCOL' to the next line to get rid of it.
> >
> > No,you can't.
> > Ending the line with '(' will cause another error.
> > Or dare you prefer such a style?
>
> ret = EFI_CALL(BS->locate_handle_buffer
> (BY_PROTOCOL,
> &efi_guid_driver_binding_protocol, NULL,
> &num, &handles));
> is what goes without warning.
I have never seen such a coding style either in u-boot or kernel.
Even more, "(BY_PROTOCOL" and so on are not arguments of EFI_CALL,
but local_hander_buffer's.
> But I would not mind if you left the
> parenthesis on the line with the function name.
So this is the only option to be left although I don't like it.
-Takahiro Akashi
>
> Regards
>
> Heinrich
>
> >
> > -Takahiro Akashi
> >
> >
> >> Otherwise:
> >>
> >> Reviewed-by: Heinrich Schuchardt <xypron.glpk@gmx.de>
> >>
> >>> + if (ret != EFI_SUCCESS)
> >>> + return CMD_RET_FAILURE;
> >>> +
> >>> + if (!num)
> >>> + return CMD_RET_SUCCESS;
> >>> +
> >>> + printf("Driver%.*s Name Image Path\n",
> >>> + EFI_HANDLE_WIDTH - 6, spc);
> >>> + printf("%.*s ==================== ====================\n",
> >>> + EFI_HANDLE_WIDTH, sep);
> >>> + for (i = 0; i < num; i++) {
> >>> + if (!efi_get_driver_handle_info(handles[i], &driver_name,
> >>> + &image_path_text)) {
> >>> + if (image_path_text)
> >>> + printf("%p %-20ls %ls\n", handles[i],
> >>> + driver_name, image_path_text);
> >>> + else
> >>> + printf("%p %-20ls <built-in>\n",
> >>> + handles[i], driver_name);
> >>> + EFI_CALL(BS->free_pool(driver_name));
> >>> + EFI_CALL(BS->free_pool(image_path_text));
> >>> + }
> >>> + }
> >>> +
> >>> + EFI_CALL(BS->free_pool(handles));
> >>> +
> >>> + return CMD_RET_SUCCESS;
> >>> +}
> >>> +
> >>> /**
> >>> * do_efi_boot_add() - set UEFI boot option
> >>> *
> >>> @@ -586,6 +675,8 @@ static cmd_tbl_t cmd_efidebug_sub[] = {
> >>> U_BOOT_CMD_MKENT(boot, CONFIG_SYS_MAXARGS, 1, do_efi_boot_opt, "", ""),
> >>> U_BOOT_CMD_MKENT(devices, CONFIG_SYS_MAXARGS, 1, do_efi_show_devices,
> >>> "", ""),
> >>> + U_BOOT_CMD_MKENT(drivers, CONFIG_SYS_MAXARGS, 1, do_efi_show_drivers,
> >>> + "", ""),
> >>> };
> >>>
> >>> /**
> >>> @@ -646,7 +737,9 @@ static char efidebug_help_text[] =
> >>> " - set/show UEFI boot order\n"
> >>> "\n"
> >>> "efidebug devices\n"
> >>> - " - show uefi devices\n";
> >>> + " - show uefi devices\n"
> >>> + "efidebug drivers\n"
> >>> + " - show uefi drivers\n";
> >>> #endif
> >>>
> >>> U_BOOT_CMD(
> >>>
> >>
> >
>
next prev parent reply other threads:[~2019-02-22 4:16 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-21 6:26 [U-Boot] [PATCH v7 0/7] cmd: add efidebug for efi environment AKASHI Takahiro
2019-02-21 6:26 ` [U-Boot] [PATCH v7 1/7] cmd: env: add "-e" option for handling UEFI variables AKASHI Takahiro
2019-02-21 19:42 ` Heinrich Schuchardt
2019-02-22 0:21 ` AKASHI Takahiro
2019-02-22 2:34 ` Heinrich Schuchardt
2019-02-22 10:13 ` Philipp Tomsich
2019-02-25 0:31 ` AKASHI Takahiro
2019-02-21 6:26 ` [U-Boot] [PATCH v7 2/7] cmd: add efidebug command AKASHI Takahiro
2019-02-21 19:24 ` Heinrich Schuchardt
2019-02-22 1:04 ` AKASHI Takahiro
2019-02-22 2:43 ` Heinrich Schuchardt
2019-02-21 6:26 ` [U-Boot] [PATCH v7 3/7] cmd: efidebug: add devices command AKASHI Takahiro
2019-02-21 19:25 ` Heinrich Schuchardt
2019-02-21 6:26 ` [U-Boot] [PATCH v7 4/7] cmd: efidebug: add drivers command AKASHI Takahiro
2019-02-21 19:32 ` Heinrich Schuchardt
2019-02-22 0:05 ` AKASHI Takahiro
2019-02-22 3:01 ` Heinrich Schuchardt
2019-02-22 4:16 ` AKASHI Takahiro [this message]
2019-02-21 6:26 ` [U-Boot] [PATCH v7 5/7] cmd: efidebug: add dh command AKASHI Takahiro
2019-02-21 19:33 ` Heinrich Schuchardt
2019-02-21 6:26 ` [U-Boot] [PATCH v7 6/7] cmd: efidebug: add images command AKASHI Takahiro
2019-02-21 6:26 ` [U-Boot] [PATCH v7 7/7] cmd: efidebug: add memmap command AKASHI Takahiro
2019-02-21 19:35 ` Heinrich Schuchardt
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=20190222041622.GP20286@linaro.org \
--to=takahiro.akashi@linaro.org \
--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.