summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Nokia RX-51: Update test scriptPali Rohár2020-11-151-12/+15
| | | | | | | | Include emmc/nand suffix into bootmenu script names and fix leaking sleep processes when asynchronously waiting for them. 'wait -n' is not provided by /bin/sh, so run script under bash. Signed-off-by: Pali Rohár <pali@kernel.org>
* Nokia RX-51: During init disable lp5523 led instead of resetting itPali Rohár2020-11-151-2/+2
| | | | | | | | | | | | | | | | | | | After commit d5243359e1af ("OMAP24xx I2C: Add support for set-speed") U-Boot is unstable to reset lp5523 led. That commit added pooling for i2c poll ARDY bit which apparently is never set. It is not known what is happening here. Purpose of resetting lp5523 led in Nokia RX-51 code is just to turn off very bright led which is powered on by NOLO and expects next boot image (kernel or U-Boot) to turn it off. After testing we observed that just disabling lp5523 led is working fine. So as a workaround to this ARDY bit i2c issue we disable lp5523 led instead of resetting it. Signed-off-by: Pali Rohár <pali@kernel.org> Cc: Ivaylo Dimitrov <ivo.g.dimitrov.75@gmail.com>
* Nokia RX-51: Fix crashing in U-Boot mmc function omap_hsmmc_stop_clock()Pali Rohár2020-11-151-0/+2
| | | | | | | | | | | | After commit 04a2ea248f58 ("mmc: disable UHS modes if Vcc cannot be switched on and off") U-Boot started crashing on Nokia RX-51 while initializing mmc and caused reboot loop. It looks like that some clocks were not enabled and this patch fixes U-Boot mmc crash. Signed-off-by: Pali Rohár <pali@kernel.org> Cc: Ivaylo Dimitrov <ivo.g.dimitrov.75@gmail.com>
* Nokia RX-51: Remove old comments from configs/nokia_rx51.h filePali Rohár2020-11-151-10/+0
| | | | | | | These comments are relict for old, now removed config options. So remove these obsoleted comments too. Signed-off-by: Pali Rohár <pali@kernel.org>
* configs: am65/j72x: Set CONFIG_LOGLEVEL to 7Roger Quadros2020-11-155-0/+5
| | | | | | | | | | | | | | | | | | | | | | | By default CONFIG_LOGLEVEL seems to be set to 4 which is too low and doesn't show dev_info/dev_notice/dev_warn messages on console. This has been deliberately set low globally to be conservative setting across the board due to primary bootloader size limitations. It is best to tune per board config as per user needs. On K3 we have separate SPL and u-boot configs so we can afford to set u-boot CONFIG_LOGLEVEL to 7. On AM65 this patch causes u-boot.img size to change from 932KB to 940KB with 1 line additional print during MMC boot. i.e. details of Net subsystem "Net: K3 CPSW: nuss_ver: 0x6BA00102 cpsw_ver: 0x6BA80102 ale_ver: 0x00293904 Ports:1 mdio_freq:1000000" Similar 8KB difference was seen on J721E. Signed-off-by: Roger Quadros <rogerq@ti.com> Reviewed-by: Nishanth Menon <nm@ti.com>
* Nokia RX-51: Convert to CONFIG_DM_I2CPali Rohár2020-11-153-8/+21
| | | | | | | Use twl4030_i2c_read(), i2c_get_chip_for_busnum() and remove CONFIG_SYS_I2C. Signed-off-by: Pali Rohár <pali@kernel.org>
* power: twl4030: Add twl4030_i2c_read() functionPali Rohár2020-11-152-7/+12
| | | | | | | | Function twl4030_i2c_read() is like twl4030_i2c_read_u8() but instead of single value it rather returns array of values. Signed-off-by: Pali Rohár <pali@kernel.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
* ARM: am335x: Add phyBOARD REGOR supportParthiban Nallathambi2020-11-156-2/+352
| | | | | | | | | | | | | | | | | | | | | | | | | phyBOARD-REGOR is based on phyCORE AM335x R2 SoM (PCL060). CPU : AM335X-GP rev 2.1 Model: Phytec AM335x phyBOARD-REGOR DRAM: 512 MiB NAND: 512 MiB MMC: OMAP SD/MMC: 0 eth0: ethernet@4a100000 Working: - Eth0 - i2C - MMC/SD - NAND - UART - USB (host) Device trees were taken from Linux mainline: commit c4d6fe731176 ("Linux 5.9.0") Signed-off-by: Parthiban Nallathambi <parthiban@linumiz.com> Reviewed-by: Tom Rini <trini@konsulko.com>
* libfdt: Fix signedness comparison warningsAndre Przywara2020-11-106-29/+42
| | | | | | | | | | | | | | | | | | | | This is a combination of upstream libfdt commits to fix warnings about comparing signed and unsigned integers: ========== scripts/dtc/libfdt/fdt.c: In function ‘fdt_offset_ptr’: scripts/dtc/libfdt/fdt.c:137:18: warning: comparison between signed and unsigned integer expressions [-Wsign-compare] if ((absoffset < offset) ... ========== For a detailed description of the fixes, see the dtc repo: https://git.kernel.org/pub/scm/utils/dtc/dtc.git/log/?id=73e0f143b73d808 For this patch the commits between 73e0f143b73d8088 and ca19c3db2bf62000 have been combined and adjusted for the slight differences in U-Boot's libfdt code base. Signed-off-by: Andre Przywara <andre.przywara@arm.com>
* Merge https://gitlab.denx.de/u-boot/custodians/u-boot-x86Tom Rini2020-11-093-7/+22
|\ | | | | | | | | | | - Avoid using hardcoded number of variable range MTRRs in mtrr_commit() - coral: Correct max98357 file - coral: Update smbios tables to latest definition
| * x86: coral: Update smbios tables to latest definitionSimon Glass2020-11-101-6/+21
| | | | | | | | | | | | | | | | The accepted binding uses multiple nodes, one for each table type. Update coral accordingly. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Bin Meng <bmeng.cn@gmail.com>
| * x86: coral: Correct max98357 fileSimon Glass2020-11-101-0/+0
| | | | | | | | | | | | | | This somehow ended up as an empty file. Fix it. Signed-off-by: Simon Glass <sjg@chromium.org> Acked-by: Bin Meng <bmeng.cn@gmail.com>
| * x86: Avoid using hardcoded number of variable range MTRRs in mtrr_commit()Bin Meng2020-11-101-1/+1
|/ | | | | | | | | | | | | | | Since commit 29d2d64ed55f ("x86: Add support for more than 8 MTRRs"), the maximum number of variable range MTRRs was increased from 8 to 10. On the BayTrail platform there are only 8 variable range MTRRs. In mtrr_commit() it still uses MTRR_MAX_COUNT which caused a #GP during VESA video driver probe. It should have been updated to use dynamically probed number. This fixes the boot failure seen on Intel Minnow Max board. Fixes: 29d2d64ed55f ("x86: Add support for more than 8 MTRRs") Signed-off-by: Bin Meng <bmeng.cn@gmail.com> Reviewed-by: Simon Glass <sjg@chromium.org>
* Prepare v2021.01-rc2Tom Rini2020-11-091-1/+1
| | | | Signed-off-by: Tom Rini <trini@konsulko.com>
* Merge tag 'efi-2021-01-rc2-2' of ↵Tom Rini2020-11-097-16/+252
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | https://gitlab.denx.de/u-boot/custodians/u-boot-efi Pull request for UEFI sub-system for efi-2021-01-rc2 (2) The following bugs are fixed: * The conitrace command failed to build. * Non-volatile UEFI variables were not delete form the file store. The following features are added: * Support for the FN1 - FN10 keys on crosswire keyboards is added. * An EFI binary is provided to dump the binary device tree. tpm2_get_capability() is adjusted in preparation of the implementation of the EFI_TCG2_PROTOCOL.
| * tpm: Change response length of tpm2_get_capability()Ilias Apalodimas2020-11-092-4/+4
| | | | | | | | | | | | | | | | | | | | | | For implementing the EFI_TCG2_PROTOCOL we need the count field returned by the TPM when reading capabilities via tpm2_get_capability(). Adjust the implementation of the 'tpm2 get_capability' command accordingly. Suggested-by: Heinrich Schuchardt <xypron.glpk@gmx.de> Signed-off-by: Ilias Apalodimas <ilias.apalodimas@linaro.org> Reviewed-by: Heinrich Schuchardt <xypron.glpk@gmx.de>
| * efi_selftest: add tool to download dtbHeinrich Schuchardt2020-11-092-0/+220
| | | | | | | | | | | | | | | | | | | | | | For validating the fixed up device tree we need a tool to need to save it to a file. dtbdump.efi copies the configuration table with the device tree to a file on the same partition from which dtbdump.efi was invoked. The file name can be entered on the console. Signed-off-by: Heinrich Schuchardt <xypron.glpk@gmx.de>
| * efi_loader: non-volatile variable not deleted from fileHeinrich Schuchardt2020-11-091-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | When deleting a non-volatile variable it was deleted from memory but the deletion was not persisted to the file system. SetVariable() may be called with attributes == 0 to delete a variable. To determine if the deletion shall be persisted we have to consider the non-volatile flag in the attributes of the deleted variable and not the value passed in the call parameter. Signed-off-by: Heinrich Schuchardt <xypron.glpk@gmx.de>
| * input: add support for FN1 - FN10 on crosswire kbdHeinrich Schuchardt2020-11-091-10/+25
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Chromebooks and the sandbox use a crosswire keyboard with function keys FN1 - FN10. These keys are needed when running UEFI applications like GRUB or the UEFI SCT. Add support for these keys when translating from key codes to ECMA-48 (or withdrawn ANSI 3.64) escape sequences. All escape sequences start with 0x1b. So we should not repeat this byte in the kbd_to_ansi364 table. For testing use: sandbox_defconfig + CONFIG_EFI_SELFTEST=y $ ./u-boot -D -l => setenv efi_selftest extended text input => bootefi selftest Signed-off-by: Heinrich Schuchardt <xypron.glpk@gmx.de> Reviewed-by: Simon Glass <sjg@chromium.org>
| * cmd: conitrace: replace getc() by getchar()Heinrich Schuchardt2020-11-091-2/+2
| | | | | | | | | | | | | | This command was missed when renaming getc() to getchar(). Fixes: c670aeee3df9 ("common: rename getc() to getchar()") Signed-off-by: Heinrich Schuchardt <xypron.glpk@gmx.de>
* | configs: Resync with savedefconfigTom Rini2020-11-0913-29/+24
| | | | | | | | | | | | Rsync all defconfig files using moveconfig.py Signed-off-by: Tom Rini <trini@konsulko.com>
* | arm: actions: increase SYS_MALLOC_F_LENAmit Singh Tomar2020-11-091-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | after commit 4ab3817ff16a ("clk: fixed-rate: Enable DM_FLAG_PRE_RELOC flag") Cubieboard7 (based on actions S700 SoC) fails to boot. It is due to the fact that the default value of CONFIG_SYS_MALLOC_F_LEN (0x400) would not provide enough memory for clock device to probe (before relocation) well. This commit fixes it, by increasing SYS_MALLOC_F_LEN to value 0x2000. Suggested-by: Andre Przywara <andre.przywara@arm.com> Signed-off-by: Amit Singh Tomar <amittomer25@gmail.com>
* | net: ks8851: Implement EEPROM MAC address readoutMarek Vasut2020-11-091-0/+29
|/ | | | | | | | | | | In case there is an EEPROM attached to the KS8851 MAC and the EEPROM contains a valid MAC address, the MAC address is loaded into the NIC registers on power on. Read the MAC address out of the NIC registers and provide it to U-Boot. Signed-off-by: Marek Vasut <marex@denx.de> Cc: Eugen Hristev <eugen.hristev@microchip.com> Cc: Joe Hershberger <joe.hershberger@ni.com>
* Merge tag 'dm-pull5nov20' of git://git.denx.de/u-boot-dmTom Rini2020-11-0637-388/+2293
|\ | | | | | | | | | | | | patman status subcommand to collect tags from Patchwork patman showing email replies from Patchwork sandbox poweroff command minor fixes in binman, tests
| * patman: Support listing comments from patchworkSimon Glass2020-11-056-36/+268
| | | | | | | | | | | | | | | | | | | | While reviewing feedback it is helpful to see the review comments on the command line to check that each has been addressed. Add an option to support that. Update the workflow documentation to describe the new features. Signed-off-by: Simon Glass <sjg@chromium.org>
| * patman: Support parsing of review snippetsSimon Glass2020-11-052-0/+168
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Add support for parsing the contents of a patchwork 'patch' web page containing comments received from reviewers. This allows patman to show these comments in a simple 'snippets' format. A snippet is some quoted code plus some unquoted comments below it. Each review is from a unique person/email and can produce multiple snippets, one for each part of the code that attracts a comment. Show the file and line-number info at the top of each snippet if available. Signed-off-by: Simon Glass <sjg@chromium.org>
| * patman: Support updating a branch with review tagsSimon Glass2020-11-056-16/+289
| | | | | | | | | | | | | | | | It is tedious to add review tags into the local branch and errors can sometimes be made. Add an option to create a new branch with the review tags obtained from patchwork. Signed-off-by: Simon Glass <sjg@chromium.org>
| * patman: Support checking for review tags in patchworkSimon Glass2020-11-056-6/+784
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Before sending out a new version of a series for review, it is important to add any review tags (e.g. Reviewed-by, Acked-by) collected by patchwork. Otherwise people waste time reviewing the same patch repeatedly, become frustrated and stop reviewing your patches. To help with this, add a new 'status' subcommand that checks patchwork for review tags, showing those which are not present in the local branch. This allows users to see what new review tags have been received and then add them. Sample output: $ patman status 1 Subject 1 Reviewed-by: Joe Bloggs <joe@napierwallies.co.nz> 2 Subject 2 Tested-by: Lord Edmund Blackaddër <weasel@blackadder.org> Reviewed-by: Fred Bloggs <f.bloggs@napier.net> + Reviewed-by: Mary Bloggs <mary@napierwallies.co.nz> 1 new response available in patchwork The '+' indicates a new tag. Colours are used to make it easier to read. Signed-off-by: Simon Glass <sjg@chromium.org>
| * patman: Detect missing upstream in CountCommitsToBranchSimon Glass2020-11-052-3/+26
| | | | | | | | | | | | | | | | At present if we fail to find the upstream then the error output is piped to wc, resulting in bogus results. Avoid the pipe and check the output directly. Signed-off-by: Simon Glass <sjg@chromium.org>
| * patman: Improve handling of filesSimon Glass2020-11-051-3/+8
| | | | | | | | | | | | | | | | Sometimes warnings are associated with a file and sometimes with the patch as a whole. Update the regular expression to handle both cases, even in emacs mode. Also add support for detecting new files. Signed-off-by: Simon Glass <sjg@chromium.org>
| * patman: Allow showing a Commit as a stringSimon Glass2020-11-051-0/+3
| | | | | | | | | | | | Use the subject of the Commit object when printing it out. Signed-off-by: Simon Glass <sjg@chromium.org>
| * patman: Don't ignore lines starting with hashSimon Glass2020-11-051-2/+5
| | | | | | | | | | | | | | | | | | These lines can indicate a continuation of an error and should not be ignored. Fix this. Fixes: 666eb15e923 ("patman: Handle checkpatch output with notes and code") Signed-off-by: Simon Glass <sjg@chromium.org>
| * patman: Fix spelling of plural for warningSimon Glass2020-11-051-4/+5
| | | | | | | | | | | | | | Tidy up the extra 's' when there is only a single warning. Fix the empty print statement also. Signed-off-by: Simon Glass <sjg@chromium.org>
| * patman: Convert testBasic() to use an interatorSimon Glass2020-11-051-28/+27
| | | | | | | | | | | | | | | | | | | | On balance it is easier to use an iterator here, particularly if we need to insert lines due to new functionality. The only niggle is the need to keep the previous iterator value around in one case. Convert this test to use iter(). Signed-off-by: Simon Glass <sjg@chromium.org>
| * patman: Add some tests for warningsSimon Glass2020-11-053-13/+116
| | | | | | | | | | | | Add tests that check that warnings are generated when expected. Signed-off-by: Simon Glass <sjg@chromium.org>
| * patman: Add a test for PatchStream tagsSimon Glass2020-11-052-5/+44
| | | | | | | | | | | | | | The current functional tests run most of patman. Add a smaller test that just checks tag handling with the PatchStream class. Signed-off-by: Simon Glass <sjg@chromium.org>
| * patman: Drop unused signoff memberSimon Glass2020-11-052-1/+1
| | | | | | | | | | | | This is not used. Drop it. Signed-off-by: Simon Glass <sjg@chromium.org>
| * patman: Convert 'Series-xxx' tag errors into warningsSimon Glass2020-11-052-2/+8
| | | | | | | | | | | | | | | | | | | | | | If the Series-xxx tag is not recognised patman currently reports a fatal error. This is inconvenient if a new feature is later added to patman that an earlier version does not support. Report a warning instead, to allow the user to take action if needed, but still allow operation to proceed. Signed-off-by: Simon Glass <sjg@chromium.org>
| * patman: Attach warnings to individual patchesSimon Glass2020-11-052-4/+13
| | | | | | | | | | | | | | | | | | | | | | At present warnings are produced across the whole set of patches when parsing them. It is more useful to associate each warning with the patch (or commit) that generated it. Attach warnings to the Commit object and move them out of PatchStream. Also avoid generating duplicate warnings for the same commit. Signed-off-by: Simon Glass <sjg@chromium.org>
| * patman: Move warning collection to a functionSimon Glass2020-11-051-13/+23
| | | | | | | | | | | | | | | | | | | | | | Add a new function in PatchStream to collect the warnings generated while parsing the stream. This will allow us to adjust the logic, such as dealing with per-commit warnings. Two of the warnings are in fact internal errors, so change them to raise and exception. Signed-off-by: Simon Glass <sjg@chromium.org>
| * patman: Fix up argument/return docs in patchstreamSimon Glass2020-11-051-32/+50
| | | | | | | | | | | | | | Add missing documentation and type information. Fix up some missing docs on exceptions also. Signed-off-by: Simon Glass <sjg@chromium.org>
| * patman: Drop unused args in patchstreamSimon Glass2020-11-051-5/+3
| | | | | | | | | | | | Drop a few arguments that are not used in functions. Signed-off-by: Simon Glass <sjg@chromium.org>
| * patman: Rename variables in patchstreamSimon Glass2020-11-051-26/+26
| | | | | | | | | | | | | | Some variables are too short or shadow other variables or types. Fix these to keep pylint3 happy. Signed-off-by: Simon Glass <sjg@chromium.org>
| * patman: Rename functions in patchstreamSimon Glass2020-11-055-56/+56
| | | | | | | | | | | | Rename these functions to lower case as per PEP8. Signed-off-by: Simon Glass <sjg@chromium.org>
| * patman: Fix constant style in patchstreamSimon Glass2020-11-051-22/+22
| | | | | | | | | | | | These constants should use upper case. Update them to keep pylint3 happy. Signed-off-by: Simon Glass <sjg@chromium.org>
| * patman: Fix indenting in patchstreamSimon Glass2020-11-051-13/+16
| | | | | | | | | | | | Update the indenting to keep pylint3 happy. Signed-off-by: Simon Glass <sjg@chromium.org>
| * patman: Allow linking a series with patchworkSimon Glass2020-11-053-1/+17
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Add a new Series-links tag to tell patman how to find the series in patchwork. Each item is the series ID optionally preceded by the series version that the link refers to. An empty version indicates this is the latest series. For example: Series-links: 209816 1:203302 Documentation is added in a later patch. Signed-off-by: Simon Glass <sjg@chromium.org>
| * patman: Fix remaining pylint3 warnings in func_testSimon Glass2020-11-051-18/+58
| | | | | | | | | | | | This fixes all but the ones about too many variables/statements. Signed-off-by: Simon Glass <sjg@chromium.org>
| * patman: Use capture_sys_output() consistentlySimon Glass2020-11-051-18/+2
| | | | | | | | | | | | | | One test still uses its own function for capturing output. Modify it to use the standard one in test_util Signed-off-by: Simon Glass <sjg@chromium.org>
| * patman: Fix whitespace errors in func_testSimon Glass2020-11-051-18/+19
| | | | | | | | | | | | Fix up various indentation and other minor things to make pylint3 happier. Signed-off-by: Simon Glass <sjg@chromium.org>
generated by cgit (git 2.34.1) at 2025-01-31 15:44:15 +0000