From: Michal Simek <monstr@monstr.eu>
To: u-boot@lists.denx.de
Subject: [PATCH 0/4] Add support for I2C Legacy/FRU decoding
Date: Tue, 27 Oct 2020 08:25:57 +0100 [thread overview]
Message-ID: <CAHTX3d+HeRXXX8xEcOJ+mE8JnVCH4cm8Venhcuse=FHX6FX6Wg@mail.gmail.com> (raw)
In-Reply-To: <cover.1603205426.git.michal.simek@xilinx.com>
?t 20. 10. 2020 v 16:50 odes?latel Michal Simek
<michal.simek@xilinx.com> napsal:
>
> Hi,
>
> the whole series add support for I2C based FRU eeprom board identification.
> EEPROMs are referenced by nvmem alias which was suggested by Rob Herring
> (dt maintainer). Previous code was using chosen xlnx,eeprom property.
> And because no platform is setting up nvmem alias the code is doing nothing
> on all boards.
>
> If you want to try it and test it just choose board and define nvmem
> aliases and you should see similar logs like this.
>
> zcu104 with legacy format and FRU on FMC
>
> U-Boot 2020.10-00835-g819dc03ff784 (Oct 20 2020 - 12:48:12 +0200)
>
> Model: ZynqMP ZCU104 RevC
> Board: Xilinx ZynqMP
> DRAM: 2 GiB
> PMUFW: v1.1
> Xilinx I2C Legacy format at nvmem0:
> Board name: zcu104
> Board rev: c
> Board SN: 895527361843-94820
> Ethernet mac: 00:0a:35:04:eb:93
> Xilinx I2C FRU format at nvmem1:
> Manufacturer Name: XILINX
> Product Name: XXX-XXX
> Serial No: 1231
> Part Number: dd
> File ID: U-Boot generator
> Revision Number: rev_A
> EL Level: EL2
> Chip ID: zu7e
> WDT: Started with servicing (60s timeout)
> NAND: 0 MiB
> MMC: mmc at ff170000: 0
> Loading Environment from FAT... *** Warning - bad CRC, using default environment
>
> In: serial at ff000000
> Out: serial at ff000000
> Err: serial at ff000000
> Bootmode: LVL_SHFT_SD_MODE1
> Reset reason: EXTERNAL
> Net:
> ZYNQ GEM: ff0e0000, mdio bus ff0e0000, phyaddr 12, interface rgmii-id
> eth0: ethernet at ff0e0000
> Hit any key to stop autoboot: 0
> ZynqMP>
>
> Based on https://lists.denx.de/pipermail/u-boot/2020-October/429382.html
>
> Thanks,
> Michal
>
>
> Michal Simek (3):
> xilinx: common: Add Makefile to common folder
> xilinx: cmd: Add basic fru format generator
> xilinx: board: Add FRU decoder support
>
> Siva Durga Prasad Paladugu (1):
> xilinx: cmd: Add support for FRU commands
>
> board/xilinx/Kconfig | 8 +
> board/xilinx/common/Makefile | 10 +
> board/xilinx/common/board.c | 83 +++++++-
> board/xilinx/common/fru.c | 91 ++++++++
> board/xilinx/common/fru.h | 83 ++++++++
> board/xilinx/common/fru_ops.c | 362 ++++++++++++++++++++++++++++++++
> board/xilinx/versal/Makefile | 1 -
> board/xilinx/zynq/Makefile | 1 -
> board/xilinx/zynqmp/MAINTAINERS | 1 +
> board/xilinx/zynqmp/Makefile | 1 -
> 10 files changed, 637 insertions(+), 4 deletions(-)
> create mode 100644 board/xilinx/common/Makefile
> create mode 100644 board/xilinx/common/fru.c
> create mode 100644 board/xilinx/common/fru.h
> create mode 100644 board/xilinx/common/fru_ops.c
>
> --
> 2.28.0
>
Applied.
M
--
Michal Simek, Ing. (M.Eng), OpenPGP -> KeyID: FE3D1F91
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel - Xilinx Microblaze
Maintainer of Linux kernel - Xilinx Zynq ARM and ZynqMP ARM64 SoCs
U-Boot custodian - Xilinx Microblaze/Zynq/ZynqMP/Versal SoCs
prev parent reply other threads:[~2020-10-27 7:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-20 14:50 [PATCH 0/4] Add support for I2C Legacy/FRU decoding Michal Simek
2020-10-20 14:50 ` [PATCH 1/4] xilinx: common: Add Makefile to common folder Michal Simek
2020-10-20 14:50 ` [PATCH 2/4] xilinx: cmd: Add support for FRU commands Michal Simek
2020-10-20 14:50 ` [PATCH 3/4] xilinx: cmd: Add basic fru format generator Michal Simek
2020-10-20 14:50 ` [PATCH 4/4] xilinx: board: Add FRU decoder support Michal Simek
2020-10-27 7:25 ` Michal Simek [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAHTX3d+HeRXXX8xEcOJ+mE8JnVCH4cm8Venhcuse=FHX6FX6Wg@mail.gmail.com' \
--to=monstr@monstr.eu \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.