On Wednesday 04 January 2023 08:50:28 Pali Rohár wrote:
> Hello!
>
> On Tuesday 03 January 2023 17:55:41 Tony Dinh wrote:
> > Hi Pali,
> >
> > I'm building a new u-boot for the Thecus N2350 board (Armada 385
> > dual-core 1Ghz 1GB DDR4). The trouble with this board is DDR4, which
> > is not curre
Hello!
On Tuesday 03 January 2023 17:55:41 Tony Dinh wrote:
> Hi Pali,
>
> I'm building a new u-boot for the Thecus N2350 board (Armada 385
> dual-core 1Ghz 1GB DDR4). The trouble with this board is DDR4, which
> is not currently supported in u-boot (also cc this to Chris for
> commenting about M
On Tue, 3 Jan 2023 at 22:42, Eddie James wrote:
>
> tmpu -> tpmu
>
> Signed-off-by: Eddie James
> ---
> include/tpm-v2.h | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/include/tpm-v2.h b/include/tpm-v2.h
> index 737e57551d..85feda3e06 100644
> --- a/include/tpm-v2.h
Hi Eddie,
Thanks for the patch
Looking at the patch there's a lot of code duplication with
lib/efi_loader/efi_tcg2.c.
Any reason why we aren't reusing that ?
Regards
/Ilias
On Tue, 3 Jan 2023 at 22:42, Eddie James wrote:
>
> This series adds support for measuring the boot images more genericall
On 04/01/23 00:33, Fabio Estevam wrote:
Printing the I2C controller base address in decimal notation
is not helpful.
Change it to hex notation, which is the standard format found
in the Reference Manual and devicetree.
Agree
Signed-off-by: Fabio Estevam
---
Acked-by: Dhruva Gole
On 12/23/22 08:47, Mihai Sain wrote:
> Add node for sdhci1 controller and its pinctrl.
>
> Signed-off-by: Mihai Sain
> ---
Applied to u-boot-at91/next, thanks !
On 12/23/22 08:43, Mihai Sain wrote:
> Add new config for storing environment from SDMMC1.
>
> Signed-off-by: Mihai Sain
> ---
Applied to u-boot-at91/next, thanks !
On 12/23/22 08:39, Mihai Sain wrote:
> Set blue led on at boot time in order to highlight that u-boot is loaded.
> This is done for all sam9x60 based boards which contain an RGB led.
>
> Signed-off-by: Mihai Sain
> ---
Applied to u-boot-at91/next, thanks !
On 1/3/23 01:12, Marek Vasut wrote:
> On 12/23/22 13:33, Sergiu Moga wrote:
>> Add the OHCI and EHCI DT nodes for the sam9x60 boards.
>>
>> Signed-off-by: Sergiu Moga
>> ---
>> arch/arm/dts/at91-sam9x60_curiosity.dts | 21 +
>> arch/arm/dts/sam9x60.dtsi | 18 ++
Hi Roger,
applied to nand-next
Thanks and regards,
Dario
On Tue, Dec 20, 2022 at 11:22 AM Roger Quadros wrote:
>
> Hi Michael & Dario,
>
> This series adds driver model support for rawnand: omap_gpmc
> and omap_elm drivers.
>
> This will enable the driver to be used on K2/K3 platforms as well.
On 1/3/23 18:00, Marek Vasut wrote:
> On 1/3/23 16:56, sergiu.m...@microchip.com wrote:
>> On 03.01.2023 17:47, Marek Vasut wrote:
>>> On 1/3/23 16:35, Sergiu Moga wrote:
Add the OHCI and EHCI DT nodes for the sam9x60 SoC's.
Signed-off-by: Sergiu Moga
---
v1 -> v2:
>>
Hi Sinthu
On 27/12/22 17:45, Sinthu Raja wrote:
From: Sinthu Raja
Add the board_init_f API for SPL and run the platform-required SoC
initialization.
Add the functionality for board name-based DTB selection from FIT
within SPL. This will make it easier to utilise one defconfig for
both the EVM
-nand-20230103
for you to fetch changes up to 49bf9d131284b75787dd2e6941d0e9a46d35eeb3:
mtd: rawnand: omap_elm: u-boot driver model support (2023-01-03
11:21:04 +0100)
Gitlab CI showed no issues:
https://source.denx.de/u-boot/custodians/u-boot-nand-flash/-/pipelines/14563
On Tue, Dec 27, 2022 at 5:46 PM Sinthu Raja
wrote:
>
> From: Sinthu Raja
>
> Hi All,
> This series of patch add initial support for AM68 starter kit.
> Design files can be referrred from https://www.ti.com/lit/zip/SPRR463
>
> Refer below link to J721S2/AM68 Technical Reference Manual for further
在 2023-01-03星期二的 17:38 +，Andre Przywara写道：
> On Tue, 06 Dec 2022 13:55:02 +0800
> Icenowy Zheng wrote:
>
> Hi Icenowy,
>
> > 在 2022-12-06星期二的 00:45 +，Andre Przywara写道：
> > > This adds the basic SoC .dtsi devicetree stub for the Allwinner
> > > T113s
> > > SoC. This shares a die with the
The fields ConsoleInHandle, ConsoleOutHandle, ConsoleErrHandle must point
to the handles with the respective console protocols. Failure to do so
leads to an error in the EFI Shell:
No SimpleTextInputEx was found. CTRL-based features are not usable.
Signed-off-by: Heinrich Schuchardt
---
lib
On the vexpress_ca9x4 $loadaddr points to a memory area used by the EFI
sub-system. Use the same value as $kernel_addr_r which is safe.
Signed-off-by: Heinrich Schuchardt
---
include/configs/vexpress_common.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/include/configs/vexpress_common.h
Add reservations for all EFI memory areas that are not
EFI_CONVENTIONAL_MEMORY.
Signed-off-by: Heinrich Schuchardt
---
lib/lmb.c | 45 +
1 file changed, 45 insertions(+)
diff --git a/lib/lmb.c b/lib/lmb.c
index c599608fa3..aee2617593 100644
--- a/lib/
As reported in Debian bug #1027176 relocation of the initrd may lead to
overwriting memory used by the EFI sub-system.
Currently the available memory for images is determined via the lmb
library functions. The lmb library has several shortcomings:
* It does not protect against overwriting one ima
On Wed, 28 Dec 2022 at 00:05, Ilias Apalodimas
wrote:
>
> On Sat, Dec 24, 2022 at 07:57:43AM +0900, Masahisa Kojima wrote:
> > This commit removes the change boot order specific
> > menu implementation. The change boot order implementation
> > calls eficonfig_process_common() same as other menus.
On Tue, 27 Dec 2022 at 23:55, Ilias Apalodimas
wrote:
>
>
> This looks correct to me.
> Heinrich can you check if that solves your scrolling issues?
>
> On Sat, Dec 24, 2022 at 07:57:44AM +0900, Masahisa Kojima wrote:
> > The current eficonfig menu does not support vertical scroll,
> > so it can n
> On Wed, Jan 4, 2023 at 10:08 AM Rick Chen wrote:
> >
> > Original openSBI (without FW_PIC) will relocate itself
>
> nits: OpenSBI
>
> > from 0x100 to 0x0. After openSBI added FW_PIC codes,
>
> ditto
OK, will fix it.
>
> > it will not relocate any more and always run at 0x100.
> > Hence
Original OpenSBI (without FW_PIC) will relocate itself
from 0x100 to 0x0. After OpenSBI added FW_PIC codes,
it will not relocate any more and always run at 0x100.
Hence, it may overlap with Kernel memory region. So it is
necessary to change OpenSBI address from 0x100 to 0x0.
More detai
Hi Ilias,
On Tue, 27 Dec 2022 at 23:41, Ilias Apalodimas
wrote:
>
> Hi Kojima-san
>
>
> Overall I think the cleanup is nice and easier to maintain in the long
> run.
>
> On Sat, Dec 24, 2022 at 07:57:42AM +0900, Masahisa Kojima wrote:
> > Current change boot order implementation does not call
> >
On Wed, Jan 4, 2023 at 10:08 AM Rick Chen wrote:
>
> Original openSBI (without FW_PIC) will relocate itself
nits: OpenSBI
> from 0x100 to 0x0. After openSBI added FW_PIC codes,
ditto
> it will not relocate any more and always run at 0x100.
> Hence, it may overlap with Kernel memory reg
Original openSBI (without FW_PIC) will relocate itself
from 0x100 to 0x0. After openSBI added FW_PIC codes,
it will not relocate any more and always run at 0x100.
Hence, it may overlap with Kernel memory region. So it is
necessary to change openSBI address from 0x100 to 0x0.
More detai
Add src and dst address checking, if they
are the same address, just return and don't
copy data anymore.
Signed-off-by: Rick Chen
---
Changes in v3
- new patch: separate from [1/2]
---
arch/riscv/lib/memcpy.S | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/riscv/lib/memcpy.S b/arch/ri
When fit image boots from ram, the payload will
be prepared in the address of SPL_LOAD_FIT_ADDRESS.
In spl fit generic flow, it will malloc another
memory address and copy whole fit image to this
malloc address. But it is un-necessary for booting
from RAM.
This patch improves this flow by declare
> Hi Rick,
>
> On 1/3/23 02:20, Rick Chen wrote:
> > When fit image boots from ram, the payload will
> > be prepared in the address of SPL_LOAD_FIT_ADDRESS.
> > In spl fit generic flow, it will malloc another
> > memory address and copy whole fit image to this
> > malloc address. But it is un-nece
Hi Samuel
> On 1/3/23 02:18, Rick Chen wrote:
> > Original openSBI (without FW_PIC) will relocate itselt
>
> typo: itself
OK, I will fix it.
>
> > from 0x100 to 0x0. After openSBI added FW_PIC codes,
> > it will not relocate any more and alaways run at 0x100.
>
> typo: always
OK, I will
On Wed, 14 Dec 2022 00:14:49 -0600
Samuel Holland wrote:
Hi Samuel,
thanks for having a look!
> On 12/13/22 18:22, Andre Przywara wrote:
> > At the moment we have an #ifdef-protected routine in
> > board/sunxi/board.c, which sets up the arch timer CNTFRQ register, if
> > that hasn't been done a
On Sun, 11 Dec 2022 17:32:05 +0100
Jernej Skrabec wrote:
Hi Jernej,
> Current H616 DRAM driver is completely customized to Orange Pi Zero2
> board, which is currently the only H616 board supported by U-Boot.
> Needless to say, this is not ideal for adding new boards. With changes
> in this serie
On Sun, 11 Dec 2022 17:32:12 +0100
Jernej Skrabec wrote:
Hi Jernej,
> These values are highly board specific and thus make sense to add
> parameter for them. To ease adding support for new boards, let's make
> them same as in vendor DRAM settings.
So scrolling up and down: does this patch miss
On Sun, 11 Dec 2022 17:32:08 +0100
Jernej Skrabec wrote:
Hi Jernej,
> While ODT values for same memory type are similar, they are not
> necessary the same. Let's parameterize them and make parameter same as
> in vendor DRAM settings. That way it will be easy to introduce new board
> support.
ch
On Sun, 11 Dec 2022 17:32:07 +0100
Jernej Skrabec wrote:
Hi,
> Fix code style for pointer declaration. This is just cosmetic change to
> avoid checkpatch errors in later commits.
>
> Signed-off-by: Jernej Skrabec
confirmed to be just s/(u32\*)/(u32 *)/:
Reviewed-by: Andre Przywara
Cheers,
On Sun, 11 Dec 2022 17:32:06 +0100
Jernej Skrabec wrote:
> Vendor DRAM code actually writes to whole CR register and not just sets
> bit 31 in mctl_ctrl_init().
>
> Just to be safe, do that here too.
>
> Signed-off-by: Jernej Skrabec
Can't really verify this, but it seems to work (TM):
Acked
On Sun, 11 Dec 2022 17:32:10 +0100
Jernej Skrabec wrote:
> Vendor H616 DRAM code always configure part which we call ODT
> configuration. Let's reflect that here too.
I wonder if we need this patch at all. "depends on !H616" looks
counter-intuitive, since this suggests it's always off.
As it sta
On Sun, 11 Dec 2022 17:32:13 +0100
Jernej Skrabec wrote:
> Part of the code, previously known as "unknown feature" also doesn't
> have constant values. They are derived from TPR0 parameter in vendor
> DRAM code. Introduce that parameter here too, to ease adding new boards.
That seems to also mis
On Sun, 11 Dec 2022 17:32:11 +0100
Jernej Skrabec wrote:
> Mentioned function result is always true and result isn't checked
> anyway. Let's make it void.
>
> Signed-off-by: Jernej Skrabec
Reviewed-by: Andre Przywara
Cheers,
Andre
> ---
> arch/arm/mach-sunxi/dram_sun50i_h616.c | 4 +---
>
CONFIG_VIDEO_COPY implemented a range based copying mechanism: If we
print a single character, it will always copy the full range of bytes
from the top left corner of the character to the lower right onto the
uncached frame buffer. This includes pretty much the full line contents
of the printed cha
Some drivers call video_set_flush_dcache() to indicate that they want to
have the dcache flushed for the frame buffer. These drivers benefit from
our new video damage control, because we can reduce the amount of memory
that gets flushed significantly.
This patch enables video damage control for al
The dcache flushing code path was conditional on ARM && !DCACHE config
options. However, dcaches exist on other platforms as well and may need
clearing if their driver requires it.
Simplify the compile logic and always enable the dcache flush logic in
the video core. That way, drivers can always r
Now that we have a damage area tells us which parts of the frame buffer
actually need updating, let's only dcache flush those on video_sync()
calls. With this optimization in place, frame buffer updates - especially
on large screen such as 4k displays - speed up significantly.
Signed-off-by: Alexa
Let's report the video damage when we draw a bitmap on the screen. This
way we can later lazily flush only relevant regions to hardware.
Signed-off-by: Alexander Graf
Reported-by: Da Xue
---
drivers/video/video_bmp.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/video/video_bmp.
Now that we have a damage tracking API, let's populate damage done by
UEFI payloads when they BLT data onto the screen.
Signed-off-by: Alexander Graf
Reported-by: Da Xue
---
v1 -> v2:
- Remove ifdefs from gop
v2 -> v3:
- Adapt to always assume DM is used
v3 -> v4:
- Skip damage on E
Now that we have a damage tracking API, let's populate damage done by
vidconsole drivers. We try to declare as little memory as damaged as
possible, with the exception of rotated screens that I couldn't get my
head wrapped around. On those, we revert to the old behavior and mark
the full screen as
We are going to introduce image damage tracking to fasten up screen
refresh on large displays. This patch adds damage tracking for up to
one rectangle of the screen which is typically enough to hold blt or
text print updates. Callers into this API and a reduced dcache flush
code path will follow in
Let's report the video damage when we clear the screen. This
way we can later lazily flush only relevant regions to hardware.
Signed-off-by: Alexander Graf
Reported-by: Da Xue
---
drivers/video/video-uclass.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/video/video-uclass.c b/d
This patch set speeds up graphics output on ARM by a factor of 60x.
On most ARM SBCs, we keep the frame buffer in DRAM and map it as cached,
but need it accessible by the display controller which reads directly
from a later point of consistency. Hence, we flush the frame buffer to
DRAM on every ch
This series adds support for measuring the boot images more generically
than the existing EFI support. The series includes optional measurement
from the bootm command.
Eventually the EFI code could be refactored to use the generic functions.
Eddie James (3):
tpm: Fix spelling for tpmu_ha union
Add a configuration option to measure the boot through the bootm
function.
Signed-off-by: Eddie James
---
boot/bootm.c| 53 +
cmd/bootm.c | 2 ++
common/Kconfig | 6 ++
include/image.h | 1 +
4 files changed, 62 insertions(+)
diff
Add TPM2 functions to support boot measurement. This includes
starting up the TPM, initializing/appending the event log, and
measuring the U-Boot version.
Signed-off-by: Eddie James
---
include/efi_tcg2.h | 44 ---
include/tpm-v2.h | 135 +
lib/tpm-v2.c | 700 +++
tmpu -> tpmu
Signed-off-by: Eddie James
---
include/tpm-v2.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/include/tpm-v2.h b/include/tpm-v2.h
index 737e57551d..85feda3e06 100644
--- a/include/tpm-v2.h
+++ b/include/tpm-v2.h
@@ -167,7 +167,7 @@ struct tcg_pcr_event {
/
On Thu, Dec 15, 2022 at 10:15:50AM +0100, Patrick Delaunay wrote:
> Much of the fastboot code predates the introduction of Kconfig and
> has quite a few #ifdefs in it which is unnecessary now that we can use
> IS_ENABLED() et al.
>
> Signed-off-by: Patrick Delaunay
> ---
>
> cmd/fastboot.c
On 30.12.22 22:12, Heinrich Schuchardt wrote:
On 12/30/22 20:58, Alexander Graf wrote:
Now that we have a damage area tells us which parts of the frame buffer
actually need updating, let's only dcache flush those on video_sync()
calls. With this optimization in place, frame buffer updates -
e
On Sat, Dec 24, 2022 at 6:04 AM Paul Barker wrote:
>
> On 20/12/2022 15:55, Rob Herring wrote:
> > On Wed, Nov 23, 2022 at 05:50:06PM +, Paul Barker wrote:
> >> Add properties to the Authenta SPI flash device node to enable access by
> >> a UEFI application using a fixed GUID.
> >>
> >> Signed
Printing the I2C controller base address in decimal notation
is not helpful.
Change it to hex notation, which is the standard format found
in the Reference Manual and devicetree.
Signed-off-by: Fabio Estevam
---
drivers/i2c/mxc_i2c.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff -
On 12/19/22 2:29 PM, Bryan Brattlof wrote:
Texas Instrument's entire K3 generation of SoCs use much of the same
frameworks and boot flow, especially at the uboot level. Though there
are small differences introduced as each new K3 based SoC is developed
and as the K3 generation matures that will a
On 1/3/23 17:35, sergiu.m...@microchip.com wrote:
On 03.01.2023 17:59, Marek Vasut wrote:
On 1/3/23 16:55, sergiu.m...@microchip.com wrote:
On 03.01.2023 17:48, Marek Vasut wrote:
On 1/3/23 16:35, Sergiu Moga wrote:
Upstream linux commit 5994f58977e0.
Add reset bindings for SAMA7G5. At the m
On 1/3/23 17:54, sergiu.m...@microchip.com wrote:
On 03.01.2023 17:31, Marek Vasut wrote:
On 1/3/23 15:30, Sergiu Moga wrote:
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
on
On Tue, 06 Dec 2022 13:55:02 +0800
Icenowy Zheng wrote:
Hi Icenowy,
> 在 2022-12-06星期二的 00:45 +，Andre Przywara写道：
> > This adds the basic SoC .dtsi devicetree stub for the Allwinner T113s
> > SoC. This shares a die with the Allwinner D1 SoC (with RISC-V cores),
> > but uses two Cortex-A7 core
Hi Simon,
hmm this is strange. I am hitting this usually before 10 repetitions,
for sure within 30 repetitions. 'gpu_freq' is missing, thus default.
I can see this also from stock JeOS/RPi3 from OpenSUSE.
Do you have enabled debug as it works as workaround? [usb_hub.c]
Dissected more, thoug
Hi Rick,
On 1/3/23 02:20, Rick Chen wrote:
> When fit image boots from ram, the payload will
> be prepared in the address of SPL_LOAD_FIT_ADDRESS.
> In spl fit generic flow, it will malloc another
> memory address and copy whole fit image to this
> malloc address. But it is un-necessary for booti
On 1/3/23 02:18, Rick Chen wrote:
> Original openSBI (without FW_PIC) will relocate itselt
typo: itself
> from 0x100 to 0x0. After openSBI added FW_PIC codes,
> it will not relocate any more and alaways run at 0x100.
typo: always
> Hence, it may overlap with Kernel memory region. So it
Hi,
On 12/15/22 13:51, Olivier Moysan wrote:
Add support of offset and linear calibration for STM32MP15.
The calibration is performed once at probe. The ADC is set in power on
state for calibration. It remains in this state after calibration,
to give to the kernel the opportunity to retrieve cal
Hi Robert,
On Fri, 30 Dec 2022 at 13:26, Robert Marko wrote:
>
>
>
> On Fri, Dec 30, 2022 at 8:02 PM Simon Glass wrote:
>>
>> Hi Pali,
>>
>> On Fri, 30 Dec 2022 at 12:02, Pali Rohár wrote:
>> >
>> > On Friday 30 December 2022 11:47:29 Simon Glass wrote:
>> > > Hi Pali,
>> > >
>> > > On Fri, 30
On Tuesday 03 January 2023 11:02:17 Simon Glass wrote:
> > > > > 3. Add a common binman image for u-boot.bin (used by every board)
> > > >
> > > > It should be u-boot-dtb.bin (not u-boot.bin). At least this is the
> > > > current file name. (See this my patch series again, which aligns this
> > > >
Hi,
On 12/7/22 16:30, Etienne Carriere wrote:
Makes OP-TEE to enumerate also services depending on tee-supplicant
support in U-Boot. This change allows OP-TEE services like fTPM TA
to be discovered and get a TPM device registered in U-Boot.
Signed-off-by: Etienne Carriere
---
drivers/tee/opt
Hi Pali,
On Fri, 30 Dec 2022 at 13:12, Pali Rohár wrote:
>
> On Friday 30 December 2022 12:51:03 Simon Glass wrote:
> > Hi Pali,
> >
> > On Fri, 30 Dec 2022 at 11:55, Pali Rohár wrote:
> > >
> > > On Friday 30 December 2022 11:43:44 Simon Glass wrote:
> > > > Hi Pali,
> > > >
> > > > On Fri, 30
On Fri, 30 Dec 2022 at 17:54, Heinrich Schuchardt
wrote:
>
> A parameter starting with a hyphen leads to an endless loop in the sound
> play command.
>
> Leave it to dectoul() to handle the hyphen. It will return 0 for a negative
> number.
>
> Signed-off-by: Heinrich Schuchardt
> ---
> cmd/sound
Hi Peter,
On Sat, 31 Dec 2022 at 03:24, Peter Robinson wrote:
>
> The Pinephone Pro is another device by PINE64. It's closely related
> to the Pinebook Pro of which this initial support is derived from.
>
> Specification:
> - A variant of the Rockchip RK3399
> - A 6 inch 720*1440 DSI display
> -
On Sat, 31 Dec 2022 at 05:04, Heinrich Schuchardt
wrote:
>
> While our EFI binaries execute without problems on EDK II they crash on
> a Lenovo X13s. Let our binaries look more like what EDK II produces:
>
> * move all writable data to a .data section
> * align sections to 4 KiB boundaries (matchi
Hi Filip,
On Mon, 19 Dec 2022 at 14:25, Filip Žaludek wrote:
>
>
>
> Hi Simon,
>
>
> On 12/19/22 20:20, Simon Glass wrote:
> > Hi Filip,
> >
> > On Mon, 19 Dec 2022 at 02:29, Filip Žaludek
> > wrote:
> >>
> >>
> >>
> >> Hi Simon,
> >>
> >>is your testing framework connected to HDMI? Only no
On 03.01.2023 17:31, Marek Vasut wrote:
> On 1/3/23 15:30, Sergiu Moga wrote:
>> 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 th
Hi,
On 12/7/22 16:29, Etienne Carriere wrote:
Fixes optee-rng driver bind sequence in optee driver to print a warning
message but not report an error status when a optee-rng service driver
fails to be bound as the optee driver itself is still fully functional.
Signed-off-by: Etienne Carriere
-
Hi,
On 12/12/22 11:44, Fabrice Gasnier wrote:
Add support for USB2514B onboard hub on stm32mp157c EV1 board. The HUB
is supplied by a 3v3 PMIC regulator.
[backport from linux ad9591b01d24]
Signed-off-by: Fabrice Gasnier
---
arch/arm/dts/stm32mp157c-ev1.dts | 8
1 file changed, 8 i
Hi Fabrice
On 12/12/22 11:32, Fabrice Gasnier wrote:
> phy-stm32-usbphyc bindings uses a connector node with vbus-supply
> property.
>
> [backport from linux 43e55d778a6b]
> Signed-off-by: Fabrice Gasnier
> ---
>
> arch/arm/dts/stm32mp157c-ev1.dts | 4
> 1 file changed, 4 insertions(+)
>
Hi,
On 12/12/22 11:44, Fabrice Gasnier wrote:
Activate the USB onboard HUB driver, that is used to enable the HUB supply
on STM32MP15 EVAL, DK1 and DK2 boards.
This avoids marking the 3v3 corresponding regulator as always-on.
Signed-off-by: Fabrice Gasnier
---
configs/stm32mp15_basic_defcon
On 03.01.2023 17:59, Marek Vasut wrote:
> On 1/3/23 16:55, sergiu.m...@microchip.com wrote:
>> On 03.01.2023 17:48, Marek Vasut wrote:
>>> On 1/3/23 16:35, Sergiu Moga wrote:
Upstream linux commit 5994f58977e0.
Add reset bindings for SAMA7G5. At the moment only USB PHYs are
incl
Hi Fabrice
On 12/12/22 11:44, Fabrice Gasnier wrote:
> Add support for USB2514B onboard hub on stm32mp157c EV1 board. The HUB
> is supplied by a 3v3 PMIC regulator.
>
> [backport from linux ad9591b01d24]
> Signed-off-by: Fabrice Gasnier
> ---
>
> arch/arm/dts/stm32mp157c-ev1.dts | 8
>
Hi Fabrice
On 12/12/22 11:44, Fabrice Gasnier wrote:
> Activate the USB onboard HUB driver, that is used to enable the HUB supply
> on STM32MP15 EVAL, DK1 and DK2 boards.
> This avoids marking the 3v3 corresponding regulator as always-on.
>
> Signed-off-by: Fabrice Gasnier
> ---
>
> configs/st
Hi,
On 12/12/22 11:44, Fabrice Gasnier wrote:
The main issue the driver addresses is that a USB hub needs to be
powered before it can be discovered. This is often solved by using
"regulator-always-on".
This driver is inspired by the Linux v6.1 driver. It only enables (or
disables) the hub vdd (
Hi Fabrice
On 12/12/22 11:44, Fabrice Gasnier wrote:
> The main issue the driver addresses is that a USB hub needs to be
> powered before it can be discovered. This is often solved by using
> "regulator-always-on".
>
> This driver is inspired by the Linux v6.1 driver. It only enables (or
> disabl
Hi Patrick,
On 1/3/23 17:10, Patrick DELAUNAY wrote:
On 12/13/22 15:48, Quentin Schulz wrote:
Hi Patrick,
On 12/13/22 15:34, neil.armstr...@linaro.org wrote:
On 13/12/2022 15:31, Patrick DELAUNAY wrote:
Hi,
On 11/22/22 20:43, Neil Armstrong wrote:
On 22/11/2022 20:11, Neil Armstrong wrote
Hi,
On 12/12/22 11:32, Fabrice Gasnier wrote:
phy-stm32-usbphyc bindings uses a connector node with vbus-supply
property.
[backport from linux 43e55d778a6b]
Signed-off-by: Fabrice Gasnier
---
arch/arm/dts/stm32mp157c-ev1.dts | 4
1 file changed, 4 insertions(+)
diff --git a/arch/arm/
On 12/13/22 15:48, Quentin Schulz wrote:
Hi Patrick,
On 12/13/22 15:34, neil.armstr...@linaro.org wrote:
On 13/12/2022 15:31, Patrick DELAUNAY wrote:
Hi,
On 11/22/22 20:43, Neil Armstrong wrote:
On 22/11/2022 20:11, Neil Armstrong wrote:
Hi,
On 21/11/2022 13:23, Quentin Schulz wrote:
Hi
On 1/3/23 17:01, sergiu.m...@microchip.com wrote:
On 03.01.2023 17:57, Marek Vasut wrote:
On 1/3/23 16:49, sergiu.m...@microchip.com wrote:
On 03.01.2023 16:34, Marek Vasut wrote:
On 1/3/23 13:11, sergiu.m...@microchip.com wrote:
On 03.01.2023 01:26, Marek Vasut wrote:
On 12/23/22 13:34, Ser
On 03.01.2023 17:57, Marek Vasut wrote:
> On 1/3/23 16:49, sergiu.m...@microchip.com wrote:
>> On 03.01.2023 16:34, Marek Vasut wrote:
>>> On 1/3/23 13:11, sergiu.m...@microchip.com wrote:
On 03.01.2023 01:26, Marek Vasut wrote:
> On 12/23/22 13:34, Sergiu Moga wrote:
>
> [...]
>>>
On 1/3/23 16:56, sergiu.m...@microchip.com wrote:
On 03.01.2023 17:47, Marek Vasut wrote:
On 1/3/23 16:35, Sergiu Moga wrote:
Add the OHCI and EHCI DT nodes for the sam9x60 SoC's.
Signed-off-by: Sergiu Moga
---
v1 -> v2:
- use usb@
arch/arm/dts/sam9x60.dtsi | 18 ++
1 f
On 1/3/23 16:55, sergiu.m...@microchip.com wrote:
On 03.01.2023 17:48, Marek Vasut wrote:
On 1/3/23 16:35, Sergiu Moga wrote:
Upstream linux commit 5994f58977e0.
Add reset bindings for SAMA7G5. At the moment only USB PHYs are
included.
Signed-off-by: Sergiu Moga
---
v1 -> v2:
- nothing
On 1/3/23 16:53, sergiu.m...@microchip.com wrote:
On 03.01.2023 16:35, Marek Vasut wrote:
On 1/3/23 12:53, sergiu.m...@microchip.com wrote:
On 03.01.2023 01:07, Marek Vasut wrote:
On 12/23/22 13:33, Sergiu Moga wrote:
Add the USB related DT nodes for the sama7g5ek board.
Signed-off-by: Sergi
On 1/3/23 16:49, sergiu.m...@microchip.com wrote:
On 03.01.2023 16:34, Marek Vasut wrote:
On 1/3/23 13:11, sergiu.m...@microchip.com wrote:
On 03.01.2023 01:26, Marek Vasut wrote:
On 12/23/22 13:34, Sergiu Moga wrote:
[...]
diff --git a/drivers/usb/host/ohci-at91.c
b/drivers/usb/host/ohci-a
On 03.01.2023 17:47, Marek Vasut wrote:
> On 1/3/23 16:35, Sergiu Moga wrote:
>> Add the OHCI and EHCI DT nodes for the sam9x60 SoC's.
>>
>> Signed-off-by: Sergiu Moga
>> ---
>>
>> v1 -> v2:
>> - use usb@
>>
>> arch/arm/dts/sam9x60.dtsi | 18 ++
>> 1 file changed, 18 insertions(
On 03.01.2023 17:48, Marek Vasut wrote:
> On 1/3/23 16:35, Sergiu Moga wrote:
>> Upstream linux commit 5994f58977e0.
>>
>> Add reset bindings for SAMA7G5. At the moment only USB PHYs are
>> included.
>>
>> Signed-off-by: Sergiu Moga
>> ---
>>
>> v1 -> v2:
>> - nothing
>>
>>
>> include/dt-binding
On 03.01.2023 16:35, Marek Vasut wrote:
> On 1/3/23 12:53, sergiu.m...@microchip.com wrote:
>> On 03.01.2023 01:07, Marek Vasut wrote:
>>> On 12/23/22 13:33, Sergiu Moga wrote:
Add the USB related DT nodes for the sama7g5ek board.
Signed-off-by: Sergiu Moga
---
arch/arm
On 03.01.2023 16:34, Marek Vasut wrote:
> On 1/3/23 13:11, sergiu.m...@microchip.com wrote:
>> On 03.01.2023 01:26, Marek Vasut wrote:
>>> On 12/23/22 13:34, Sergiu Moga wrote:
>>>
>>> [...]
>>>
diff --git a/drivers/usb/host/ohci-at91.c
b/drivers/usb/host/ohci-at91.c
index 9b955c1bd
On 1/3/23 16:35, Sergiu Moga wrote:
Upstream linux commit 5994f58977e0.
Add reset bindings for SAMA7G5. At the moment only USB PHYs are
included.
Signed-off-by: Sergiu Moga
---
v1 -> v2:
- nothing
include/dt-bindings/reset/sama7g5-reset.h | 10 ++
1 file changed, 10 insertions(+)
On 1/3/23 16:35, Sergiu Moga wrote:
Add the OHCI and EHCI DT nodes for the sam9x60 SoC's.
Signed-off-by: Sergiu Moga
---
v1 -> v2:
- use usb@
arch/arm/dts/sam9x60.dtsi | 18 ++
1 file changed, 18 insertions(+)
diff --git a/arch/arm/dts/sam9x60.dtsi b/arch/arm/dts/sam9x60.d
On 1/3/23 15:30, Sergiu Moga wrote:
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:
- use *_bulk API's
drivers/usb/host/ohci-at91.c | 35 +++
On 1/3/23 15:30, Sergiu Moga wrote:
[...]
+static int ohci_atmel_probe(struct udevice *dev)
+{
+ struct at91_usbh_data *pdata = dev_get_plat(dev);
+ struct ohci_at91_priv *ohci_at91 = dev_get_priv(dev);
+ u32 i;
+ int ret;
+ stru
1 - 100 of 188 matches
Mail list logo
