From: Michal Simek <michal.simek@amd.com>
To: Stefan Herbrechtsmeier
<stefan.herbrechtsmeier-oss@weidmueller.com>,
<u-boot@lists.denx.de>
Cc: Stefan Herbrechtsmeier <stefan.herbrechtsmeier@weidmueller.com>
Subject: Re: [PATCH 10/10] xilinx: zynqmp: Support vendor specific board_init
Date: Mon, 20 Jun 2022 08:53:49 +0200 [thread overview]
Message-ID: <531b0b77-5861-4938-a754-71e3e2172903@amd.com> (raw)
In-Reply-To: <2a4a01ae-4828-2187-91fb-aa165000567d@weidmueller.com>
On 6/20/22 08:48, Stefan Herbrechtsmeier wrote:
> Am 16.06.2022 um 17:12 schrieb Michal Simek:
>>
>>
>> On 6/8/22 18:20, Stefan Herbrechtsmeier wrote:
>>> [CAUTION: External Email]
>>>
>>> From: Stefan Herbrechtsmeier <stefan.herbrechtsmeier@weidmueller.com>
>>>
>>> Add a board_init_xilinx function to allow foreign vendors to reuse the
>>> xilinx zynqmp board code and add addition code to the board_init
>>> function.
>>
>> Do you plan to add support for that board who will be using it?
>
> Yes. You could drop the patch for now but it will be good to know if this is the
> right direction to reuse common code from the xilinx board files.
Hard to say without seeing what others need to do at this stage.
I am not saying it is bad directly but question I have is what you have there
that you need it. Maybe this is something what others want to use too and we can
integrated it directly to common xilinx files.
Thanks,
Michal
next prev parent reply other threads:[~2022-06-20 6:54 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-08 16:20 [PATCH 00/10] xilinx: zynqmp: Support foreign vendor boards Stefan Herbrechtsmeier
2022-06-08 16:20 ` [PATCH 01/10] firmware: firmware-zynqmp: Check if rx channel dev pointer is valid Stefan Herbrechtsmeier
2022-06-08 16:20 ` [PATCH 02/10] firmware: firmware-zynqmp: Probe driver before use Stefan Herbrechtsmeier
2022-06-16 14:22 ` Michal Simek
2022-06-20 6:40 ` Stefan Herbrechtsmeier
2022-06-20 6:51 ` Michal Simek
2022-06-20 9:33 ` Stefan Herbrechtsmeier
2022-06-08 16:20 ` [PATCH 03/10] soc: xilinx: zynqmp: Add machine identification support Stefan Herbrechtsmeier
2022-06-17 10:41 ` Michal Simek
2022-06-20 9:16 ` Stefan Herbrechtsmeier
2022-06-08 16:20 ` [PATCH 04/10] xilinx: zynqmp: Use soc machine function to get silicon idcode name Stefan Herbrechtsmeier
2022-06-17 10:41 ` Michal Simek
2022-06-08 16:20 ` [PATCH 05/10] xilinx: cpuinfo: Print soc machine Stefan Herbrechtsmeier
2022-06-08 16:20 ` [PATCH 06/10] xilinx: common: Separate display cpu info function Stefan Herbrechtsmeier
2022-06-08 16:20 ` [PATCH 07/10] xilinx: zynqmp: make spi flash support optional Stefan Herbrechtsmeier
2022-06-08 16:20 ` [PATCH 08/10] tools: zynqmp_psu_init_minimize: Remove low level uart settings Stefan Herbrechtsmeier
2022-06-08 16:20 ` [PATCH 09/10] tools: zynqmp_psu_init_minimize: Add serdes_illcalib forward declaration Stefan Herbrechtsmeier
2022-06-16 15:13 ` Michal Simek
2022-06-20 7:07 ` Stefan Herbrechtsmeier
2022-06-20 7:18 ` Michal Simek
2022-06-20 13:38 ` Stefan Herbrechtsmeier
2022-06-20 13:53 ` Michal Simek
2022-06-08 16:20 ` [PATCH 10/10] xilinx: zynqmp: Support vendor specific board_init Stefan Herbrechtsmeier
2022-06-16 15:12 ` Michal Simek
2022-06-20 6:48 ` Stefan Herbrechtsmeier
2022-06-20 6:53 ` Michal Simek [this message]
2022-06-20 9:36 ` Stefan Herbrechtsmeier
2022-06-17 11:06 ` [PATCH 00/10] xilinx: zynqmp: Support foreign vendor boards 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=531b0b77-5861-4938-a754-71e3e2172903@amd.com \
--to=michal.simek@amd.com \
--cc=stefan.herbrechtsmeier-oss@weidmueller.com \
--cc=stefan.herbrechtsmeier@weidmueller.com \
--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.