On Thu, 19 Jan 2023 at 16:11, Jens Wiklander wrote:
>
> On Thu, Jan 19, 2023 at 3:36 PM Ilias Apalodimas
> wrote:
> >
> > commit fe8a4ed0111073 ("tee: optee: discover services dependent on
> > tee-supplicant")
> > is trying to automatically scan and add TAs that are presented on pseudo
> > bus f
On Thu, 19 Jan 2023 at 10:21, Ilias Apalodimas
wrote:
>
> When comparing UUIDs for discovered services we only compare up to the
> ptr size instead of the entire UUID
>
> Fixes: 94ccfb78a4d61 ("drivers: tee: optee: discover OP-TEE services")
> Signed-off-by: Ilias Apalodimas
> ---
> drivers/tee/
On Thu, 19 Jan 2023 at 22:48, Dzmitry Sankouski wrote:
>
> GPIO button driver requires direction functions to probe
> button gpio. Those functions are blank, since pwrkey gpio
> configured earlier not by u-boot.
>
> Signed-off-by: Dzmitry Sankouski
> ---
> Changes for v2:
> - none
>
> drivers/gp
Signed-off-by: Sumit Garg
---
arch/arm/dts/qcs404-evb.dts | 97 +
1 file changed, 97 insertions(+)
diff --git a/arch/arm/dts/qcs404-evb.dts b/arch/arm/dts/qcs404-evb.dts
index 2de0e7537b..8d7893c116 100644
--- a/arch/arm/dts/qcs404-evb.dts
+++ b/arch/arm/dts/q
Add support for Qualcomm I2C QUP driver which is inspired from
corresponding driver in Linux: drivers/i2c/busses/i2c-qup.c.
Currently this driver only support FIFO polling mode which is sufficient
to support devices like eeprom, rtc etc.
Co-developed-by: Mike Worsfold
Signed-off-by: Mike Worsfol
Co-developed-by: Mike Worsfold
Signed-off-by: Mike Worsfold
Signed-off-by: Sumit Garg
---
arch/arm/mach-snapdragon/pinctrl-qcs404.c | 6 ++
1 file changed, 6 insertions(+)
diff --git a/arch/arm/mach-snapdragon/pinctrl-qcs404.c
b/arch/arm/mach-snapdragon/pinctrl-qcs404.c
index 5a7fbfd441..
Co-developed-by: Mike Worsfold
Signed-off-by: Mike Worsfold
Signed-off-by: Sumit Garg
---
arch/arm/mach-snapdragon/clock-qcs404.c | 58 +++
.../include/mach/sysmap-qcs404.h | 17 ++
2 files changed, 75 insertions(+)
diff --git a/arch/arm/mach-snapdragon/c
Add clk_rcg_set_rate() which allows to configure clocks without programming
MND values. This is required for configuring I2C clocks on QCS404.
Co-developed-by: Mike Worsfold
Signed-off-by: Mike Worsfold
Signed-off-by: Sumit Garg
---
arch/arm/mach-snapdragon/clock-snapdragon.c | 24
Signed-off-by: Sumit Garg
---
arch/arm/dts/qcs404-evb.dts | 98 -
1 file changed, 97 insertions(+), 1 deletion(-)
diff --git a/arch/arm/dts/qcs404-evb.dts b/arch/arm/dts/qcs404-evb.dts
index cc70afa4c8..2de0e7537b 100644
--- a/arch/arm/dts/qcs404-evb.dts
+++ b
The Qualcom ETHQOS hardware supports an RGMII macro which needs to be
configured according to following link speeds:
- SPEED_1000
- SPEED_100
- SPEED_10
So add a corresponding glue driver to configure RGMII macro.
Signed-off-by: Sumit Garg
---
drivers/net/Kconfig| 7 +
drivers/net
The GMAC controller on QCS404 SoC (support added by upcoming patch) fails
to work with maximum tx/rx_fifo_sz supported by the hardware (16K). So
allow platforms to override FIFO size using corresponding DT node
properties.
Signed-off-by: Sumit Garg
---
drivers/net/dwc_eth_qos.c | 19
Signed-off-by: Sumit Garg
---
drivers/net/dwc_eth_qos.c | 9 ++---
1 file changed, 6 insertions(+), 3 deletions(-)
diff --git a/drivers/net/dwc_eth_qos.c b/drivers/net/dwc_eth_qos.c
index afc47b56ff..753a912607 100644
--- a/drivers/net/dwc_eth_qos.c
+++ b/drivers/net/dwc_eth_qos.c
@@ -774,10
Use standard pinconf drive-strength values from Linux DT bindings rather
than ones based on custom u-boot header. These changes are in direction
to make u-boot DTs for Qcom SoCs to be compatible with standard Linux
DT bindings.
Also, add support for pinconf bias-pull-up.
Signed-off-by: Sumit Garg
Signed-off-by: Sumit Garg
---
arch/arm/mach-snapdragon/pinctrl-qcs404.c | 7 +++
1 file changed, 7 insertions(+)
diff --git a/arch/arm/mach-snapdragon/pinctrl-qcs404.c
b/arch/arm/mach-snapdragon/pinctrl-qcs404.c
index 889ead0f57..5a7fbfd441 100644
--- a/arch/arm/mach-snapdragon/pinctrl-qcs4
Signed-off-by: Sumit Garg
---
arch/arm/mach-snapdragon/clock-qcs404.c | 60 +++
.../include/mach/sysmap-qcs404.h | 14 +
2 files changed, 74 insertions(+)
diff --git a/arch/arm/mach-snapdragon/clock-qcs404.c
b/arch/arm/mach-snapdragon/clock-qcs404.c
index
Signed-off-by: Sumit Garg
---
arch/arm/dts/qcs404-evb.dts | 4
configs/qcs404evb_defconfig | 1 +
2 files changed, 5 insertions(+)
diff --git a/arch/arm/dts/qcs404-evb.dts b/arch/arm/dts/qcs404-evb.dts
index 0639af8fe3..c8bcf9f71d 100644
--- a/arch/arm/dts/qcs404-evb.dts
+++ b/arch/arm/dts/
Currently u-boot maps whole of 1G RAM but there reserved memory ranges on
QCS404 which are reserved for TrustZone, various firmware components etc.
Any access to these reserved memory ranges causes a bus hang issue. So
disable mapping for reserved memory ranges in u-boot.
Signed-off-by: Sumit Garg
Patch#1 is a fix for QCS404 system memory map to not map reserved memory
regions as an occasional system hang is observed.
Rest of the patches add support for Qualcomm ethernet and I2C drivers
specifically tested on QCS404 SoC.
Sumit Garg (14):
qcs404: sysmap: Don't map reserved memory ranges
From: Algapally Santosh Sagar
tuning_loop_counter is of char type, which is not capable of handling
the entire data range of this variable. This is pointed by below sparse
warning. Change datatype to int to fix this.
warning: comparison is always false due to limited range of data type.
Signed-o
From: Algapally Santosh Sagar
Add missing prototype to fix the sparse warning, warning: no
previous prototype for 'do_go_exec' [-Wmissing-prototypes].
Signed-off-by: Algapally Santosh Sagar
Signed-off-by: Ashok Reddy Soma
---
Changes in v2:
- Changed subject from missing prototype to missing
From: Algapally Santosh Sagar
There is a unused variable ret, due to which we are getting sparse warning
as below.
warning: variable 'ret' set but not used [-Wunused-but-set-variable].
Return ret incase of error.
Signed-off-by: Algapally Santosh Sagar
Signed-off-by: Ashok Reddy Soma
---
Chan
From: Algapally Santosh Sagar
Prototype is missing for board_get_usable_ram_top, which is pointed by
below sparse warning. Include init.h header file to fix this.
warning: no previous prototype for 'board_get_usable_ram_top'
[-Wmissing-prototypes].
Signed-off-by: Algapally Santosh Sagar
Signed
Run and fix sparse warnings in below files
-drivers/mmc/zynq_sdhci.c
-board/xilinx/common/board.h
-drivers/gpio/zynqmp_gpio_modepin.c
-board/xilinx/versal/board.c
Changes in v2:
- Included header file instead of declaring prototype
- Modified description to reflect the same
- Instead of rem
From: Takahiro Kuwano
Cypress defines two flavors of configuration registers, volatile and
non volatile, and both use the same bit fields. Rename the bitfields in
the configuration registers so that they can be used for both flavors.
Suggested-by: Tudor Ambarus
Signed-off-by: Takahiro Kuwano
-
From: Takahiro Kuwano
CFR5[6] is reserved bit and must be always 1. Set it to comply with flash
requirements. While fixing SPINOR_REG_CYPRESS_CFR5V_OCT_DTR_EN definition,
stop using magic numbers and describe the missing bit fields in CFR5
register. This is useful for both readability and future
From: Takahiro Kuwano
Same fix is needed in Linux MTD [0] and Tudor helped for that [1][2].
This series applies the same changes as Linux MTD.
[0]
https://patchwork.ozlabs.org/project/linux-mtd/patch/20230106030601.6530-1-takahiro.kuw...@infineon.com/
[1]
https://patchwork.ozlabs.org/project/l
Hello Simon,
Sorry, do you have time to check v2 patch?
Ryan Chen
> -Original Message-
> From: Ryan Chen
> Sent: Wednesday, January 11, 2023 2:53 PM
> To: Heiko Schocher ; Ryan Chen ;
> BMC-SW ; u-boot@lists.denx.de
> Subject: [PATCH v2 1/1] i2c:aspeed:support ast2600 i2c new reg
On 1/19/23 14:25, Conor Dooley wrote:
On Thu, Jan 19, 2023 at 02:16:51PM -0500, Sean Anderson wrote:
On 1/19/23 13:30, Conor Dooley wrote:
Hey Seán, David,
On Thu, Jan 19, 2023 at 01:26:52AM -0500, Sean Anderson wrote:
On 1/19/23 01:18, David Abdurachmanov wrote:
On Wed, Jan 18, 2023 at 10:1
On Fri, Jan 20, 2023 at 01:07:50AM +0100, Marek Vasut wrote:
> On 1/20/23 00:26, Simon Glass wrote:
> > Now that a new schema has been accepted upstream, press it into service in
> > U-Boot.
>
> git grep in latest linux-next 20230119 does not provide any hits on bootph ,
&g
On 1/20/23 00:26, Simon Glass wrote:
Now that a new schema has been accepted upstream, press it into service in
U-Boot.
git grep in latest linux-next 20230119 does not provide any hits on
bootph , is there at least any link to this new schema ? Really, the
documentation or even commit
Now that Linux has accepted these tags, move U-Boot over to use them.
Tidy up the comments and formatting, making sure that VPL is mentioned
too.
Signed-off-by: Simon Glass
---
doc/README.TPL| 4 +--
doc/develop/driver-model/design.rst | 15 +--
Now that Linux has accepted these tags, move U-Boot over to use them.
Signed-off-by: Simon Glass
---
doc/device-tree-bindings/chosen.txt | 2 +-
.../clock/rockchip,rk3368-dmc.txt | 2 +-
.../clock/rockchip,rk3399-dmc.txt | 2 +-
.../clock/st,stm32mp1.txt
Update various build and test components to use the new schema.
Signed-off-by: Simon Glass
---
drivers/core/ofnode.c| 10 +-
drivers/video/video-uclass.c | 4 ++--
dts/Kconfig | 2 +-
include/dm/device.h | 2 +-
include/dm/ofnode.h
Now that Linux has accepted these tags, update the dtoc tool to use them.
Signed-off-by: Simon Glass
---
tools/dtoc/dtb_platdata.py | 10 +-
tools/dtoc/test/dtoc_test_add_prop.dts | 4 ++--
tools/dtoc/test/dtoc_test_addr32.dts | 4 ++--
tools/dtoc
Now that a new schema has been accepted upstream, press it into service in
U-Boot.
Simon Glass (5):
dm: dts: Convert driver model tags to use new schema
dm: doc: Update device tree binding docs for new schema
dm: doc: Update documentation for new driver model schema
dm: doc: Move to new d
These SoMs may ship with SMSC LAN8740Ai PHYs, enable the SMSC PHY driver.
Signed-off-by: Marek Vasut
---
Cc: "Ariel D'Alessandro"
Cc: "NXP i.MX U-Boot Team"
Cc: Andrey Zhizhikin
Cc: Fabio Estevam
Cc: Joe Hershberger
Cc: Lukasz Majewski
Cc: Marcel Ziswiler
Cc: Marek Vasut
Cc: Michael Trima
These SoMs never ship with Atheros PHYs, disable the Atheros PHY driver.
Signed-off-by: Marek Vasut
---
Cc: "Ariel D'Alessandro"
Cc: "NXP i.MX U-Boot Team"
Cc: Andrey Zhizhikin
Cc: Fabio Estevam
Cc: Joe Hershberger
Cc: Lukasz Majewski
Cc: Marcel Ziswiler
Cc: Marek Vasut
Cc: Michael Trimar
With DM clock support in place, it is easy to add RMII support into the
MAC driver. The RMII cannot operate at 1000 Mbps and at 100 and 10 Mbps
the clock frequency is 50 MHz and 5 MHz instead of 25 MHz and 2.5 MHz.
The board DT requires the following adjustments to EQoS node:
phy-mode = "rmii";
The assigned-clock no longer have to be dropped, the clock are now
defined in clk-imx8mp.c and used by DWMAC driver to configure the
DWMAC clock. Drop the workarounds from U-Boot specific DT extras.
Signed-off-by: Marek Vasut
---
Cc: "Ariel D'Alessandro"
Cc: "NXP i.MX U-Boot Team"
Cc: Andrey Zh
Implement common board_interface_eth_init() and call it from the DWMAC
driver to configure IOMUXC GPR[1] register according to the PHY mode
obtained from DT. This supports all three interface modes supported by
the i.MX8M Plus DWMAC and supersedes current board-side configuration
of the same IOMUX
The DWMAC clock in i.MX8M Plus were so far configured via ad-hoc
architecture code. Replace that with DM clock instead. This way,
the driver claims all its required clock, enables and disables
them, and even gets the CSR clock rate and sets the TX clock rate,
without any need of architecture specif
The EQoS interface mode is now configured in common board_interface_eth_init()
and called by EQoS MAC driver when appropriate. Drop the board side duplicates
if the same functionality.
Signed-off-by: Marek Vasut
---
Cc: "Ariel D'Alessandro"
Cc: "NXP i.MX U-Boot Team"
Cc: Andrey Zhizhikin
Cc: F
The driver currently only waits for DMA_MODE SWR bit to clear itself.
This is insufficient e.g. on i.MX8M Plus, where the MAC must be reset
before IOMUX GPR[1] content is latched into the MAC and used. Without
the proper reset, the i.MX8M Plus MAC variant does not take the value
in IOMUX GPR[1] int
The dm_gpio_free() is never called, because for stm32, the phy_reset_gpio
pointer is never valid. This is because only tegra186 ever claims the
phy_reset_gpio, all other platforms use the PHY framework to reset the
PHY instead. Drop the dm_gpio_free() and dm_gpio_is_valid().
Signed-off-by: Marek V
The return is never triggered due to the goto just above it.
Drop it. No functional change.
Signed-off-by: Marek Vasut
---
Cc: "Ariel D'Alessandro"
Cc: "NXP i.MX U-Boot Team"
Cc: Andrey Zhizhikin
Cc: Fabio Estevam
Cc: Joe Hershberger
Cc: Lukasz Majewski
Cc: Marcel Ziswiler
Cc: Marek Vasut
Add clock for the DWMAC EQoS block. This is used among other things
to configure the MII clock via DM CLK.
Signed-off-by: Marek Vasut
---
Cc: "Ariel D'Alessandro"
Cc: "NXP i.MX U-Boot Team"
Cc: Andrey Zhizhikin
Cc: Fabio Estevam
Cc: Joe Hershberger
Cc: Lukasz Majewski
Cc: Marcel Ziswiler
C
On Wed, Jan 18, 2023 at 07:18:12PM -0700, Simon Glass wrote:
> Hi Tom,
>
> https://source.denx.de/u-boot/custodians/u-boot-dm/-/pipelines/14776
>
>
> The following changes since commit 5b958dea5c678dbdb2aeb6ac3c0c8cc8dfea065c:
>
> Merge branch '2022-01-16-bootstd-updates' (2023-01-17 08:55:4
Hi Matthew,
On Thu, 19 Jan 2023 at 10:42, matthew.more...@gd-ms.com
wrote:
>
> Hello,
>
> I have been working with trying to build U-Boot version 2022.04, cloning from
> branch boundary-v2022.04 from the following link:
> https://github.com/boundarydevices/u-boot/tree/boundary-v2022.04
>
> I am
On Thu, 19 Jan 2023 at 10:18, Dzmitry Sankouski wrote:
>
> gpio-keys linux driver enforces user to specify linux,code.
> Add missing linux,code before implementing button input support.
>
> - arch/arm/dts/rk3288-popmetal.dtsi -> KEY_POWER
> - arch/arm/dts/rk3288-tinker.dtsi -> KEY_POWER
> - arch/a
Hi Pali,
On Thu, Jan 19, 2023 at 10:05 AM Pali Rohár wrote:
>
> Hello! If I read the whole change correctly then all changes are done
> under ifdef CONFIG_DDR4. So for existing (ddr3) boards this is noop.
>
> Reviewed-by: Pali Rohár
>
> The reaming part is the changes which you done on top of th
Hi Dzmitry,
On Thu, 19 Jan 2023 at 10:19, Dzmitry Sankouski wrote:
>
> Linux event code may be used in input devices, using buttons.
Do you mean 'must be used' ?
>
> Signed-off-by: Dzmitry Sankouski
> ---
> Changes for v2:
> - fail, if linux,code not found
>
> drivers/button/button-gpio.c |
The MNT Reform 2 is a modular DIY laptop. In its initial version it
is based on the BoundaryDevices i.MX8MQ SoM. Some parts have been
lifted from BoundaryDevices official U-Boot downstream project.
Signed-off-by: Patrick Wildt
---
Changes since v5:
- Adjusted to further Binman changes.
- Adjust
On Tue, 10 Jan 2023 at 20:13, Ramon Fried wrote:
> Reviewed-by: Ramon Fried
Hello, Ramon! I have just submitted a v2 of this patch. The only
substantial difference there is a Kconfig addition. If you are fine
with it, could you please give it your "Reviewed-by"?
Register mii_bus with read and write callbacks to allow the 'mii'
command to work. Use a timeout of 10 ms to wait for the R/W
operations to complete.
Signed-off-by: Sergei Antonov
---
v1 -> v2:
* fix a typo in the description
* add a dependency from MII to Kconfig
* rebase to the current master
Replace 'phys_addr_t iobase' with 'struct ftmac100 *ftmac100'
in order to cast once on assignment and remove casting in a
number of other places.
Signed-off-by: Sergei Antonov
Reviewed-by: Ramon Fried
---
v1 -> v2:
no change
drivers/net/ftmac100.c | 14 +++---
1 file changed, 7 insert
So it will be named similarly to the related ftgmac100 driver.
The old name 'nds32_mac' is not referred to anywhere in U-Boot.
Signed-off-by: Sergei Antonov
Reviewed-by: Ramon Fried
---
v1 -> v2:
no change
drivers/net/ftmac100.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --gi
On Thu, Jan 19, 2023 at 02:16:51PM -0500, Sean Anderson wrote:
> On 1/19/23 13:30, Conor Dooley wrote:
> > Hey Seán, David,
> >
> > On Thu, Jan 19, 2023 at 01:26:52AM -0500, Sean Anderson wrote:
> >> On 1/19/23 01:18, David Abdurachmanov wrote:
> >> > On Wed, Jan 18, 2023 at 10:19 AM Yanhong Wang
On 1/19/23 13:30, Conor Dooley wrote:
> Hey Seán, David,
>
> On Thu, Jan 19, 2023 at 01:26:52AM -0500, Sean Anderson wrote:
>> On 1/19/23 01:18, David Abdurachmanov wrote:
>> > On Wed, Jan 18, 2023 at 10:19 AM Yanhong Wang
>> > wrote:
>
>> > > + U74_4: cpu@4 {
>> > > +
чт, 19 січ. 2023 р. о 18:19 Simon Glass пише:
>
> Hi Svyatoslav,
>
> On Thu, 19 Jan 2023 at 00:12, Svyatoslav Ryhel wrote:
> >
> > ср, 18 січ. 2023 р. о 21:42 Simon Glass пише:
> > >
> > > Hi Svyatoslav,
> > >
> > > On Wed, 18 Jan 2023 at 01:44, Svyatoslav Ryhel wrote:
> > > >
> > > > Add timer
Hey Seán, David,
On Thu, Jan 19, 2023 at 01:26:52AM -0500, Sean Anderson wrote:
> On 1/19/23 01:18, David Abdurachmanov wrote:
> > On Wed, Jan 18, 2023 at 10:19 AM Yanhong Wang
> > wrote:
> > > + U74_4: cpu@4 {
> > > + compatible = "sifive,u74-mc", "riscv";
>
On Thu, Jan 19, 2023 at 10:41 AM Simon Glass wrote:
>
> Hi Abdellatif,
>
> On Thu, 19 Jan 2023 at 09:32, Abdellatif El Khlifi
> wrote:
> >
> > On Wed, Jan 18, 2023 at 08:59:32AM -0500, Tom Rini wrote:
> > > On Wed, Jan 18, 2023 at 01:46:54PM +, Sudeep Holla wrote:
> > > > On Wed, Jan 18, 2023
Hello! If I read the whole change correctly then all changes are done
under ifdef CONFIG_DDR4. So for existing (ddr3) boards this is noop.
Reviewed-by: Pali Rohár
The reaming part is the changes which you done on top of the Marvell
code to make it compile under u-boot (floating point, basic type
Hi Tom,
On Thu, 19 Jan 2023 at 10:24, Tom Rini wrote:
>
> On Thu, Jan 19, 2023 at 10:21:07AM -0700, Simon Glass wrote:
> > Hi Tom,
> >
> > On Thu, 19 Jan 2023 at 09:57, Tom Rini wrote:
> > >
> > > On Thu, Jan 19, 2023 at 09:54:29AM -0700, Simon Glass wrote:
> > > > Hi Sudeep,
> > > >
> > > > On
Hello,
I have been working with trying to build U-Boot version 2022.04, cloning from
branch boundary-v2022.04 from the following link:
https://github.com/boundarydevices/u-boot/tree/boundary-v2022.04
I am running into a couple errors, none of which I was able to find on the
email threads and F
To improve startup times when booting from QSPI flash, the QSPI frequency
can be configured very early in the boot process [1] to reduce loading
times of U-Boot itself. This patch adds an option to disable setting the
frequency to a default value during SoC initialization.
[1] https://www.nxp.com/
With this additional parameter, a board-specific implementation of this
function can return an alternative address in case booting from the first
address in the NOR flash fails.
Signed-off-by: Mario Kicherer
---
arch/arm/mach-imx/image-container.c| 2 +-
arch/mips/mach-mtmips/mt7621/spl/spl
Add BOOT_DEVICE_NOR2 as a second SPL_LOAD_IMAGE_METHOD to enable a
board-specific spl_nor_get_uboot_base() function to return an alternative
address in the NOR flash in case booting from BOOT_DEVICE_NOR fails.
Signed-off-by: Mario Kicherer
---
arch/arm/include/asm/spl.h | 1 +
arch/mips/includ
Add a second SPL_LOAD_IMAGE_METHOD BOOT_DEVICE_NOR2 to enable booting
from an alternative NOR address in case loading from the first address
fails - e.g., if no valid header is found.
Changes since v1:
- addressed right email recipients
Mario Kicherer (2):
spl: spl_nor: add BOOT_DEVICE_NOR2 as
On Thu, Jan 19, 2023 at 10:21:07AM -0700, Simon Glass wrote:
> Hi Tom,
>
> On Thu, 19 Jan 2023 at 09:57, Tom Rini wrote:
> >
> > On Thu, Jan 19, 2023 at 09:54:29AM -0700, Simon Glass wrote:
> > > Hi Sudeep,
> > >
> > > On Thu, 19 Jan 2023 at 09:46, Sudeep Holla wrote:
> > > >
> > > > Hi Abdellat
Hi Sudeep,
On Thu, 19 Jan 2023 at 10:09, Sudeep Holla wrote:
>
> On Thu, Jan 19, 2023 at 11:57:44AM -0500, Tom Rini wrote:
> >
> > But it's also true that at run-time, within U-Boot, we can modify the
> > device tree we have, with live tree yes? So, the whole series in
> > question here can be do
On Thu, Jan 19, 2023 at 05:09:45PM +, Sudeep Holla wrote:
> On Thu, Jan 19, 2023 at 11:57:44AM -0500, Tom Rini wrote:
> >
> > But it's also true that at run-time, within U-Boot, we can modify the
> > device tree we have, with live tree yes? So, the whole series in
> > question here can be done
Hi Tom,
On Thu, 19 Jan 2023 at 09:57, Tom Rini wrote:
>
> On Thu, Jan 19, 2023 at 09:54:29AM -0700, Simon Glass wrote:
> > Hi Sudeep,
> >
> > On Thu, 19 Jan 2023 at 09:46, Sudeep Holla wrote:
> > >
> > > Hi Abdellatif,
> > >
> > > On Thu, Jan 19, 2023 at 04:31:57PM +, Abdellatif El Khlifi wr
Bootmenu requires an input device with arrows and enter key.
A common smartphone luckily has power, volume up/down buttons,
which may be used for controlling bootmenu.
To use driver, add 'button-kbd' to stdin.
Signed-off-by: Dzmitry Sankouski
Reviewed-by: Simon Glass
---
Changes for v2:
- add do
Linux event code may be used in input devices, using buttons.
Signed-off-by: Dzmitry Sankouski
---
Changes for v2:
- fail, if linux,code not found
drivers/button/button-gpio.c | 16 +++-
drivers/button/button-uclass.c | 10 ++
include/button.h | 16 ++
gpio-keys linux driver enforces user to specify linux,code.
Add missing linux,code before implementing button input support.
- arch/arm/dts/rk3288-popmetal.dtsi -> KEY_POWER
- arch/arm/dts/rk3288-tinker.dtsi -> KEY_POWER
- arch/arm/dts/am3517-evm-ui.dtsi -> KEY_RECORD
- sandbox/dts/sandbox.dtsi ->
GPIO button driver requires direction functions to probe
button gpio. Those functions are blank, since pwrkey gpio
configured earlier not by u-boot.
Signed-off-by: Dzmitry Sankouski
---
Changes for v2:
- none
drivers/gpio/qcom_pmic_gpio.c | 15 +++
1 file changed, 15 insertions(+)
Bootmenu requires an input device with arrows and enter key.
A common smartphone luckily has power, volume up/down buttons,
which may be used for controlling bootmenu.
Button keyboard driver relies on button driver - iterates over
all button with linux,code, checks state and sends events.
Add supp
On Thu, Jan 19, 2023 at 11:57:44AM -0500, Tom Rini wrote:
>
> But it's also true that at run-time, within U-Boot, we can modify the
> device tree we have, with live tree yes? So, the whole series in
> question here can be done without modifying the base DT and getting in
> to the further discussion
On Thu, Jan 19, 2023 at 09:54:29AM -0700, Simon Glass wrote:
> Hi Sudeep,
>
> On Thu, 19 Jan 2023 at 09:46, Sudeep Holla wrote:
> >
> > Thanks for the details. But IIRC this discussion is not about the FF-A bus
> > and device(partitions) discovery, but the support for FF-A itself. The
> > discuss
On Thu, Jan 19, 2023 at 09:54:29AM -0700, Simon Glass wrote:
> Hi Sudeep,
>
> On Thu, 19 Jan 2023 at 09:46, Sudeep Holla wrote:
> >
> > Hi Abdellatif,
> >
> > On Thu, Jan 19, 2023 at 04:31:57PM +, Abdellatif El Khlifi wrote:
> > >
> > > Hi Simon, Tom,
> > >
> > > The FF-A transport is a SW bu
Hi Simon,
(sorry we just crossed the emails)
On Thu, Jan 19, 2023 at 09:41:12AM -0700, Simon Glass wrote:
>
> Can you add a DT node for the 'FF-A SW interfaces' and attach some
> sort of top-level driver to that? Perhaps simple-bus, or your own
> thing? You don't need to add compatible strings fo
Hi Sudeep,
On Thu, 19 Jan 2023 at 09:46, Sudeep Holla wrote:
>
> Hi Abdellatif,
>
> On Thu, Jan 19, 2023 at 04:31:57PM +, Abdellatif El Khlifi wrote:
> >
> > Hi Simon, Tom,
> >
> > The FF-A transport is a SW bus and is not associated to any HW peripheral or
> > undiscoverable base address.
>
Hi Abdellatif,
On Thu, Jan 19, 2023 at 04:31:57PM +, Abdellatif El Khlifi wrote:
>
> Hi Simon, Tom,
>
> The FF-A transport is a SW bus and is not associated to any HW peripheral or
> undiscoverable base address.
>
> There is only 1 way of discovering the FF-A bus and it's through the FF-A SW
>
On Thu, Jan 19, 2023 at 09:41:12AM -0700, Simon Glass wrote:
> Hi Abdellatif,
>
> On Thu, 19 Jan 2023 at 09:32, Abdellatif El Khlifi
> wrote:
> >
> > On Wed, Jan 18, 2023 at 08:59:32AM -0500, Tom Rini wrote:
> > > On Wed, Jan 18, 2023 at 01:46:54PM +, Sudeep Holla wrote:
> > > > On Wed, Jan 1
Hi Abdellatif,
On Thu, 19 Jan 2023 at 09:32, Abdellatif El Khlifi
wrote:
>
> On Wed, Jan 18, 2023 at 08:59:32AM -0500, Tom Rini wrote:
> > On Wed, Jan 18, 2023 at 01:46:54PM +, Sudeep Holla wrote:
> > > On Wed, Jan 18, 2023 at 12:49 PM Tom Rini wrote:
> > >
> > > >
> > > > I guess the proble
On Thu, Jan 19, 2023 at 04:31:57PM +, Abdellatif El Khlifi wrote:
> On Wed, Jan 18, 2023 at 08:59:32AM -0500, Tom Rini wrote:
> > On Wed, Jan 18, 2023 at 01:46:54PM +, Sudeep Holla wrote:
> > > On Wed, Jan 18, 2023 at 12:49 PM Tom Rini wrote:
> > >
> > > >
> > > > I guess the problem come
On Wed, Jan 18, 2023 at 08:59:32AM -0500, Tom Rini wrote:
> On Wed, Jan 18, 2023 at 01:46:54PM +, Sudeep Holla wrote:
> > On Wed, Jan 18, 2023 at 12:49 PM Tom Rini wrote:
> >
> > >
> > > I guess the problem comes down to, can we have one discovery method that
> > > everyone shares, or do we h
Hi Jonas,
On Thu, 19 Jan 2023 at 05:40, Jonas Karlman wrote:
>
> Hi Simon,
>
> On 2023-01-18 20:42, Simon Glass wrote:
> > Hi Jonas,
> >
> > On Tue, 17 Jan 2023 at 15:54, Jonas Karlman wrote:
> >>
> >> Add support to indicate what alignment to use for the FIT and its
> >> external data. Pass the
Hi Svyatoslav,
On Thu, 19 Jan 2023 at 00:12, Svyatoslav Ryhel wrote:
>
> ср, 18 січ. 2023 р. о 21:42 Simon Glass пише:
> >
> > Hi Svyatoslav,
> >
> > On Wed, 18 Jan 2023 at 01:44, Svyatoslav Ryhel wrote:
> > >
> > > Add timer support for T20/T30/T114 and T124 based devices.
> > > Driver is base
On Thu, 19 Jan 2023 at 05:56, John Keeping wrote:
>
> The highest register on ACT8846 is 0xf5, so set the number of registers
> to 0xf6, ensuring that the pmic read/write commands are able to access
> all of the supported registers (and many that are not valid, since the
> register space is quite
On Thu, 19 Jan 2023 at 03:24, Marcel Ziswiler
wrote:
>
> Hi Simon
>
> On Wed, 2023-01-18 at 21:11 -0500, Simon Glass wrote:
> > On Fri, 2023-01-13 at 08:50 -0500, Maxim Cournoyer wrote:
> > > This reverts commit 648d8186dd7f9c444fb07f355090d275dcdd4de4, because
> > > it broke usage of patman on Li
On Thu, 19 Jan 2023 at 05:55, John Keeping wrote:
>
> Add the related include files to the power MAINTAINERS entry.
>
> Signed-off-by: John Keeping
> ---
> MAINTAINERS | 1 +
> 1 file changed, 1 insertion(+)
>
Reviewed-by: Simon Glass
On Thu, 19 Jan 2023 at 08:22, Heinrich Schuchardt
wrote:
>
> The readme file for buildman is called buildman.rst.
>
> Signed-off-by: Heinrich Schuchardt
> ---
> tools/buildman/toolchain.py | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Reviewed-by: Simon Glass
On 1/19/23 15:29, Ilias Apalodimas wrote:
"Unable to find TPMv2 device" doesn't explain much with regards to the
error origin. Update it to match what we have in the RNG protocol
installation.
Signed-off-by: Ilias Apalodimas
Reviewed-by: Heinrich Schuchardt
---
lib/efi_loader/efi_tcg2.c
On Thu, 19 Jan 2023 at 17:17, Tom Rini wrote:
>
> On Thu, Jan 19, 2023 at 04:16:24PM +0100, Heinrich Schuchardt wrote:
> > On 1/19/23 16:13, Tom Rini wrote:
> > > On Thu, Jan 19, 2023 at 04:11:48PM +0100, Heinrich Schuchardt wrote:
> > >
> > > > UEFI applications call file system functions to dete
The readme file for buildman is called buildman.rst.
Signed-off-by: Heinrich Schuchardt
---
tools/buildman/toolchain.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/buildman/toolchain.py b/tools/buildman/toolchain.py
index 38b0dea8c7..ea1ad1bcb8 100644
--- a/tools/bu
On Thu, Jan 19, 2023 at 04:16:24PM +0100, Heinrich Schuchardt wrote:
> On 1/19/23 16:13, Tom Rini wrote:
> > On Thu, Jan 19, 2023 at 04:11:48PM +0100, Heinrich Schuchardt wrote:
> >
> > > UEFI applications call file system functions to determine if a file
> > > exists.
> > > The return codes are
On 1/19/23 16:13, Tom Rini wrote:
On Thu, Jan 19, 2023 at 04:11:48PM +0100, Heinrich Schuchardt wrote:
UEFI applications call file system functions to determine if a file exists.
The return codes are evaluated to show appropriate messages.
U-Boot's file system layer should not interfere with th
On Thu, Jan 19, 2023 at 04:11:48PM +0100, Heinrich Schuchardt wrote:
> UEFI applications call file system functions to determine if a file exists.
> The return codes are evaluated to show appropriate messages.
> U-Boot's file system layer should not interfere with the output.
>
> Rename file_fat_
On Thu, Jan 19, 2023 at 4:11 PM Ilias Apalodimas
wrote:
>
> Since I do have a look on TEE patches regardless and Jens doesn't have
> his own tree, add myself as a co-maintainer. I'll be carrying over the
> TEE related patches from now own. While at it add the maintenance tree
from now on.
> fo
1 - 100 of 181 matches
Mail list logo
