From: Julius Lehmann <lehmanju@devpi.de>
To: Caleb Connolly <caleb.connolly@linaro.org>,
Neil Armstrong <neil.armstrong@linaro.org>,
Sumit Garg <sumit.garg@linaro.org>, Tom Rini <trini@konsulko.com>,
Simon Glass <sjg@chromium.org>
Cc: u-boot-qcom@groups.io, u-boot@lists.denx.de
Subject: Re: [PATCH v2 1/4] board/qualcomm: introduce phone config
Date: Fri, 6 Dec 2024 17:50:27 +0100 [thread overview]
Message-ID: <d8546140-414d-4dff-ae8b-9ecc9452c17c@devpi.de> (raw)
In-Reply-To: <20241004-qcom-phones-v2-1-c7ab67ac3043@linaro.org>
On 04.10.24 14:46, Caleb Connolly wrote:
> Phones don't have keyboards! Introduce a phone-specific config fragment
> and associated environment file to make U-Boot more useful on these
> devices. This allows for navigating via the buttons and enabling
> various USB gadget modes or displaying info about U-Boot.
>
> Signed-off-by: Caleb Connolly <caleb.connolly@linaro.org>
> ---
> board/qualcomm/qcom-phone.config | 12 ++++++++++
> board/qualcomm/qcom-phone.env | 49 ++++++++++++++++++++++++++++++++++++++++
> 2 files changed, 61 insertions(+)
>
> diff --git a/board/qualcomm/qcom-phone.config b/board/qualcomm/qcom-phone.config
> new file mode 100644
> index 000000000000..388d4c3e7398
> --- /dev/null
> +++ b/board/qualcomm/qcom-phone.config
> @@ -0,0 +1,12 @@
> +# Settings for phones
> +CONFIG_USE_DEFAULT_ENV_FILE=y
> +CONFIG_DEFAULT_ENV_FILE="board/qualcomm/qcom-phone.env"
> +CONFIG_PANIC_HANG=y
> +CONFIG_CMD_PAUSE=y
> +CONFIG_BOOTSTD=y
> +CONFIG_BOOT_RETRY=y
> +CONFIG_BOOT_RETRY_TIME=1
> +CONFIG_BUTTON_REMAP_PHONE_KEYS=y
should also include fastboot, serial gadget and
CONFIG_CMD_USB_MASS_STORAGE. otherwise some menu options wouldn't work.
> +
> +# Many phones don't actually define a serial port in their DTS
> +# CONFIG_REQUIRE_SERIAL_CONSOLE is not set
> diff --git a/board/qualcomm/qcom-phone.env b/board/qualcomm/qcom-phone.env
> new file mode 100644
> index 000000000000..2a0791c888c6
> --- /dev/null
> +++ b/board/qualcomm/qcom-phone.env
> @@ -0,0 +1,49 @@
> +bootdelay=0
> +bootretry=1
> +stdin=serial,button-kbd
> +stdout=serial,vidconsole
> +stderr=serial,vidconsole
> +
> +# Fastboot is keen to use the address from kconfig, but we
> +# allocate its buffer at runtime.
> +fastboot=fastboot -l $fastboot_addr_r usb 0
> +
> +# Shortcut to enable USB serial gadget and disable bootretry
> +serial_gadget=setenv stdin serial,button-kbd,usbacm; \
> + setenv stdout serial,vidconsole,usbacm; \
> + setenv stderr serial,vidconsole,usbacm; \
> + setenv bootretry -1; \
> + echo Enabled U-Boot console serial gadget
this doesn't work. according to doc
(https://docs.u-boot.org/en/latest/usage/environment.html), multiline
variables don't need "\".
but even without "\" it only executes the first line.
> +
> +# bootretry will run this command over and over, if we fail once
> +# then bail out to the boot menu instead (with a pause to read
> +# the error message)
> +bootcmd=bootefi bootmgr; pause; run menucmd
> +
> +# When entering the menu (either from button press or failed boot)
> +# remap bootcmd so it will re-open the menu and we won't get stuck
> +# at the console with no way to type
> +menucmd=setenv bootcmd run menucmd; bootmenu -1
> +
> +# Pause is used so the output can be read on the display
> +bootmenu_0=Boot=bootefi bootmgr; pause
> +bootmenu_1=Enable serial console gadget=run serial_gadget
> +bootmenu_2=Enable USB mass storage=ums 0 scsi 0
> +bootmenu_3=Reset device=reset
> +bootmenu_4=Dump clocks=clk dump; pause
> +bootmenu_5=Dump environment=printenv; pause
> +bootmenu_6=Board info=bdinfo; pause
> +bootmenu_7=Dump bootargs=fdt print /chosen bootargs; pause
> +bootmenu_8=Enable fastboot mode=run fastboot
> +# Disabling bootretry means we'll just drop the shell
> +bootmenu_9=Drop to shell=setenv bootretry -1
maybe at an entry for ufetch? ;)
> +
> +# Allow holding the power button while U-Boot loads to enter
> +# the boot menu
> +button_cmd_0_name=pwrkey
> +button_cmd_0=run menucmd
> +
> +# Hold volume down to drop to a shell with the USB serial gadget
> +# enabled for debugging
> +button_cmd_1_name=Volume down
> +button_cmd_1=run serial_gadget
>
next prev parent reply other threads:[~2024-12-06 16:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-04 12:46 [PATCH v2 0/4] Better smartphone support (Qualcomm) Caleb Connolly
2024-10-04 12:46 ` [PATCH v2 1/4] board/qualcomm: introduce phone config Caleb Connolly
2024-10-07 15:23 ` Simon Glass
2024-12-06 16:50 ` Julius Lehmann [this message]
2024-12-07 1:02 ` Alexey Minnekhanov
2024-10-04 12:46 ` [PATCH v2 2/4] cli_hush: run bootmenu on retry Caleb Connolly
2024-10-04 17:14 ` Tom Rini
2024-10-04 12:46 ` [PATCH v2 3/4] bootretry: check for bootretry variable changes Caleb Connolly
2024-10-04 17:16 ` Tom Rini
2024-10-04 12:46 ` [PATCH v2 4/4] doc: board/qualcomm: describe phone support and bringup Caleb Connolly
2024-10-07 15:23 ` Simon Glass
-- strict thread matches above, loose matches on Subject: below --
2025-03-11 12:31 [PATCH v2 0/4] Better smartphone support (Qualcomm) Caleb Connolly
2025-03-11 12:31 ` [PATCH v2 1/4] board/qualcomm: introduce phone config Caleb Connolly
2025-03-30 8:23 ` Sam Day
2025-03-30 13:30 ` Caleb Connolly
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=d8546140-414d-4dff-ae8b-9ecc9452c17c@devpi.de \
--to=lehmanju@devpi.de \
--cc=caleb.connolly@linaro.org \
--cc=neil.armstrong@linaro.org \
--cc=sjg@chromium.org \
--cc=sumit.garg@linaro.org \
--cc=trini@konsulko.com \
--cc=u-boot-qcom@groups.io \
--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