Heinrich,
On Fri, Sep 28, 2018 at 04:35:57AM +0200, Heinrich Schuchardt wrote:
> On 08/09/2018 08:50 AM, AKASHI Takahiro wrote:
> > Currently, unload function in EFI_LOADED_IMAGE_PROTOCOL is never called
> > at UnloadImage Boot Service. This is not compliant to UEFI specification.
> > See chapter
Hi, York,
I prefer not to rename it. This is consistent with Linux kernel.
-Original Message-
From: York Sun
Sent: 2018年9月22日 5:06
To: Ying Zhang
Cc: u-boot@lists.denx.de
Subject: Re: [PATCH 01/18] gpio: mpc8xxx: add support for Layerscape SoC
On 08/23/2018 08:27 AM, York Sun
Hi,
On Fri, Sep 28, 2018 at 11:30 AM Mrun Lele wrote:
>
> Hello Everyone,
>
> I am using U-Boot-2017.09. I want to enable MMU before U-Boot loads uImage.
>
> I googled it and I found one thread dated back in July 2010.
> this is the link
>
Hello Everyone,
I am using U-Boot-2017.09. I want to enable MMU before U-Boot loads uImage.
I googled it and I found one thread dated back in July 2010.
this is the link
https://lists.denx.de/pipermail/u-boot/2010-July/073510.html
Basically, it involved code change (enabling MMU in start.S and
On 08/09/2018 08:51 AM, AKASHI Takahiro wrote:
> Currently, image's image_base points to an address where the image was
> temporarily uploaded for further loading. Since efi_loader relocates
> the image to final destination, image_base and image_size should reflect
> that.
Thanks for pointing
On 08/09/2018 08:50 AM, AKASHI Takahiro wrote:
> Currently, unload function in EFI_LOADED_IMAGE_PROTOCOL is never called
> at UnloadImage Boot Service. This is not compliant to UEFI specification.
> See chapter "9.1 EFI Loaded Image Protocol."
With all the patches we got into U-Boot (+HII
Hi York,
> -Original Message-
> From: York Sun
> Sent: Friday, September 28, 2018 00:53
> To: Ran Wang ; Alison Wang
> Cc: Qiang Zhao ; u-boot@lists.denx.de
> Subject: Re: [PATCH v3 2/2] armv7: ls102xa: Disable QE before enter deep
> sleep
>
> On 09/25/2018 10:46 PM, Ran Wang wrote:
> >
Hi Rick,
On Wed, Sep 26, 2018 at 9:50 PM Bin Meng wrote:
>
> This series adds QEMU RISC-V 'virt' board target support, with the
> hope of helping people easily test U-Boot on RISC-V.
>
> Some existing RISC-V codes have been changed to make it easily to
> support new targets. Some spotted coding
Hi Simon,
On 09/27/2018 04:43 PM, Simon Glass wrote:
...
How does this all get tested? Could we have a simple sandbox driver?
We can switch the Travis-CI jobs for the QEMU boards to use virtio-net
instead of the current network cards for the TFTP tests. I don't know
if there are pytest
Hi Bin,
On 09/23/2018 04:42 PM, Bin Meng wrote:
With the virtio net and blk drivers, we can do more stuff with some
useful commands. Imply those in the board Kconfig.
Signed-off-by: Bin Meng
---
board/emulation/qemu-riscv/Kconfig | 8
1 file changed, 8 insertions(+)
diff --git
Hi Bin,
On 09/23/2018 04:42 PM, Bin Meng wrote:
Currently devices on the virtio bus is not automatically enumerated,
which means peripherals on the virtio bus are not discovered by their
drivers. This uses board_init() to do the virtio enumeration.
Signed-off-by: Bin Meng
---
Hi Simon,
On 09/27/2018 04:42 PM, Simon Glass wrote:
On 23 September 2018 at 06:42, Bin Meng wrote:
From: Tuomas Tynkkynen
This adds virtio block device driver support.
Signed-off-by: Tuomas Tynkkynen
Signed-off-by: Bin Meng
---
...
Why does this use __u32 instead of u32?
The
Hi Bin,
On 09/23/2018 04:42 PM, Bin Meng wrote:
From: Tuomas Tynkkynen
This adds virtio net device driver support.
Signed-off-by: Tuomas Tynkkynen
Signed-off-by: Bin Meng
---
...
+static u32 feature[] = {
+ VIRTIO_NET_F_MAC
+};
+
+static u32 feature_legacy[] = {
+
Hi Bin,
On 09/23/2018 04:42 PM, Bin Meng wrote:
From: Tuomas Tynkkynen
This adds support for managing virtual queue/ring, the channel
for high performance I/O between host and guest.
Signed-off-by: Tuomas Tynkkynen
Signed-off-by: Bin Meng
---
...
+
+/*
+ * Barriers in virtio are tricky.
Hi Bin,
Thanks for the patches, they look great. Some minor comments:
On 09/23/2018 04:42 PM, Bin Meng wrote:
This adds a new virtio uclass driver for “virtio” [1] family of
devices that are are found in virtual environments like QEMU,
yet by design they look like physical devices to the
On 09/27/2018 08:37 AM, Ang, Chee Hong wrote:
> On Thu, 2018-09-27 at 08:21 +0200, Marek Vasut wrote:
>> On 09/27/2018 07:08 AM, Ang, Chee Hong wrote:
>>>
>>> On Wed, 2018-09-26 at 16:53 +0200, Marek Vasut wrote:
On 09/26/2018 11:03 AM, chee.hong@intel.com wrote:
>
>
>
In the case where one deletes an already-non-existing variable, or sets
a variable to the value it already has, there is no point in writing the
environment back, thus reducing wear on the underlying storage
device.
In the case of redundant environments, if the two environments
differ (e.g.
On Thu, Sep 27, 2018 at 12:43:34PM +0200, Michal Simek wrote:
> Hi Tom,
>
> please pull these changes to your tree.
> Travis build looks good.
> https://travis-ci.org/michalsimek/u-boot/builds/433924161
>
> Both net patches are acked by Joe.
>
> Thanks,
> Michal
>
> The following changes
Rock960 is a family of boards based on Rockchip RK3399 SoC from Vamrs.
It consists of Rock960 (Consumer Edition) and Ficus (Enterprise Edition)
96Boards.
Below are some of the key differences between both Rock960 and Ficus
boards:
1. Different host enable GPIO for USB
2. Different power and
Add board support for Rock960 CE board from Vamrs. This board utilizes
common Rock960 family support.
Following peripherals are tested and known to work:
* USB 2.0
* MMC
This commit also adds DDR configuration for LPDDR3-2GiB-1600MHz which
is being used on the board.
Signed-off-by: Manivannan
Add board support for Ficus EE board from Vamrs. This board utilizes
common Rock960 family support.
Following peripherals are tested and known to work:
* Gigabit Ethernet
* USB 2.0
* MMC
Signed-off-by: Ezequiel Garcia
[Reworked based on common Rock960 family support]
Signed-off-by: Manivannan
From: Randy Li
Those pins would be used by many boards.
Commit grabbed from Linux:
commit b41023282d07b61a53e2c9b9508912b1e7ce7b4f
Author: Randy Li
Date: Thu Jun 21 21:32:10 2018 +0800
arm64: dts: rockchip: add some common pin-settings to rk3399
Those pins would be used by many
This patchset adds support for Rock960 and Ficus 96Boards from Vamrs.
Since both boards share most of the configurations, a common Rock960
family support is added with common support and the actual boards are
based on this.
The previous version of the patchseries were adding Rock960 [1] and
Ficus
Remove a superfluous statement in efi_dp_get_next_instance().
Signed-off-by: Heinrich Schuchardt
---
lib/efi_loader/efi_device_path.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/lib/efi_loader/efi_device_path.c b/lib/efi_loader/efi_device_path.c
index 6040bcff19..172317b9a0 100644
---
fix typos
correct the header comment of efi_selftest_variables.c
Signed-off-by: Heinrich Schuchardt
---
lib/efi_selftest/efi_selftest_config_table.c | 12 ++--
lib/efi_selftest/efi_selftest_controllers.c | 2 +-
lib/efi_selftest/efi_selftest_crc32.c| 4 ++--
Hi Simon,
On Thu, Sep 27, 2018 at 06:41:37AM -0700, Simon Glass wrote:
> Hi Angelo,
>
> On 26 September 2018 at 11:53, Angelo Dureghello wrote:
> > Hi Simon,
> >
> > thanks for the review.
> >
> > On Tue, Sep 25, 2018 at 10:42:08PM -0700, Simon Glass wrote:
> >> Hi Angelo,
> >>
> >> On 20
On 09/12/2018 04:18 AM, Vinitha V Pillai wrote:
> Change bootscript and its header name in
> ls1088ardb_pb board specific file
>
> Signed-off-by: Vinitha V Pillai
> ---
> include/configs/ls1088ardb_pb.h | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
Are you sure you are using
On 09/25/2018 10:46 PM, Ran Wang wrote:
> Otherwise system will hang after executing wfi.
This patch doesn't depend on the first patch, does it? In another word,
this issue exists before, we didn't notice before because no one put the
system on deep sleep. Is that right?
York
Hi Simon
On 09/26/2018 07:42 AM, Simon Glass wrote:
> Hi Patrice,
>
> On 20 September 2018 at 07:37, Patrice Chotard wrote:
>> pinmux_show() allows to display the muxing of all pins
>> belonging to a pin-controller
>>
>> Signed-off-by: Patrice Chotard
>> ---
>>
>>
Hi Simon
On 09/26/2018 07:41 AM, Simon Glass wrote:
> Hi Patrice,
>
> On 20 September 2018 at 07:37, Patrice Chotard wrote:
>> pinmux_show allows to display the muxing of all pins
>> belonging to pin-controller.
>>
>> Signed-off-by: Patrice Chotard
>> ---
>>
>> drivers/pinctrl/pinctrl_stm32.c
Hi Simon,
On Thu, Sep 27, 2018 at 3:45 PM Simon Glass wrote:
>
> Hi Mario,
>
> On 26 September 2018 at 06:36, Mario Six wrote:
> > Hi Simon,
> > On Tue, Jul 31, 2018 at 11:46 AM Mario Six wrote:
> >>
> >> Add tests for the new board uclass.
> >>
> >> Reviewed-by: Simon Glass
> >>
Hi Simon,
On Thu, Sep 27, 2018 at 3:42 PM Simon Glass wrote:
>
> Hi Mario,
>
> On 26 September 2018 at 06:34, Mario Six wrote:
> >
> > Hi Simon,
> > On Wed, Jun 27, 2018 at 1:18 AM Simon Glass wrote:
> > >
> > > On 26 June 2018 at 00:46, Mario Six wrote:
> > > > Implement a set of functions to
On 23 September 2018 at 06:42, Bin Meng wrote:
> With the virtio net and blk drivers, we can do more stuff with some
> useful commands. Imply those in the board Kconfig.
>
> Signed-off-by: Bin Meng
> ---
>
> board/emulation/qemu-riscv/Kconfig | 8
> 1 file changed, 8 insertions(+)
On 23 September 2018 at 06:42, Bin Meng wrote:
> From: Tuomas Tynkkynen
>
> This adds virtio block device driver support.
>
> Signed-off-by: Tuomas Tynkkynen
> Signed-off-by: Bin Meng
> ---
>
> drivers/virtio/Kconfig | 7 +++
> drivers/virtio/Makefile | 1 +
>
On 23 September 2018 at 06:42, Bin Meng wrote:
> From: Tuomas Tynkkynen
>
> This adds a new block interface type for VirtIO block devices.
>
> Signed-off-by: Tuomas Tynkkynen
> Signed-off-by: Bin Meng
> ---
>
> disk/part.c| 6 ++
> drivers/block/blk-uclass.c | 2 ++
>
On 23 September 2018 at 06:42, Bin Meng wrote:
> blk_next_free_devnum() can be helpful in some cases. Make it
> a public API.
>
> Signed-off-by: Bin Meng
> ---
>
> drivers/block/blk-uclass.c | 2 +-
> include/blk.h | 11 +++
> 2 files changed, 12 insertions(+), 1
Hi Bin,
On 23 September 2018 at 06:42, Bin Meng wrote:
> Add REAME.virtio to describe the information about U-Boot support for
> VirtIO devices, including supported boards, build instructions, driver
> details etc.
>
> Signed-off-by: Bin Meng
>
> ---
>
> doc/README.virtio | 247
>
Hi Bin,
On 23 September 2018 at 06:41, Bin Meng wrote:
> This series brings in VirtIO driver support in U-Boot. The work is based
> on Tuomas's virtio support on QEMU ARM targets.
>
> VirtIO is a virtualization standard for network and disk device drivers
> where just the guest's device driver
On 23 September 2018 at 06:42, Bin Meng wrote:
> Add virtio drivers for QEMU x86 targets.
>
> Signed-off-by: Bin Meng
> ---
>
> board/emulation/qemu-x86/Kconfig | 3 +++
> 1 file changed, 3 insertions(+)
Reviewed-by: Simon Glass
___
U-Boot mailing
On 23 September 2018 at 06:42, Bin Meng wrote:
> With the post_probe() changes, this API is no longer needed.
>
> Signed-off-by: Bin Meng
> ---
>
> drivers/block/blk-uclass.c | 9 -
> include/blk.h | 10 --
> 2 files changed, 19 deletions(-)
Reviewed-by: Simon
On 23 September 2018 at 06:42, Bin Meng wrote:
> Introduce a new Kconfig option for architecture codes to control
> whether it provides io{read,write}{8,16,32} I/O accessor functions.
>
> Signed-off-by: Bin Meng
> ---
>
> include/linux/io.h | 4
> lib/Kconfig| 6 ++
> 2 files
On 23 September 2018 at 06:42, Bin Meng wrote:
> From: Tuomas Tynkkynen
>
> This adds support for managing virtual queue/ring, the channel
> for high performance I/O between host and guest.
>
> Signed-off-by: Tuomas Tynkkynen
> Signed-off-by: Bin Meng
> ---
>
> drivers/virtio/Makefile |
On 23 September 2018 at 06:42, Bin Meng wrote:
> For v1.0 compliant device, it always assumes the member 'num_buffers'
> exists in the struct virtio_net_hdr while the legacy driver only
> presented 'num_buffers' when VIRTIO_NET_F_MRG_RXBUF was negotiated.
> Without that feature the structure was
On 23 September 2018 at 06:42, Bin Meng wrote:
> The blk_base test case creates a USB mass storage block device with
> the Sandbox host block device as its parent. This does not make any
> sense and causes potential issue, for example if the test case tries
> to read/write anything on the USB
On 23 September 2018 at 06:42, Bin Meng wrote:
> Add test cases to cover the two newly added PCI APIs:
> dm_pci_find_next_capability() & dm_pci_find_next_ext_capability().
>
> Signed-off-by: Bin Meng
> ---
>
> test/dm/pci.c | 20
> 1 file changed, 20 insertions(+)
On 23 September 2018 at 06:42, Bin Meng wrote:
> By default QEMU creates legacy PCI transport devices, but we can
> ask QEMU to create non-legacy one if we pass additional device
> property/value pairs in the command line:
>
> -device virtio-blk-pci,disable-legacy=true,disable-modern=false
>
>
On 23 September 2018 at 06:42, Bin Meng wrote:
> Currently devices on the virtio bus is not automatically enumerated,
> which means peripherals on the virtio bus are not discovered by their
> drivers. This uses board_init() to do the virtio enumeration.
>
> Signed-off-by: Bin Meng
> ---
>
>
On 23 September 2018 at 06:42, Bin Meng wrote:
> At present the generic io{read,write}{8,16,32} routines only support
> MMIO access. With architecture like x86 that has a separate IO space,
> these routines cannot be used to access I/O ports.
>
> Implement x86-specific version to support both PIO
Hi Bin,
On 23 September 2018 at 06:42, Bin Meng wrote:
> This adds a transport driver that implements UCLASS_VIRTIO for
> virtio over pci, which is commonly used on x86.
>
> It only supports the legacy interface of the pci transport, which
> is the default device that QEMU emulates.
>
>
On 23 September 2018 at 06:42, Bin Meng wrote:
> This introduces two new APIs dm_pci_find_next_capability() and
> dm_pci_find_next_ext_capability() to get PCI capability address
> and PCI express extended capability address for a given PCI device
> starting from a given offset.
>
> Signed-off-by:
On 23 September 2018 at 06:42, Bin Meng wrote:
> Currently the sandbox block driver uses priv_auto_alloc_size for
> the driver data, however that's only available after the device
> probe phase. In order to make it accessible in an earlier phase,
> switch to use platdata_auto_alloc_size instead.
On 23 September 2018 at 06:42, Bin Meng wrote:
> From: Tuomas Tynkkynen
>
> This adds virtio net device driver support.
>
> Signed-off-by: Tuomas Tynkkynen
> Signed-off-by: Bin Meng
> ---
>
> drivers/virtio/Kconfig | 7 ++
> drivers/virtio/Makefile | 1 +
>
Hi Bin,
On 23 September 2018 at 06:42, Bin Meng wrote:
> This adds a new virtio uclass driver for “virtio” [1] family of
> devices that are are found in virtual environments like QEMU,
> yet by design they look like physical devices to the guest.
>
> The uclass driver provides child_pre_probe()
On 23 September 2018 at 06:42, Bin Meng wrote:
> Currently the efi block driver uses priv_auto_alloc_size for the
> driver data, however that's only available after the device probe
> phase. In order to make it accessible in an earlier phase, switch
> to use platdata_auto_alloc_size instead.
>
>
On 23 September 2018 at 06:42, Bin Meng wrote:
> part_init() is currently called in every DM BLK driver, either
> in its bind() or probe() method. However we can use the BLK
> uclass driver's post_probe() method to do it automatically.
>
> Update all DM BLK drivers to adopt this change.
>
>
On 23 September 2018 at 06:42, Bin Meng wrote:
> Currently devices on the virtio bus is not automatically enumerated,
> which means peripherals on the virtio bus are not discovered by their
> drivers. This uses board_init() to do the virtio enumeration.
>
> Signed-off-by: Bin Meng
> ---
>
>
Hi Cedric,
On 10 September 2018 at 07:16, Cédric Le Goater wrote:
> The Aspeed AST2500 SoC comes with three static memory controllers, all
> with a similar interface :
>
> * Firmware SPI Memory Controller (FMC)
>. BMC firmware
>. 3 chip select pins (CE0 ~ CE2)
>. supports SPI type
On 23 September 2018 at 06:42, Bin Meng wrote:
> This adds a Kconfig file in the board directory, so that some
> board-specific options can be specified there.
>
> Signed-off-by: Bin Meng
> ---
>
> arch/arm/Kconfig | 1 +
> board/emulation/qemu-arm/Kconfig | 9 +
>
Hi Cedric,
On 10 September 2018 at 07:21, Cédric Le Goater wrote:
> The driver is based on the previous one and adds the same support for
> the Faraday ftgmac100 controller with MAC and MDIO bus support for
> RGMII/RMII modes.
>
> Driver model support was added as well as some enhancements and
On 23 September 2018 at 06:42, Bin Meng wrote:
> From: Tuomas Tynkkynen
>
> Add 'virtio' command in U-Boot command line.
>
> Signed-off-by: Tuomas Tynkkynen
> Signed-off-by: Bin Meng
> ---
>
> cmd/Kconfig | 7 +++
> cmd/Makefile | 1 +
> cmd/virtio.c | 37
On 23 September 2018 at 06:42, Bin Meng wrote:
> VirtIO can use various different buses and virtio devices are
> commonly implemented as PCI devices. But virtual environments
> without PCI support (a common situation in embedded devices
> models) might use simple memory mapped device
Hi Bin,
On 23 September 2018 at 06:41, Bin Meng wrote:
> Some buses need to set up their child devices after they are probed.
> Support a common child_post_probe() method for the uclass.
>
> With this change, the two APIs uclass_pre_probe_device() and
> uclass_post_probe_device() become
On 10 September 2018 at 07:16, Cédric Le Goater wrote:
> The AHB clock is used by the FMC/SPI controllers.
>
> Signed-off-by: Cédric Le Goater
> ---
> arch/arm/include/asm/arch-aspeed/scu_ast2500.h | 2 ++
> include/dt-bindings/clock/ast2500-scu.h| 1 +
>
On 10 September 2018 at 07:21, Cédric Le Goater wrote:
> Signed-off-by: Cédric Le Goater
> ---
> drivers/clk/aspeed/clk_ast2500.c | 1 +
> 1 file changed, 1 insertion(+)
Reviewed-by: Simon Glass
___
U-Boot mailing list
U-Boot@lists.denx.de
Hi Cedric,
On 10 September 2018 at 07:21, Cédric Le Goater wrote:
> The Faraday ftgmac100 MAC controllers as found on the Aspeed SoCs have
> some slight differences in the HW interface (End-Of-Rx/Tx-Ring
> bits). Also include the Aspeed clock enablement.
>
> Signed-off-by: Cédric Le Goater
>
On 10 September 2018 at 07:21, Cédric Le Goater wrote:
> Signed-off-by: Cédric Le Goater
> ---
> arch/arm/dts/ast2500-evb.dts | 17 +
> arch/arm/dts/ast2500.dtsi | 4 ++--
> configs/evb-ast2500_defconfig | 8
> 3 files changed, 27 insertions(+), 2 deletions(-)
Hi Bin,
On 25 September 2018 at 23:39, Bin Meng wrote:
> Hi Simon,
>
> On Wed, Sep 26, 2018 at 1:42 PM Simon Glass wrote:
>>
>> Hi Bin,
>>
>> On 4 September 2018 at 03:06, Bin Meng wrote:
>> > Hi Simon,
>> >
>> > On Mon, Sep 3, 2018 at 7:02 AM Simon Glass wrote:
>> >>
>> >> In
Hi Mario,
On 26 September 2018 at 06:36, Mario Six wrote:
> Hi Simon,
> On Tue, Jul 31, 2018 at 11:46 AM Mario Six wrote:
>>
>> Add tests for the new board uclass.
>>
>> Reviewed-by: Simon Glass
>> Signed-off-by: Mario Six
>> ---
>>
>> v3 -> v4:
>> No changes
>>
>> v2 -> v3:
>> * Accomodated
Hi Angelo,
On 26 September 2018 at 11:53, Angelo Dureghello wrote:
> Hi Simon,
>
> thanks for the review.
>
> On Tue, Sep 25, 2018 at 10:42:08PM -0700, Simon Glass wrote:
>> Hi Angelo,
>>
>> On 20 September 2018 at 15:07, Angelo Dureghello wrote:
>> > This patch converts cf_spi.c to DM and to
On 26 September 2018 at 06:02, Alexander Graf wrote:
> When running sandbox with the new pointer sanitization we just recently
> introduced, we're running into a case with FIT images where we end up
> interpreting pointers as addresses.
>
> What happened is that most callers of
Hi Mario,
On 26 September 2018 at 06:34, Mario Six wrote:
>
> Hi Simon,
> On Wed, Jun 27, 2018 at 1:18 AM Simon Glass wrote:
> >
> > On 26 June 2018 at 00:46, Mario Six wrote:
> > > Implement a set of functions to manipulate properties in a live device
> > > tree:
> > >
> > > *
On Wed, Sep 26, 2018 at 06:11:47PM +0200, Alexander Graf wrote:
> Hi Tom,
>
> This is my current patch queue for efi. Please pull.
>
> Alex
>
>
> The following changes since commit 9dc8d155d4e88563f572ee79aab758eb4272f3fd:
>
> Merge git://git.denx.de/u-boot-imx (2018-09-19 20:35:27 -0400)
On 27/09/2018 12:14:14+0200, Gregory CLEMENT wrote:
> Hi Daniel,
>
> First thanks for you prompt review, it is much appreciate. :)
>
> This week I am at kernel recipes conference, so I won't be able to fully
> address your comments but I will do it next week.
>
> However, here are some answers:
Instead of manually specifying CONFIG_SYS_EXTRA_ENV_RELOC
for every board that needs it, it shouldn't hurt to let
initr_reloc_global_data() always relocate gd->env_addr
unless we know this pointer is outside the initial binary.
To achieve this, the relocation is omitted if
CONFIG_ENV_ADDR is
On Thu, 2018-09-27 at 08:21 +0200, Marek Vasut wrote:
> On 09/27/2018 07:08 AM, Ang, Chee Hong wrote:
> >
> > On Wed, 2018-09-26 at 16:53 +0200, Marek Vasut wrote:
> > >
> > > On 09/26/2018 11:03 AM, chee.hong@intel.com wrote:
> > > >
> > > >
> > > > From: "Ang, Chee Hong"
> > > >
> > >
> -Original Message-
> From: York Sun
> Sent: Wednesday, September 26, 2018 11:24 PM
> To: Nipun Gupta ; u-boot@lists.denx.de
> Cc: albert.u.b...@aribaud.net; Prabhakar Kushwaha
> ; Ashish Kumar ;
> Priyanka Jain ; joe.hershber...@ni.com; Alison
> Wang ; shaohui@nxp.com
> Subject:
On Wed, 2018-09-26 at 16:53 +0200, Marek Vasut wrote:
> On 09/26/2018 11:03 AM, chee.hong@intel.com wrote:
> >
> > From: "Ang, Chee Hong"
> >
> > Add a generic mailbox API for FPGA reconfig status which can be
> > called by others. This new function accepts 2 different mailbox
> > commands:
At present we have no standard way of passing information from SPL to
U-Boot. Such information may be the size of DRAM banks or some information
about the reset state of the machine,for example.
This series first adds a bloblist, which allows a list of 'blobs' to be
created, each with a tag so
Xilinx DLC20 has I2C0 with EEPROM(1KB), UART1, GPIO, SD0 (EMMC 4GB),
USB0 device, ENET0, QSPI (16MB) and DDR(two of 256MB each).
Signed-off-by: Michal Simek
---
arch/arm/dts/Makefile | 1 +
arch/arm/dts/zynq-dlc20-rev1.0.dts | 98
Hi Mario,
Am Do., 27. Sep. 2018 um 11:48 Uhr schrieb Mario Six :
>
> The regmap functions currently assume that all register map accesses
> have a data width of 32 bits, but there are maps that have different
> widths.
>
> To rectify this, implement the regmap_raw_read and regmap_raw_write
>
Hi Tom,
please pull these changes to your tree.
Travis build looks good.
https://travis-ci.org/michalsimek/u-boot/builds/433924161
Both net patches are acked by Joe.
Thanks,
Michal
The following changes since commit 284b27cf81da10d55070a49ee8b739f71377a4fb:
Merge branch 'master' of
On Thu, Sep 27, 2018 at 5:48 PM Mario Six wrote:
>
> Add some overview documentation that explains the purpose and some of
> the features and limitations of the regmap interface.
>
> Signed-off-by: Mario Six
>
> ---
>
> v7 -> v8:
> New in v8
>
> ---
> include/regmap.h | 25
Hi Daniel,
First thanks for you prompt review, it is much appreciate. :)
This week I am at kernel recipes conference, so I won't be able to fully
address your comments but I will do it next week.
However, here are some answers:
On mer., sept. 26 2018, Daniel Schwierzeck
wrote:
> Hi
It would be convenient if one could use the regmap API in conjunction
with register maps defined as structs (i.e. structs that directly mirror
the memory layout of the registers in question). A similar approach was
planned with the regmap_write32/regmap_read32 macros, but was never
used.
Hence,
Add test for regmap_{set,get} functions.
Reviewed-by: Anatolij Gustschin
Reviewed-by: Simon Glass
Signed-off-by: Mario Six
---
v7 -> v8:
No changes
v6 -> v7:
No changes
v5 -> v6:
No changes
v4 -> v5:
No changes
v3 -> v4:
No changes
v2 -> v3:
New in v3
---
test/dm/regmap.c | 28
The regmap functions currently assume that all register map accesses
have a data width of 32 bits, but there are maps that have different
widths.
To rectify this, implement the regmap_raw_read and regmap_raw_write
functions from the Linux kernel API that specify the width of a desired
read or
The upcoming changes to the regmap interface will contain a proper check
for plausibility when reading/writing from/to a register map. To still
have the current tests pass, increase the size of the memory region for
the syscon0 device, since one of the tests reads and writes beyond this
range.
Add some overview documentation that explains the purpose and some of
the features and limitations of the regmap interface.
Signed-off-by: Mario Six
---
v7 -> v8:
New in v8
---
include/regmap.h | 25 +
1 file changed, 25 insertions(+)
diff --git a/include/regmap.h
This patch adds a driver for the bus associated with a IHS FPGA.
Reviewed-by: Simon Glass
Signed-off-by: Mario Six
---
v7 -> v8:
No changes
v6 -> v7:
No changes
v5 -> v6:
No changes
v4 -> v5:
No changes
v3 -> v4:
No changes
v2 -> v3:
* Fixed style violations
* Added bindings file
* Added
It is useful to be able to treat the different ranges of a regmap
separately to be able to use distinct offset for them, but this is
currently not implemented in the regmap API.
To preserve backwards compatibility, add regmap_read_range and
regmap_write_range functions that take an additional
Add a driver for gdsys IHS (Integrated Hardware Systems) FPGAs, which
supports initialization of the FPGA, as well as information gathering.
Reviewed-by: Simon Glass
Signed-off-by: Mario Six
---
v7 -> v8:
No changes
v6 -> v7:
No changes
v5 -> v6:
No changes
v4 -> v5:
No changes
v3 -> v4:
Makefile entries should be sorted.
Reviewed-by: Anatolij Gustschin
Reviewed-by: Simon Glass
Signed-off-by: Mario Six
Signed-off-by: Anatolij Gustschin
---
v7 -> v8:
No changes
v6 -> v7:
No changes
v5 -> v6:
No changes
v4 -> v5:
Drop re-ordered entries that are not in mainline
(e.g.
Document the regmap_alloc() function.
Reviewed-by: Anatolij Gustschin
Reviewed-by: Simon Glass
Signed-off-by: Mario Six
---
v7 -> v8:
No changes
v6 -> v7:
No changes
v5 -> v6:
No changes
v4 -> v5:
No changes
v3 -> v4:
No changes
v2 -> v3:
New in v3
---
drivers/core/regmap.c | 6 ++
MIPS is the only architecture currently supported by U-Boot that does
not implement any of the in/out register access functions.
To have a interface that is useable across architectures, add the
functions to the MIPS architecture (implemented using the __raw_write
and __raw_read functions).
The documentation in regmap.h is not in kernel-doc format. Correct this.
Reviewed-by: Anatolij Gustschin
Reviewed-by: Simon Glass
Signed-off-by: Mario Six
---
v7 -> v8:
No changes
v6 -> v7:
No changes
v5 -> v6:
No changes
v4 -> v5:
No changes
v3 -> v4:
No changes
v2 -> v3:
New in v3
Add some debug output in cases where the initialization of a regmap
fails.
Reviewed-by: Anatolij Gustschin
Reviewed-by: Simon Glass
Signed-off-by: Mario Six
---
v7 -> v8:
No changes
v6 -> v7:
No changes
v5 -> v6:
No changes
v4 -> v5:
No changes
v3 -> v4:
No changes
v2 -> v3:
New in v3
Both fdtdec_get_addr_size_fixed and of_address_to_resource can fail with
an error, which is not currently checked during regmap initialization.
Since the indentation depth is already quite deep, extract a new
'init_range' method to do the initialization.
Reviewed-by: Anatolij Gustschin
ofnode_read_simple_addr_cells may fail and return a negative error code.
Check for this when initializing regmaps.
Also check if both_len is zero, since this is perfectly possible, and
would lead to a division-by-zero further down the line.
Reviewed-by: Anatolij Gustschin
Reviewed-by: Simon
UBI should not mess with MTD partitions, now that the partitions are
handled in a clean way, clean the ubi command and avoid using this
uneeded extra-glue to reference the devices.
Signed-off-by: Miquel Raynal
Reviewed-by: Stefan Roese
Reviewed-by: Boris Brezillon
---
cmd/Kconfig | 2 ++
There should not be a 'nand' command, a 'sf' command and certainly not
a new 'spi-nand' command. Write a 'mtd' command instead to manage all
MTD devices/partitions at once. This should be the preferred way to
access any MTD device.
Signed-off-by: Miquel Raynal
Acked-by: Jagan Teki
Reviewed-by:
1 - 100 of 134 matches
Mail list logo
