Hi Simon,
>-Original Message-
>From: U-Boot On Behalf Of Pragnesh Patel
>Sent: 01 December 2020 11:17
>To: Simon Glass
>Cc: U-Boot Mailing List ; Atish Patra
>; Palmer Dabbelt ; Bin
>Meng ; Paul Walmsley ( Sifive)
>; Anup Patel ; Sagar Kadam
>; rick ; Naoki Hayama
>; Marek Vasut ;
>Patri
Hi Simon,
>-Original Message-
>From: Simon Glass
>Sent: 01 December 2020 01:42
>To: Pragnesh Patel
>Cc: U-Boot Mailing List ; Atish Patra
>; Palmer Dabbelt ; Bin
>Meng ; Paul Walmsley ( Sifive)
>; Anup Patel ; Sagar Kadam
>; rick ; Naoki Hayama
>; Marek Vasut ;
>Patrick Delaunay ; Adam F
The Kontron SMARC-sAL28 board uses that flash.
This is the same change as in the linux commit f3418718c0ec ("mtd:
spi-nor: Add support for w25q32jwm").
Signed-off-by: Michael Walle
Reported-by: Leo Krueger
---
Hi,
I totally forgot that some revisions of the Kontron sl28 boards have the
newer
On 11/30/20 9:11 PM, Simon Glass wrote:
+Marek Vasut who originally wrote it
Hi Heinrich,
On Sun, 29 Nov 2020 at 23:20, Heinrich Schuchardt wrote:
Am 30. November 2020 02:53:36 MEZ schrieb Simon Glass :
The linker script uses alphabetic sorting to group the different linker
lists together.
On Mon, 23 Nov 2020 at 01:08, Michal Simek wrote:
>
> The origin patch didn't have this change and it was caused by manual
> resolution where additional backslash was added.
>
> Fixes: 6723b4c6ca7b ("binman: Call helper function binman_set_rom_offset() to
> fill offset")
> Signed-off-by: Michal S
Hi Alper,
On Tue, 10 Nov 2020 at 07:45, Alper Nebi Yasak wrote:
>
> On 09/11/2020 17:45, Simon Glass wrote:
> > At present if CROSS_COMPILE contains a tilde, such as
> > ~/.buildman-toolchains/gcc-7.3.0-nolibc/i386-linux/bin/i386-linux-gcc
> > then binman gives a confusing error:
> >
> >binma
Since commit 690079767803 ("cros_ec: Support keyboard scanning with
EC_CMD_GET_NEXT_EVENT") the cros-ec-keyb driver has started using this
command, but the sandbox EC emulator does not recognize it and
continuously prints:
** Unknown EC command 0x67
This patch makes the sandbox driver send ba
On Sun, 15 Nov 2020 at 13:23, Marek Vasut wrote:
>
> The test should be checking whether $flags are non-zero and $drv_flags
> contain specific flags, however these two sets of flags are separate,
> and the two tests should be logically ANDed, not bitwise ANDed.
>
> Signed-off-by: Marek Vasut
> Cc
On Fri, 27 Nov 2020 at 03:21, Patrick Delaunay wrote:
>
> Add a check of the _log function with LOGL_FORCE_DEBUG flags,
> used to force the trace display.
>
> The trace should be displayed for all the level when flags
> have LOGL_FORCE_DEBUG bit is set, for any filter.
>
> Signed-off-by: Patrick D
Hi Sean,
On Fri, 27 Nov 2020 at 07:50, Sean Anderson wrote:
>
> On 11/27/20 5:20 AM, Patrick Delaunay wrote:
> > Update _log function to drop any traces when log is yet initialized:
> > vsnprintf is no more executed in this case.
> >
> > This patch allows to reduce the cost for the dropped early
On Fri, 27 Nov 2020 at 03:21, Patrick Delaunay wrote:
>
> Add a new test to check the content of the dropped messages
> sent to console puts function.
>
> Signed-off-by: Patrick Delaunay
> ---
>
> Changes in v2:
> - added test for content of dropped messages (NEW)
>
> test/log/log_test.c | 8 +++
Hi Patrick,
On Fri, 27 Nov 2020 at 03:49, Patrick Delaunay wrote:
>
> Remove the specific sandbox code in console.c, as the config
> CONFIG_DEBUG_UART is already supported in drivers/serial/sandbox.c
> and activated by default in all sandbox defconfig
> (CONFIG_DEBUG_UART_SANDBOX=y and CONFIG_DEB
On Thu, 26 Nov 2020 at 12:46, Heinrich Schuchardt wrote:
>
> With our optimization settings the linker eliminates unused functions.
>
> But for debugging it is better to compile with -Og or -O0. With -O0
> compiling the sandbox fails due to the missing function fixup_cmdtable()
> called by dm_relo
Hi Philippe,
On Tue, 24 Nov 2020 at 06:40, Philippe Reynes
wrote:
>
> The propoerty sign-images points to images in the configuration
spelling
> node. But thoses images may references severals "sub-images" (for
reference several
> example for images loadable). This commit adds the support of
On Fri, 27 Nov 2020 at 03:49, Patrick Delaunay wrote:
>
> Add CONFIG_DEBUG_UART=y for all sandbox defconfig
> as it is already done in sandbox_defconfig.
>
> Signed-off-by: Patrick Delaunay
> ---
>
> configs/sandbox64_defconfig| 1 +
> configs/sandbox_flattree_defconfig | 1 +
> configs/
On Sun, 22 Nov 2020 at 09:11, Dario Binacchi wrote:
>
> The __of_translate_address routine translates an address from the
> device tree into a CPU physical address. A note in the description of
> the routine explains that the crossing of any level with
> #size-cells = <0> is to be considered an er
On Tue, 24 Nov 2020 at 08:15, Philippe Reynes
wrote:
>
> When the hash check fails on a loadable image, the SPL/TPL simply
> jump to the next one. This commit changes this behaviour, when the
> hash check fails on a loadable image, the function spl_load_simple_fit
> stops and report an error.
>
>
On Fri, 27 Nov 2020 at 03:21, Patrick Delaunay wrote:
>
> Reorder test on gd value and remove the duplicated test (!gd)
> in putc and puts function.
>
> This patch is a preliminary step for rework of this function.
>
> Signed-off-by: Patrick Delaunay
> ---
>
> Changes in v2:
> - update gd test in
On Sat, 28 Nov 2020 at 01:44, Ovidiu Panait wrote:
>
> Add a return value to cpu_secondary_init_r and use it directly in the
> post-relocation init sequence, rather than using a wrapper stub.
>
> Signed-off-by: Ovidiu Panait
> ---
> v4 updates:
> - add reviewed-by tag
>
> v3 updates:
> -none
>
>
Hi Philippe,
On Tue, 24 Nov 2020 at 06:40, Philippe Reynes
wrote:
>
> This commit creates a function fit_config_add_hash that will be
> used in the next commit to support several 'sub-images'.
>
> Signed-off-by: Philippe Reynes
> ---
> tools/image-host.c | 132 ++
On Fri, 27 Nov 2020 at 08:59, Andy Shevchenko
wrote:
>
> xFSTK sources got a new home under Edison Firmware Group on GitHub [1].
> Update Intel Edison documentation accordingly.
>
> While here, fix couple of typos.
>
> [1]: https://github.com/edison-fw
>
> Signed-off-by: Andy Shevchenko
> ---
> v
On Fri, 27 Nov 2020 at 05:41, Andy Shevchenko
wrote:
>
> None of the driver for Edison is using DM_PCI_COMPAT, hence drop it.
>
> Signed-off-by: Andy Shevchenko
> ---
> configs/edison_defconfig | 1 -
> 1 file changed, 1 deletion(-)
Reviewed-by: Simon Glass
On Fri, 27 Nov 2020 at 05:40, Andy Shevchenko
wrote:
>
> It appears that U-Boot works by luck on Intel Edison board because the amount
> of RAM is less than 1 GB and standard way of calculating the top of it work
> for this configuration. However, this won't work if the amount of RAM is
> differen
Hi Patrick,
On Fri, 27 Nov 2020 at 03:21, Patrick Delaunay wrote:
>
> Allow to record the console output before before U-Boot
> has a console ready.
>
> This patch allows to test the console output in sandbox test
> based on console record.
>
> It is possible because GD_FLG_RECORD and GD_FLG_SERI
On Fri, 27 Nov 2020 at 03:21, Patrick Delaunay wrote:
>
> Add test for dropped trace before log_init, displayed by debug uart.
>
> Signed-off-by: Patrick Delaunay
> ---
>
> Changes in v2:
> - Add test of displayed messages requested before log_init (NEW)
>
> arch/sandbox/cpu/start.c | 5 +
On Fri, 27 Nov 2020 at 03:21, Patrick Delaunay wrote:
>
> Add a new test to check the dropped messages when LOG is not ready
> with log_drop_count and the result of _log().
>
> Signed-off-by: Patrick Delaunay
> ---
>
> Changes in v2:
> - add test to count the dropped messages (NEW)
>
> test/log/
On Mon, 30 Nov 2020 at 01:04, Heinrich Schuchardt wrote:
>
> Correct several typos.
>
> Signed-off-by: Heinrich Schuchardt
> ---
> include/log.h | 8
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
Reviewed-by: Simon Glass
On Mon, 30 Nov 2020 at 01:08, Heinrich Schuchardt wrote:
>
> include/log.h belongs to LOGGING.
>
> Signed-off-by: Heinrich Schuchardt
> ---
> MAINTAINERS | 1 +
> 1 file changed, 1 insertion(+)
>
Reviewed-by: Simon Glass
+Marek Vasut who originally wrote it
Hi Heinrich,
On Sun, 29 Nov 2020 at 23:20, Heinrich Schuchardt wrote:
>
> Am 30. November 2020 02:53:36 MEZ schrieb Simon Glass :
> >The linker script uses alphabetic sorting to group the different linker
> >lists together. Each group has its own struct and p
Hi Aswath,
On Fri, 27 Nov 2020 at 07:05, Aswath Govindraju wrote:
>
> On 22/11/20 4:37 am, Simon Glass wrote:
> > Hi,
> >
> > On Wed, 18 Nov 2020 at 10:55, Vignesh Raghavendra wrote:
> >>
> >>
> >>
> >> On 11/18/20 8:44 PM, Aswath Govindraju wrote:
> >>> Hi Simon,
> >>>
> >>> On 18/11/20 8:07 pm
Hi Pragnesh,
On Thu, 26 Nov 2020 at 03:48, Pragnesh Patel wrote:
>
> Add the command "pwm" for controlling the pwm channels. This
> command provides pwm invert/config/enable/disable functionalities
> via PWM uclass drivers
>
> Signed-off-by: Pragnesh Patel
> ---
>
> Changes in v2:
> - Add test f
enable Environment protection with:
CONFIG_ENV_APPEND=y
CONFIG_ENV_WRITEABLE_LIST=y
CONFIG_ENV_ACCESS_IGNORE_FORCE
and add board specific env_get_location()
function.
Signed-off-by: Heiko Schocher
---
board/aristainetos/aristainetos.c| 20
configs/aristainetos2c_defco
Removed aristainetos2, 2b, 2b-csl. This boards have been
recalled and destroyed.
Adapt board code to remove stuff not needed anymore.
Fix checkpatch warning, remove fdt_high and initrd_high
from default environment.
Signed-off-by: Heiko Schocher
zu remove
---
arch/arm/dts/Makefile
sync with comaptible changes in linux from
Krzysztof Kozlowski.
https://patchwork.kernel.org/project/linux-arm-kernel/patch/20200930190143.27032-12-k...@kernel.org/
Signed-off-by: Heiko Schocher
---
arch/arm/dts/imx6dl-aristainetos2c_7.dts | 2 +-
arch/arm/dts/imx6dl-aristainetos2c_cslb_7
add support for aristainetos2c_cslb board variant.
Signed-off-by: Heiko Schocher
---
arch/arm/dts/Makefile | 1 +
.../imx6dl-aristainetos2c_cslb_7-u-boot.dtsi | 19 ++
arch/arm/dts/imx6dl-aristainetos2c_cslb_7.dts | 16 ++
.../imx6qdl-aristainetos2c_cslb-u-boot.dtsi
- remove the not longer used boards: aristainetos2, 2b, 2b-csl
- add support for aristainetos2c_cslb board variant
- sync defconfigs with current mainline
- sync dts files with latest changes in linux mainline
(not all variants in linux yet)
Travis build:
https://travis-ci.org/github/hsdenx/u-bo
Now when usbtty serial console is fixed in U-Boot enable CONFIG_USB_TTY for
Nokia RX-51 board by default.
Fix also USB product id as U-Boot ignores CONFIG_USBD_PRODUCTID macro and
include U-Boot string into USB product name to indicate usage of U-Boot.
CONFIG_CONSOLE_MUX is already used and U-Boo
Hi Tom,
please pull some bugfixes and some minor updates for compatibility with
the Marvell Octeon MIPS64 boot header. Although this adds a new tool,
everything is small and isolated to MIPS/Octeon.
Gitlab CI: https://gitlab.denx.de/u-boot/custodians/u-boot-mips/-/pipelines/5455
Azure:
https://d
Those two commands now doing same thing, reading from ext2/3/4 filesystem.
So remove useless duplicated call.
Signed-off-by: Pali Rohár
---
include/configs/nokia_rx51.h | 17 +++--
1 file changed, 3 insertions(+), 14 deletions(-)
diff --git a/include/configs/nokia_rx51.h b/include/c
Am Mittwoch, den 18.11.2020, 17:54 + schrieb Richard Thanki:
> Hi Heinrich
>
> > On 18 Nov 2020, at 17:27, Heinrich Schuchardt wrote:
> >
> >
> > The driver will not be compiled because your config does not select
> > CONFIG_AG7XXX.
>
> So clear when you point it out. I’ll modify this, and
Hi Heinrich,
Heinrich Schuchardt writes:
> On 11/30/20 4:16 PM, Paulo Alcantara wrote:
>> This script generates EFI variables for U-Boot variable store format.
>
> Wouldn't it make sense to allow overwriting and deleting variables too?
Absolutely. I'll repost it with those features.
Thanks!
Am Samstag, den 28.11.2020, 10:43 +0200 schrieb Ovidiu Panait:
> In order to remove the arch-specific ifdefs around initr_trap, introduce
> arch_initr_trap weak initcall. Implementations for ppc/m68k/mips have
> been moved to arch//lib/traps.c
>
> Default implementation is a nop stub.
>
> Signed-
Hi Heinrich,
Heinrich Schuchardt writes:
> On 11/30/20 3:58 PM, Paulo Alcantara wrote:
>> Introduce a new config option CONFIG_EFI_SECURE_BOOT_VAR_DISABLE to
>> allow disabling EFI secure boot when the platform is operating in User
>> Mode and there is an NV+BS EFI variable called "SecureBootDis
Hey all,
Well, I managed to miss a calendar reminder, and with the US holiday
last week, I just pushed out until today. So here's -rc3, a bit behind
schedule. But the good news is I think we're close enough to final
release to open the next window now.
I feel like I've been following through on
Am Montag, den 30.11.2020, 13:14 +0100 schrieb Stefan Roese:
> Add a tool to update or insert an Octeon specific header into the U-Boot
> image. This is needed e.g. for booting via SPI NOR, eMMC and NAND.
>
> While working on this, move enum cvmx_board_types_enum and
> cvmx_board_type_to_string()
On 11/16/20 10:46 AM, Andre Przywara wrote:
So far all GBit users of the sun8i-emac driver were using the "rgmii"
PHY mode, even though this turns out to be mostly wrong. It just worked
because the PHY driver doesn't do the proper setup (yet).
In fact for most boards the "rgmii-id" or "rgmii-txid
On 11/30/20 4:16 PM, Paulo Alcantara wrote:
This script generates EFI variables for U-Boot variable store format.
Hello Paulo,
thanks for you valuable contribution.
Wouldn't it make sense to allow overwriting and deleting variables too?
Best regards
Heinrich
An example of generating secu
On 11/30/20 3:58 PM, Paulo Alcantara wrote:
Introduce a new config option CONFIG_EFI_SECURE_BOOT_VAR_DISABLE to
allow disabling EFI secure boot when the platform is operating in User
Mode and there is an NV+BS EFI variable called "SecureBootDisable".
Otherwise, keep it enabled by default.
Hello
On Sun, Nov 29, 2020 at 12:30:50PM +, Peng Fan wrote:
> Hi Tom
>
> Please pull mmc-2020-11-29
>
Applied to u-boot/master, thanks!
--
Tom
signature.asc
Description: PGP signature
On Sun, Nov 29, 2020 at 10:30:29AM +0100, Heinrich Schuchardt wrote:
> Dear Tom,
>
> The following changes since commit 7889951d0f56eab746a7c8fde350a022ba0361ca:
>
> Merge tag 'u-boot-stm32-20201125' of
> https://gitlab.denx.de/u-boot/custodians/u-boot-stm (2020-11-25 11:00:52
> -0500)
>
> ar
This script generates EFI variables for U-Boot variable store format.
An example of generating secure boot variables
$ openssl x509 -in foo.crt -outform DER -out foo.der
$ efisiglist -a -c foo.der -o foo.esl
$ efivar.py -i ubootefi.var add -n db -d foo.esl -t file
$ efivar.py -i ubootefi.
Introduce a new config option CONFIG_EFI_SECURE_BOOT_VAR_DISABLE to
allow disabling EFI secure boot when the platform is operating in User
Mode and there is an NV+BS EFI variable called "SecureBootDisable".
Otherwise, keep it enabled by default.
Signed-off-by: Paulo Alcantara (SUSE)
---
lib/efi_
On 29/11/2020 23:07, Heinrich Schuchardt wrote:
Hi,
> since Linux patch
> bbc4d71d6354 ("net: phy: realtek: fix rtl8211e rx/tx delay config")
> i.e. since v5.8.15 or v5.9 many if not all Sunxi A64, H6, H5 boards
> require phy-mode = "rgmii-id" to provide network in Linux
>
> The U-Boot device-tr
Hi Jean,
Quick disclaimer: I am not familiar with the IP or the driver so I just
gave this patch a brief read and did not dig into it a lot. This is in
no way a comprehensive review.
On 29/11/20 11:39AM, Jean Pihet wrote:
> TI QSPI: the TI QSPI IP has a limitation of 64MB of MMIO so use
> the M
Hi Jean,
On 29/11/20 11:39AM, Jean Pihet wrote:
> Use the flags field of the SPI slave struct to pass the dual and quad
> read properties, from the SPI NOR layer to the low level driver.
> Tested with TI QSPI in 1, 2 and 4 bits modes.
>
> Signed-off-by: Jean Pihet
> ---
> drivers/mtd/spi/spi-no
Add a tool to update or insert an Octeon specific header into the U-Boot
image. This is needed e.g. for booting via SPI NOR, eMMC and NAND.
While working on this, move enum cvmx_board_types_enum and
cvmx_board_type_to_string() to cvmx-bootloader.h and remove the
unreferenced (unsupported) board de
The UBI_IOCVOLUP ioctl can fail if exclusive access to the volume isn't
obtained. If this happens, the flush operation doesn't return error,
leaving the caller without knowledge of missing flush.
Fix this by forwarding the error (-1) from ubi_update_start().
Fixes: 34255b92e6e ("tools: env: Add s
Hi Daniel,
On 27.11.20 20:01, Daniel Schwierzeck wrote:
Am Mittwoch, den 28.10.2020, 15:10 +0100 schrieb Stefan Roese:
Add a tool to update or insert an Octeon specific header into the U-Boot
image. This is needed e.g. for booting via SPI NOR, eMMC and NAND.
While working on this, move enum cv
In the previous patches we only introduced a minimal subset of the
EFI_TCG2_PROTOCOL protocol implementing GetCapability().
So let's continue adding features to it, introducing the
GetEventLog() and HashLogExtendEvent() functions.
In order to do that we first need to construct the eventlog in memo
A previous commit is adding EFI_TCG2_PROTOCOL, which in it's eventlog
support registers an EFI configuration table.
Let's add the necessary GUID so 'efidebug table' command can display
table names properly.
Signed-off-by: Ilias Apalodimas
---
cmd/efidebug.c | 4
1 file changed, 4 insertions
A following patch introduces support for the EFI_TCG2_PROTOCOL
eventlog management.
Introduce the necessary tpm related headers
Signed-off-by: Ilias Apalodimas
---
include/tpm-v2.h | 82
1 file changed, 82 insertions(+)
diff --git a/include/tpm-v
Hi!
This is v2 of [1].
The issues regarding comments have been addressed and all of the
newly added structures now have Sphinx style comments.
Changes since v1:
- Eventlog size is now a Kconfig instead of a #define. The default
size has been kept to 4096b
- Replaced struct tpm_digest with u8 d
Hi Rick,
[]
>> >After add CONFIG_TIMER_EARLY, U-Boot boots ok.
>> >But When I try to booting kernel with FTRACE=1, following are the test
>> >stats:
>> >
>> >ae350_rv64_spl_defconfig without FTRACE=1, kernel booting is ok.
>> >ae350_rv64_spl_defconfig with FTRACE=1, kernel booting fail.
>> >ae
Hi All,
Gentle Ping. Please let me know, are we happy with this patch series?
The patch series[1] is blocked by this.
[1]
http://u-boot.10912.n7.nabble.com/PATCH-v7-0-4-Add-CPU-identification-support-for-RZ-G2-SoC-s-tt433694.html#a433807
Cheers,
Biju
> -Original Message-
> From: Biju D
Add more configuration options to allow for efi capsule update
on sandbox.
Signed-off-by: AKASHI Takahiro
---
configs/sandbox64_defconfig | 6 ++
configs/sandbox_defconfig | 6 ++
2 files changed, 12 insertions(+)
diff --git a/configs/sandbox64_defconfig b/configs/sandbox64_defconfig
The test can run on sandbox build and it attempts to execute a firmware
update via a capsule-on-disk, using a FIT image capsule,
CONFIG_EFI_CAPSULE_FIT.
To run this test successfully, you need configure U-Boot specifically;
See test_capsule_firmware.py for requirements, and hence it won't run
on T
The test can run on sandbox build and it attempts to execute a firmware
update via a capsule-on-disk, using a raw image capsule,
CONFIG_EFI_CAPSULE_RAW.
To run this test successfully, you need configure U-Boot specifically;
See test_capsule_firmware.py for requirements, and hence it won't run
on T
This is a utility mainly for test purpose.
mkeficapsule -f: create a test capsule file for FIT image firmware
Having said that, you will be able to customize the code to fit
your specific requirements for your platform.
Signed-off-by: AKASHI Takahiro
---
tools/Makefile | 2 +
tools/mk
"efidebug capsule" is more or less a debugging utility.
efidebug capsule update: invoke UpdateCapsule against data on memory
efidebug capsule show: show a capsule header
efidebug capsule result: dump a capsule result variable
Signed-off-by: AKASHI Takahiro
---
cmd/efidebug.c | 235
In this commit, a very simple firmware management protocol driver
is implemented. It will take a binary image in a capsule file and
apply the data using dfu backend storage drivers via dfu_write_by_alt()
interface.
So "dfu_alt_info" variable should be properly set to specify a device
and location
In this commit, a very simple firmware management protocol driver
is implemented. It will take a common FIT image firmware in a capsule
file and apply the data using dfu backend storage drivers via
update_fit() interface.
So "dfu_alt_info" variable should be properly set to specify a device
and lo
A capsule tagged with the guid, EFI_FIRMWARE_MANAGEMENT_CAPSULE_ID_GUID,
is handled as a firmware update object.
What efi_update_capsule() basically does is to load any firmware management
protocol (or fmp) drivers contained in a capsule, find out an appropriate
fmp driver and then invoke its set_i
Capsule data can be loaded into the system either via UpdateCapsule
runtime service or files on a file system (of boot device).
The latter case is called "capsules on disk", and actual updates will
take place at the next boot time.
In this commit, we will support capsule on disk mechanism.
Please
Memory range capsule gives us a way to notify that some memory regions
should be left untouched across the next reset.
See UEFI specification, section 8.5.3.
Since how we should handle this kind of capsule is totally up to
the system, no implementation will be added in this commit.
Signed-off-by:
Summary
===
'UpdateCapsule' is one of runtime services defined in UEFI specification
and its aim is to allow a caller (OS) to pass information to the firmware,
i.e. U-Boot. This is mostly used to update firmware binary on devices by
instructions from OS.
While 'UpdateCapsule' is a runtime serv
In this commit, skeleton functions for capsule-related API's are
added under CONFIG_EFI_UPDATE_CAPSULE configuration.
Detailed implementation for a specific capsule type will be added
in the succeeding patches.
Signed-off-by: AKASHI Takahiro
---
include/efi_api.h| 12 +++
include/ef
On 29.11.20 11:08, Harm Berntsen wrote:
The Armada driver also works on Nedap's custom Kirkwood board with a
Marvell 88F6180 CPU. The original commit of that driver,
commit 704d9a645e17 ("gpio: Add DM GPIO driver for Marvell MVEBU"),
also mentions that this driver would be suitable for Kirkwood.
Hi Harm,
On 29.11.20 11:01, Harm Berntsen wrote:
Hi Stefan,
Thanks for your review.
I've looked into the usage of the kw_gpio driver. The soft_i2c part I
mentioned in the commit appeared to be specific to my board
configuration. I've replaced the usage of that driver with the DM based
i2c-gpio
Due to removed function c_funcptr_sig_re building with Sphinx 3 fails.
With the patch building succeeds with a lot of warnings if the '-W' flag is
removed from doc/Makefile. Most of the documentation is correct
This follows the approach taken by the Linux kernel.
Signed-off-by: Heinrich Schuchar
include/log.h belongs to LOGGING.
Signed-off-by: Heinrich Schuchardt
---
MAINTAINERS | 1 +
1 file changed, 1 insertion(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 874cf2c0e5..2625fc629c 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -758,6 +758,7 @@ T: git https://gitlab.denx.de/u-boot/u-b
Correct several typos.
Signed-off-by: Heinrich Schuchardt
---
include/log.h | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/include/log.h b/include/log.h
index e53afa490e..6bce560648 100644
--- a/include/log.h
+++ b/include/log.h
@@ -29,7 +29,7 @@ enum log_level_t {
81 matches
Mail list logo
