On 3/24/22 14:54, Masahisa Kojima wrote:
This commit adds the UEFI related menu entries and
distro_boot entries into the bootmenu.
For UEFI, user can select which UEFI "Boot" option
to execute, call UEFI bootmgr and UEFI boot variable
maintenance menu. UEFI bootmgr entry is required to
corre
On 3/24/22 14:54, Masahisa Kojima wrote:
From: AKASHI Takahiro
Under the current implementation, booting from removable media using
a architecture-specific default image name, say BOOTAA64.EFI, is
supported only in distro_bootcmd script. See the commit 74522c898b35
("efi_loader: Add distro boot
On 3/24/22 14:54, Masahisa Kojima wrote:
The bootmenu enumerates the UEFI boot variable and distro boot
(boot_targets) for boot device selection.
Signed-off-by: Masahisa Kojima
---
Newly created in v4
doc/usage/bootmenu.rst | 65 ++
In origin/master t
On 3/24/22 14:54, Masahisa Kojima wrote:
This patch series adds the menu-driven boot device selection,
by extending the existing "bootmenu" to include UEFI and distro_boot
related entries, and supports menu-driven UEFI boot variable
maintenance.
This patch series also includes the removable medi
* add link to booti man-page
* correct link description for efidebug command
* correct punctuation
Signed-off-by: Heinrich Schuchardt
---
doc/usage/cmd/bootefi.rst | 9 +
1 file changed, 5 insertions(+), 4 deletions(-)
diff --git a/doc/usage/cmd/bootefi.rst b/doc/usage/cmd/bootefi.rst
i
From: qianfan Zhao
eth_device_priv maybe unaccessable after @stop handler due to eth device
is removed in @stop, touch it will trigger data abort.
Fix data abort bug when run dhcp or tftp command via usbnet.
Signed-off-by: qianfan Zhao
---
net/eth-uclass.c | 11 +--
1 file changed, 9
From: qianfan Zhao
tftp_handler do eth_halt when TFTP_ERROR, but eth_halt will remove eth
device if it is an usb network. usbeth's private data will be unaccessable
when usb_eth_free_pkt, touch it will trigger data abort.
Next is the console messages:
=> tftp xxx
...
Loading: *
TFTP error: 'ope
在 2022/4/2 3:26, Ramon Fried 写道:
On Mon, Mar 28, 2022 at 9:14 AM wrote:
From: qianfan Zhao
eth_device_priv maybe unaccessable after @stop handler due to eth device
is removed in @stop. Setting private data before @stop handler.
This also fix data abort bug when run dhcp or tftp command via
It is possible for power domain IDs to be great than 31. If this
happens, the PTCMD and PTSTAT registers must overflow into adjacent
corresponding PTCMD_H and PTSTAT_H registers for each. Update the driver
to account for this.
Signed-off-by: Dave Gerlach
---
drivers/power/domain/ti-power-domain.
On 4/1/22 23:28, Tim Harvey wrote:
On Fri, Apr 1, 2022 at 7:32 AM Marek Vasut wrote:
The i.MX8MP glue needs to be configured based on a couple of DT
properties, implement .glue_configure callback to parse those DT
properties and configure the glue accordingly.
Signed-off-by: Marek Vasut
Cc:
On Tue, Mar 22, 2022 at 04:59:35PM -0400, Sean Anderson wrote:
> This implements puts for sandbox. It is fairly straightforward, except
> that we break out the shared color printing functionality into its own
> function.
>
> Signed-off-by: Sean Anderson
> Reviewed-by: Simon Glass
This breaks t
Hi Sean
On Fri, Apr 1, 2022 at 8:53 PM Sean Anderson wrote:
>
>
>
> On 4/1/22 2:46 PM, Sean Anderson wrote:
> > Hi all,
> >
> > I don't understand how spl_nand_fit_read is supposed to work. This
> > function has been seemingly hacked together by multiple people over the
> > years, and it (presuma
On Fri, Apr 1, 2022 at 7:32 AM Marek Vasut wrote:
>
> The i.MX8MP glue needs to be configured based on a couple of DT
> properties, implement .glue_configure callback to parse those DT
> properties and configure the glue accordingly.
>
> Signed-off-by: Marek Vasut
> Cc: Angus Ainslie
> Cc: Bin M
On Thu, Mar 31, 2022 at 3:30 AM Marek Behún wrote:
>
> On Wed, 30 Mar 2022 08:46:06 -0700
> Tim Harvey wrote:
>
> > On Tue, Mar 29, 2022 at 4:22 PM Marek Behún wrote:
> > >
> > > On Tue, 29 Mar 2022 15:52:39 -0700
> > > Tim Harvey wrote:
> > >
> > > > Add a DSA driver for the MV88E61xx compatib
On Thu, Mar 31, 2022 at 2:50 PM Arjan Minzinga Zijlstra
wrote:
>
> Some globals where not properly initialized causing timeouts
> as data packets where not immediately acknowledged.
I don't see a scenario where these two variables will not be initialized.
Can you please elaborate ?
>
> Signed-off-
On Wed, Mar 30, 2022 at 1:52 AM Tim Harvey wrote:
>
> In order to ensure that a DSA driver probe gets called before
> dsa_ops->port_probe move the port_probe of the cpu_port to
> a post-probe function.
>
> Signed-off-by: Tim Harvey
> ---
> net/dsa-uclass.c | 14 +++---
> 1 file changed,
On Wed, Mar 30, 2022 at 1:52 AM Tim Harvey wrote:
>
> If a DM_MDIO driver is used we need to scan the subnodes as well.
>
> Signed-off-by: Tim Harvey
> Signed-off-by: Vladimir Oltean
> ---
> net/mdio-uclass.c | 4
> 1 file changed, 4 insertions(+)
>
> diff --git a/net/mdio-uclass.c b/net/m
On Tue, Mar 29, 2022 at 11:08 PM Marek Behún wrote:
>
> From: Marek Behún
>
> Hello,
>
> this is v3 of https://patchwork.ozlabs.org/project/uboot/list/?series=290889.
>
> Changes since v2:
> - added UT tests for ofnode_get_phy_node() and ofnode_get_phy_mode(), as
> requested by Simon
>
> Marek
On Mon, Mar 28, 2022 at 9:14 AM wrote:
>
> From: qianfan Zhao
>
> eth_device_priv maybe unaccessable after @stop handler due to eth device
> is removed in @stop. Setting private data before @stop handler.
>
> This also fix data abort bug when run dhcp or tftp command via usbnet.
>
> Signed-off-by
On Mon, Mar 28, 2022 at 12:58 PM wrote:
>
> From: qianfan Zhao
>
> tftp_handler do eth_halt when TFTP_ERROR, but eth_halt will remove eth
> device if it is an usb network. usbeth's private data will be unaccessable
> when usb_eth_free_pkt, touch it will trigger data abort.
>
> Next is the console
On Fri, Apr 1, 2022 at 6:32 PM Ramon Fried wrote:
>
> On Sat, Mar 19, 2022 at 4:02 PM wrote:
> >
> > From: Haolin Li
> >
> > The type of the return value of phy_read() and phy_read_mmd() is int.
> > Change the variable to not be unsigned so that we not get into an
> > unsigned compared against 0
The capsule update code has been modified for getting the image GUID
values from the platform code. With this, each image now has a unique
GUID value. With this change, there is no longer a need for defining
GUIDs for FIT and raw images. Remove these GUID values.
Signed-off-by: Sughosh Ganu
Revie
Update the capsule update functionality related documentation to
refect the additional definitions that need to be made per platform
for supporting the capsule update feature.
Signed-off-by: Sughosh Ganu
---
Changes since V4:
* Change the description of the platform data based on the changes
While building a capsule, the GUID value of that specific image is to
be passed through the --guid command option to the mkeficapsule
tool. This renders the EFI_FIRMWARE_IMAGE_TYPE_UBOOT_FIT_GUID and
EFI_FIRMWARE_IMAGE_TYPE_UBOOT_RAW_GUID values superfluous. Remove the
--raw and --fit command line
The current UEFI capsule updation code uses two GUID values, one for
FIT images, and one for raw images across platforms. This logic is
being changed to have GUID values per image, per platform. Change the
tests for the capsule update code to reflect this change. The GUID
values now used are the on
The current capsule update code compares the image GUID value in the
capsule header with the image GUID value obtained from the
GetImageInfo function of the Firmware Management Protocol(FMP). This
comparison is done to ascertain if the FMP's SetImage function can be
called for the update. Make this
Currently, there are a bunch of boards which enable the UEFI capsule
update feature. The actual update of the firmware images is done
through the dfu framework which uses the dfu_alt_info environment
variable for getting information on the update, like device, partition
number/address etc. The dfu
Currently, the image descriptor array that has been passed to the
GetImageInfo function of the Firmware Management Protocol(FMP) gets
populated through the data stored with the dfu framework. The
dfu data is not restricted to contain information only of the images
updatable through the capsule upda
Add a structure which defines the information that is needed for
executing capsule updates on a platform. Some information in the
structure is used for making the update process more robust while some
information is used for fixing some issues. Initialise this structure
in the board file, and use t
This series is cleaning up the usage of the image GUIDs that are used
in capsule update and the EFI System Resource Table(ESRT). There are
some other enhancements being made to the capsule update code to make
it more robust.
Firstly, an overview of the fixes being made.
Currently, there are two
On Fri, Apr 01, 2022 at 10:53:14AM -0700, Tim Harvey wrote:
> Can you review 'net: add MV88E61xx DSA driver' for me?
I will. I've been thinking all day today about what to say that isn't
stupid. Give me some time and I'll provide feedback.
On Thu, Mar 3, 2022 at 9:52 AM Ramon Fried wrote:
>
> On Wed, Feb 23, 2022 at 3:21 PM Vladimir Oltean
> wrote:
> >
> > A DM_ETH driver may use phy_connect() towards a PHY address on an MDIO
> > bus which is not specified in the device tree, as evidenced by:
> >
> > pfe_eth_probe
> > -> pfe_phy_c
On Thu, Mar 3, 2022 at 9:53 AM Ramon Fried wrote:
>
> On Wed, Feb 23, 2022 at 3:21 PM Vladimir Oltean
> wrote:
> >
> > A DM_ETH driver may use phy_connect() towards a PHY address on an MDIO
> > bus which is not specified in the device tree, as evidenced by:
> >
> > pfe_eth_probe
> > -> pfe_phy_c
This converts the spi load method to use spl_load. As a consequence, it
also adds support for LOAD_FIT_FULL.
Signed-off-by: Sean Anderson
---
common/spl/spl_spi.c | 48 +++-
1 file changed, 7 insertions(+), 41 deletions(-)
diff --git a/common/spl/spl_spi
This converts the net load method to use spl_load. As a result, it also
adds support for LOAD_FIT_FULL and IMX images.
Signed-off-by: Sean Anderson
---
common/spl/spl_net.c | 24 +---
1 file changed, 5 insertions(+), 19 deletions(-)
diff --git a/common/spl/spl_net.c b/commo
This converts the nor load method to use spl_load. As a result it also
adds support LOAD_FIT_FULL.
Signed-off-by: Sean Anderson
---
common/spl/spl_nor.c | 35 ++-
1 file changed, 6 insertions(+), 29 deletions(-)
diff --git a/common/spl/spl_nor.c b/common/spl/spl
This converts the mmc loader to spl_load. Legacy images are handled by
spl_load (via spl_parse_image_header), so mmc_load_legacy can be
omitted.
Signed-off-by: Sean Anderson
---
common/spl/spl_mmc.c | 73
1 file changed, 6 insertions(+), 67 deletions
This converts the ext load method to use spl_load. As a consequence, it
also adds support for FIT and IMX images.
Signed-off-by: Sean Anderson
---
common/spl/spl_ext.c | 24 +---
1 file changed, 17 insertions(+), 7 deletions(-)
diff --git a/common/spl/spl_ext.c b/common/spl
This converts the fat loader to use spl_load.
Signed-off-by: Sean Anderson
---
common/spl/spl_fat.c | 36 ++--
1 file changed, 6 insertions(+), 30 deletions(-)
diff --git a/common/spl/spl_fat.c b/common/spl/spl_fat.c
index 5b270541fc..c092eb3481 100644
--- a/com
This series adds support for loading all image types (Legacy, FIT (with
and without LOAD_FIT_FULL), and i.MX) to the MMC, SPI, NOR, NET, FAT,
and EXT load methods. It does this by introducing a helper function
which handles the minutiae of invoking the proper parsing function, and
reading the rest
Implementers of SPL_LOAD_IMAGE_METHOD have to correctly determine what
type of image is being loaded and then call the appropriate image load
function correctly. This is tricky, because some image load functions
expect the whole image to already be loaded (CONFIG_SPL_LOAD_FIT_FULL),
some will load
On 4/1/22 2:46 PM, Sean Anderson wrote:
> Hi all,
>
> I don't understand how spl_nand_fit_read is supposed to work. This
> function has been seemingly hacked together by multiple people over the
> years, and it (presumably) (somehow) works despite mass confusion of
> units. I tried to do some r
Hi all,
I don't understand how spl_nand_fit_read is supposed to work. This
function has been seemingly hacked together by multiple people over the
years, and it (presumably) (somehow) works despite mass confusion of
units. I tried to do some refactoring, but the contradictions make it
very difficu
On Thu, Mar 24, 2022 at 05:17:56PM -0400, Tom Rini wrote:
> The value CONFIG_DB_784MP_GP is only used in the DDR code to refer to
> CONFIG_TARGET_DB_MV784MP_GP so just use that second value directly.
>
> Cc: Stefan Roese
> Signed-off-by: Tom Rini
> Reviewed-by: Stefan Roese
For the whole of t
On Wed, Mar 23, 2022 at 05:19:48PM -0400, Tom Rini wrote:
> This converts the following to Kconfig:
>CONFIG_CF_DSPI
>
> Signed-off-by: Tom Rini
For the whole of the series, applied to u-boot/next, thanks!
--
Tom
signature.asc
Description: PGP signature
On Mon, Mar 21, 2022 at 09:33:27PM -0400, Tom Rini wrote:
> At this point DM and OF_CONTROL are used to configure how the USB ports
> are enabled, with the exception of in SPL and no SPL_OF_CONTROL. Remove
> a bunch of now unused logic to simplify the code.
>
> Signed-off-by: Tom Rini
For the
On Thu, Mar 31, 2022 at 12:36 PM Vladimir Oltean
wrote:
>
> On Thu, Mar 31, 2022 at 10:48:55AM -0700, Tim Harvey wrote:
> > > On which branch does this apply? The context above
> > > fecmxc_read_rom_hwaddr()
> > > is different in the branches I've checked:
> > > https://source.denx.de/u-boot/u-bo
Hi Michal,
On 4/1/22 6:13 AM, Michal Simek wrote:
> Based on discussion at
> https://lore.kernel.org/r/20200318125003.ga2727...@kroah.com we got
> recommendation to use explicit values for all enum values.
> The patch is following this recommendation.
To comment on Greg's comment
> Yes, but is t
On Wed, Mar 30, 2022 at 11:08 PM Tom Rini wrote:
>
> This option is only enabled for CI_UDC and !TEGRA20, so implement it as
> such in Kconfig directly.
>
> Signed-off-by: Tom Rini
Reviewed-by: Peter Robinson
Tested-by: Peter Robinson
> ---
> arch/arm/mach-tegra/Kconfig | 4 ++
On Thu, Mar 24, 2022 at 11:58 AM Robert Marko wrote:
>
> Add support for handling SFP TX disable for MVNETA in the same fashion as
> to what MVPP2 is doing in order to enable using SFP-s.
>
> This allows using ethernet on SFP only boards.
>
> Signed-off-by: Robert Marko
> ---
> Changes in v3:
> *
On Sat, Mar 19, 2022 at 4:02 PM wrote:
>
> From: Haolin Li
>
> The type of the return value of phy_read() and phy_read_mmd() is int.
> Change the variable to not be unsigned so that we not get into an
> unsigned compared against 0.
>
> Signed-off-by: Haolin Li
> ---
> drivers/net/phy/dp83867.c
Add DT bindings for a subset of GPCv2 which handles USB and PCIe PDs,
HSIOMIX PD controller and missing USB PD properties. This is required
to bring up the DWC3 USB controller up.
This is based on linux next and patches which are still pending
review, but which are likely going to be part of Linux
The i.MX8MP glue needs to be configured based on a couple of DT
properties, implement .glue_configure callback to parse those DT
properties and configure the glue accordingly.
Signed-off-by: Marek Vasut
Cc: Angus Ainslie
Cc: Bin Meng
Cc: Fabio Estevam
Cc: Kunihiko Hayashi
Cc: Michal Simek
Cc
Rename the select_dr_mode callback to glue_configure, the callback is
used for more than enforcing controller mode even on the TI chips, so
change the name to a more generic one. No functional change.
Signed-off-by: Marek Vasut
Cc: Angus Ainslie
Cc: Bin Meng
Cc: Fabio Estevam
Cc: Kunihiko Haya
Add clock tables required to bring up DWC3 USB, USB PHY and HSIOMIX domain.
Signed-off-by: Marek Vasut
Cc: Fabio Estevam
Cc: Peng Fan
Cc: Stefano Babic
Cc: Ye Li
---
V2: - Get and probe 24m clock without registering it again (suggested by Ye)
- Add 32k clock the same way for usb_root_clk
On Thu, Sep 23, 2021 at 09:55:21AM +0200, Francesco Dolcini wrote:
> colibri-imx6ull ethernet device is fec2, while the optional secondary
> ethernet is fec1, update the ethernet aliases in the .dts file so that
> ethaddr is set to fec2 and eth1addr to fec1.
>
> Without this change the ethernet i
Explicit make commands were earlier used to generate tispl.bin image,
now it is replaced using binman.
Binman picks up and packages entries according to the description of
entries given in the binman node in the device tree. The make commands
that were earlier responsible for generating tispl.bin
K3 devices introduces the concept of centralized power, resource and
security management to System Firmware. This is to overcome challenges
by the traditional approach that implements system control functions on
each of the processing units.
The software interface for System Firmware is split into
By providing entries in the binman node of the device tree, binman will
be able to find and package board config binary artifacts generated by
TIBoardConfig with sysfw.bin and generate the final image sysfw.itb.
j721e-r5-binman.dtsi has been introduced for R5 specific binman node. It
can be then b
For devices that require sysfw.itb, board config binary artifacts must
be populated in the R5 output directory. These can be used by binman to
package sysfw.itb.
config.mk for mach-k3 updated to generate the required binaries using
tibcfg_gen.py.
K3_CERT_GEN has been introduced in config.mk to re
Board config file must be provided in board/ti/ in YAML.
These can then be consumed for generation of binaries to package system
firmware. Added YAML config for J721E EVM in particular.
It is to be noted that the bootflow followed by J721E requires
tiboot3.bin, TIFS and board config binaries to be
Schema file in YAML must be provided in board/ti/common for validating
input config files and packaging system firmware. The schema includes
entries for rm-cfg, board-cfg, pm-cfg and sec-cfg.
Signed-off-by: Tarun Sahu
[n-fran...@ti.com: cleaned up config and schema files]
Signed-off-by: Neha Malc
For K3 devices that require a sysfw image, add entry for SYSFW. It can
contain system firmware image that can be packaged into sysfw.itb by
binman. The method ReadBlobContents in sysfw.py runs the TI K3
certificate generation script to create the signed sysfw image that can
be used for packaging by
For validating config files and generating binary config artifacts, here
board specific config class is added.
Add function cfgBinaryGen() in tibcfg_gen.py. It uses TIBoardConfig
class to load given schema and config files in YAML, validate them and
generate binaries.
Signed-off-by: Tarun Sahu
[
Devices that belong to the K3 architecture require SYSFW which is a FIT
image consisting of a signed system firmware image and board config
binaries.
Board config binaries are needed to bring up SYSFW during U-Boot SPL
startup. The board config data is given in YAML as input. These board
configs c
Add trivial driver for i.MX8MP HSIOMIX handling. This is responsible
for enabling the GPCv2 power domains and clock for USB 3.0 and PCIe
in the correct order. Currently supported is the USB 3.0 part which
can be tested, PCIe support should be easy to add.
Signed-off-by: Marek Vasut
Cc: Fabio Este
On Fri, Apr 01, 2022 at 10:04:04AM -0400, Tom Rini wrote:
> On Fri, Apr 01, 2022 at 02:01:25PM +, Marcel Ziswiler wrote:
> > On Fri, 2022-04-01 at 09:43 -0400, Tom Rini wrote:
> > > On Fri, Apr 01, 2022 at 12:57:40PM +, Marcel Ziswiler wrote:
> > >
> > > > May I inquire about the status of
On Fri, Apr 01, 2022 at 02:01:25PM +, Marcel Ziswiler wrote:
> On Fri, 2022-04-01 at 09:43 -0400, Tom Rini wrote:
> > On Fri, Apr 01, 2022 at 12:57:40PM +, Marcel Ziswiler wrote:
> >
> > > May I inquire about the status of this one? Thanks!
> >
> > Should I take it for this release?
>
>
On Fri, Apr 01, 2022 at 02:01:25PM +, Marcel Ziswiler wrote:
> On Fri, 2022-04-01 at 09:43 -0400, Tom Rini wrote:
> > On Fri, Apr 01, 2022 at 12:57:40PM +, Marcel Ziswiler wrote:
> >
> > > May I inquire about the status of this one? Thanks!
> >
> > Should I take it for this release?
>
>
On Fri, 2022-04-01 at 09:43 -0400, Tom Rini wrote:
> On Fri, Apr 01, 2022 at 12:57:40PM +, Marcel Ziswiler wrote:
>
> > May I inquire about the status of this one? Thanks!
>
> Should I take it for this release?
Yes, please. Thanks!
> > On Fri, 2022-02-04 at 14:55 -0300, Fabio Estevam wrote:
On Fri, Apr 01, 2022 at 03:21:14AM +0200, Heinrich Schuchardt wrote:
> Dear Tom,
>
> The following changes since commit 64b78f5721e65e96ea5a3d100d46b2e6fda722df:
>
> Merge branch '2022-03-31-critical-fixes' (2022-03-31 08:28:43 -0400)
>
> are available in the Git repository at:
>
> https:/
On Fri, Apr 01, 2022 at 12:57:40PM +, Marcel Ziswiler wrote:
> May I inquire about the status of this one? Thanks!
Should I take it for this release?
>
> On Fri, 2022-02-04 at 14:55 -0300, Fabio Estevam wrote:
> > On Thu, Sep 23, 2021 at 4:55 AM Francesco Dolcini
> > wrote:
> > >
> > > co
Before relocating to SDRAM, the ECC is initialized by clearing the
whole SDRAM. In order to speed this up, dcache_enable is used (see
sdram_init_ecc_bits).
Since commit 503eea451903 ("arm: cp15: update DACR value to activate
access control"), this no longer works, because running code in OCRAM
wit
Add board directory for Google Chameleon V3 board
Signed-off-by: Paweł Anikiel
---
board/google/chameleonv3/Makefile | 5 +++
board/google/chameleonv3/board.c | 27 ++
board/google/chameleonv3/fpga.its | 28 ++
board/google/chameleonv3/fpga_ea
For some reason, on the Mercury+ AA1 module, calling
fpgamgr_wait_early_user_mode immediately after writing the peripheral
bitstream leaves the fpga in a broken state (ddr calibration hangs).
Adding a delay before the first sync word is written seems to fix this.
Inspecting the fpgamgr registers be
Using udelay while the clocks aren't fully configured causes the timer
system to save the wrong clock rate. Use sdelay and wait_on_value
instead (the values used in these functions were found experimentally).
Signed-off-by: Paweł Anikiel
---
arch/arm/mach-socfpga/clock_manager.c |
Apply some optimizations to speed up bitstream loading
(both for full and split periph/core bitstreams):
* Change the size of the first fs read, so that all the subsequent
reads are aligned to a specific value (called MAX_FIRST_LOAD_SIZE).
This value was chosen so that in subsequent reads t
Add defconfig and Kconfig files for Google Chameleon V3 board
Signed-off-by: Paweł Anikiel
---
arch/arm/mach-socfpga/Kconfig | 15
configs/socfpga_chameleonv3_defconfig | 29
include/configs/socfpga_chameleonv3.h | 49 +++
3 files changed
This driver is a child of the rstmgr driver, both of which share the
same devicetree node. As a result, passing the child's udevice pointer
to dev_read_addr_ptr results in a failure of reading the #address-cells
property. Use the parent udevice pointer instead.
Signed-off-by: Paweł Anikiel
---
d
>From the ATSHA204A datasheet (document DS40002025A):
Wake: If SDA is held low for a period greater than tWLO, the device
exits low-power mode and, after a delay of tWHI, is ready to receive
I2C commands.
tWHI value can be found in table 7-2.
Signed-off-by: Paweł Anikiel
---
drivers/misc/atsha
Add devicetree for Google Chameleon V3 board
Signed-off-by: Paweł Anikiel
---
arch/arm/dts/Makefile | 2 ++
arch/arm/dts/socfpga_chameleonv3.dtsi | 21 +
arch/arm/dts/socfpga_chameleonv3_270_3.dts | 9 +
arch/arm/dts/socfpga_chameleonv3_480
Add handoff headers for the Google Chameleonv3 variants: 480-2 and
270-3. Both files were generated using qts-filter-a10.sh.
Signed-off-by: Paweł Anikiel
---
.../dts/socfpga_chameleonv3_270_3_handoff.h | 305 ++
.../dts/socfpga_chameleonv3_480_2_handoff.h | 305 ++
Device tree header for Mercury+ AA1 module
Signed-off-by: Paweł Anikiel
---
arch/arm/dts/socfpga_mercury_aa1.dtsi | 95 +++
1 file changed, 95 insertions(+)
create mode 100644 arch/arm/dts/socfpga_mercury_aa1.dtsi
diff --git a/arch/arm/dts/socfpga_mercury_aa1.dtsi
b/ar
The Google Chameleon V3 is a board made for testing both video and audio
interfaces of external devices. It has a connector compatible with the
Mercury+ AA1 module, which itself contains an Arria 10 SoCFPGA. The AA1
module comes in a few different configurations, the Chameleon V3 supports
ME-AA1-27
May I inquire about the status of this one? Thanks!
On Fri, 2022-02-04 at 14:55 -0300, Fabio Estevam wrote:
> On Thu, Sep 23, 2021 at 4:55 AM Francesco Dolcini
> wrote:
> >
> > colibri-imx6ull ethernet device is fec2, while the optional secondary
> > ethernet is fec1, update the ethernet aliases
Just noticed this having been only a private discussion.
CCing mailing list as well.
Forwarded Message
From: Tom Rini
To: Marcel Ziswiler
Cc: ma...@denx.de , tsi-chung.l...@nxp.com
, stel...@popies.net
, ezequ...@collabora.com ,
we...@corscience.de
Subject: Re: U-Boot and D
On 4/1/22 11:59, Jim Liu wrote:
Add watchdog controller driver for NPCM7xx/npcm8xx
the wdt design of npcm750 and npcm845 is the same.
so the driver can work on npcm750 and npcm845.
about npcm845 wdt dtsi i will followed kernel dts name
to use nuvoton,npcm750-wdt.
Signed-off-by: Jim Liu
Reviewe
Based on discussion at
https://lore.kernel.org/r/20200318125003.ga2727...@kroah.com we got
recommendation to use explicit values for all enum values.
The patch is following this recommendation.
The same change was also done by commit 31431dd466e7 ("firmware: xilinx:
Use explicit values for all enu
Add watchdog controller driver for NPCM7xx/npcm8xx
the wdt design of npcm750 and npcm845 is the same.
so the driver can work on npcm750 and npcm845.
about npcm845 wdt dtsi i will followed kernel dts name
to use nuvoton,npcm750-wdt.
Signed-off-by: Jim Liu
Reviewed-by: Stefan Roese
Reviewed-by:
Hi Sughosh
On Fri, 1 Apr 2022 at 09:58, Sughosh Ganu wrote:
>
> hi Ilias,
>
> On Fri, 1 Apr 2022 at 01:05, Ilias Apalodimas
> wrote:
> >
> > Hi Sughosh,
> >
> > Some nots below
> >
> > On Thu, Mar 31, 2022 at 06:57:46PM +0530, Sughosh Ganu wrote:
> > > Currently, there are a bunch of boards whic
There is not covered dependency on DWC3.
Signed-off-by: Michal Simek
---
drivers/usb/host/Kconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/usb/host/Kconfig b/drivers/usb/host/Kconfig
index 8f77412cc71b..48cbed15e104 100644
--- a/drivers/usb/host/Kconfig
+++ b/drivers/usb/host
On Tue, Mar 22, 2022 at 4:26 PM Luca Ellero
wrote:
>
> From: Luca Ellero
>
> Take as reference Linux kernel code:
> drivers/mtd/devices/mtd_dataflash.c
Linux commit id?
On Tue, Mar 15, 2022 at 3:03 PM wrote:
>
> From: "Lokanathan, Raaj"
>
> Add support for reading data/images from this ISSI QSPI flash.
Look like the patch is doing quad enable for ISSI but the commit head
and body seem misleading or confusing. Can you elaborate on the same?
Jagan.
93 matches
Mail list logo
