From: Michal Simek <monstr@monstr.eu>
To: Victor Lim <vlim@gigadevice.com>, u-boot@lists.denx.de
Cc: vigneshr@ti.com, jagan@amarulasolutions.com,
michal.simek@xilinx.com, vikhyat.goyal@amd.com,
ashok.reddy.soma@amd.com
Subject: Re: [PATCH 0/4] Enable gigadevice and add new part #s
Date: Tue, 3 Jan 2023 12:02:46 +0100 [thread overview]
Message-ID: <3d2a5e8b-0c35-b516-374c-61aabb326f5a@monstr.eu> (raw)
In-Reply-To: <20221219224818.6801-1-vlim@gigadevice.com>
On 12/19/22 23:48, Victor Lim wrote:
> Enabling gigadevice part #s.
> These are the part #s added,
> gd25b256: 3V QSPI, QE=1, 256Mbit
> gd25b512: 3V QSPI, QE=1, 512Mbit
> gd55b01g: 3V QSPI, QE=1, 1Gbit
> gd55b02g: 3V QSPI, QE=1, 2Gbit
> gd25f64: 3V QSPI, QE=1, 64Mbit, high performance
> gd25f128: 3V QSPI, QE=1, 128Mbit, high performance
> gd25f256: 3V QSPI, QE=1, 256Mbit, high performance
> gd55f512: 3V QSPI, QE=1, 512Mbit, high performance
> gd25t512: 3V QSPI, 512Mbit, ultra high performance
> gd55t01g: 3V QSPI, 1Gbit, ultra high performance
> gd55t02g: 3V QSPI, 2Gbit, ultra high performance
> gd25x512: 3V OSPI, 512Mbit, ultra high performance
> gd55x01g: 3V OSPI, 1Gbit, ultra high performance
> gd55x02g: 3V OSPI, 2Gbit, ultra high performance
> gd25lb256: 1.8V QSPI, QE=1, 256Mbit
> gd25lb512: 1.8V QSPI, QE=1, 512Mbit
> gd55lb01g: 1.8V QSPI, QE=1, 1Gbit
> gd55lb02g: 1.8V QSPI, QE=1, 2Gbit
> gd25lf64: 1.8V QSPI, QE=1, 64Mbit, high performance
> gd25lf128: 1.8V QSPI, QE=1, 128Mbit, high performance
> gd25lf256: 1.8V QSPI, QE=1, 256Mbit, high performance
> gd55lf512: 1.8V QSPI, QE=1, 512Mbit, high performance
> gd25lt512: 1.8V QSPI, 512Mbit, ultra high performance
> gd55lt01g: 1.8V QSPI, 1Gbit, ultra high performance
> gd55lt02g: 1.8V QSPI, 2Gbit, ultra high performance
> gd25lx512: 1.8V OSPI, 512Mbit, ultra high performance
> gd55lx01g: 1.8V OSPI, 1Gbit, ultra high performance
> gd55lx02g: 1.8V OSPI, 2Gbit, ultra high performance
>
> This is the link to the datasheet.
> https://www.gigadevice.com/products/memory/flash/spi-nor/
>
>> Victor Lim (4):
> xilinx: zynq: Enable gigadevice
> arm64: zynqmp: Enable gigadevice
> xilinx: versal: Enable gigadevice parts
> mtd: spi-nor-ids: add gigadevice part #
>
> configs/xilinx_versal_mini_qspi_defconfig | 1 +
> configs/xilinx_zynq_virt_defconfig | 1 +
> configs/xilinx_zynqmp_mini_qspi_defconfig | 1 +
> configs/xilinx_zynqmp_virt_defconfig | 1 +
> configs/zynq_cse_qspi_defconfig | 1 +
> drivers/mtd/spi/spi-nor-ids.c | 68 +++++++++++++++++++++++
> 6 files changed, 73 insertions(+)
>
First of all this should be v3 series.
Second. When I run this
for i in `ls configs/xilinx_*`; do NAME=`basename $i`; echo $NAME; make $NAME;
make savedefconfig; cp defconfig $i; done
I see that locations your added entries are not correct.
Third b4 am -g is showing that base is not upstream version.
Please use next branch as base.
Definitely this series is better then previous one.
Thanks,
Michal
--
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/Versal ARM64 SoCs
U-Boot custodian - Xilinx Microblaze/Zynq/ZynqMP/Versal/Versal NET SoCs
next prev parent reply other threads:[~2023-01-03 11:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-19 22:48 [PATCH 0/4] Enable gigadevice and add new part #s Victor Lim
2022-12-19 22:48 ` [PATCH 1/4] xilinx: zynq: Enable gigadevice Victor Lim
2022-12-19 22:48 ` [PATCH 2/4] arm64: zynqmp: " Victor Lim
2022-12-19 22:48 ` [PATCH 3/4] xilinx: versal: Enable gigadevice parts Victor Lim
2022-12-19 22:48 ` [PATCH 4/4] mtd: spi-nor-ids: add gigadevice part # Victor Lim
2023-01-03 11:02 ` Michal Simek [this message]
2023-01-04 18:50 ` [PATCH 0/4] Enable gigadevice and add new part #s Vlim
2023-01-05 7:25 ` Michal Simek
2023-01-05 19:47 ` Vlim
2023-01-06 7:14 ` Michal Simek
2023-01-06 19:53 ` Vlim
2023-01-09 7:59 ` Michal Simek
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=3d2a5e8b-0c35-b516-374c-61aabb326f5a@monstr.eu \
--to=monstr@monstr.eu \
--cc=ashok.reddy.soma@amd.com \
--cc=jagan@amarulasolutions.com \
--cc=michal.simek@xilinx.com \
--cc=u-boot@lists.denx.de \
--cc=vigneshr@ti.com \
--cc=vikhyat.goyal@amd.com \
--cc=vlim@gigadevice.com \
/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.