Hi Tom
> This patch adds the necessary configs and docs for FPIOA and GPIO support
> on the K210.
>
> The board does not boot unless CONSOLE_LOGLEVEL is set to a non-default
> value . It also boots when the tree is dirty (and CONSOLE_LOGLEVEL is not
> changed). It also boots when changes are made
Hi Adam,
On Tue, Aug 18, 2020 at 6:20 PM Adam Ford wrote:
>
> The PMIC which powers the whole board is connected to the I2C1
> bus. This patch enables I2C. With this enabled, the PMIC needs
> to told to keep the rail enabled, or it gets shutdown before the
Looks like a typo.
> system boots.
a polite ping ...
On Wed, Jul 29, 2020 at 8:51 PM wrote:
>
> From: Jassi Brar
>
> MAX3420 implements FullSpeed USB Device over SPI.
> Another version MAX3421, also implements USB Host mode.
> This driver should be good for the device mode of max3421 as well.
>
> Signed-off-by: Jassi Brar
As explained in the CONFIG_DM_MDIO text inside drivers/net/Kconfig:
"Useful in particular for systems that support
DM_ETH and have a stand-alone MDIO hardware block shared by multiple
Ethernet interfaces."
i.MX6 has a single FEC instance, so there is no need to select
CONFIG_DM_MDIO.
The PMIC which powers the whole board is connected to the I2C1
bus. This patch enables I2C. With this enabled, the PMIC needs
to told to keep the rail enabled, or it gets shutdown before the
system boots.
Signed-off-by: Adam Ford
diff --git a/arch/arm/dts/imx6q-logicpd-u-boot.dtsi
On 8/18/20 8:01 PM, Jason Wessel wrote:
>>From the Raspberry Pi3 - With the patch removed:
>
> U-Boot> setenv usb_pgood_delay 2000
> U-Boot> usb reset
> resetting USB...
> Bus usb@7e98: USB DWC2
> scanning bus usb@7e98 for devices... unable to get device descriptor
> (error=-22)
> 6 USB
On 8/18/20 8:16 PM, Jason Wessel wrote:
>
>
> On 8/18/20 10:08 AM, Marek Vasut wrote:
>> On 8/18/20 4:34 PM, Jason Wessel wrote:
>>> When resetting the rpi3 board sometimes it will display:
>>> USB device not accepting new address (error=0)
>>>
>>> After the message appears, the usb
On 8/18/20 8:47 PM, Jason Wessel wrote:
>
>
> On 8/18/20 12:20 PM, Marek Vasut wrote:
>> On 8/18/20 6:54 PM, Jason Wessel wrote:
>>>
>>>
>>> On 8/18/20 10:05 AM, Marek Vasut wrote:
On 8/18/20 4:34 PM, Jason Wessel wrote:
> After the initial configuration some USB keyboard+mouse devices
Hello,
On Tue, 18 Aug 2020 17:17:21 +0200
Joao Marcos Costa wrote:
> Add sqfs_decompressor_init() and sqfs_decompressor_cleanup(). These
> functions are called respectively in sqfs_probe() and sqfs_close(). For
> now, only ZSTD requires an initialization logic. ZSTD support will be
> added in a
The R5 SPL on J7200 SoCs will be limited to booting just the
MCU R5FSS0 R5F core in LockStep-mode at present, so add the
two required environment variables 'addr_mcur5f0_0load' and
'name_mcur5f0_0fw' that are needed by the R5 SPL early-boot
logic. The firmware name used is also different from that
Enable the FS_LOADER and associated configs in the j7200_evm_r5_defconfig
so that the R5 SPL can support the loading of firmware files from a boot
media/file system.
Signed-off-by: Suman Anna
---
configs/j7200_evm_r5_defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git
Add a generic fs_loader node to the K3 J7200 R5 common board dts
file and use it as the chosen firmware-loader so that it can be
used for loading various firmwares from a boot media/filesystem
in R5 SPL on K3 J7200 EVM.
Signed-off-by: Suman Anna
---
Hi Lokesh,
The following series adds the support for the branch-only boot of an
application firmware on MCU R5F from R5 SPL after it has finished
launching the A72.
Most of the changes are just related to updating J7200 defconfigs or
dts nodes, as the core logic for R5 SPL branch-only boot is
On 8/18/20 12:20 PM, Marek Vasut wrote:
> On 8/18/20 6:54 PM, Jason Wessel wrote:
>>
>>
>> On 8/18/20 10:05 AM, Marek Vasut wrote:
>>> On 8/18/20 4:34 PM, Jason Wessel wrote:
After the initial configuration some USB keyboard+mouse devices never
return any kind of event on the
[Resending as mailer dropped the Cc recipients]
This patch adds support for more PMBus compatible devices to the NXP
drivers for its QorIQ family devices. At runtime, the voltage regulator is
queried over I2C, and the required voltage multiplier determined. This
change supports the DIRECT and
On 8/18/20 10:08 AM, Marek Vasut wrote:
> On 8/18/20 4:34 PM, Jason Wessel wrote:
>> When resetting the rpi3 board sometimes it will display:
>> USB device not accepting new address (error=0)
>>
>> After the message appears, the usb keyboard will not work. It seems
>> that the
>From the Raspberry Pi3 - With the patch removed:
U-Boot> setenv usb_pgood_delay 2000
U-Boot> usb reset
resetting USB...
Bus usb@7e98: USB DWC2
scanning bus usb@7e98 for devices... unable to get device descriptor
(error=-22)
6 USB Device(s) found
scanning usb for storage
On 8/18/20 6:54 PM, Jason Wessel wrote:
>
>
> On 8/18/20 10:05 AM, Marek Vasut wrote:
>> On 8/18/20 4:34 PM, Jason Wessel wrote:
>>> After the initial configuration some USB keyboard+mouse devices never
>>> return any kind of event on the interrupt line. In particular, the
>>> device identified
Provide a command to display information about the SBI implementation.
The output might look like:
=> sbi
SBI 0.2
OpenSBI
Extensions:
sbi_set_timer
sbi_console_putchar
sbi_console_getchar
sbi_clear_ipi
sbi_send_ipi
sbi_remote_fence_i
sbi_remote_sfence_vma
On 8/18/20 10:05 AM, Marek Vasut wrote:
> On 8/18/20 4:34 PM, Jason Wessel wrote:
>> After the initial configuration some USB keyboard+mouse devices never
>> return any kind of event on the interrupt line. In particular, the
>> device identified by "Cypress Cypress USB Keyboard / PS2 Mouse as
On 8/5/20 11:26 PM, Marek Vasut wrote:
> Add SH4 R2Dplus machine configured to test various U-Boot PCI ethernet
> options -- RTL8139, EEPRO100, AMD PCnet, DEC Tulip.
>
Bump ?
Hello Sudeep,
On Tue, 18 Aug 2020 at 17:44, Etienne Carriere
wrote:
>
> This change introduces SCMI agent driver in U-Boot in the firmware
> U-class.
> (...)
> --- a/drivers/firmware/Kconfig
> +++ b/drivers/firmware/Kconfig
> @@ -1,6 +1,26 @@
> config FIRMWARE
> bool "Enable Firmware
Dump SCMI DT bindings documentation from Linux kernel source
tree v5.8-rc1.
Signed-off-by: Etienne Carriere
Reviewed-by: Simon Glass
---
Changes in v2:
- No change but added R-b tag.
- Yet a question: do we need to add this binding doc in U-Boot
since already existing in Linux DT bindings
This change introduces a clock driver for SCMI agent devices. When
SCMI agent and SCMI clock drivers are enabled, SCMI agent binds a
clock device for each SCMI clock protocol devices enabled in the FDT.
SCMI clock driver is embedded upon CONFIG_CLK_SCMI=y. If enabled,
CONFIG_SCMI_AGENT is also
This change introduces a reset controller driver for SCMI agent devices.
When SCMI agent and SCMI reset domain drivers are enabled, SCMI agent
binds a reset controller device for each SCMI reset domain protocol
devices enabled in the FDT.
SCMI reset driver is embedded upon CONFIG_RESET_SCMI=y. If
This change introduces SCMI agent driver in U-Boot in the firmware
U-class.
SCMI agent driver is designed for platforms that embed a SCMI server in
a firmware hosted for example by a companion co-processor or the secure
world of the executing processor.
SCMI protocols allow an SCMI agent to
Improve SquashFS tests architecture. Add 'Compression' class. LZO
algorithm may crash if the file is fragmented, so the fragments are
disabled when testing LZO.
Signed-off-by: Joao Marcos Costa
---
Changes in v4:
- No changes since the last version.
Changes in v3:
- No changes
Add call to ZSTD's ZSTD_decompressDCtx(). In this use case, the caller
can upper bound the decompressed size, which will be the SquashFS data
block (or metadata block) size, so there is no need to use streaming
API. Add ZSTD's worskpace to squashfs_ctxt structure.
Signed-off-by: Joao Marcos Costa
Replace 'u16 comp_type' by a reference to squashfs_ctxt structure.
Signed-off-by: Joao Marcos Costa
---
Changes in v4:
- This patch was not present in the previous version.
fs/squashfs/sqfs.c | 25 +
fs/squashfs/sqfs_decompressor.c | 5 +++--
Add sqfs_decompressor_init() and sqfs_decompressor_cleanup(). These
functions are called respectively in sqfs_probe() and sqfs_close(). For
now, only ZSTD requires an initialization logic. ZSTD support will be
added in a follow-up commit.
Move squashfs_ctxt definition to sqfs_filesystem.h. This
Add call to lzo's lzo1x_decompress_safe() into sqfs_decompress().
U-Boot's LZO sources may still have some unsolved issues that could make the
decompression crash when dealing with fragmented files, so those should be
avoided. The "-no-fragments" option can be passed to mksquashfs.
Hello,
Following the SquashFS support, this series adds support for LZO and ZSTD
algorithms.
Changes in v4:
- Replace sqfs_decompress() 1st parameter by a reference to
squashfs_ctxt.
- Undo changes in squashfs_ctxt instance at sqfs.c
Changes in v3:
- Reorganize
On Tue, 18 Aug 2020 16:35:27 +0200
Thomas Petazzoni wrote:
> Hello,
>
> On Tue, 18 Aug 2020 16:31:16 +0200
> Joao Marcos Costa wrote:
>
> > +#if IS_ENABLED(CONFIG_ZSTD)
> > +static int sqfs_zstd_decompress(void *dest, unsigned long dest_len,
> > + void *source, u32
On 8/18/20 4:34 PM, Jason Wessel wrote:
> These patches are now in use by other developers, and I would like to
> get them into the upstream u-boot. This 3 patches were part of a 9
> patch series posted in July prior to the merge window closure.
>
> -- Travis CI checks
On 8/18/20 4:34 PM, Jason Wessel wrote:
> When resetting the rpi3 board sometimes it will display:
> USB device not accepting new address (error=0)
>
> After the message appears, the usb keyboard will not work. It seems
> that the configuration actually did succeed however. Checking the
>
On 8/18/20 4:34 PM, Jason Wessel wrote:
> I have found through testing some USB 2 composite mouse/keyboard
> devices do not response to the usb_set_address call immediately
> following the port reset. It can take anywhere from 2ms to 20ms.
Does it work if you do
=> setenv usb_pgood_delay 2000
On 8/18/20 4:34 PM, Jason Wessel wrote:
> After the initial configuration some USB keyboard+mouse devices never
> return any kind of event on the interrupt line. In particular, the
> device identified by "Cypress Cypress USB Keyboard / PS2 Mouse as
>
Hi Stefan,
On Tue, 18 Aug 2020 at 08:13, Stefan Roese wrote:
>
> Hi Simon,
>
> On 18.08.20 15:22, Simon Glass wrote:
> > Hi Marek,
> >
> > +Stefan Roese who wrote the existing code.
>
> Hmmm, I was not Cc'ed.
>
> > On Fri, 7 Aug 2020 at 15:40, Marek Vasut wrote:
> >>
> >> On 8/7/20 6:23 PM,
When resetting the rpi3 board sometimes it will display:
USB device not accepting new address (error=0)
After the message appears, the usb keyboard will not work. It seems
that the configuration actually did succeed however. Checking the
device status for a return code of zero and
I have found through testing some USB 2 composite mouse/keyboard
devices do not response to the usb_set_address call immediately
following the port reset. It can take anywhere from 2ms to 20ms.
This patch adds a retry and delay for usb_prepare_device() and allows
all the USB keyboards I tried to
These patches are now in use by other developers, and I would like to
get them into the upstream u-boot. This 3 patches were part of a 9
patch series posted in July prior to the merge window closure.
-- Travis CI checks https://github.com/u-boot/u-boot/pull/35 --
Pull Request #35 Rpi master
Hello,
On Tue, 18 Aug 2020 16:31:16 +0200
Joao Marcos Costa wrote:
> +#if IS_ENABLED(CONFIG_ZSTD)
> +static int sqfs_zstd_decompress(void *dest, unsigned long dest_len,
> + void *source, u32 src_len)
Pass the squashfs_context structure as argument to the
After the initial configuration some USB keyboard+mouse devices never
return any kind of event on the interrupt line. In particular, the
device identified by "Cypress Cypress USB Keyboard / PS2 Mouse as
3f98.usb/usb1/1-1/1-1.3/1-1.3:1.0/0003:04B4:0101.0001/input/input0"
never returns a data
Hello,
In your commit title: spurious . after "init".
On Tue, 18 Aug 2020 16:31:15 +0200
Joao Marcos Costa wrote:
> -static struct squashfs_ctxt ctxt;
> +struct squashfs_ctxt sqfs_ctxt;
Why are you dropping the "static" here ? This symbol only needs to be
visible from that file. If you keep
Hello,
Following the SquashFS support, this series adds support for LZO and ZSTD
algorithms.
Changes in v3:
- Reorganize patches order.
- Remove memory leak from sqfs_zstd_decompress().
Changes in v2:
- Change tests architecture.
- Add tests for LZO and ZSTD.
Add sqfs_decompressor_init() and sqfs_decompressor_cleanup(). These
functions are called respectively in sqfs_probe() and sqfs_close(). For
now, only ZSTD requires an initialization logic. ZSTD support will be
added in a follow-up commit.
Move squashfs_ctxt definition to sqfs_filesystem.h. This
Add call to ZSTD's ZSTD_decompressDCtx(). In this use case, the caller
can upper bound the decompressed size, which will be the SquashFS data
block (or metadata block) size, so there is no need to use streaming
API. Add ZSTD's worskpace to squashfs_ctxt structure.
Signed-off-by: Joao Marcos Costa
Improve SquashFS tests architecture. Add 'Compression' class. LZO
algorithm may crash if the file is fragmented, so the fragments are
disabled when testing LZO.
Signed-off-by: Joao Marcos Costa
---
Changes in v3:
- No changes since the last version.
Changes in v2:
- This patch
Add call to lzo's lzo1x_decompress_safe() into sqfs_decompress().
U-Boot's LZO sources may still have some unsolved issues that could make the
decompression crash when dealing with fragmented files, so those should be
avoided. The "-no-fragments" option can be passed to mksquashfs.
Hi Simon,
On 18.08.20 15:22, Simon Glass wrote:
Hi Marek,
+Stefan Roese who wrote the existing code.
Hmmm, I was not Cc'ed.
On Fri, 7 Aug 2020 at 15:40, Marek Vasut wrote:
On 8/7/20 6:23 PM, Simon Glass wrote:
[...]
diff --git a/drivers/core/device-remove.c
Hi Marek,
+Stefan Roese who wrote the existing code.
On Fri, 7 Aug 2020 at 15:40, Marek Vasut wrote:
>
> On 8/7/20 6:23 PM, Simon Glass wrote:
>
> [...]
>
> >> diff --git a/drivers/core/device-remove.c b/drivers/core/device-remove.c
> >> index efdb0f2905..07b241b6bb 100644
> >> ---
The ethernet controller can read the MAC from EEPROM and display it,
but if ethaddr is not set, the ethernet is still unavailable.
This patch checks will automatically set the MAC address if it has
not already been set.
Signed-off-by: Adam Ford
---
V2: Fix typo
diff --git
Improve SquashFS tests architecture. Add 'Compression' class. LZO
algorithm may crash if the file is fragmented, so the fragments are
disabled when testing LZO.
Signed-off-by: Joao Marcos Costa
---
Changes in v2:
- This patch was not present in the previous version.
Add sqfs_decompressor_init() and sqfs_decompressor_cleanup(). These
functions are called respectively in sqfs_probe() and sqfs_close(). For
now, only ZSTD requires an initialization logic.
Move squashfs_ctxt definition to sqfs_filesystem.h. This structure is
passed to sqfs_decompressor_init() and
Add call to lzo's lzo1x_decompress_safe() and rename source length
parameter from 'lenp' to 'src_len'.
U-Boot's LZO sources may still have some unsolved issues that could make the
decompression crash when dealing with fragmented files, so those should be
avoided. The "-no-fragments" option can be
Add call to ZSTD's ZSTD_decompressDCtx(). In this use case, the caller
can upper bound the decompressed size, which will be the SquashFS data
block (or metadata block) size, so there is no need to use streaming
API.
Signed-off-by: Joao Marcos Costa
---
Changes in v2:
- No changes since
Hello,
Following the SquashFS support, this series adds support for LZO and ZSTD
algorithms.
Changes in v2:
- Change tests architecture.
- Add tests for LZO and ZSTD.
- Skip compression algorithms unsupported by the host's squashfs-tools
version.
- Add
On Tue, Aug 18, 2020 at 12:31:32PM +0200, Wolfgang Denk wrote:
> Dear Stefan Roese,
>
> In message <20200813054800.469284-2...@denx.de> you wrote:
> > Since commit 86cf1c82850f ("configs: Migrate CONFIG_NR_DRAM_BANKS") &
> > commit 999a772d9f24 ("Kconfig: Migrate CONFIG_NR_DRAM_BANKS"),
> >
Tom Rini writes:
> We have a number of platforms that are a combination of a carrier board
> and System-on-Module (SoM) that in turn allows for the board to have
> different SoCs on it. In some cases, this is handled via board-specific
> Kconfig options. In other cases we make use of
>
Hi Peng,
> > Subject: Re: [PATCH v2 4/7] f_sdp: Support searching and loading
> > FIT or container image
> >
> > Hi Peng,
> >
> > > Add support to f_sdp to search and load iMX8 container image or
> > > iMX8M FIT image by new UUU command SDPV.
> > >
> > > When using the SDPV, the uuu will
> Subject: Re: [PATCH v2 4/7] f_sdp: Support searching and loading FIT or
> container image
>
> Hi Peng,
>
> > Add support to f_sdp to search and load iMX8 container image or iMX8M
> > FIT image by new UUU command SDPV.
> >
> > When using the SDPV, the uuu will continue to send out data after
>
> From: Wig Cheng
> Here is the test commands:
> => ums 0 mmc 0
> UMS: LUN 0, dev 0, hwpart 0, sector 0x0, count 0x71
> Signed-off-by: Wig Cheng
> Reviewed-by: Fabio Estevam
Applied to u-boot-imx, master, thanks !
Best regards,
Stefano Babic
--
> The correct order is load address, offset, length. The order was
> accidentally switched a while ago; make it match the HAB Blocks output and
> what CST expects again.
> Fixes: e97bdfa5da70 ("tools/imximage: share DCD information via Kconfig")
> Signed-off-by: Matthias Schiffer
Applied to
> Add the basic differentiation between i.MX6 and i.MX7 into the bmode
> command, the mechanism really works almost the same on both platforms.
> Signed-off-by: Marek Vasut
> Cc: Fabio Estevam
> Cc: NXP i.MX U-Boot Team
> Cc: Peng Fan
> Cc: Stefano Babic
Applied to u-boot-imx, master, thanks
> Fill is code for programming the DDR_PHY_CMD_DESKEW_CONx registers,
> which are optional, but can be used to fill in the byte lane delays.
> Signed-off-by: Marek Vasut
> Cc: Fabio Estevam
> Cc: NXP i.MX U-Boot Team
> Cc: Peng Fan
> Cc: Stefano Babic
Applied to u-boot-imx, master, thanks !
> The i.MX6/i.MX7 is capable of booting a secondary "redundant" system
> image in case the primary one is corrupted. The user can force this
> boot mode as well by explicitly setting SRC GPR10 bit 30. This can be
> potentially useful when upgrading the bootloader itself. Expose this
>
> Implement the 'getprisec' subcommand of 'bmode' command for i.MX7 by
> reading out the SRC GPR10 bit 30. This bit is either set by the BootROM
> if it switched to the secondary copy due to primary copy being corrupted
> OR it can be overridden by the user.
> Signed-off-by: Marek Vasut
> Cc:
> From: Wig Cheng
> - Remove pinmux definition from pico-imx6ul.c
> - Enable NET_RANDOM_ETHADDR for temporary solution, because micrel_ksz8xxx
> driver does not support DM_ETH yet, so cannot read MAC address directly.
> Before enable DM_ETH:
> Net: FEC [PRIME]
> After enable DM_ETH:
> Net:
> From: Wig Cheng
> It's due to the warning messages issue after compiled:
> = WARNING ==
> This board does not use CONFIG_DM_VIDEO Please update
> the board to use CONFIG_DM_VIDEO before the v2019.07 release.
> Failure to update by the deadline may
> Add new 'getprisec' subcommand to 'bmode' command, which sets the return
> value of the 'bmode' command to either 0 if the system booted from primary
> copy or to 1 if the system booted from secondary copy. This can be used
> e.g. in 'test' command to determine which copy of the system is
> Subject: Re: [PATCH v2 1/7] sdp: call board_usb_init at spl_sdp_load_image
>
> Hi Peng,
>
> > From: Frank Li
> >
> > Need initialize UDC before run sdp download
> >
> > Signed-off-by: Frank Li
> > Signed-off-by: Peng Fan
> > ---
> > common/spl/spl_sdp.c | 2 ++
> > 1 file changed, 2
Dear Stefan,
In message <8ddb672c-956c-68d2-ceb4-d77f96cdf...@denx.de> you wrote:
>
> > Especially the default value of 4 makes no sense to me - whiy is
> > this not 1?
>
> I can't really tell. I can only assume, that it originates from this
> patch:
Yes, probably.
I think the issue here
We have a number of platforms that are a combination of a carrier board
and System-on-Module (SoM) that in turn allows for the board to have
different SoCs on it. In some cases, this is handled via board-specific
Kconfig options. In other cases we make use of
CONFIG_SYS_EXTRA_OPTIONS. This
On Tue, Aug 18, 2020 at 10:09:31AM +0200, Stefano Babic wrote:
> On 13.08.20 03:16, Tom Rini wrote:
> > On Thu, Aug 13, 2020 at 12:52:22AM +, Peng Fan wrote:
> >> Hi Tom,
> >>
> >>> Subject: [PATCH] arm: mx6: Make all i.MX6 SoCs user-selectable
> >>>
> >> []
> >>
> >>> +
> >>> config
Hi Wolfgang,
On 18.08.20 12:35, Wolfgang Denk wrote:
In message <20200813054800.469284-5...@denx.de> you wrote:
With the removal of bi_memstart & bi_memsize, this patch now moves the
references to the better suiting gd->ram_base/ram_size variables.
This sounds as if bi_memstart & bi_memsize
Hi Wolfgang,
(added Ramon to Cc)
On 18.08.20 12:31, Wolfgang Denk wrote:
In message <20200813054800.469284-2...@denx.de> you wrote:
Since commit 86cf1c82850f ("configs: Migrate CONFIG_NR_DRAM_BANKS") &
commit 999a772d9f24 ("Kconfig: Migrate CONFIG_NR_DRAM_BANKS"),
CONFIG_NR_DRAM_BANKS is
On 13.08.20 03:16, Tom Rini wrote:
> On Thu, Aug 13, 2020 at 12:52:22AM +, Peng Fan wrote:
>> Hi Tom,
>>
>>> Subject: [PATCH] arm: mx6: Make all i.MX6 SoCs user-selectable
>>>
>> []
>>
>>> +
>>> config MX6UL_LITESOM
>>> bool
>>> select DM
>>> select DM_THERMAL
>>> - select
On Tue, 18 Aug 2020 18:16:47 +0800
Peng Fan wrote:
> Add g_dnl_get_board_bcd_device_number, the new BCD value is used by
> uuu to distinguish if the SPL supports the SDPV.
>
> Signed-off-by: Peng Fan
> ---
> arch/arm/mach-imx/spl.c | 6 ++
> 1 file changed, 6 insertions(+)
>
> diff --git
Hi Peng,
> Add support to f_sdp to search and load iMX8 container image or iMX8M
> FIT image by new UUU command SDPV.
>
> When using the SDPV, the uuu will continue to send out data after
> first level boot loader used by ROM. This means uuu won't skip to the
> offset of the second boot loader,
On Tue, 18 Aug 2020 18:16:45 +0800
Peng Fan wrote:
> From: Ye Li
>
> Because the buffer length of sdp usb request is 65, we have to
> allocate 65 bytes not 64 bytes. Otherwise there is potential buffer
> overflow.
>
> Signed-off-by: Ye Li
> Signed-off-by: Peng Fan
> ---
>
On Tue, 18 Aug 2020 18:16:44 +0800
Peng Fan wrote:
> From: Ye Li
>
> Add HS endpoint descriptor for SDP. So that we can use high speed
> endpoint, and the SDP device can send packet with 512 byte size.
Do you use uuu for it? On which board do you perform tests?
>
> Signed-off-by: Ye Li
>
On 18.08.20 11:14, Bin Meng wrote:
> Hi Heinrich,
>
> On Tue, Aug 11, 2020 at 11:57 AM Heinrich Schuchardt
> wrote:
>>
>> At least on the Kendryte K210:
>>
>> gd->arch.available_harts= 0x0003
>> gd->arch.ipi[0].addr= 0x
>> gd->arch.ipi[0].arg0= 0x
>>
Hi Peng,
> From: Frank Li
>
> Need initialize UDC before run sdp download
>
> Signed-off-by: Frank Li
> Signed-off-by: Peng Fan
> ---
> common/spl/spl_sdp.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/common/spl/spl_sdp.c b/common/spl/spl_sdp.c
> index e7f7b68411..ae9c09883a
Hi Pali,
On 18.08.20 09:33, Pali Rohár wrote:
CCing Konstantin, you may have be interested in my following Espressobin patch.
BTW, ./scripts/get_maintainer.pl does not shows you as maintainer of
board/Marvell/mvebu_armada-37xx/board.c file, even it contains
Espressobin specific code.
On
Hi Chris,
On 13.08.20 03:37, Chris Packham wrote:
> When building envtools via tools-only_defconfig the builtin defaults
> are based on options in the defconfig. For example:
>
> bootcmd=bootp; setenv bootargs root=/dev/nfs
> nfsroot=${serverip}:${rootpath}
>
Dear Adam,
In message
you wrote:
>
> Any chance you can update the statistics for v2020.07?
sorry for the delay, I was on vacation.
Here we go:
U-Boot 2020.07 Release Statistics
(Changes since v2020.04)
Processed 1918 csets from 203 developers
31 employers found
A total of 122895 lines
From: Laurentiu Tudor
In the current implementation, u-boot creates iommu mappings only
for PCI devices enumarated at boot time thus does not take into
account more dynamic scenarios such as SR-IOV or PCI hot-plug.
Add an u-boot env var and a device tree property (to be used for
example in more
Dear Stefan,
In message <20200813054800.469284-5...@denx.de> you wrote:
> With the removal of bi_memstart & bi_memsize, this patch now moves the
> references to the better suiting gd->ram_base/ram_size variables.
This sounds as if bi_memstart & bi_memsize have already been
removed, in whih case
From: Laurentiu Tudor
Add a few defines related to ARI and SRIOV configuration.
Signed-off-by: Laurentiu Tudor
---
include/pci.h | 14 ++
1 file changed, 14 insertions(+)
diff --git a/include/pci.h b/include/pci.h
index 2089db9f16..88a09505a5 100644
--- a/include/pci.h
+++
From: Laurentiu Tudor
Move the pci device related fdt fixup in a function in order to
re-use it in a following patch. While at it, improve the error
handling.
Signed-off-by: Laurentiu Tudor
---
drivers/pci/pcie_layerscape_fixup.c | 60 -
1 file changed, 34
From: Laurentiu Tudor
Fix duplication of this code by placing it in a common function.
Furthermore, the resulting function will be re-used in upcoming
patches.
Signed-off-by: Laurentiu Tudor
---
drivers/pci/pcie_layerscape_fixup.c | 68 +
1 file changed, 30
From: Laurentiu Tudor
In the current implementation, u-boot creates iommu mappings only
for PCI devices enumarated at boot time thus does not take into
account more dynamic scenarios such as SR-IOV or PCI hot-plug.
Add support for specifying extra IOMMU mappings for PCI
controllers through a
Dear Stefan Roese,
In message <20200813054800.469284-2...@denx.de> you wrote:
> Since commit 86cf1c82850f ("configs: Migrate CONFIG_NR_DRAM_BANKS") &
> commit 999a772d9f24 ("Kconfig: Migrate CONFIG_NR_DRAM_BANKS"),
> CONFIG_NR_DRAM_BANKS is always defined with a value (4 is default).
Has there
Dear Chris Packham,
In message <20200813013727.8186-1-judge.pack...@gmail.com> you wrote:
> When building envtools via tools-only_defconfig the builtin defaults
> are based on options in the defconfig. For example:
>
> bootcmd=bootp; setenv bootargs root=/dev/nfs
>
On 8/18/20 5:00 AM, Heinrich Schuchardt wrote:
> On 11.08.20 12:32, Sean Anderson wrote:
>> On 8/11/20 3:50 AM, Heinrich Schuchardt wrote:
>>> On 11.08.20 08:20, Rick Chen wrote:
Hi Heinrich
> From: Heinrich Schuchardt [mailto:xypron.g...@gmx.de]
> Sent: Tuesday, August 11,
On 8/18/20 5:22 AM, Bin Meng wrote:
> +Anup Patel
>
> On Wed, Jul 29, 2020 at 5:57 PM Sean Anderson wrote:
>>
>> We may need to add a clock-frequency binding like for the K210.
>>
>> Signed-off-by: Sean Anderson
>> ---
>> This patch builds but has NOT been tested.
>>
>> Changes in v2:
>> - Fix
Add g_dnl_get_board_bcd_device_number, the new BCD value is used by uuu to
distinguish
if the SPL supports the SDPV.
Signed-off-by: Peng Fan
---
arch/arm/mach-imx/spl.c | 6 ++
1 file changed, 6 insertions(+)
diff --git a/arch/arm/mach-imx/spl.c b/arch/arm/mach-imx/spl.c
index
From: Sherry Sun
Since the USB HID limits the maximum bandwidth(3072) for interrupt
endpoint transfers, when the bInterval set to 1, we can only support 3
boards to run sdp at the same time. In order to support more boards,
change the bInterval of interrupt endpoint to 3, which will not affect
From: Sherry Sun
EP0 has been used to transfer file data in sdp before, but the max
packetsize of ep0 is 64 bytes. So in order to improve the file transfer
speed, here add the EP1_OUT interrupt endpoint which max packetsize is
set to 1024 byte.
After testing, it turns out that using ep1out is
From: Ye Li
Add HS endpoint descriptor for SDP. So that we can use high speed endpoint,
and the SDP device can send packet with 512 byte size.
Signed-off-by: Ye Li
Signed-off-by: Peng Fan
---
drivers/usb/gadget/f_sdp.c | 30 --
1 file changed, 28 insertions(+), 2
1 - 100 of 124 matches
Mail list logo
