Hello Heiko
On Tue, Apr 16, 2019 at 06:03:31AM +0200, Heiko Schocher wrote:
>may I am to dummy, but I cannot find your patches in patchwork :-(
>
>any ideas?
As this was a first post from this address, I think they are still in
the list moderation queue...
Best regards
Markus
--
Markus Klotzb
Hello Heiko
On Tue, Apr 16, 2019 at 05:52:15AM +0200, Heiko Schocher wrote:
>
>Am 15.04.2019 um 17:32 schrieb Markus Klotzbuecher:
>> From: Markus Klotzbuecher
>>
>> Hello Heiko and Kyungmin
>>
>> This series contains a couple of UBI and UBI SPL improvements, notably
>> a ubispl extension to al
From: Markus Klotzbuecher
- drop CONFIG_ prefix from kconfig entry
- fix small compilation issue with CONFIG_UBI_SILENCE_MSG
Signed-off-by: Markus Klotzbuecher
Cc: Heiko Schocher
Cc: Kyungmin Park
---
drivers/mtd/ubi/Kconfig | 2 +-
drivers/mtd/ubi/io.c| 2 ++
2 files changed, 3 insert
From: Markus Klotzbuecher
Signed-off-by: Markus Klotzbuecher
Cc: Heiko Schocher
Cc: Kyungmin Park
Cc: Javier Martinez Canillas
Cc: Enric Balletbo i Serra
---
common/spl/Kconfig | 79
scripts/config_whitelist.txt | 12 --
2 files changed, 79
From: Hamish Guthrie
The motivation is to use the UBI atomic volume rename functionality to
allow double copy software updates on UBI. To that end the SPL is
configured to always load the same volume name (e.g. "u-boot"),
whereas a software updater always installs into the secondary volume
"u-boo
From: Hamish Guthrie
Signed-off-by: Hamish Guthrie
Signed-off-by: Markus Klotzbuecher
Cc: Heiko Schocher
Cc: Kyungmin Park
---
env/Kconfig | 6 ++
env/ubi.c | 17 +
2 files changed, 19 insertions(+), 4 deletions(-)
diff --git a/env/Kconfig b/env/Kconfig
index 44c47220
From: Markus Klotzbuecher
Hello Heiko and Kyungmin
This series contains a couple of UBI and UBI SPL improvements, notably
a ubispl extension to allow loading volumes by name. The motivation is
to use the UBI atomic volume rename functionality to allow double copy
software updates of U-Boot on UB
From: Markus Klotzbuecher
Signed-off-by: Markus Klotzbuecher
Cc: Heiko Schocher
Cc: Kyungmin Park
---
env/Kconfig | 6 ++
scripts/config_whitelist.txt | 1 -
2 files changed, 6 insertions(+), 1 deletion(-)
diff --git a/env/Kconfig b/env/Kconfig
index 78300660c7..44c47220
Allow the default environment file to contain long lines split into
multiples lines.
Leading white spaces can be added for readability as well.
Signed-off-by: Samuel Mescoff
---
Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Makefile b/Makefile
index 2824a6e159..d1
>-Original Message-
>From: Michal Simek
>Sent: 2019年4月17日 13:58
>To: Peng Ma ; Michal Simek ;
>albert.u.b...@aribaud.net; s...@chromium.org; Fabio Estevam
>; York Sun ; Prabhakar
>Kushwaha
>Cc: Andy Tang ; Yinbo Zhu ;
>u-boot@lists.denx.de
>Subject: Re: [EXT] Re: [PATCH 1/2] scsi: ceva:
On Mon, Apr 15, 2019 at 7:14 PM Shyam Saini
wrote:
>
> The default value of CONFIG_SYS_BOOTM_LEN is 0x80 i.e, 8MB which
> causes board reset because of larger uImage size.
>
> Error log snippet:
>Booting using the fdt blob at 0x1f0
>Loading Kernel Image ... Image too large: increas
Perfect, thanks Igor.
The most minor little nitpick: I would order otg1, otg2 and maybe add some
comment about what exact USB ports in the Colibri pin muxing each of those
actually is. With that:
Acked-by: Marcel Ziswiler
On April 16, 2019 10:19:01 AM GMT+02:00, Igor Opaniuk
wrote:
>As Max
On 17. 04. 19 4:50, Peng Ma wrote:
>
>
>> -Original Message-
>> From: Michal Simek
>> Sent: 2019年4月16日 18:49
>> To: Peng Ma ; Michal Simek ;
>> albert.u.b...@aribaud.net; s...@chromium.org; Fabio Estevam
>> ; York Sun ; Prabhakar
>> Kushwaha
>> Cc: Andy Tang ; Yinbo Zhu ;
>> u-boot@list
>-Original Message-
>From: Michal Simek
>Sent: 2019年4月16日 18:49
>To: Peng Ma ; Michal Simek ;
>albert.u.b...@aribaud.net; s...@chromium.org; Fabio Estevam
>; York Sun ; Prabhakar
>Kushwaha
>Cc: Andy Tang ; Yinbo Zhu ;
>u-boot@lists.denx.de
>Subject: Re: [EXT] Re: [PATCH 1/2] scsi: ceva:
Hi,
On Tue, 16 Apr 2019 at 16:28, Peng Fan wrote:
> HI Igor,
>
> >
> > Marek, Peng,
> >
> > Writing to you as you were the main contributors to U-boot mxsfb driver
> > implementation (i.MX23/i.MX28 LCDIF driver).
> >
> > I was about to start working on it's migration to DM (currently mxsfb is
>
HI Igor,
>
> Marek, Peng,
>
> Writing to you as you were the main contributors to U-boot mxsfb driver
> implementation (i.MX23/i.MX28 LCDIF driver).
>
> I was about to start working on it's migration to DM (currently mxsfb is being
> used on our SoM Colibri iMX7S/D), but found it a bit out-date
Hi Tom,
Please pull some updates for v2019.07
Thanks!
The following changes since commit 216800acf1fbf9f498455bf3c92d4513d9a4c681:
Merge branch 'master' of git://git.denx.de/u-boot-spi (2019-04-14
00:03:06 -0400)
are available in the git repository at:
git://git.denx.de/u-boot-uniphier.g
From: Stephen Warren
Fix test_mmc_dev(), test_mmc_rescan(), test_mmc_info() not to use the
same configuration data that test_mmc_rd() does. Doing so causes the
following issues:
* The new code uncondtionally expects certain keys to exist in the
configuration data. These keys do not exist in exis
On 4/16/19 10:04 PM, Simon Goldschmidt wrote:
> To clean up reset handling for socfpga gen5, port the DDR driver to DM
> using UCLASS_RAM and implement proper reset handling.
>
> This gets us rid of one ad-hoc call to socfpga_per_reset().
>
> The gen5 driver is implemented in 2 distinct files. On
On 4/16/19 10:08 PM, Simon Goldschmidt wrote:
> Hi Marek,
>
> Am 12.04.2019 um 12:31 schrieb Marek Vasut:
>> On 4/11/19 10:07 PM, Simon Goldschmidt wrote:
>>>
>>>
>>> Marek Vasut mailto:ma...@denx.de>> schrieb am Do., 11.
>>> Apr. 2019, 21:59:
>>>
>>> On 4/11/19 9:30 PM, Simon Goldschmidt wro
Hi Marek,
Am 12.04.2019 um 12:31 schrieb Marek Vasut:
On 4/11/19 10:07 PM, Simon Goldschmidt wrote:
Marek Vasut mailto:ma...@denx.de>> schrieb am Do., 11.
Apr. 2019, 21:59:
On 4/11/19 9:30 PM, Simon Goldschmidt wrote:
>
>
> On 11.04.19 21:03, Tom Rini wrote:
>> On Th
To clean up reset handling for socfpga gen5, port the DDR driver to DM
using UCLASS_RAM and implement proper reset handling.
This gets us rid of one ad-hoc call to socfpga_per_reset().
The gen5 driver is implemented in 2 distinct files. One of it (containing
the calibration training) is not touch
The Standard Host Controller Interface (SDHCI) specification version
3.00 adds support for Advanced DMA (ADMA) for both 64 and 32 bit widths
of DMA. ADMA2 uses a table of descriptors for aggregating DMA requests.
This significantly improves read and write throughput.
Add Support for the same.
Sig
In preparation for addition of ADMA2 support, cleanup SDMA handling by
moving it to a new sdhci_prepare_dma() function. Also add a flags field
in sdhci_host to indicate if DMA is enabled.
Signed-off-by: Faiz Abbas
---
drivers/mmc/sdhci.c | 92 -
includ
The following patches add support for ADMA2 in SDHCI.
Tested with Am65x_evm with some out of tree patches unrelated to MMC.
Faiz Abbas (2):
mmc: sdhci: Move DMA handling to prepare_dma() function
mmc: sdhci: Add Support for ADMA2
drivers/mmc/Kconfig | 14
drivers/mmc/sdhci.c | 188 +++
NanoPi M1 plus have a 10/100/1000M ethernet with external phy.
Phy power is controlled by PD6.
Add the required configuration for it.
Signed-off-by: Emmanuel Vadot
---
configs/nanopi_m1_plus_defconfig | 2 ++
1 file changed, 2 insertions(+)
diff --git a/configs/nanopi_m1_plus_defconfig b/config
Hi Tom et al.,
On Wed, Mar 27, 2019 at 01:17:26PM -0500, Andreas Dannenberg wrote:
> When using memalign() in a scenario where U-Boot is configured for full
> malloc support with simple malloc not explicitly enabled and before the
> full malloc support is initialized, a memory block is being alloc
On Tue, Apr 16, 2019 at 11:24 AM Thierry Reding
wrote:
>
> From: Thierry Reding
>
> In order for the device to use the proper MAC address, which can have
> been configured in the environment prior to the device being registered,
> ensure that the MAC address is written after the device has been p
On Tue, Apr 16, 2019 at 11:21 AM Thierry Reding
wrote:
>
> From: Thierry Reding
>
> This version of the RTL-8168 is present on some development boards and
> is compatible with this driver. Add support for identifying this version
> of the chip so that U-Boot won't complain about it being unknown.
On Tue, Apr 16, 2019 at 11:21 AM Thierry Reding
wrote:
>
> From: Thierry Reding
>
> Implement this callback that allows the MAC address to be set for the
> Ethernet card. This is necessary in order for the device to be able to
> receive packets for the MAC address that U-Boot advertises.
>
> Sign
On Fri, Mar 15, 2019 at 04:32:32PM +0100, Thierry Reding wrote:
> From: Thierry Reding
>
> Make sure that we don't overflow the hose->regions array, otherwise we
> would end up overwriting the hose->region_count field and cause mayhem
> to ensue. Also print an error message when we'd be overflowi
From: Thierry Reding
Add the standard Ethernet device tree bindings (imported from v5.0 of
the Linux kernel) and implement support for reading the MAC address for
Ethernet devices in the Ethernet uclass. If the "mac-address" property
exists, the MAC address will be parsed from that. If that prope
From: Thierry Reding
In order for the device to use the proper MAC address, which can have
been configured in the environment prior to the device being registered,
ensure that the MAC address is written after the device has been probed.
For devices that are registered before the network stack is
Tom, Jagan
On 16/04/19 9:31 PM, Vignesh Raghavendra wrote:
Now that SPI NOR Supports MMIO SPI controllers via spi-mem framework,
move TI QSPI to SPI MEM framework for better performance and avoid
repeating SPI NOR generic code in the driver.
While at that get rid of non DM code, as all boards a
From: Thierry Reding
This version of the RTL-8168 is present on some development boards and
is compatible with this driver. Add support for identifying this version
of the chip so that U-Boot won't complain about it being unknown.
Signed-off-by: Thierry Reding
---
drivers/net/rtl8169.c | 1 +
On 4/16/19 12:56 PM, Heinrich Schuchardt wrote:
On 4/16/19 6:24 AM, AKASHI Takahiro wrote:
In the current implementation, bootefi command and EFI boot manager
don't use load_image API, instead, use more primitive and internal
functions. This will introduce duplicated code and potentially
unknown
From: Thierry Reding
Implement this callback that allows the MAC address to be set for the
Ethernet card. This is necessary in order for the device to be able to
receive packets for the MAC address that U-Boot advertises.
Signed-off-by: Thierry Reding
---
drivers/net/rtl8169.c | 18 +++
Convert driver to use spi-mem ops in order to support accelerated MMIO
flash interface in generic way and for better performance.
Signed-off-by: Vignesh Raghavendra
Reviewed-by: Tom Rini
---
drivers/spi/ti_qspi.c | 132 ++
1 file changed, 68 insertions(+
Now that all boards using TI QSPI have moved to DM and DT, drop non DM
code completely.
Signed-off-by: Vignesh Raghavendra
Reviewed-by: Tom Rini
---
drivers/spi/Kconfig | 13 +-
drivers/spi/Makefile | 2 +-
drivers/spi/ti_qspi.c| 231 ++---
Now that SPI NOR Supports MMIO SPI controllers via spi-mem framework,
move TI QSPI to SPI MEM framework for better performance and avoid
repeating SPI NOR generic code in the driver.
While at that get rid of non DM code, as all boards are expected to
support DM and DT by now.
Tested on AM43xx, dr
Hi Hans,
On Fri, Apr 12, 2019 at 6:23 PM Jagan Teki wrote:
>
> Enable ahci node for a20-wits-pro-a20-dkt, this would require since
> we have DM_SCSI enabled on the respective SoC.
>
> Cc: Hans de Goede
> Signed-off-by: Jagan Teki
> ---
> Note: This change would need to send Linux first.
Would
Only some Soc need Schmitter feature, so move the
implementation into their own files.
Signed-off-by: David Wu
---
Change in v3:
- None
drivers/pinctrl/rockchip/pinctrl-rk3328.c | 17 -
.../pinctrl/rockchip/pinctrl-rockchip-core.c | 19 +++
drivers/pinctrl/
As the mux/pull/drive feature implement at own file,
the type and label are not necessary.
Signed-off-by: David Wu
---
Change in v3:
- None
drivers/pinctrl/rockchip/pinctrl-rk3036.c | 2 --
drivers/pinctrl/rockchip/pinctrl-rk3128.c | 2 --
drivers/pinctrl/rockchip/pinctrl-rk3188.c | 2
RK3288 pmu_gpio0 pull setting have no higher 16 writing corresponding
bits, need to read before write the register.
Signed-off-by: David Wu
---
Change in v3:
- None
drivers/pinctrl/rockchip/pinctrl-rk3288.c | 11 +--
1 file changed, 9 insertions(+), 2 deletions(-)
diff --git a/drivers
As the common set_mux func(), implement the feature at the own file
for each Soc.
Signed-off-by: David Wu
---
Change in v3:
- None
drivers/pinctrl/rockchip/pinctrl-rk3036.c | 23 -
drivers/pinctrl/rockchip/pinctrl-rk3128.c | 23 -
drivers/pinctrl/rockchip/pinctrl-rk3188.c |
RK3288 pmu_gpio0 drive strength setting have no higher 16 writing
corresponding bits, need to read before write the register.
Signed-off-by: David Wu
---
Change in v3:
- Add some comment
drivers/pinctrl/rockchip/pinctrl-rk3288.c | 11 +--
1 file changed, 9 insertions(+), 2 deletions(-)
As the common set_mux func(), implement the feature at the own file
for each Soc.
Signed-off-by: David Wu
---
Change in v3:
- None
drivers/pinctrl/rockchip/pinctrl-rk322x.c | 25 -
drivers/pinctrl/rockchip/pinctrl-rk3288.c | 35 +--
drivers/pinctrl/rockchip/pinctrl-rk3328.c
Some files have the redundant spaces, remove them.
Signed-off-by: David Wu
---
Change in v3:
- None
drivers/pinctrl/rockchip/pinctrl-rk3036.c | 12 ++--
drivers/pinctrl/rockchip/pinctrl-rk3188.c | 12 ++--
drivers/pinctrl/rockchip/pinctrl-rk322x.c | 18 -
driver
RK3288 pmu_gpio0 iomux setting have no higher 16 writing corresponding
bits, need to read before write the register.
Signed-off-by: David Wu
---
Change in v3:
- Add some comment
drivers/pinctrl/rockchip/pinctrl-rk3288.c | 10 +-
1 file changed, 9 insertions(+), 1 deletion(-)
diff --gi
Such as rk3288's pins of pmu_gpio0 are a special feature, which have no
higher 16 writing corresponding bits, use common set_mux() func would
introduce more code, so implement their set_mux() in each Soc's own
file to reduce the size of code.
Signed-off-by: David Wu
---
Change in v3:
- None
dr
Some Socs use the pull-pin-default config param, need to add it.
And input-enable/disable config params are not necessary, remove it.
Signed-off-by: David Wu
---
Change in v3:
- Add some commit message
drivers/pinctrl/rockchip/pinctrl-rockchip-core.c | 3 +--
1 file changed, 1 insertion(+), 2
To reduce the pinctrl driver, implement the mux/drive/pull/schmitt
func at per Soc.
David Wu (10):
pinctrl: rockchip: Add pull-pin-default param and remove unused param
pinctrl: rockchip: Remove redundant spaces
pinctrl: rockchip: Split the common set_mux() into per Soc
pinctrl: rockchip
Hi Anatolij,
Thanks for your feedback!
On Tue, Apr 16, 2019 at 2:31 PM Anatolij Gustschin wrote:
>
> Hi Igor,
>
> On Tue, 16 Apr 2019 12:04:41 +
> Igor Opaniuk igor.opan...@toradex.com wrote:
> ...
> > So there are 2 questions spinning in my mind:
> > 1) In case if you are maybe aware, if th
Hi Jagan,
On Tue, Apr 16, 2019 at 2:35 PM Jagan Teki wrote:
>
> On Tue, Apr 16, 2019 at 5:36 PM Igor Opaniuk wrote:
> >
> > Marek, Peng,
> >
> > Writing to you as you were the main contributors to U-boot mxsfb
> > driver implementation (i.MX23/i.MX28 LCDIF driver).
> >
> > I was about to start w
On Tue, Apr 16, 2019 at 5:36 PM Igor Opaniuk wrote:
>
> Marek, Peng,
>
> Writing to you as you were the main contributors to U-boot mxsfb
> driver implementation (i.MX23/i.MX28 LCDIF driver).
>
> I was about to start working on it's migration to DM (currently mxsfb
> is being used on our SoM Colib
Hi Igor,
On Tue, 16 Apr 2019 12:04:41 +
Igor Opaniuk igor.opan...@toradex.com wrote:
...
> So there are 2 questions spinning in my mind:
> 1) In case if you are maybe aware, if there were any intentions to do
> this migration before? (maybe someone asked similar questions or even
> send some
Hi,
Le mardi 16 avril 2019 à 16:26 +0530, Jagan Teki a écrit :
> Add initial support for Rockpro64 board.
>
> Specification
> - Rockchip RK3399
> - 2/4GB Dual-Channel LPDDR3
> - SD card slot
> - eMMC socket
> - 128Mb SPI Flash
> - Gigabit ethernet
> - PCIe 4X slot
> - WiFI/BT module socket
> - HD
Hi,
Le mardi 16 avril 2019 à 16:26 +0530, Jagan Teki a écrit :
> Add initial support for Nanopi NEO4 board.
>
> Specification
> - Rockchip RK3399
> - 1GB DDR3-1866
> - SD card slot
> - eMMC Socket
> - RTL8211E 1Gbps
> - AP6212 WiFI/BT
> - HDMI In/Out, DP, MIPI CSI
> - USB 3.0, 2.0
> - USB Type C
Hi,
Le mardi 16 avril 2019 à 16:26 +0530, Jagan Teki a écrit :
> Sync rk3399-nanopi4.dtsi from Linux 5.1-rc2 tag.
>
> Linux commit details about the rk3399-nanopi4.dtsi sync:
> "arm64: dts: rockchip: Add nanopi4 bluetooth"
> (sha1: 3e2f0bb72be36aa6c14ee7f11ac4dd8014801030)
>
> Signed-off-by: Jag
Hi,
Le mardi 16 avril 2019 à 16:26 +0530, Jagan Teki a écrit :
> Add initial support for Nanopc T4 board.
>
> Specification
> - Rockchip RK3399
> - Dual-Channel 4GB LPDDR3-1866
> - SD card slot
> - 16GB eMMC
> - RTL8211E 1Gbps
> - AP6356S WiFI/BT
> - HDMI In/Out, DP, MIPI DSI/CSI, eDP
> - USB 3.0
Hi,
Le mardi 16 avril 2019 à 16:26 +0530, Jagan Teki a écrit :
> Add initial support for Nanopi M4 board.
>
> Specification
> - Rockchip RK3399
> - Dual-Channel 4GB LPDDR3-1866
> - SD card slot
> - eMMC socket
> - RTL8211E 1Gbps
> - AP6356S WiFI/BT
> - HDMI In/Out, DP, MIPI DSI/CSI
> - USB 3.0 x4
Marek, Peng,
Writing to you as you were the main contributors to U-boot mxsfb
driver implementation (i.MX23/i.MX28 LCDIF driver).
I was about to start working on it's migration to DM (currently mxsfb
is being used on our SoM Colibri iMX7S/D), but found it a bit
out-dated (no one introduced any ch
Hi,
Le mardi 16 avril 2019 à 16:26 +0530, Jagan Teki a écrit :
> Add initial support for Orangepi RK3399 board.
>
> Specification
> - Rockchip RK3399
> - 2GB/4GB DDR3
> - 16GB eMMC
> - SD card slot
> - RTL8211E 1Gbps
> - AP6356S WiFI/BT
> - HDMI In/Out, DP, MIPI DSI/CSI
> - Mini PCIe
> - Sensors,
Hi,
Le mardi 16 avril 2019 à 16:26 +0530, Jagan Teki a écrit :
> Few SPL and U-Boot proper configs are common to all rk3399 target
> defconfigs, move them and select it from platform kconfig.
>
> Moved configs:
> - SPL_ATF
> - SPL_ATF_NO_PLATFORM_PARAM if SPL_ATF
> - SPL_LOAD_FIT
> - SPL_CLK
> -Original Message-
> From: Vignesh Raghavendra
> Sent: Friday, April 12, 2019 1:01 PM
> To: Rajat Srivastava ; u-boot@lists.denx.de;
> tr...@konsulko.com; marek.va...@gmail.com;
> marek.vasut+rene...@gmail.com; ja...@openedev.com
> Cc: Ashish Kumar
> Subject: [EXT] Re: [PATCH] mtd: sp
Hi,
Le mardi 16 avril 2019 à 16:26 +0530, Jagan Teki a écrit :
> Add default SPL_FIT_GENERATOR py script for rockchip platforms if
> specific target enabled SPL_LOAD_FIT.
>
> So, this would help get rid of explicitly mentioning the default
> SPL FIT generator in defconfigs. however some targets,
Hi,
Le mardi 16 avril 2019 à 16:26 +0530, Jagan Teki a écrit :
> u-boot,dm-pre-reloc is required for SDMMC booted rk3399 boards and
> which is U-Boot specific devicetrees binding.
>
> Move it on global rk3399-u-boot.dtsi file and rest of the U-Boot
> bindings will move it future based on the requ
Le mardi 16 avril 2019 à 16:26 +0530, Jagan Teki a écrit :
> To make successful build with dts(i) files syncing from Linux 5.1-rc2
> the rk3399.dtsi would require pwm2_pin_pull_down.
>
> So, sync the pwm2_pin_pull_down node from Linux 5.1-rc2. Since this
> node is strictly not part of any commit
Maximum write size in a single write operation in
spi_nor_write_data() function can be equal to slave
tx buffer, which is adjusted in spi_mem_adjust_op_size()
and write operation gets fragmented.
Previously data write for the above fragmentation
didn't incorporate write enable and status checks.
I
Le mardi 16 avril 2019 à 16:26 +0530, Jagan Teki a écrit :
> Sync rk3399-opp.dtsi from Linux.
>
> Linux commit details about the rk3399-opp.dtsi sync:
> "arm64: dts: rockchip: use SPDX-License-Identifier"
> (sha1: 4ee99cebd486238ac433da823b95cc5f8d8a6905)
>
> Signed-off-by: Jagan Teki
Reviewed-
Hi,
Le mardi 16 avril 2019 à 16:26 +0530, Jagan Teki a écrit :
> This series is combination of previous version[1] plus new rk3399
> boards addition.
Thanks for following-up on this series!
> Overall this series add support below rk3399 boards
> - Orangepi RK3399
> - Nanopc T4
> - Nanopi M4
> -
If u-boot gets used as coreboot payload it might be nice to get
vendor, model and bios version from smbios. I am not sure about
the output of all the read information.
With qemu target for coreboot this could look this:
CBFS: 'Master Header Locator' located CBFS at [7a0200:80)
CBFS: Locating
Add an very simple API to be able to access SMBIOS strings
like vendor, model and bios version.
Signed-off-by: Christian Gmeiner
---
include/smbios.h| 37 ++
lib/Kconfig | 6 ++
lib/Makefile| 1 +
lib/smbios-parser.c | 162
generate define for an alias only if the struct is not
created already.
This prevents compilerwarning:
PLATspl/dts/dt-platdata.o
spl/dts/dt-platdata.c:11:46: error: missing braces around initializer
[-Werror=missing-braces]
static const struct dtd_simple_bus dtv_ahb = {
- at91sam9g20-taurus.dts: use labels
- cleanup taurus port to compile clean with
current mainline again. SPL has no serial
output anymore, so it fits into SRAM.
Signed-off-by: Heiko Schocher
---
Changes in v2:
- add comment from Eugen
fix axm_defconfig
- sync defconfig
make savedefconf
Fix build Warnings:
= WARNING ==
This board does not use CONFIG_DM_USB. Please update
the board to use CONFIG_DM_USB before the v2019.07 release.
Failure to update by the deadline may result in board removal.
See doc/driver-model/MIGRATION.txt for more info.
El 12/4/19 a las 09:52, Jagan Teki escribió:
This would Migrate DM_MMC, DM_SCSI for A20 and R40 platforms.
Note:
- a20-wits-pro-a20-dkt change would need to send Linux first
- BPI-M2-Berry would break, but will import Linux dts once approved.
Andre Przywara (1):
sunxi: update SATA driver to
Add sdram dtsi file for 4GB LPDDR3-1866 DMC settings by reverse
engineered from the rk3399_ddr_933Mhz_v1.14.bin file.
Full credits to 'Liviu Dudau' who is the real author for this change.
Signed-off-by: Liviu Dudau
Signed-off-by: Jagan Teki
---
.../arm/dts/rk3399-sdram-lpddr3-4GB-1866.dtsi | 1
On 11. 04. 19 12:18, Alexander Dahl wrote:
> Passing on a return value of -1 from a called function leads to printing
> out usage text. In case of actually correct usage with correctly
> specified parameters but some fail at runtime printing out that usage
> text is distracting.
>
> The reason is
sdmmc cd pin is configured as RK_FUNC_GPIO which is wrong and
indeed failed to detect the sdcard on the board with below error
Card did not respond to voltage select!
So, fix it by replacing RK_FUNC_GPIO with RK_FUNC_1 which
is already defined in rk3399.dts so make use of same like
other boards
Sync rk3399-nanopi4.dtsi from Linux 5.1-rc2 tag.
Linux commit details about the rk3399-nanopi4.dtsi sync:
"arm64: dts: rockchip: Add nanopi4 bluetooth"
(sha1: 3e2f0bb72be36aa6c14ee7f11ac4dd8014801030)
Signed-off-by: Jagan Teki
---
arch/arm/dts/rk3399-nanopi4.dtsi | 703 +
Few SPL and U-Boot proper configs are common to all rk3399 target
defconfigs, move them and select it from platform kconfig.
Moved configs:
- SPL_ATF
- SPL_ATF_NO_PLATFORM_PARAM if SPL_ATF
- SPL_LOAD_FIT
- SPL_CLK if SPL
- SPL_PINCTRL if SPL
- SPL_RAM if SPL
- SPL_REGMAP if SPL
- SPL_SYSCO
Add initial support for Nanopi NEO4 board.
Specification
- Rockchip RK3399
- 1GB DDR3-1866
- SD card slot
- eMMC Socket
- RTL8211E 1Gbps
- AP6212 WiFI/BT
- HDMI In/Out, DP, MIPI CSI
- USB 3.0, 2.0
- USB Type C power and data
- GPIO expansion ports
- DC 5V/3A
Commit details of rk3399-nanopi-neo4.d
Add initial support for Nanopc T4 board.
Specification
- Rockchip RK3399
- Dual-Channel 4GB LPDDR3-1866
- SD card slot
- 16GB eMMC
- RTL8211E 1Gbps
- AP6356S WiFI/BT
- HDMI In/Out, DP, MIPI DSI/CSI, eDP
- USB 3.0, 2.0
- USB Type C power and data
- GPIO expansion ports
- DC 12V/2A
Commit details o
Add initial support for Nanopi M4 board.
Specification
- Rockchip RK3399
- Dual-Channel 4GB LPDDR3-1866
- SD card slot
- eMMC socket
- RTL8211E 1Gbps
- AP6356S WiFI/BT
- HDMI In/Out, DP, MIPI DSI/CSI
- USB 3.0 x4
- USB Type C power and data
- GPIO1, GPIO2 expansion ports
- DC5V/3A
Commit details
Since rockchip have an individual doc/README.rockchip, it would
be better to update the same instead of maintaining it separately
in board files.
So, add the documentation for rk3399
- procedure to build for Rockchip miniloader and
U-Boot SPL options
- procedure to boot from SD for Rockchip mini
Add initial support for Orangepi RK3399 board.
Specification
- Rockchip RK3399
- 2GB/4GB DDR3
- 16GB eMMC
- SD card slot
- RTL8211E 1Gbps
- AP6356S WiFI/BT
- HDMI In/Out, DP, MIPI DSI/CSI
- Mini PCIe
- Sensors, Keys etc
- DC12V-2A and DC5V-2A
Commit details about Linux DTS sync:
"arm64: dts: rock
On 11. 04. 19 12:18, Alexander Dahl wrote:
> Some code parts stood too far left …
>
> Signed-off-by: Alexander Dahl
> ---
> drivers/fpga/cyclon2.c | 36 ++--
> 1 file changed, 18 insertions(+), 18 deletions(-)
>
> diff --git a/drivers/fpga/cyclon2.c b/drivers/fpg
Add initial support for Rockpro64 board.
Specification
- Rockchip RK3399
- 2/4GB Dual-Channel LPDDR3
- SD card slot
- eMMC socket
- 128Mb SPI Flash
- Gigabit ethernet
- PCIe 4X slot
- WiFI/BT module socket
- HDMI In/Out, DP, MIPI DSI/CSI, eDP
- USB 3.0, 2.0
- USB Type C power and data
- GPIO expan
Add default SPL_FIT_GENERATOR py script for rockchip platforms if
specific target enabled SPL_LOAD_FIT.
So, this would help get rid of explicitly mentioning the default
SPL FIT generator in defconfigs. however some targets, like puma_rk3399
still require their own FIT generator so in those cases t
u-boot,dm-pre-reloc is required for SDMMC booted rk3399 boards and
which is U-Boot specific devicetrees binding.
Move it on global rk3399-u-boot.dtsi file and rest of the U-Boot
bindings will move it future based on the requirement.
This would help to sync the devicetrees from Linux whenever requ
To make successful build with dts(i) files syncing from Linux 5.1-rc2
the rk3399.dtsi would require pwm2_pin_pull_down.
So, sync the pwm2_pin_pull_down node from Linux 5.1-rc2. Since this
node is strictly not part of any commit alone, I have mentioned
Linux 5.1-rc2 tag for future reference of whe
This series is combination of previous version[1] plus new rk3399
boards addition.
Overall this series add support below rk3399 boards
- Orangepi RK3399
- Nanopc T4
- Nanopi M4
- Nanopi NEO4
- Orangepi RK3399
- Rockpro64
All the respective dts(i) files are synced from Linux 5.1-rc2 and few
dts(i)
Sync rk3399-opp.dtsi from Linux.
Linux commit details about the rk3399-opp.dtsi sync:
"arm64: dts: rockchip: use SPDX-License-Identifier"
(sha1: 4ee99cebd486238ac433da823b95cc5f8d8a6905)
Signed-off-by: Jagan Teki
---
arch/arm/dts/rk3399-opp.dtsi | 133 +++
1 file
On 4/16/19 6:24 AM, AKASHI Takahiro wrote:
In the current implementation, bootefi command and EFI boot manager
don't use load_image API, instead, use more primitive and internal
functions. This will introduce duplicated code and potentially
unknown bugs as well as inconsistent behaviours.
With t
On 16. 04. 19 12:29, Peng Ma wrote:
>
>
>> -Original Message-
>> From: Michal Simek
>> Sent: 2019年4月16日 18:01
>> To: Peng Ma ; Michal Simek ;
>> albert.u.b...@aribaud.net; s...@chromium.org; Fabio Estevam
>> ; York Sun ; Prabhakar
>> Kushwaha
>> Cc: Andy Tang ; Yinbo Zhu ;
>> u-boot@lis
On 11/04/2019 07:23, akaher wrote:
> There are compilation errors, if CONFIG_CMD_USB is enabled
> and CONFIG_USB is disabled.
>
> CONFIG_CMD_USB depends upon CONFIG_USB, so CONFIG_CMD_USB
> should not be enabled if CONFIG_USB is disabled.
>
> Signed-off-by: Ajay Kaher
>
Reviewed-by: Matthias
On 05/04/2019 10:30, Heiko Stuebner wrote:
> Function to get the contents of the mpidr register, similar to
> its arm64 counterpart.
>
> Signed-off-by: Heiko Stuebner
Reviewed-by: Matthias Brugger
> ---
> arch/arm/include/asm/system.h | 9 +
> 1 file changed, 9 insertions(+)
>
> di
>-Original Message-
>From: Michal Simek
>Sent: 2019年4月16日 18:01
>To: Peng Ma ; Michal Simek ;
>albert.u.b...@aribaud.net; s...@chromium.org; Fabio Estevam
>; York Sun ; Prabhakar
>Kushwaha
>Cc: Andy Tang ; Yinbo Zhu ;
>u-boot@lists.denx.de
>Subject: Re: [EXT] Re: [PATCH 1/2] scsi: ceva:
On 03/04/2019 14:58, Alexander Dahl wrote:
> Hello Pascal,
>
> Am Mittwoch, 3. April 2019, 09:08:57 CEST schrieb Linder Pascal:
>> I am new to U-Boot and I am trying to understand what I need to code for
>> using my own board with the bootloader.
>
> Welcome. :-)
>
> I try to describe my view
1 - 100 of 116 matches
Mail list logo
