Building 32bit boards with the TCG2 protocol enabled leads to a build
warning due to a missing conversion.
lib/efi_loader/efi_tcg2.c: In function 'tcg2_measure_pe_image':
lib/efi_loader/efi_tcg2.c:856:47: error: cast from pointer to
integer of different size
There is a QSPI NOR flash part on the board. Because this chip isn't
yet supported in Linux, but it is supported in U-Boot, and the
face that the RPC_SPI compatible names are different in U-Boot and
Linux, the device tree updates are confined to -u-boot.dtsi files.
Signed-off-by: Adam Ford
Re: [PATCH] common: The do_repeat flag interferes with commands issued via
run_command API
The tag here should be "hush: ..." The subject should be an action,
such as "Clear do_repeat flag after running commands".
On 5/27/21 5:24 PM, Farhan Ali wrote:
Must clear the do_repeat flag once it is
On 21/05/2021 16.42, Heinrich Schuchardt wrote:
> On 21.05.21 16:27, Tom Rini wrote:
>> On Fri, May 21, 2021 at 04:15:39PM +0200, Heinrich Schuchardt wrote:
>>> On 21.05.21 14:53, Rasmus Villemoes wrote:
On 20/05/2021 19.51, Simon Glass wrote:
> Hi Rasmus,
>
> On Thu, 20 May 2021
U-Boot doesn't support %pS/%pF or any other kind of kallsyms-like
lookups. Remove the comment.
Reviewed-by: Simon Glass
Signed-off-by: Rasmus Villemoes
---
lib/vsprintf.c | 3 ---
1 file changed, 3 deletions(-)
diff --git a/lib/vsprintf.c b/lib/vsprintf.c
index cf3982eb03..af0a6e1dcf 100644
There's currently no user of %p[iI]6, so including ip6_addr_string()
in the image is a waste of bytes. It's easy enough to have the
compiler elide it without removing the code completely.
The closest I can find to anybody "handling" ipv6 in U-Boot currently
is in efi_net.c which does
if
This saves some code, both in terms of #LOC and .text size, and it is
also the normal convention that foo(...) is implemented in terms of
vfoo().
Reviewed-by: Simon Glass
Signed-off-by: Rasmus Villemoes
---
lib/vsprintf.c | 13 +
1 file changed, 1 insertion(+), 12 deletions(-)
Apparently, improving the QoI of vsnprintf() is too controversial. So
here are the uncontended parts of that series with Simon's R-bs added.
It's not a huge image reduction:
$ ../linux/scripts/bloat-o-meter lib/vsprintf.o.{0,1}
add/remove: 0/0 grow/shrink: 0/2 up/down: 0/-218 (-218)
Function
It seems that no other test has claimed gpio_a:7 yet, so use that.
The only small wrinkle is modifying the existing wdt test to use
uclass_get_device_by_driver() since we now have two UCLASS_WDT
instances in play, so it's a little more robust to fetch the device by
driver and not merely
Check that the watchdog_reset() implementation in wdt-uclass behaves
as expected:
- resets all activated watchdog devices
- leaves unactivated/stopped devices alone
- that the rate-limiting works, with a per-device threshold
Signed-off-by: Rasmus Villemoes
---
arch/sandbox/dts/test.dts | 2 ++
A rather common kind of external watchdog circuit is one that is kept
alive by toggling a gpio. Add a driver for handling such a watchdog.
The corresponding linux driver apparently has support for some
watchdog circuits which can be disabled by tri-stating the gpio, but I
have never actually
A later refactoring will put most of initr_watchdog() into a
.post_probe function, which means that all watchdog devices end up
being subject to the auto-start functionality. For the unit tests, it
is more convenient if the tests are in charge of when the watchdog
devices are started and stopped.
A board can have and make use of more than one watchdog device, say
one built into the SOC and an external gpio-petted one. Having
wdt-uclass only handle the first is both a little arbitrary and
unexpected.
So change initr_watchdog() so we visit (probe) all DM watchdog
devices. This essentially
In preparation for handling all DM watchdogs in watchdog_reset(), pull
out the code which handles starting (or not) the gd->watchdog_dev
device.
Include the device name in various printfs.
Signed-off-by: Rasmus Villemoes
---
drivers/watchdog/wdt-uclass.c | 37
As a step towards handling all DM watchdogs in watchdog_reset(), use a
per-device flag to keep track of whether the device has been started
instead of a bit in gd->flags.
We will still need that bit to know whether we are past
initr_watchdog() and hence have populated gd->watchdog_dev -
As preparation for having the wdt-uclass provided watchdog_reset()
function handle all DM watchdog devices, and not just the first such,
introduce a uclass-owned struct to hold the reset_period and
next_reset, so these become per-device instead of being static
variables.
No functional change
The addition of .pre_probe and .per_device_auto made this look
bad. Fix it.
Signed-off-by: Rasmus Villemoes
---
drivers/watchdog/wdt-uclass.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/watchdog/wdt-uclass.c b/drivers/watchdog/wdt-uclass.c
index
wdt_start() does the "no ->start? return -ENOSYS" check, don't
open-code that in wdt_expire_now().
Also, wdt_start() maintains some global (and later some per-device)
state, which would get out of sync with this direct method call - not
that it matters much here since the board is supposed to
This series is an attempt at expanding the wdt-uclass provided
watchdog_reset() to handle all DM watchdogs, not just the first
one. As a sort of nice side effect, it turns out that doing that makes
wdt-uclass fit better into the uclass model, in that we now do the
work that was previously done in
The original URL that explains the boot mode setting is no longer
valid.
Update to the new one.
Signed-off-by: Fabio Estevam
---
board/technexion/pico-imx6/README | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/board/technexion/pico-imx6/README
On 5/27/21 2:33 AM, opensource@gmail.com wrote:
From: Adarsh Babu Kalepalli
After executing the test-cases from pytest ,the board
is still powered.Shutting down the board power supply at
this point ,would keep the board safe.
FWIW, this violates the original design of the test system.
Must clear the do_repeat flag once it is consumed.
Signed-off-by: Farhan Ali
Cc: Simon Glass
Cc: Sean Anderson
Cc: Rasmus Villemoes
Cc: Farhan Ali
Cc: "peng.w...@smartm.com"
Cc: Patrick Delaunay
---
common/cli_hush.c | 5 +
1 file changed, 5 insertions(+)
diff --git
On 26/05/21 10:35PM, Jagan Teki wrote:
> On Mon, May 10, 2021 at 6:50 PM Pratyush Yadav wrote:
> >
> > Jagan,
> >
> > On 05/05/21 03:11PM, Pratyush Yadav wrote:
> > > Hi,
> > >
> > > This series adds support for octal DTR flashes in the SPI NOR framework,
> > > and then adds hooks for the Cypress
This should have
Reviewed-by: Heiko Schocher
from v1, which I forgot to add.
On 5/27/21 12:02 PM, Sean Anderson wrote:
If a chunk was larger than 4GiB, then chunk_data_sz would overflow and
blkcnt would not be calculated correctly. Upgrade it to a u64 and cast
its multiplicands as well. Also
If a chunk was larger than 4GiB, then chunk_data_sz would overflow and
blkcnt would not be calculated correctly. Upgrade it to a u64 and cast
its multiplicands as well. Also fix bytes_written while we're at it.
Signed-off-by: Sean Anderson
---
sizes for pico-dwarf-imx7d are as follows:
text
On 5/27/21 11:40 AM, Stefano Babic wrote:
Hi Sean,
On 27.05.21 17:27, Sean Anderson wrote:
On 5/27/21 10:59 AM, Stefano Babic wrote:
> Hi Frieder,
>
> On 27.05.21 16:47, Frieder Schrempf wrote:
>> Hi,
>>
>> On 06.04.21 11:34, Peng Fan (OSS) wrote:
>>> Hi Stefano,
>>>
>>> Please
Greetings,
I support various iMX8M PCB's via board/gateworks/venice that are SOM based
and we are starting to add SOM's that have different IMX8M variant SoC's on
them which for various reasons are not binary compatible. I'm very
interested in coming up with a way to make them binary compatible
Hi Sean,
On 27.05.21 17:27, Sean Anderson wrote:
On 5/27/21 10:59 AM, Stefano Babic wrote:
> Hi Frieder,
>
> On 27.05.21 16:47, Frieder Schrempf wrote:
>> Hi,
>>
>> On 06.04.21 11:34, Peng Fan (OSS) wrote:
>>> Hi Stefano,
>>>
>>> Please pull nxp-imx-2021-4-6. This PR is based on
On 5/27/21 10:59 AM, Stefano Babic wrote:
> Hi Frieder,
>
> On 27.05.21 16:47, Frieder Schrempf wrote:
>> Hi,
>>
>> On 06.04.21 11:34, Peng Fan (OSS) wrote:
>>> Hi Stefano,
>>>
>>> Please pull nxp-imx-2021-4-6. This PR is based on Tom's master branch. If
you need
>>> me rebase on imx/master,
Hi Stefano,
On 27.05.21 16:59, Stefano Babic wrote:
> Hi Frieder,
>
> On 27.05.21 16:47, Frieder Schrempf wrote:
>> Hi,
>>
>> On 06.04.21 11:34, Peng Fan (OSS) wrote:
>>> Hi Stefano,
>>>
>>> Please pull nxp-imx-2021-4-6. This PR is based on Tom's master branch. If
>>> you need
>>> me rebase on
On Thu, May 27, 2021 at 05:04:58PM +0530, Lokesh Vutla wrote:
> Hi Tom,
> Please find the PR for master branch targeted for v2021.07-rc4 release.
> Details about the PR are updated in the tag message.
>
> Gitlab CI report:
>
Hi Frieder,
On 27.05.21 16:47, Frieder Schrempf wrote:
Hi,
On 06.04.21 11:34, Peng Fan (OSS) wrote:
Hi Stefano,
Please pull nxp-imx-2021-4-6. This PR is based on Tom's master branch. If you
need
me rebase on imx/master, I could redo this PR. This is quite a large PR, since
lots
stuff in
Hi,
On 06.04.21 11:34, Peng Fan (OSS) wrote:
> Hi Stefano,
>
> Please pull nxp-imx-2021-4-6. This PR is based on Tom's master branch. If you
> need
> me rebase on imx/master, I could redo this PR. This is quite a large PR,
> since lots
> stuff in downstream tree.
>
> I ran local buildman test
On Thu, May 27, 2021 at 7:20 PM Tom Rini wrote:
> On Thu, May 27, 2021 at 06:41:35PM +0800, Leo Liang wrote:
> > On Thu, May 27, 2021 at 04:57:17PM +0800, Green Wan wrote:
> > > Hi Tom,
> > >
> > > Thanks for the comments.
> > >
> > > Not sure whether it catches differentconcerns, I plan to
Add defconfig and board support for HiFive Unmatched.
Signed-off-by: Green Wan
Reviewed-by: Bin Meng
Reviewed-by: Rick Chen
---
arch/riscv/Kconfig | 4 +
board/sifive/unleashed/Kconfig | 1 +
board/sifive/unmatched/Kconfig | 51 +++
Add dts files for SiFive Unmatched board.
Signed-off-by: Green Wan
Reviewed-by: Rick Chen
---
arch/riscv/dts/Makefile |1 +
.../dts/fu740-hifive-unmatched-a00-ddr.dtsi | 1489 +
.../dts/hifive-unmatched-a00-u-boot.dtsi | 41 +
Clear feature disable CSR to turn on all features of hart. The detail
is specified at section, 'SiFive Feature Disable CSR', in user manual
https://sifive.cdn.prismic.io/sifive/aee0dd4c-d156-496e-a6c4-db0cf54bbe68_sifive_U74MC_rtl_full_20G1.03.00_manual.pdf
Signed-off-by: Green Wan
Reviewed-by:
Add dts support for fu740. The HiFive Unmatched support is based on
fu740 cpu and drivers in following patch set.
Signed-off-by: Green Wan
[greentime.hu: set fu740 speed to 1.2GHz]
Signed-off-by: Greentime Hu
Reviewed-by: Bin Meng
Reviewed-by: Rick Chen
---
Add pcie driver for SiFive fu740, the driver depends on
fu740 gpio, clk and reset driver to do init. Force running at Gen1
for better capatible enumeration.
Several devices are tested:
a) M.2 NVMe SSD
b) USB-to-PCI adapter
c) Ethernet adapter (E1000 compatible)
Signed-off-by: Green Wan
Add fu740 support. One abstract layer is added for supporting
multiple chips such as fu540 and fu740.
Signed-off-by: Green Wan
---
arch/riscv/cpu/fu540/Kconfig | 2 +-
drivers/clk/sifive/Kconfig | 8 +-
drivers/clk/sifive/Makefile | 4 +-
drivers/clk/sifive/fu540-prci.c |
Rename fu540_ddr.c to sifive_ddr.c and add fu740 support
Signed-off-by: Green Wan
Reviewed-by: Bin Meng
---
drivers/ram/sifive/Kconfig| 8 +-
drivers/ram/sifive/Makefile | 2 +-
.../ram/sifive/{fu540_ddr.c => sifive_ddr.c} | 89 ++-
3
Add SiFive fu740 cpu to support RISC-V arch
Signed-off-by: Green Wan
Reviewed-by: Bin Meng
---
arch/riscv/Kconfig| 1 +
arch/riscv/cpu/fu740/Kconfig | 37 +++
arch/riscv/cpu/fu740/Makefile | 12 +
arch/riscv/cpu/fu740/cache.c
This patch set is to add SiFive fu740 chip and HiFive Unmatched board
support. Patches are split into several parts:
- [PATCH v12 1/8] support for fu740 cpu
- [PATCH v12 2/8] support for fu740 clk driver
- [PATCH v12 3/8] rename and support for fu740 ram driver
- [PATCH v12 4/8] add pcie
On Wed, 26 May 2021 at 13:57, Jorge Ramirez-Ortiz wrote:
>
> Use the more generic reset-gpios propery name.
>
> Signed-off-by: Jorge Ramirez-Ortiz
> ---
> doc/device-tree-bindings/tpm2/tis-tpm2-spi.txt | 2 +-
> drivers/tpm/tpm2_tis_spi.c | 2 +-
> 2 files changed, 2
Hi Andre,
On Sun, 23 May 2021 at 18:37, Andre Przywara wrote:
>
> At the moment the fastboot code relies on the Kconfig variable
> CONFIG_FASTBOOT_FLASH_MMC_DEV to point to the MMC device to use for the
> flash command. This value needs to be the *U-Boot device number*, which
> recently got more
Hi Joao,
On Sun, 23 May 2021 at 20:31, Joao Marcos Costa wrote:
>
> Remove the previous OOP approach, which was confusing and incomplete.
> Add more test cases by making SquashFS images with various options,
> concerning file fragmentation and its compression. Add comments to
> properly document
On 27.05.21 15:19, Jan Kiszka wrote:
> From: Jan Kiszka
>
> dev_read_addr_size() is inconsistent in too many ways. In particular,
> it does not retrieve the correct address/size cell number from the DT.
> dev_read_addr_size_index() does the right thing, so use that for now.
>
> This fixes
From: Jan Kiszka
dev_read_addr_size() is inconsistent in too many ways. In particular,
it does not retrieve the correct address/size cell number from the DT.
dev_read_addr_size_index() does the right thing, so use that for now.
This fixes reading the address size e.g. on boards with the 64-bit
On Sun, May 23, 2021 at 01:00:56PM -0400, Sean Anderson wrote:
> ut_asserteq_strn is defined twice. Remove one definition.
>
> Fixes: 33d7edfd5f ("test: Add a way to check part of a console line or skip
> it")
> Signed-off-by: Sean Anderson
> Reviewed-by: Heinrich Schuchardt
Applied to
On Fri, May 21, 2021 at 09:59:45PM +0200, Harm Berntsen wrote:
> Commit 712cc962b70d ("GitLab: Remove "tags" stanzas") removed the 'all'
> tag from all the jobs. The sandbox_noinst_test.py test was added in
> between the author date and commit date (commit 6c914e4232cd
> ("azure/gitlab: Add tests
On Thu, May 20, 2021 at 10:09:46PM +0300, Alper Nebi Yasak wrote:
> Commit 1ba21bb06b08 ("test: Don't unmount not (yet) mounted system")
> fixes an issue in the filesystem tests where the test setup may fail
> to mount an image and still attempt to unmount it. However, the commit
>
On Thu, May 20, 2021 at 01:08:44PM +0200, Michal Simek wrote:
> A lot of entries were using spaces instead of tab for alignment that's why
> it is good to fix it to use the same style everywhere.
>
> Signed-off-by: Michal Simek
> Reviewed-by: Simon Glass
Applied to u-boot/master, thanks!
--
On Mon, May 17, 2021 at 05:32:48PM +, Matt Merhar wrote:
> The assembly output of the arch_initr_trap() function differed by a
> single byte after common.h was removed from traps.c:
>
> fff49a18 :
> fff49a18: 94 21 ff f0 stwur1,-16(r1)
> fff49a1c: 7c 08 02 a6 mflr
On Tue, May 18, 2021 at 12:39:39AM +0200, Marek Vasut wrote:
> The superblock buffer must be cache aligned, since it might be used
> in DMA context, allocate it using ALLOC_CACHE_ALIGN_BUFFER() just
> like it was done in btrfs_read_superblock() and read_tree_node().
>
> This fixes this output on
On Mon, May 17, 2021 at 08:21:39AM +0200, Heinrich Schuchardt wrote:
> When reading directories the UEFI sub-system must supply file attributes
> and timestamps. These fields will have to be added to struct fs_dirent.
> SquashFS should not fill these fields with random data. Ensure that they
>
On Sat, May 15, 2021 at 02:13:54PM -0400, Sean Anderson wrote:
> Some callers (e.g. cmd/fs.c) of fs_set_blk_dev may use a NULL dev_part_str.
> While blk_get_device_part_str handles this fine,
> part_get_info_by_dev_and_name does not. This fixes commands crashing when
> implicitly using
On Fri, May 07, 2021 at 02:40:34PM +0530, Vignesh Raghavendra wrote:
> If reg property of pinctrl-single node requires address translation then
> probe fails with following message:
>
> single-pinctrl pinctrl@4301c000: failed to get base register size
>
> This is because driver uses
Hi Tom,
Please find the PR for master branch targeted for v2021.07-rc4 release.
Details about the PR are updated in the tag message.
Gitlab CI report:
https://source.denx.de/u-boot/custodians/u-boot-ti/-/pipelines/7645
The following changes since commit
On Thu, May 27, 2021 at 12:38 AM Andre Przywara wrote:
>
> On Wed, 26 May 2021 23:51:41 +0530
> Jagan Teki wrote:
>
> Hi,
>
> > On Wed, May 26, 2021 at 11:02 PM Andre Przywara
> > wrote:
> > >
> > > On Wed, 26 May 2021 22:37:14 +0530
> > > Jagan Teki wrote:
> > >
> > > Hi Jagan,
> > >
> > >
Macronix NAND Flash devices are available in different configurations
and densities.
MX"35" means SPI NAND
MX35"LF"/"UF" , LF means 3V and UF meands 1.8V
MX35LF"2G" , 2G means 2Gbits
MX35LF2G"E4"/"24"/"14",
E4 means internal ECC and Quad I/O(x4)
24 means 8-bit ecc requirement and Quad I/O(x4)
14
On Thu, May 27, 2021 at 06:41:35PM +0800, Leo Liang wrote:
> On Thu, May 27, 2021 at 04:57:17PM +0800, Green Wan wrote:
> > Hi Tom,
> >
> > Thanks for the comments.
> >
> > Not sure whether it catches differentconcerns, I plan to remove
> > fdt_high and initrd_high sincethe bootm_* settings
On Wed, 12 May 2021 20:08:25 +0530, Vignesh Raghavendra wrote:
> AM64x GP and SK EVM have DP83867 PHY connected to CPSW external port0.
> Enable the driver in order to use ethernet at U-Boot prompt.
> CONFIG_PHY_TI is selected by CONFIG_PHY_TI_DP83867 and thus can be dropped.
Applied to
On Tue, 18 May 2021 16:38:25 -0500, Suman Anna wrote:
> The default U-Boot environment variables and design are all set up for
> both the MAIN R5FSS clusters to be in Split-mode. This is the setting
> in v2021.01 U-Boot and the dt nodes are synched with the kernel binding
> property names in
On Thu, 13 May 2021 20:10:54 -0500, Suman Anna wrote:
> The following patches fix the 'reset' command functionality for various
> TI K3 SoCs. Patches are based on the latest master that includes the
> AM64x board support, commit ea184cbff99e ("Merge tag 'ti-v2021.07-rc3'
> of
On Mon, 19 Apr 2021 12:20:27 +0530, Aswath Govindraju wrote:
> MLO has increased to a size greater than the allocated
> 128 kB in dfu_alt_info_emmc and _mmc.
>
> Therefore, double the allocated size for MLO.raw in
> the default environment.
Applied to
On Thu, May 27, 2021 at 04:57:17PM +0800, Green Wan wrote:
> Hi Tom,
>
> Thanks for the comments.
>
> Not sure whether it catches differentconcerns, I plan to remove
> fdt_high and initrd_high sincethe bootm_* settings should be sufficient
> to calculate the values related to fdt_high and
The Linux commit f8f79fa6bb25 ("dt-bindings: at25: convert the binding
document to yaml") converted binding to yaml and 3 deprecated properties
pop up.
The patch is fixing these warnings:
.../zynq-zc770-xm013.dt.yaml: eeprom@2: 'pagesize' is a required property
.../zynq-zc770-xm013.dt.yaml:
The Linux commit f69629919942 ("dt-bindings: sram: Convert SRAM bindings to
json-schema") converted binding to yaml and some missing required
properties started to be reported. Align binding based on it.
The patch is fixing these warnings:
.../zynq-zc702.dt.yaml: sram@fffc: '#address-cells'
On 07/05/21 9:45 am, Dario Binacchi wrote:
> Update the driver to support the device tree and the driver model.
> The read / write helpers in rtc_ops allow access to scratch registers
> only. The offset parameter is added to the address of the scratch0
> register.
>
> Signed-off-by: Dario
On 26.05.21 05:09, Masahisa Kojima wrote:
> "TCG PC Client Platform Firmware Profile Specification"
> requires to measure every attempt to load and execute
> a OS Loader(a UEFI application) into PCR[4].
> This commit adds the PE/COFF image measurement, extends PCR,
> and appends measurement into
On 07/05/21 9:45 am, Dario Binacchi wrote:
> The Davinci's onchip RTC is also present on TI OMAP1, AM33XX, AM43XX and
> DRA7XX SOCs. So, let's enable compilation for these architectures too.
>
> Signed-off-by: Dario Binacchi
> ---
>
> drivers/rtc/Kconfig | 7 +++
>
Hi Gireesh,
On 22/04/21 7:01 pm, gireesh.hirem...@in.bosch.com wrote:
> From: Gireesh Hiremath
>
> add support for updated TI clock driver, backlight, splash screen,
> swi logic, add ubi fastmap support, update pinmux, code clean up
>
> address the v1 review comments like:
> split board
Hi Jaime,
Jaime Liao wrote on Thu, 27 May 2021 16:51:12
+0800:
> Macronix NAND Flash devices are available in different configurations
> and densities.
>
> MX"35" means SPI NAND
> MX35"LF"/"UF" , LF means 3V and UF meands 1.8V
> MX35LF"2G" , 2G means 2Gbits
> MX35LF2G"E4"/"24"/"14",
> E4 means
Hi Tom,
Thanks for the comments.
Not sure whether it catches different concerns, I plan to remove fdt_high
and initrd_high since the bootm_* settings should be sufficient to
calculate the values related to fdt_high and initrd_high. And I checked the
bootm_* settings as below, the system can boot
just ignore - this patch - it was wrong - sorry ;-)
On Thu, May 27, 2021 at 4:37 PM Artem Lapkin wrote:
>
> change max freq to 104Mhz for SPI-NOR flash
>
> Signed-off-by: Artem Lapkin
> ---
> arch/arm/dts/meson-gxm-khadas-vim2-u-boot.dtsi | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git
change max freq to 104Mhz for SPI-NOR flash
Signed-off-by: Artem Lapkin
---
arch/arm/dts/meson-gxm-khadas-vim2-u-boot.dtsi | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/dts/meson-gxm-khadas-vim2-u-boot.dtsi
b/arch/arm/dts/meson-gxm-khadas-vim2-u-boot.dtsi
index
From: Adarsh Babu Kalepalli
After executing the test-cases from pytest ,the board
is still powered.Shutting down the board power supply at
this point ,would keep the board safe.
Signed-off-by: Adarsh Babu Kalepalli
---
test/py/conftest.py | 7 +++
1 file changed, 7 insertions(+)
diff
On Thursday 27 May 2021 08:17:41 Stefan Roese wrote:
> On 25.05.21 19:42, Marek Behún wrote:
> > From: Pali Rohár
> >
> > Unfortunately the UART driver in current Linux for Armada 3700 expects
> > UART's parent clock to be XTAL and calculats baudrate divisor according
> > to XTAL clock.
This adds the XTX Technology Inc. flash producer Kconfig entry to enable support
for the 128Mbit XT25F128B NOR SPI flash.
Signed-off-by: Neil Armstrong
---
drivers/mtd/spi/Kconfig | 6 ++
drivers/mtd/spi/spi-nor-ids.c | 4
2 files changed, 10 insertions(+)
diff --git
On 5/27/21 4:35 PM, Artem Lapkin wrote:
> need return -1 if boot source is not EMMC or SD ( for example it will be
> useful if we have multy env sources configuration and device was booted
> from SPI flash and env need read from SPI not from mmc )
>
> Signed-off-by: Artem Lapkin
Reviewed-by:
On 27/05/2021 08:43, Artem Lapkin wrote:
> make possible to load simple compressed linux kernel for meson64
>
> Signed-off-by: Artem Lapkin
> ---
> include/configs/meson64.h | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/include/configs/meson64.h b/include/configs/meson64.h
> index
On 27/05/2021 09:35, Artem Lapkin wrote:
> need return -1 if boot source is not EMMC or SD ( for example it will be
> useful if we have multy env sources configuration and device was booted
> from SPI flash and env need read from SPI not from mmc )
>
> Signed-off-by: Artem Lapkin
> ---
>
Hi,
On 27/05/2021 09:20, Artem Lapkin wrote:
> change max freq to 104Mhz for SPI-NOR flash
>
> Signed-off-by: Artem Lapkin
> ---
> arch/arm/dts/meson-gxm-khadas-vim2.dts | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/arm/dts/meson-gxm-khadas-vim2.dts
>
need return -1 if boot source is not EMMC or SD ( for example it will be
useful if we have multy env sources configuration and device was booted
from SPI flash and env need read from SPI not from mmc )
Signed-off-by: Artem Lapkin
---
board/amlogic/vim3/vim3.c | 10 --
1 file changed, 8
change max freq to 104Mhz for SPI-NOR flash
Signed-off-by: Artem Lapkin
---
arch/arm/dts/meson-gxm-khadas-vim2.dts | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/dts/meson-gxm-khadas-vim2.dts
b/arch/arm/dts/meson-gxm-khadas-vim2.dts
index bff8ec2c1c..e2bd9c7c81
On 5/26/21 9:57 PM, Jorge Ramirez-Ortiz wrote:
> Use the more generic reset-gpios propery name.
>
> Signed-off-by: Jorge Ramirez-Ortiz
> ---
> doc/device-tree-bindings/tpm2/tis-tpm2-spi.txt | 2 +-
> drivers/tpm/tpm2_tis_spi.c | 2 +-
> 2 files changed, 2 insertions(+), 2
make possible to load simple compressed linux kernel for meson64
Signed-off-by: Artem Lapkin
---
include/configs/meson64.h | 2 ++
1 file changed, 2 insertions(+)
diff --git a/include/configs/meson64.h b/include/configs/meson64.h
index e3d25493..552a08c2 100644
--- a/include/configs/meson64.h
On 26.05.21 17:59, Pali Rohár wrote:
The `ranges` DT property of the PCIe node is currently ignored by
Aardvark driver - all entries are used as transparent PCIe MEM, despite
some of them being defined for IO in DT.
This is because the driver does not setup PCIe outbound windows and thus
a
On 26.05.21 17:59, Pali Rohár wrote:
For some configurations with more PCIe cards and PCIe bridges, 16 MiB of
PCIe MEM space may not be enough. Since TF-A already allocates a 128 MiB
CPU window for PCIe, and since IO port space is only 64 KiB in total,
use all the remaining space (64 + 32 + 16 +
On 26.05.21 17:59, Pali Rohár wrote:
Current version of this function uses a lot of incorrect assumptions about
the `ranges` DT property:
* parent(#address-cells) == 2
* #size-cells == 2
* number of entries == 2
* address size of first entry == 0x100
* second child address entry
On 26.05.21 17:59, Pali Rohár wrote:
Find PCIe DT node by compatible string instead of retrieving it by using
hardcoded DT path.
Signed-off-by: Pali Rohár
Reviewed-by: Marek Behún
Reviewed-by: Stefan Roese
Thanks,
Stefan
---
arch/arm/mach-mvebu/armada3700/cpu.c | 4 +---
1 file
On 26.05.21 17:59, Pali Rohár wrote:
Change DT compatible string for A3700 PCIe from 'marvell,armada-37xx-pcie'
to 'marvell,armada-3700-pcie' to make U-Boot A3700 PCIe DT node compatible
with Linux' DT node.
Signed-off-by: Pali Rohár
Reviewed-by: Marek Behún
Reviewed-by: Stefan Roese
On 26.05.21 17:59, Pali Rohár wrote:
Disable Root Bridge I/O space, memory space and bus mastering in Aardvark's
remove method, which is called before booting Linux kernel.
This ensures that PCIe device which was initialized and used by U-Boot
cannot do new DMA transfers until Linux initializes
On 26.05.21 17:59, Pali Rohár wrote:
During our debugging of the Aardvark driver in Linux we have discovered
that the PCIE_CORE_LINK_CTRL_STAT_REG register in fact controls standard
PCIe Link Control Register for PCIe Root Bridge. This led us to discover
that the name of the
On 25.05.21 19:42, Marek Behún wrote:
From: Pali Rohár
Unfortunately the UART driver in current Linux for Armada 3700 expects
UART's parent clock to be XTAL and calculats baudrate divisor according
to XTAL clock. Therefore we must switch back to XTAL clock before
booting kernel.
Do you plan
On 25.05.21 19:42, Marek Behún wrote:
From: Pali Rohár
Extend CONFIG_SYS_BAUDRATE_TABLE and include all standard baudrates and
also nonstandard up to the 6 MBaud. U-Boot's A3720 UART driver can use
baudrates from 300 Baud to 6 MBaud.
This changes all A3720 boards, since all of them include
On 25.05.21 19:42, Marek Behún wrote:
From: Pali Rohár
Using TBG clock as parent clock for UART allows us using higher
baudrates than 230400.
Turris MOX with external FT232RL USB-UART works fine up to 3 MBaud
(which is maximum for this USB-UART controller), while EspressoBIN with
integrated
On 25.05.21 19:42, Marek Behún wrote:
Setting DM_FLAG_PRE_RELOC for Armada 3720 clock drivers (TBG and
peripheral clocks) makes it possible for serial driver to retrieve clock
rates via clk API.
Signed-off-by: Marek Behún
Reviewed-by: Stefan Roese
Thanks,
Stefan
---
On 25.05.21 19:42, Marek Behún wrote:
From: Pali Rohár
UART parent clock is by default the platform's xtal clock, which is
25 MHz.
The value defined in the driver, though, is 25.8048 MHz. This is a hack
for the suboptimal divisor calculation
Divisor = UART clock / (16 * baudrate)
which
99 matches
Mail list logo
