On Tue, Sep 24, 2019 at 04:58:48PM +1000, Jonathan Gray wrote:
> As of v2019.10-rc3 am335x_evm builds fail here as SPL doesn't fit.
>
> v2019.10-rc2 builds.
> v2019.10-rc4 still fails:
>
> LD spl/u-boot-spl
> arm-none-eabi-ld.bfd: u-boot-spl section `.u_boot_list' will not fit in
>
mt25qu512a flash has Flag status register that indicates various errors
that may be encountered during erase/write operations. Therefore add
USE_FSR flag to the entry
Signed-off-by: Vignesh Raghavendra
---
drivers/mtd/spi/spi-nor-ids.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
Newer variants of mt25q* flashes support 4 Byte addressing opcodes. Add
entries for the same. These flashes have bit 6 set in 5th byte of READ ID
response.
Signed-off-by: Vignesh Raghavendra
---
drivers/mtd/spi/spi-nor-ids.c | 3 +++
1 file changed, 3 insertions(+)
diff --git
Older variants of n25q256* and n25q512* do not support 4 Byte stateless
addressing opcodes. Therefore drop SPI_NOR_4B_OPCODES flag from these
entries.
Signed-off-by: Vignesh Raghavendra
---
drivers/mtd/spi/spi-nor-ids.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git
n25q variants do not support stateless 4 byte addressing opcodes by default,
therefore first patch disables this flag for those parts. Second patch
adds entries for mt25q variants which are similar to n25q but supports
stateless 4 byte opcodes. Third patch adds USE_FSR flag for mt25qu512a as
flash
On Tue, 24 Sep 2019 at 22:25, Lokesh Vutla wrote:
>
> Hi Peng,
>
> On 25/09/19 6:56 AM, Peng Fan wrote:
> > Hi Lokesh,
> >
> >> Subject: Re: [PATCH V2 2/2] core: device: use dev_power_domain_on
> >>
> >>
> >>
> >> On 17/09/19 2:59 PM, Peng Fan wrote:
> >>> When multiple power domains attached to
When multiple power domains attached to a device, need power on
them all, so use dev_power_domain_on to do that.
Signed-off-by: Peng Fan
Reviewed-by: Simon Glass
---
V3:
Add R-b tag
V2:
Use dev_power_domain_on
drivers/core/device.c | 6 +++---
1 file changed, 3 insertions(+), 3
Add this new API to power on multiple domains attached
to a device.
Signed-off-by: Peng Fan
Reviewed-by: Lokesh Vutla
Reviewed-by: Simon Glass
---
V3:
Fix build break
Add R-b tag
V2:
create dev_power_domain_on
drivers/power/domain/power-domain-uclass.c | 22 ++
On Sat, 14 Sep 2019 at 06:41, Thomas Fitzsimmons wrote:
>
> Hi Bin,
>
> Bin Meng writes:
>
> [...]
>
> > On Fri, Sep 6, 2019 at 7:52 PM Thomas Fitzsimmons
> > wrote:
> >>
> >> For CONFIG_OF_PRIOR_STAGE, in the absence of a device tree alias for a
> >> given device, use the next request number
On Tue, 24 Sep 2019 at 02:32, Philippe Reynes
wrote:
>
> The aes command used to segfault when accessing memory in sandbox.
> The pointer accesses should be mapped.
>
> Signed-off-by: Philippe Reynes
> ---
> cmd/aes.c | 14 ++
> 1 file changed, 10 insertions(+), 4 deletions(-)
On Mon, 16 Sep 2019 at 22:48, Simon Glass wrote:
>
> On Thu, 5 Sep 2019 at 02:49, wrote:
> >
> > From: Matthias Brugger
> >
> > The commit "libfdt: fdt_address_cells() and fdt_size_cells()" introduced
> > a bug as it consolidated code between the helpers for getting
> > be 0, and is frequently
Hi Doug,
On Tue, 3 Sep 2019 at 13:15, Douglas Anderson wrote:
>
> As per the centithread on ksummit-discuss [1], there are folks who
> feel that if a Change-Id is present in a developer's local commit that
> said Change-Id could be interesting to include in upstream posts.
> Specifically if two
On Tue, 24 Sep 2019 at 02:32, Philippe Reynes
wrote:
>
> This commit add the support of command aes.
> Then, it may be used on pytest.
>
> Signed-off-by: Philippe Reynes
> ---
> configs/sandbox64_defconfig | 1 +
> 1 file changed, 1 insertion(+)
>
Reviewed-by: Simon Glass
You could add this
On Tue, 17 Sep 2019 at 09:52, Simon Glass wrote:
>
> Hi Matthias,
>
> On Tue, 17 Sep 2019 at 00:29, Matthias Brugger wrote:
> >
> > Hi Simon,
> >
> > On 17/09/2019 07:48, Simon Glass wrote:
> > > Hi,
> > >
> > > On Thu, 5 Sep 2019 at 02:49, wrote:
> > >>
> > >> From: Matthias Brugger
> > >>
>
Hi Anatolij,
On Thu, 1 Aug 2019 at 00:44, Anatolij Gustschin wrote:
>
> Hi Lokesh,
>
> On Thu, 1 Aug 2019 09:43:39 +0530
> Lokesh Vutla lokeshvu...@ti.com wrote:
>
> >On 01/08/19 2:55 AM, Anatolij Gustschin wrote:
> >> The power domain associated with a device is enabled when probing,
> >> but
On Thu, 5 Sep 2019 at 01:49, wrote:
>
> From: Matthias Brugger
>
> Default address cells value on the livetree access function
> returns the wrong value. Fix this so that the value returned
> corresponds to the device tree specification.
>
> Signed-off-by: Matthias Brugger
> ---
>
>
Hi Patrick,
On Fri, 2 Aug 2019 at 05:48, Patrick Delaunay wrote:
>
> At present the 'Index' column of 'dm tree' assumes there is
> two digits, this patch increase it to 3 digits.
>
> It also aligns output of 'dm uclass', assuming the same 3 digits index.
>
> The boards with CONFIG_PINCTRL_FULL
On Wed, 18 Sep 2019 at 08:22, Giulio Benetti
wrote:
>
> Signed-off-by: Giulio Benetti
> ---
> scripts/dtc/libfdt/libfdt.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
Reviewed-by: Simon Glass
___
U-Boot mailing list
U-Boot@lists.denx.de
On Fri, 6 Sep 2019 at 04:52, Thomas Fitzsimmons wrote:
>
> When CONFIG_OF_PRIOR_STAGE is enabled, this workaround was needed
> before device_bind_common assigned request numbers sequentially in the
> absence of aliases.
>
> Signed-off-by: Thomas Fitzsimmons
> Cc: Bin Meng
> Cc: Simon Glass
>
On Tue, 24 Sep 2019 at 02:32, Philippe Reynes
wrote:
>
> This commit add a simple test to check that
> a text may be ciphered and unciphered. Each
> step are checked with the known result.
>
> Signed-off-by: Philippe Reynes
> ---
> test/py/tests/aes/iv128.bin | 1 +
>
On Tue, 24 Sep 2019 at 00:58, Lokesh Vutla wrote:
>
>
>
> On 17/09/19 2:59 PM, Peng Fan wrote:
> > Add this new API to power on multiple domains attached
> > to a device.
> >
> > Signed-off-by: Peng Fan
> > ---
> >
>
> [..snip..]
>
> > + */
> > +#if (CONFIG_IS_ENABLED(OF_CONTROL) &&
On Tue, 24 Sep 2019 at 02:32, Philippe Reynes
wrote:
>
> This commit enable the command aes on sandbox.
> Then, it may be used on pytest.
>
> Signed-off-by: Philippe Reynes
> ---
> configs/sandbox_defconfig | 1 +
> 1 file changed, 1 insertion(+)
Reviewed-by: Simon Glass
On Fri, 6 Sep 2019 at 16:08, Kayla Theil wrote:
>
> The reset function sets the pin to 0 then 1 but if the pin is marked
> ACTIVE_LOW in the DT it gets inverted and leaves the TPM in reset.
> Let the gpio driver take care of the reset polarity.
>
> Signed-off-by: Kayla Theil
> ---
>
On Fri, 6 Sep 2019 at 01:06, Patrick Delaunay wrote:
>
> Add a new flag CONFIG_ENV_SUPPORT to compile all
> the environment features in U-Boot (attributes, callbacks
> and flags); it is the supplement of the 2 existing flags
> for SPL/TPL.
> To have ENV support, enable the flag:
> -
Hi Jean-Jacques,
On Fri, 20 Sep 2019 at 09:18, Jean-Jacques Hiblot wrote:
>
> Hi Simon,
>
> while working with the FDT in the SPL, I came across an alignment issue.
> I have seen 64-bits integers not aligned on a 64-bit boundary, although
> is doesn't happen very often. According to the FDT
On Wed, 18 Sep 2019 at 08:05, Philippe Reynes
wrote:
>
> From: Daniele Alessandrelli
>
> Currently, if image verification with a required key fails, rsa_verify()
> code tries to find another key to verify the FIT image. This however, is
> not the intended behavior as the documentation says that
On Wed, 18 Sep 2019 at 08:05, Philippe Reynes
wrote:
>
> This commit add a test in the vboot test to check that
> when a required key is asked, only FIT signed with this
> key is used/accepted by u-boot.
>
> Signed-off-by: Philippe Reynes
> ---
> test/py/tests/test_vboot.py
On Wed, 18 Sep 2019 at 03:30, Patrick Delaunay wrote:
>
> This patch introduce a macro ENV_IS_IN_SOMEWHERE to check if the
> the environment can be saved somewhere, in a device or in a file system,
> without assumption on CONFIG$(SPL_TPL_)ENV_IS_NOWHERE.
>
> Since the commit 208bd2b85ecc ("env:
On Wed, 18 Sep 2019 at 03:30, Patrick Delaunay wrote:
>
> This patch corrects the check of env_flags_validate presence because
> "flags.c" is always compiled in U-Boot and CONFIG_ENV_SUPPORT
> don't exist; so the macro CONFIG_IS_ENABLED(ENV_SUPPORT) only provides
> the expected result for SPL and
On 2019/9/22 下午6:06, Andyshrk wrote:
From: Andy Yan
Specification
- Rockchip RK3399
- LPDDR4
- TF sd scard slot
- eMMC
- M.2 B-Key for 4G LTE
- AP6256 for WiFi + BT
- Gigabit ethernet
- HDMI out
- 40 pin header
- USB 2.0 x 2
- USB 3.0 x 1
- USB 3.0 Type-C x 1
- TYPE-C Power supply
Commit
On 2019/9/26 上午2:40, Heiko Stuebner wrote:
Originally the cpuid var the value gets read into was defined as
u8 cpuid[RK3399_CPUID_LEN];
hence the sizeof(cpuid) would return the correct the correct number
of array elements.
With the move to a separate function cpuid becomes a pointer and
On 2019/9/27 上午3:15, Heiko Stuebner wrote:
The commit 619f002db864 ("rockchip: make_fit_atf.py: fix loadables property
set error") fixed the double-loading of the primary atf-image, but didn't
take into account that there may be rare atf images with only that main
section present.
Right now
At present these two sections of code are linked together into a single
2KB chunk in a single file. Some Intel SoCs like to have a FIT (Firmware
Interface Table) in the ROM and the pointer for this needs to go at
0xffc0 which is in the middle of these two sections.
Make use of the new 'reset'
We use the Makefile for all ELF test files now, so drop all the code that
checks whether to get the test file from the Makefile or from the git
repo.
Also add a comment to the Makefile indicating that it is run from binman.
Signed-off-by: Simon Glass
---
tools/binman/elf_test.py | 5 +
Remove this file from git and instead build it using the Makefile.
Signed-off-by: Simon Glass
---
tools/binman/elf_test.py | 5 +++--
tools/binman/ftest.py | 2 +-
tools/binman/test/u_boot_binman_syms_size | Bin 4825 -> 0 bytes
3 files changed, 4
Entries which include a section and need to obtain its contents call
GetData(), as with any other entry. But the current implementation of this
method in entry_Section requires the size of the section to be known. If
it is unknown, an error is produced, since size is None:
TypeError: can't
Remove this file from git and instead build it using the Makefile.
Update tools.GetInputFilename() to support reading files from an absolute
path, so that we can read the Elf test files easily. Also make sure that
the temp directory is report in ELF tests as this was commented out.
At present this class reads its entries in the constructor. This is not
how things should be done now. Update it.
Signed-off-by: Simon Glass
---
tools/binman/etype/intel_ifwi.py | 3 +++
1 file changed, 3 insertions(+)
Applied to u-boot-dm, thanks!
Two of the test files somehow were not converted to three digits. Fix
them, using the next available numbers.
Signed-off-by: Simon Glass
---
tools/binman/ftest.py | 4 ++--
...rt_together.dts => 098_4gb_and_skip_at_start_together.dts} | 0
At present if libfdt is not available binman can't do anything much.
Improve the situation a little.
Ideally there should be a test to cover this, but I'm not quite sure how
to fake this.
Signed-off-by: Simon Glass
---
tools/binman/control.py | 10 --
Remove this file from git and instead build it using the Makefile.
With this change a few things need to be adjusted:
1. The 'notes' section no-longer appears at the start of the ELF file
(before the code), so update testSymbols to adjust the offsets.
2. The dynamic linker is disabled to avoid
At present these are large enough to hold 20 bytes of symbol data. Add
four more bytes so we can add another test.
Unfortunately at present this involves changing a few test files to make
room. We could adjust the test files to not specify sizes for entries.
Then we could make the tests check the
Since cros_subprocess use bytestrings now, this feature not needed. Drop
it.
Signed-off-by: Simon Glass
---
tools/patman/cros_subprocess.py | 3 +--
tools/patman/tools.py | 15 +++
2 files changed, 8 insertions(+), 10 deletions(-)
Applied to u-boot-dm, thanks!
At present the ELF test files are checked into the U-Boot tree. This is
covenient since the files never change and can be used on non-x86
platforms. However it is not good practice to check in binaries and in
this case it does not seem essential.
Update the binman test-file Makefile to support
It is more common to use the name 'cls' for the class object of a class
method, to distinguish it from normal methods, which use 'self' Update the
binman tests accordingly.
Signed-off-by: Simon Glass
---
tools/binman/ftest.py | 54 +--
1 file changed, 27
At present this command silently fails if something goes wrong. Use the
tools.Run() function instead, since it reports errors.
Signed-off-by: Simon Glass
---
tools/binman/elf.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Applied to u-boot-dm, thanks!
At present the Intel IFWI entry uses 'replace' without the 'ifwi-' prefix.
This is a fairly generic name which might conflict with the main Entry
base class at some point, if more features are added. Add a prefix.
Signed-off-by: Simon Glass
---
tools/binman/README.entries | 6
Remove this file from git and instead build it using the Makefile.
Signed-off-by: Simon Glass
---
tools/binman/elf_test.py | 2 +-
tools/binman/ftest.py | 10 +-
tools/binman/test/u_boot_no_ucode_ptr | Bin 4182 -> 0 bytes
3 files changed, 6
Remove this file from git and instead build it using the Makefile.
Signed-off-by: Simon Glass
---
tools/binman/elf_test.py | 4 ++--
tools/binman/test/Makefile | 2 +-
tools/binman/test/u_boot_binman_syms_bad | Bin 4890 -> 0 bytes
3 files changed, 3
Some versions of binutils generate hidden symbols which are currently not
parsed by binman. Correct this.
Signed-off-by: Simon Glass
---
tools/binman/elf.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Applied to u-boot-dm, thanks!
___
A Firmware Image Table (FIT) is a data structure defined by Intel which
contains information about various things needed by the SoC, such as
microcode.
Add support for this entry as well as the pointer to it. The contents of
FIT are fixed at present. Future work is needed to support adding
Recent versions of binutils add a '.note.gnu.property' into the ELF file.
This is not required and interferes with the expected output. Drop it.
Also fix testMakeElf() to use a different file for input and output.
Signed-off-by: Simon Glass
---
tools/binman/elf.py | 3 +++
At present tools are not expected to fail. If they do an exception is
raised but there is no detail about what went wrong. This makes it hard
to debug if something does actually go wrong.
Fix this by outputting both stderr and stdout on failure.
Signed-off-by: Simon Glass
---
At present the symbol information is written to binaries just before
binman exits. This is fine for entries within sections since the section
contents is calculated when it is needed, so the updated symbol values are
included in the image that is written.
However some binaries are inside entries
At present binman adds the image base address to the symbol value before
it writes it to the binary. This is not correct since the symbol value
itself (e.g. image position) has no relationship to the image base.
Fix this and update the tests to cover this case.
Signed-off-by: Simon Glass
---
At present a small number of test files use hyphens instead of
underscores. Rename them for consistency.
Signed-off-by: Simon Glass
---
tools/binman/ftest.py | 28 +--
.../test/{029_x86-rom.dts => 029_x86_rom.dts} | 0
...no-desc.dts =>
The Intel IFWI (Integrated Firmware Image) is effectively a section with
other entries inside it. Support writing symbol information into entries
within it.
Signed-off-by: Simon Glass
---
tools/binman/etype/intel_ifwi.py | 5 +
1 file changed, 5 insertions(+)
Applied to u-boot-dm, thanks!
It is useful to be able to access the size of an image in SPL, with
something like:
binman_sym_declare(unsigned long, u_boot_any, size);
...
ulong u_boot_size = binman_sym(ulong, u_boot_any, size);
Add support for this and update the tests.
Signed-off-by: Simon Glass
---
This comment references another entry type. Fix it.
Signed-off-by: Simon Glass
---
tools/binman/etype/intel_descriptor.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Applied to u-boot-dm, thanks!
___
U-Boot mailing list
At present binman has a single entry type for the 16-bit code code needed
to start up an x86 processor. This entry is intended to include both the
reset vector itself as well as the code to move to 32-bit mode.
However this is not very flexible since in some cases other data needs to
be included
Add support for the ProcessContents() method in this entry so that it is
possible to support entries which change after initial creation.
Signed-off-by: Simon Glass
---
tools/binman/etype/intel_ifwi.py | 46 +++-
1 file changed, 28 insertions(+), 18 deletions(-)
The Intel FSP supports initialising memory early during boot using a binary
blob called 'fspm'. Add support for this.
Signed-off-by: Simon Glass
---
tools/binman/README.entries | 17 +
tools/binman/etype/intel_fsp_m.py | 27 +++
At present this entry does not work correctly when a FIT image is used as
the input. It updates the FIT instead of the output image. The test passed
because the FIT image happened to have the right data already.
Fix it.
Signed-off-by: Simon Glass
---
tools/binman/etype/intel_ifwi.py | 6
At present we only support symbols inside binaries which are at the top
level of an image. This restrictions seems unreasonable since more complex
images may want to group binaries within different sections.
Relax the restriction.
Also fix a typo in the comment for testTpl().
Signed-off-by:
This code is not needed so drop it.
Signed-off-by: Simon Glass
---
tools/binman/ftest.py | 2 --
1 file changed, 2 deletions(-)
Applied to u-boot-dm, thanks!
___
U-Boot mailing list
U-Boot@lists.denx.de
https://lists.denx.de/listinfo/u-boot
Sometimes binman takes multiple passes to complete packing an image. Add
logging to indicate this.
Signed-off-by: Simon Glass
---
tools/binman/control.py | 1 +
1 file changed, 1 insertion(+)
Applied to u-boot-dm, thanks!
___
U-Boot mailing list
On 9/26/19 8:52 PM, Vagrant Cascadian wrote:
> On 2019-08-20, Vagrant Cascadian wrote:
>> On 2019-08-19, Marek Vasut wrote:
>>> On 6/4/19 9:06 AM, Vagrant Cascadian wrote:
On 2019-05-17, Marek Vasut wrote:
> Update Kosagi Novena to DM / DT and remove the warnings.
>> ...
I have two
Hi Vagrant,
On Thu, Sep 26, 2019 at 4:16 PM Vagrant Cascadian wrote:
>
> I just tested mx6cuboxi with 2019.10-rc4, and it fails to load
> u-boot.img from MMC:
>
> 1 2019-09-26_17:31:27.63089 U-Boot SPL 2019.10-rc4+dfsg-1 (Sep 24 2019 -
> 08:03:23 +)
> 2 2019-09-26_17:31:27.63092 Trying to
I just tested mx6cuboxi with 2019.10-rc4, and it fails to load
u-boot.img from MMC:
1 2019-09-26_17:31:27.63089 U-Boot SPL 2019.10-rc4+dfsg-1 (Sep 24 2019 -
08:03:23 +)
2 2019-09-26_17:31:27.63092 Trying to boot from MMC2
3 2019-09-26_17:31:27.63095 MMC Device 1 not found
4
The commit 619f002db864 ("rockchip: make_fit_atf.py: fix loadables property
set error") fixed the double-loading of the primary atf-image, but didn't
take into account that there may be rare atf images with only that main
section present.
Right now this will result in a broken its due to the
On 2019-08-20, Vagrant Cascadian wrote:
> On 2019-08-19, Marek Vasut wrote:
>> On 6/4/19 9:06 AM, Vagrant Cascadian wrote:
>>> On 2019-05-17, Marek Vasut wrote:
Update Kosagi Novena to DM / DT and remove the warnings.
> ...
>>> I have two oustanding issues... with some files it sometimes
The following changes since commit 31e086e460fb5de6dd42559babdc1e027ed2fe96:
Prepare v2019.10-rc4 (2019-09-23 12:24:39 -0400)
are available in the Git repository at:
https://gitlab.denx.de/u-boot/custodians/u-boot-efi.git
tags/efi-2019-10-rc5
for you to fetch changes up to
On 9/25/2019 5:30 PM, Troy Kisky wrote:
> This fixes commit <91435cd40d30> "ARM: i.MX6: exclude the ARM errata
> from i.MX6 UP system"
>
> for nitrogen6x. The above commit removed the errata for the board
> since MX6Q/MXDL/MX6S is selected via CONFIG_SYS_EXTRA_OPTIONS
>
> This restores the
On Thu, Sep 26, 2019 at 7:32 PM Schrempf Frieder
wrote:
>
> On 14.09.19 00:44, Schrempf Frieder wrote:
> > From: Frieder Schrempf
> >
> > Most boards currently use SPI_FLASH_MTD only in U-Boot proper, not in
> > SPL. They often rely on hacks in the board header files to include
> > this option
On 14.09.19 00:44, Schrempf Frieder wrote:
> From: Frieder Schrempf
>
> Most boards currently use SPI_FLASH_MTD only in U-Boot proper, not in
> SPL. They often rely on hacks in the board header files to include
> this option conditionally. To be able to fix this, we previously
> introduced a
pcl063 phycore SoM with eMMC also got usdhc reset pin,
add reset pin to pinmux.
Signed-off-by: Parthiban Nallathambi
---
arch/arm/dts/pcl063-common.dtsi | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/arch/arm/dts/pcl063-common.dtsi b/arch/arm/dts/pcl063-common.dtsi
index
When DEVRES is not set, devm_kmalloc_array() is spelled
devm_kmaloc_array() (with one 'l' only).
Fixing it so that the name is the same with and without DEVRES.
Signed-off-by: Jean-Jacques Hiblot
---
include/dm/device.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
According to the documentation in clk.h, clk_set_parent() return the new
rate of the clock or a negative error code.
Signed-off-by: Jean-Jacques Hiblot
---
drivers/clk/clk-uclass.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/clk/clk-uclass.c
U-Boot uses CONFIG_SPI_FLASH_USE_4K_SECTORS to enable 4K small sector
support. Use that instead of MTD_SPI_NOR_USE_4K_SECTORS.
Reported-by: Eugeniy Paltsev
Signed-off-by: Vignesh Raghavendra
---
drivers/mtd/spi/spi-nor-core.c | 2 +-
drivers/mtd/spi/spi-nor-ids.c | 2 +-
2 files changed, 2
Use dev_err() when reporting reason for erase/write failures so that
users can be made aware of the reason for failure.
Signed-off-by: Vignesh Raghavendra
---
drivers/mtd/spi/spi-nor-core.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/mtd/spi/spi-nor-core.c
First patch improves error reporting on erase/write failures
Second patch makes sure small sector is used even when SFDP is enabled
and CONFIG_SPI_FLASH_USE_4K_SECTORS is set.
Jagan,
Could you please consider these patches for next -rc?
Vignesh Raghavendra (2):
mtd: spi-nor-core: Use dev_err
Looking at the original commit
https://lists.denx.de/pipermail/u-boot/2014-June/181599.html
It looks like it puts the result into the variable $filesize just as the
other commands which read files do.
Regards,
Jack.
On 26/09/2019 08:27, Adarsh Babu Kalepalli wrote:
> Hello,
>
> Commands "size
On Thu, 2019-09-19 at 11:03 +0530, Jagan Teki wrote:
> Hi Kever,
>
> On Wed, Sep 18, 2019 at 10:31 AM Jagan Teki
> wrote:
> >
> >
> > On Wed, Sep 18, 2019 at 9:09 AM Kever Yang
> > wrote:
> > >
> > >
> > > Hi Jagan,
> > >
> > > Seems like your and Kurt's board have different DRAM
On Wed, Sep 25, 2019 at 4:15 PM Simon Glass wrote:
>
> At present the name of the image comes first in the linker-list symbol
> used. This means that the name of the function sets the sort order, which
> is not the intention.
>
> Update it to put the board device type first, then the priority.
You've got the config name wrong in the summary (forgot '_SIZE' in the middle).
On Wed, Sep 25, 2019 at 5:24 PM Simon Glass wrote:
>
> This is currently a decimal value which is not as convenient or
> meaningful. Also U-Boot tends to use hex everywhere.
>
> Convert this option to hex and add a
Hi Simon,
On Wed, Sep 25, 2019 at 5:36 PM Simon Glass wrote:
>
> We have the ability to enforce a maximum size for SPL but not yet for TPL.
> Add a new option for this.
>
> Document the size check macro while we are here.
>
> Signed-off-by: Simon Glass
> ---
>
> Makefile | 7 +++
Hello,
Commands "size / ext4size / fatsize" do not display the file size.
+ u-boot version:2019.10-rc4
+ H/W Board : Beaglebone Black
+ Command Causing Issue: size/ext4size/fatsize
+ Command Output: Size of the mentioned file is not displayed on serial
console.
Console Output from
Hi,
+ u-boot version:2019.10-rc4
+ H/W Board : Beaglebone Black
+ Issue : Unable to delete the hush shell local variables
with 'local_variable_name=' at the shell prompt
(similar to 'setenv env_variable_name'),I tried to
delete a Hush shell local variable after creating it.
This approach did
Hi Tom,
> From: Tom Rini
> Sent: vendredi 20 septembre 2019 21:03
>
> On Fri, Sep 20, 2019 at 11:09:14AM +0200, Stefan Roese wrote:
> > Hi Patrick,
> >
> > On 18.09.19 11:29, Patrick Delaunay wrote:
> > >This patchset is a the 3rd version of
> > >
Hi Patrick,
Patrick DELAUNAY wrote on Thu, 26 Sep 2019
09:31:46 +:
> Hi Stefan,
>
> > From: Stefan Roese
> > Sent: vendredi 20 septembre 2019 11:20
> >
> > Hi Patrick,
> >
> > On 20.09.19 09:20, Patrick Delaunay wrote:
> > > This patch modify the loop in mtd erase command to erase one
Hi Stefan,
> From: Stefan Roese
> Sent: vendredi 20 septembre 2019 11:20
>
> Hi Patrick,
>
> On 20.09.19 09:20, Patrick Delaunay wrote:
> > This patch modify the loop in mtd erase command to erase one by one
> > the blocks in the requested area.
> >
> > It solves issue on "mtd erase" command
Hi Tom, Simon,
> On Wed, Sep 25, 2019 at 02:42:03PM -0600, Simon Glass wrote:
> > Hi Lukasz,
> >
> > On Tue, 17 Sep 2019 at 15:06, Lukasz Majewski
> > wrote:
> > >
> > > On Tue, 17 Sep 2019 14:19:33 -0500
> > > Adam Ford wrote:
> > >
> > > > On Tue, Sep 17, 2019 at 1:34 PM Simon Glass
> >
From: Joseph Chen
The RK809 is a Power Management IC (PMIC) for multimedia
and handheld devices. They contains the following components:
- Regulators(5*BUCKs, 9*LDOs, 2*SWITCHs)
- RTC
- Clocking
Signed-off-by: Joseph Chen
Signed-off-by: Elaine Zhang
Reviewed-by: Kever Yang
---
The RK805 are a Power Management IC (PMIC) for multimedia
and handheld devices. They contains the following components:
- Regulators(4*BUCKs, 3*LDOs)
- RTC
- Clocking
Signed-off-by: Elaine Zhang
Reviewed-by: Kever Yang
---
drivers/power/pmic/rk8xx.c | 1 +
From: Joseph Chen
The RK817 is a Power Management IC (PMIC) for multimedia
and handheld devices. They contains the following components:
- Regulators(4*BUCKs, 1* BOOST, 9*LDOs, 1*SWITCH)
- RTC
- Clocking
Signed-off-by: Joseph Chen
Signed-off-by: Elaine Zhang
Reviewed-by: Kever
The RK816 is a Power Management IC (PMIC) for multimedia
and handheld devices. They contains the following components:
- Regulators(4*BUCKs, 1*BOOST, 6*LDOs, 1*SWITCH)
- RTC
- Clocking
Signed-off-by: Elaine Zhang
Reviewed-by: Kever Yang
---
drivers/power/pmic/rk8xx.c | 1 +
From: Joseph Chen
support parse regulator standard property:
regulator-off-in-suspend;
regulator-init-microvolt;
regulator-suspend-microvolt:
regulator_get_suspend_enable
regulator_set_suspend_enable
regulator_get_suspend_value
regulator_set_suspend_value
Signed-off-by: Joseph Chen
In order to adapt the following pmics, make the interface more compatible.
Support buck and ldo suspend voltage setting and getting.
Supprot buck and ldo suspend enable/disable setting and getting.
Signed-off-by: Elaine Zhang
Reviewed-by: Kever Yang
---
drivers/power/regulator/rk8xx.c | 547
Support more PMIC and improve compatibility between pmics.
Change in V4:
[PATCH v4 1/6]: No change.
[PATCH v4 2/6]: No change.
[PATCH v4 3/6]: No change.
[PATCH v4 4/6]: No change.
[PATCH v4 5/6]: Resolve code conflicts after ptach v3 5/8 and 6/8 deletion.
[PATCH v4 6/6]: Resolve code conflicts
Add support for printing CPU info for all K3 devices.
Signed-off-by: Lokesh Vutla
---
arch/arm/mach-k3/common.c| 43
arch/arm/mach-k3/common.h| 15 +
arch/arm/mach-k3/include/mach/hardware.h | 24 +
3 files changed, 82
1 - 100 of 105 matches
Mail list logo
