Hi
On Fri, Dec 9, 2022 at 8:53 AM wrote:
>
> On 12/8/22 18:18, Michael Nazzareno Trimarchi wrote:
> > Hi
> >
> > On Thu, Dec 8, 2022 at 5:12 PM wrote:
> >>
> >> On 10/25/22 13:51, Balamanikandan Gunasundar wrote:
> >>> Change include:
> >>>
> >>> - Adapt GPIO descriptor apis for U-Boot. Use
>
On 12/8/22 18:18, Michael Nazzareno Trimarchi wrote:
> Hi
>
> On Thu, Dec 8, 2022 at 5:12 PM wrote:
>>
>> On 10/25/22 13:51, Balamanikandan Gunasundar wrote:
>>> Change include:
>>>
>>> - Adapt GPIO descriptor apis for U-Boot. Use
>>> gpio_request_by_name_nodev, dm_gpio_get_value etc.
>>> -
On Thu, Dec 08, 2022 at 08:45:09PM -0600, Rob Herring wrote:
> The 'base' GPIO controller property is unused in u-boot and Linux. It is
> also not documented in the binding. So drop it.
>
> Signed-off-by: Rob Herring
> ---
> arch/arm/dts/synquacer-sc2a11.dtsi | 1 -
> 1 file changed, 1
On Thu, Dec 08, 2022 at 08:45:08PM -0600, Rob Herring wrote:
> 'active_clk_edges' and 'chipselect_num' SPI controller properties are
> unused in u-boot and Linux. They are also not documented in the binding.
> So drop them.
>
> Signed-off-by: Rob Herring
> ---
>
Hello Heinrich and all,
Thanks for the feedback.
On Thu, 8 Dec 2022 at 10:10, Heinrich Schuchardt wrote:
>
> Am 8. Dezember 2022 09:01:26 MEZ schrieb Ilias Apalodimas
> :
> >Hi Heinrich
> >
> >On Thu, Dec 08, 2022 at 05:12:26AM +0100, Heinrich Schuchardt wrote:
> >> On 12/7/22 16:11, Etienne
Hi Tony,
On 12/9/22 04:55, Tony Dinh wrote:
Hi Simon et al,
(Resend to include u-boot mailing list)
I'm in the process of converting Kirkwood boards to use DM SERIAL. I
could not seem to get it to work, having tried adding
CONFIG_DM_SERIAL, and also playing with various related CONFIG
+ Jassi
On Fri, 9 Dec 2022 at 11:45, Rob Herring wrote:
>
> The 'base' GPIO controller property is unused in u-boot and Linux. It is
> also not documented in the binding. So drop it.
>
> Signed-off-by: Rob Herring
> ---
> arch/arm/dts/synquacer-sc2a11.dtsi | 1 -
> 1 file changed, 1
+ Jassi
On Fri, 9 Dec 2022 at 11:45, Rob Herring wrote:
>
> 'active_clk_edges' and 'chipselect_num' SPI controller properties are
> unused in u-boot and Linux. They are also not documented in the binding.
> So drop them.
>
> Signed-off-by: Rob Herring
> ---
>
Hi Simon et al,
(Resend to include u-boot mailing list)
I'm in the process of converting Kirkwood boards to use DM SERIAL. I
could not seem to get it to work, having tried adding
CONFIG_DM_SERIAL, and also playing with various related CONFIG
options (CONFIG_SPECIFY_CONSOLE_INDEX and
Use log_warning() instead of printf() to print out driver information
Signed-off-by: Pengfei Fan
Reviewed-by: Simon Glass
---
drivers/spi/sh_qspi.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/drivers/spi/sh_qspi.c b/drivers/spi/sh_qspi.c
index 5ba8a8ea79..861423bef3
>From v1 to v2, the printf() in drivers/spi/sh_qspi.c was changed to
>log_warning().
Which avoids using __func__ to output driver information.
Pengfei Fan (2):
drivers: spi: fix some typos
drivers: spi: sh_qspi.c: Use log_warning() instead of printf()
drivers/spi/bcm63xx_hsspi.c | 2 +-
Fix some typos in spi drivers
Signed-off-by: Pengfei Fan
Reviewed-by: Simon Glass
---
drivers/spi/bcm63xx_hsspi.c | 2 +-
drivers/spi/cadence_qspi.c| 2 +-
drivers/spi/fsl_dspi.c| 4 ++--
drivers/spi/mtk_snfi_spi.c| 4 ++--
drivers/spi/mvebu_a3700_spi.c | 2 +-
'active_clk_edges' and 'chipselect_num' SPI controller properties are
unused in u-boot and Linux. They are also not documented in the binding.
So drop them.
Signed-off-by: Rob Herring
---
arch/arm/dts/synquacer-sc2a11-developerbox-u-boot.dtsi | 2 --
1 file changed, 2 deletions(-)
diff --git
The 'base' GPIO controller property is unused in u-boot and Linux. It is
also not documented in the binding. So drop it.
Signed-off-by: Rob Herring
---
arch/arm/dts/synquacer-sc2a11.dtsi | 1 -
1 file changed, 1 deletion(-)
diff --git a/arch/arm/dts/synquacer-sc2a11.dtsi
On 12/5/22 10:28, Szymon Heidrich wrote:
Prevent access to arbitrary memory locations in gen_ndis_set_resp
via manipulation of buf->InformationBufferOffset. Original
implementation permits manipulation of InformationBufferOffset to
exploit OID_GEN_CURRENT_PACKET_FILTER to set arbitrary memory
On 9/9/22 11:45, Patrick Delaunay wrote:
Add a new CONFIG_USB_HUB_DEBOUNCE_TIMEOUT to increase the
HUB_DEBOUNCE_TIMEOUT value, for example to 2s because some usb device
needs around 1.5s or more to make the hub port status to be
connected steadily after being powered off and powered on.
This 2s
On 12/8/22 22:00, Xavier Drudis Ferran wrote:
El Thu, Dec 08, 2022 at 09:12:08PM +0100, Marek Vasut deia:
On 12/8/22 17:53, Xavier Drudis Ferran wrote:
[...]
+++ b/drivers/phy/rockchip/phy-rockchip-inno-usb2.c
@@ -7,7 +7,7 @@
*/
#include
-#include
+#include
#include
#include
El Thu, Dec 08, 2022 at 09:12:08PM +0100, Marek Vasut deia:
> On 12/8/22 17:53, Xavier Drudis Ferran wrote:
>
> [...]
>
> > +++ b/drivers/phy/rockchip/phy-rockchip-inno-usb2.c
> > @@ -7,7 +7,7 @@
> >*/
> > #include
> > -#include
> > +#include
> > #include
> > #include
> >
On Sun, Dec 04, 2022 at 01:31:08PM +0100, Pali Rohár wrote:
> Replace 0x1b21 by macro PCI_VENDOR_ID_ASMEDIA with the same value.
>
> Signed-off-by: Pali Rohár
> Reviewed-by: Simon Glass
Applied to u-boot/next, thanks!
--
Tom
signature.asc
Description: PGP signature
On Thu, Dec 01, 2022 at 04:30:32PM +0100, kas...@krinvent.dk wrote:
> From: Kasper Revsbech
>
> When compling for x86:
> u-boot/fs/squashfs/sqfs.c:90: undefined reference to `__udivmoddi4'
>
> Signed-off-by: Kasper Revsbech
> Tested-by: Sean Nyekjaer
Applied to u-boot/next, thanks!
--
Tom
On Mon, Nov 28, 2022 at 09:41:22AM +0100, Max Krummenacher wrote:
> From: Max Krummenacher
>
> With LTO enabled the U-Boot initial environment is no longer stored
> in an easy accessible section in env/common.o. I.e. the section name
> changes from build to build, its content maybe compressed
On Fri, Nov 25, 2022 at 12:56:29PM +0100, Patrick Delaunay wrote:
> In scmi firmware driver, it is better to bind the scmi protocol driver
> "scmi_voltage_domain" with the node name of the protocol 17 and not
> the sub-node named "regulator", because is a fixed string which doesn't
> provide
On Wed, Nov 23, 2022 at 12:55:33PM +0100, Marc Kleine-Budde wrote:
> If the user select the image type "flat_dt" a FIT image will be build.
> This breaks the legacy use case of putting a Flat Device Tree into a
> legacy u-boot image.
>
> Add a new image type "fdt_legacy" to build a legacy u-boot
On Wed, Nov 23, 2022 at 12:55:32PM +0100, Marc Kleine-Budde wrote:
> In case there's no struct image_type_params::set_header callback, no
> "errno" will be set. Don't fail with an error message, followed by
> "Success". Remove the printing of the human readable "errno" value.
>
> Signed-off-by:
On Wed, Nov 23, 2022 at 02:31:03PM +0300, Mikhail Ilin wrote:
> The handle "fd" was created in fdtgrep.c:708 by calling the
> "open" function and is lost in fdtgrep.c:716 and fdtgrep.c:723.
> Close file descriptor 'fd' before exiting with an error from function
> utilfdt_read_err_len(const
On Wed, Nov 23, 2022 at 12:39:36PM +0300, Mikhail Ilin wrote:
> The copy_datafile(ifd, params.datafile) function has been
> implemented to copy data by reducing the number of lines in the main
> function.
>
> Signed-off-by: Mikhail Ilin
Applied to u-boot/next, thanks!
--
Tom
On Tue, Nov 22, 2022 at 11:00:55AM +0300, Mikhail Ilin wrote:
> Fixes: 934b14f2bb30 ("ext4: free allocations by parse_path()")
> Signed-off-by: Mikhail Ilin
Applied to u-boot/next, thanks!
--
Tom
signature.asc
Description: PGP signature
On Fri, Nov 18, 2022 at 02:50:24PM +0300, Mikhail Ilin wrote:
> An incorrect 1st parameter is passed to the fix_member()
> function. Should use a pointer to the beginning of the parent structure
> (bpdt or subpart_dir, because are boxed), not to their fields. Otherwise,
> this leads to an
On Fri, Nov 18, 2022 at 11:50:02AM +0300, Mikhail Ilin wrote:
> This will cause the local_time pointer is passed as the 4th argument
> to function strftime() to also point to NULL. This result in a
> segmentation fault. Thus, it's necessary to add a check of the local_time
> pointer to NULL.
On Thu, Oct 13, 2022 at 05:41:21PM +0900, Jaehoon Chung wrote:
> Fix unused-result warning about fread.
>
> tools/env/fw_env.c: In function ‘find_nvmem_device’:
> tools/env/fw_env.c:1751:3: warning: ignoring return value of ‘fread’,
> declared with attribute warn_unused_result [-Wunused-result]
On 12/8/22 17:53, Xavier Drudis Ferran wrote:
[...]
+++ b/drivers/phy/rockchip/phy-rockchip-inno-usb2.c
@@ -7,7 +7,7 @@
*/
#include
-#include
+#include
#include
#include
#include
@@ -168,6 +168,9 @@ static struct phy_ops rockchip_usb2phy_ops = {
.of_xlate =
On Thu, Dec 8, 2022 at 3:16 PM Detlev Casanova
wrote:
>
> In commit d0399a46e7cda63c07e3eb8558bef84cfb068028, the device tree was
> synchronized from linux and the aliases were dropped.
>
> They need to be kept so that the mmc cards are in the right order.
> Without the aliases, u-boot reports:
>
In commit d0399a46e7cda63c07e3eb8558bef84cfb068028, the device tree was
synchronized from linux and the aliases were dropped.
They need to be kept so that the mmc cards are in the right order.
Without the aliases, u-boot reports:
MMC: FSL_SDHC: 2, FSL_SDHC: 3
With the aliases, u-boot reports:
Hi Sergei,
On Fri, 9 Dec 2022 at 00:50, Sergei Antonov wrote:
>
> On Thu, 8 Dec 2022 at 00:52, Simon Glass wrote:
> > > > Is this some sort of I2C protocol?
> > >
> > > Like I2C it uses a pin for clock and a pin for data in/out. Unlike I2C
> > > it does not use addressing. I am not sure whether
On Thu, Dec 08, 2022 at 03:57:40PM +0100, Patrice CHOTARD wrote:
> Hi Tom,
>
> Please pull the STM32 related patches for v2023.01-rc4.
>
> CI status:
> https://source.denx.de/u-boot/custodians/u-boot-stm/-/pipelines/13840
>
> There is an error which is fixed with following patch:
>
On Thu, Dec 08, 2022 at 03:47:18PM +0100, Marek Vasut wrote:
> Small fixes MR:
>
> The following changes since commit 14f2d087a3d6347ba0ff7a7e9aaff6955e53e7a8:
>
> Merge tag 'sound-2023-01-rc4' of
> https://source.denx.de/u-boot/custodians/u-boot-efi (2022-12-06 10:07:01
> -0500)
>
> are
Hi Xavier,
On Fri, 9 Dec 2022 at 03:25, Xavier Drudis Ferran wrote:
>
> El Thu, Dec 08, 2022 at 08:56:57AM +1300, Simon Glass deia:
> > + @tee-SEQ {
> > + fit,operation = "split-elf";
> > +
arch/arm/dts/rk3399.dtsi has a node
usb_host0_ehci: usb@fe38 {
compatible = "generic-ehci";
with clocks:
clocks = < HCLK_HOST0>, < HCLK_HOST0_ARB>,
<>;
The first 2 refer to nodes with class UCLASS_CLK, but
has class UCLASS_PHY.
u2phy0: usb2phy@e450 {
Hi Detlev,
[Please keep Troy on Cc as he is the board maintainer]
Subject should be:
imx6q-sabrelite: Re-add mmc aliases
On Thu, Dec 8, 2022 at 12:23 PM Detlev Casanova
wrote:
>
> In commit d0399a46e7cda63c07e3eb8558bef84cfb068028, the device tree was
> synchronized from linux and the aliases
On 08/12/2022 04:01, Rob Kramer wrote:
> Hi all,
>
> I have a RK3288 board from a Chinese display vendor that came with the
> usual giant Rockchip tarball that they patched here and there to make
> the board work. It seems to be based on a rk3288-evb, since that is what
> they patched in the
On Thu, Dec 08, 2022 at 11:23:37AM +, Leo Liang wrote:
> Hi Tom,
>
> The following changes since commit 14f2d087a3d6347ba0ff7a7e9aaff6955e53e7a8:
>
> Merge tag 'sound-2023-01-rc4' of
> https://source.denx.de/u-boot/custodians/u-boot-efi (2022-12-06 10:07:01
> -0500)
>
> are available
On Thu, Dec 08, 2022 at 11:08:16AM +, eugen.hris...@microchip.com wrote:
> Hello Tom,
>
> Please pull tag u-boot-at91-fixes-2023.01-b , the second set of at91
> fixes for the 2023.01 cycle.
>
> This is a single tiny fix that allows the correct name for one pin on
> sama7g5 device. People
Hi
On Thu, Dec 8, 2022 at 5:12 PM wrote:
>
> On 10/25/22 13:51, Balamanikandan Gunasundar wrote:
> > Change include:
> >
> > - Adapt GPIO descriptor apis for U-Boot. Use
> >gpio_request_by_name_nodev, dm_gpio_get_value etc.
> > - Use U_BOOT_DRIVER instead of platform_driver.
> > - Replace
On 10/25/22 13:51, Balamanikandan Gunasundar wrote:
> Change include:
>
> - Adapt GPIO descriptor apis for U-Boot. Use
>gpio_request_by_name_nodev, dm_gpio_get_value etc.
> - Use U_BOOT_DRIVER instead of platform_driver.
> - Replace struct platform_device with struct udevice
> - Check the
On Sun, Dec 04, 2022 at 01:36:55PM +0100, Pali Rohár wrote:
> U-Boot serial code already handles -EAGAIN value from getc and putc
> callbacks. So change drivers code to return -EAGAIN when HW is busy instead
> of doing its own busy loop and waiting until HW is ready.
>
> Signed-off-by: Pali
In commit d0399a46e7cda63c07e3eb8558bef84cfb068028, the device tree was
synchronized from linux and the aliases were dropped.
They need to be kept so that the mmc cards are in the right order.
Without the aliases, u-boot reports:
MMC: FSL_SDHC: 2, FSL_SDHC: 3
With the aliases, u-boot reports:
Hi Tom,
Please pull the STM32 related patches for v2023.01-rc4.
CI status: https://source.denx.de/u-boot/custodians/u-boot-stm/-/pipelines/13840
There is an error which is fixed with following patch:
Small fixes MR:
The following changes since commit 14f2d087a3d6347ba0ff7a7e9aaff6955e53e7a8:
Merge tag 'sound-2023-01-rc4' of
https://source.denx.de/u-boot/custodians/u-boot-efi (2022-12-06 10:07:01
-0500)
are available in the Git repository at:
git://source.denx.de/u-boot-usb.git
El Thu, Dec 08, 2022 at 08:56:57AM +1300, Simon Glass deia:
> + @tee-SEQ {
> + fit,operation = "split-elf";
> + description = "TEE";
> + type = "tee";
> +
On 12/8/22 14:53, Patrice CHOTARD wrote:
On 12/8/22 14:27, Marek Vasut wrote:
On 12/8/22 09:19, Patrice CHOTARD wrote:
Hi Marek
Hello Patrice,
I am preparing a STM32 pull request which includes this series
On 12/8/22 14:27, Marek Vasut wrote:
> On 12/8/22 09:19, Patrice CHOTARD wrote:
>> Hi Marek
>
> Hello Patrice,
>
>> I am preparing a STM32 pull request which includes this series
>>
>> https://patchwork.ozlabs.org/project/uboot/patch/20221206023515.113556-1-ma...@denx.de/
>>
>> We got a DFU
This series includes refactoring and bugfix of GetNextVariableName
calls in eficonfig.
After "eficonfig: curve out efi_get_next_variable_name_int calls" patch
is merged, I will send the follow-up patch to use common function in
cmd/efidebug.c and cmd/nvedit_efi.c. These files also implement
alloc
The current code calls efi_set_variable_int() to delete the
invalid boot option between calls to efi_get_next_variable_name_int(),
it may produce unpredictable results.
This commit moves removal of the invalid boot option outside
of the efi_get_next_variable_name_int() calls.
EFI_NOT_FOUND
To retrieve the EFI variable name by efi_get_next_variable_name_int(),
the sequence of alloc -> efi_get_next_variable_name_int ->
realloc -> efi_get_next_variable_name_int is required.
In current code, this sequence repeatedly appears in
the several functions. It should be curved out a common
Hi,
>> I'm not really happy with this approach. It's not that upstream doesn't
>> have aliases now, it's that it has different aliases, right? That's why
>> they won't accept these?
>
> imx6q.dtsi does have the default mmc aliases:
>
> mmc0 =
> mmc1 =
> mmc2 =
> mmc3 =
>
> Upstream does
On 12/8/22 09:19, Patrice CHOTARD wrote:
Hi Marek
Hello Patrice,
I am preparing a STM32 pull request which includes this series
https://patchwork.ozlabs.org/project/uboot/patch/20221206023515.113556-1-ma...@denx.de/
We got a DFU compilation issue with this series :
arm: +
Add initial version of device tree for Meta Greatlakes BMC which is
equipped with Aspeed AST2600 BMC SoC.
Signed-off-by: Delphine CC Chiu
---
arch/arm/dts/Makefile | 1 +
arch/arm/dts/ast2600-greatlakes.dts | 191 ++
Hi all,
I have a RK3288 board from a Chinese display vendor that came with the
usual giant Rockchip tarball that they patched here and there to make
the board work. It seems to be based on a rk3288-evb, since that is what
they patched in the kernel. The kernel is a 4.4 kernel with Android
On Thu, 8 Dec 2022 at 00:52, Simon Glass wrote:
> > > Is this some sort of I2C protocol?
> >
> > Like I2C it uses a pin for clock and a pin for data in/out. Unlike I2C
> > it does not use addressing. I am not sure whether this driver can
> > utilize some of the existing I2C code in U-Boot. Wrote
Hi Tom,
The following changes since commit 14f2d087a3d6347ba0ff7a7e9aaff6955e53e7a8:
Merge tag 'sound-2023-01-rc4' of
https://source.denx.de/u-boot/custodians/u-boot-efi (2022-12-06 10:07:01 -0500)
are available in the Git repository at:
Hello Tom,
Please pull tag u-boot-at91-fixes-2023.01-b , the second set of at91
fixes for the 2023.01 cycle.
This is a single tiny fix that allows the correct name for one pin on
sama7g5 device. People with DT coming from Linux will have build errors
without this if they add NAND device.
Enable the OHCI and EHCI related configs required in order to be
able to use the USB command properly.
Signed-off-by: Sergiu Moga
---
v1 -> v2:
- No change
configs/sama5d27_som1_ek_mmc1_defconfig| 5 +
configs/sama5d27_som1_ek_mmc_defconfig | 5 +
From: Cristian Birsan
The `ohci_register` function expects that the OHCI driver's
priv is a struct whose first field is of type `ohci_t`.
The original conversion to DM did not have it and this
inconsistency revealed itself whenever U-Boot required
multiple memory allocations resulting in a
Add the pinctrl nodes required by the USB related DT nodes.
Signed-off-by: Sergiu Moga
---
v1 -> v2:
- No change
arch/arm/dts/at91-sama5d27_wlsom1_ek.dts | 25
1 file changed, 25 insertions(+)
diff --git a/arch/arm/dts/at91-sama5d27_wlsom1_ek.dts
Add the pinctrl subnodes required by the USB related DT nodes.
Signed-off-by: Sergiu Moga
---
v1 -> v2:
- No change
arch/arm/dts/at91-sama5d2_icp.dts | 22 ++
1 file changed, 22 insertions(+)
diff --git a/arch/arm/dts/at91-sama5d2_icp.dts
Enable USB and RESET functionality. In order for USB to
work properly on SAMA7, the driver needs to be able
to have access to PHY's, which, in turn, need to have
access to the RSTC driver's assert/deassert functionalities.
Signed-off-by: Sergiu Moga
Tested-by: Mihai Sain
---
v1 -> v2:
- No
Add the ability to enable/disable whatever USB PHY's are
passed to the AT91 OHCI driver through DT.
Signed-off-by: Sergiu Moga
Tested-by: Mihai Sain
---
v1 -> v2:
- No change
drivers/usb/host/ohci-at91.c | 31 +++
1 file changed, 31 insertions(+)
diff --git
In order to have USB functionality, drivers for SAMA7's
USB 2.0 PHY's have been added. There is one driver
for UTMI clock's SFR and RESET required functionalities and
one for its three possible subclocks of the phy's themselves.
In order for this layout to properly work in conjunction with
CCF and
Add support for at91 reset controller's basic assert/deassert
operations. Since this driver conflicts with the
SYSRESET driver because they both bind to the same RSTC node,
implement a custom bind hook that would manually bind the
sysreset driver, if enabled, to the same RSTC DT node.
Furthermore,
From: Cristian Birsan
Special Function Registers(SFR) definitions for SAMA7 product family.
Signed-off-by: Cristian Birsan
Signed-off-by: Sergiu Moga
---
v1 -> v2:
- No change
arch/arm/mach-at91/include/mach/sama7-sfr.h | 59 +
1 file changed, 59 insertions(+)
create
Add definitions for an additional main UTMI clock as well as its
respective subclocks.
Signed-off-by: Sergiu Moga
---
v1 -> v2:
- No change
include/dt-bindings/clk/at91.h | 5 +
1 file changed, 5 insertions(+)
diff --git a/include/dt-bindings/clk/at91.h b/include/dt-bindings/clk/at91.h
Add the USB related DT nodes for the sama7g5ek board.
Signed-off-by: Sergiu Moga
---
v1 -> v2:
- No change
arch/arm/dts/at91-sama7g5ek.dts | 34 +++
arch/arm/dts/sama7g5.dtsi | 73 +
2 files changed, 107 insertions(+)
diff --git
Add the configs required to use the USB-related functionalities within
the bootloader.
Signed-off-by: Sergiu Moga
---
v1 -> v2:
- No change
configs/sam9x60ek_mmc_defconfig | 10 ++
configs/sam9x60ek_nandflash_defconfig | 10 ++
configs/sam9x60ek_qspiflash_defconfig |
Upstream linux commit 5994f58977e0.
Add reset bindings for SAMA7G5. At the moment only USB PHYs are
included.
Signed-off-by: Sergiu Moga
---
v1 -> v2:
- No change
include/dt-bindings/reset/sama7g5-reset.h | 10 ++
1 file changed, 10 insertions(+)
create mode 100644
Register the OHCI driver into DM by properly initializing the required
clocks and pins required by the DT node of OHCI. In order for the VBUS
to stay enabled, a `child_pre_probe` method has been added to overcome
the DM core disabling it in `usb_scan_device`: when the generic
`device_probe` method
In order for some of the functionalities, such as the USB clocks,
to work properly we need some clocks to be properly initialised
at the very beginning of booting.
Signed-off-by: Sergiu Moga
---
v1 -> v2:
- Adapted according to the additional 04/19 PATCH, now making use of
`at91_clk_setup`
Register into DM the clocks required to properly enable USB functionality
within the bootloader.
Signed-off-by: Sergiu Moga
---
v1 -> v2:
- No change
drivers/clk/at91/sam9x60.c | 37 +
1 file changed, 37 insertions(+)
diff --git
From: Claudiu Beznea
Clock setup was intended for setting clocks at boot time on SAMA7G5,
e.g. for root clocks like PLLs, that were used to feed IPs needed alive
in u-boot (e.g. Ethernet clock feed by a PLL). Export this functionality
to all at91 clocks as it may be necessary on other SoCs.
Implement sam9x60 USB clock driver. This clock has
three parents: PLLA, UPLL and MAINXTAL. The driver is
aware of the three possible parents with the help of the
two mux tables provied to the driver during the registration
of the clock.
Signed-off-by: Sergiu Moga
---
v1 -> v2:
- No change
Add the OHCI and EHCI DT nodes for the sam9x60 board.
Signed-off-by: Sergiu Moga
---
v1 -> v2:
- No change
arch/arm/dts/sam9x60.dtsi | 18 ++
arch/arm/dts/sam9x60ek.dts | 21 +
2 files changed, 39 insertions(+)
diff --git a/arch/arm/dts/sam9x60.dtsi
This series of patches is meant to add support for USB Mass Storage
on SAM9X60, SAMA7G5 and SAMA5D2 boards and register ohci-at91 driver into
Driver Model. In order for this to be achieved, the respective
DT nodes have been added, the USB clock has been registered into CCF
and the required
Hi Heinrich,
On Thu, 8 Dec 2022 at 18:05, Heinrich Schuchardt wrote:
>
> Am 8. Dezember 2022 09:01:26 MEZ schrieb Ilias Apalodimas
> :
> >Hi Heinrich
> >
> >On Thu, Dec 08, 2022 at 05:12:26AM +0100, Heinrich Schuchardt wrote:
> >> On 12/7/22 16:11, Etienne Carriere wrote:
> >> > Measures the
Am 8. Dezember 2022 09:01:26 MEZ schrieb Ilias Apalodimas
:
>Hi Heinrich
>
>On Thu, Dec 08, 2022 at 05:12:26AM +0100, Heinrich Schuchardt wrote:
>> On 12/7/22 16:11, Etienne Carriere wrote:
>> > Measures the DTB passed to the EFI application upon new boolean config
>> > switch
Hi Marek
I am preparing a STM32 pull request which includes this series
https://patchwork.ozlabs.org/project/uboot/patch/20221206023515.113556-1-ma...@denx.de/
We got a DFU compilation issue with this series :
arm: + stm32mp15_dhcom_basic
The two configuration CONFIG_MTDIDS_DEFAULT and CONFIG_MTDPARTS_DEFAULT
are not needed with mtd configuration CONFIG_SYS_MTDPARTS_RUNTIME which
allows the MTDIDS and MTDPARTS to be configured at runtime.
This patch has no defconfig impacts because CONFIG_SYS_MTDPARTS_RUNTIME
is only used by two
Hi Heinrich
On Thu, Dec 08, 2022 at 05:12:26AM +0100, Heinrich Schuchardt wrote:
> On 12/7/22 16:11, Etienne Carriere wrote:
> > Measures the DTB passed to the EFI application upon new boolean config
> > switch CONFIG_EFI_TCG2_PROTOCOL_MEASURE_DTB. For platforms where the
> > content of the DTB
86 matches
Mail list logo
