From: Michal Simek <michal.simek@amd.com>
To: Simon Glass <sjg@chromium.org>
Cc: u-boot@lists.denx.de, git@xilinx.com,
Francesco Dolcini <francesco.dolcini@toradex.com>,
Heinrich Schuchardt <xypron.glpk@gmx.de>,
Martyn Welch <martyn.welch@collabora.com>,
Max Krummenacher <max.krummenacher@toradex.com>,
Peter Robinson <pbrobinson@gmail.com>,
Tejas Bhumkar <tejas.arvind.bhumkar@amd.com>,
Tom Rini <trini@konsulko.com>,
Venkatesh Yadav Abbarapu <venkatesh.abbarapu@amd.com>,
Ilias Apalodimas <ilias.apalodimas@linaro.org>
Subject: Re: [PATCH 0/3] lib: smbios: Extend driver with using sysinfo driver
Date: Fri, 7 Jun 2024 09:53:15 +0200 [thread overview]
Message-ID: <1cbaa06c-2f08-4d44-9829-e8c4b04a3f03@amd.com> (raw)
In-Reply-To: <CAC_iWjJzTrTSFNmnRcXH2JoPK5EB1bNgBzbHLvyEy0-JxQ-E2A@mail.gmail.com>
On 5/24/24 12:07, Ilias Apalodimas wrote:
> Hi Michal
>
>
> On Fri, 24 May 2024 at 12:45, Michal Simek <michal.simek@amd.com> wrote:
>>
>> Hi Ilias,
>>
>> On 4/26/24 15:38, Michal Simek wrote:
>>> Hi,
>>>
>>> currently only DT way is supported and it is added directly to lib/smbios.c
>>> but I think DT and env is only one way how information can be found that's
>>> why this series is improving handling with using sysinfo driver which can
>>> be platform specific.
>>> At the end of day DT should be taken from smbios.c and put to sysinfo DT
>>> driver instead of implementing it directly in this generic file.
>>>
>>> Thanks,
>>> Michal
>>>
>>>
>>> Michal Simek (3):
>>> xilinx: Enable SMBIOS command
>>> lib: smbios: Let detect the system via sysinfo
>>> lib: smbios: Detect system properties via SYSINFO IDs
>>>
>>> configs/xilinx_versal_net_virt_defconfig | 1 +
>>> configs/xilinx_versal_virt_defconfig | 1 +
>>> configs/xilinx_zynqmp_kria_defconfig | 1 +
>>> configs/xilinx_zynqmp_virt_defconfig | 1 +
>>> include/sysinfo.h | 9 +++++
>>> lib/smbios.c | 42 +++++++++++++++++++-----
>>> 6 files changed, 46 insertions(+), 9 deletions(-)
>>>
>>
>>
>> Any comment on this series?
>
> It's mostly Simon that created that sysinfo stuff, so I was expecting
> him to have a look.
> I can put in on my bucket list, but that's going to take some time
Simon: Any comment?
Thanks,
Michal
next prev parent reply other threads:[~2024-06-07 7:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-26 13:38 [PATCH 0/3] lib: smbios: Extend driver with using sysinfo driver Michal Simek
2024-04-26 13:38 ` [PATCH 1/3] xilinx: Enable SMBIOS command Michal Simek
2024-06-07 7:52 ` Michal Simek
2024-04-26 13:38 ` [PATCH 2/3] lib: smbios: Let detect the system via sysinfo Michal Simek
2024-06-10 15:03 ` Simon Glass
2024-04-26 13:38 ` [PATCH 3/3] lib: smbios: Detect system properties via SYSINFO IDs Michal Simek
2024-06-10 15:03 ` Simon Glass
2024-05-24 9:44 ` [PATCH 0/3] lib: smbios: Extend driver with using sysinfo driver Michal Simek
2024-05-24 10:07 ` Ilias Apalodimas
2024-06-07 7:53 ` Michal Simek [this message]
2024-06-10 15:03 ` Simon Glass
2024-06-20 8:51 ` Michal Simek
2024-06-20 19:57 ` Tom Rini
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=1cbaa06c-2f08-4d44-9829-e8c4b04a3f03@amd.com \
--to=michal.simek@amd.com \
--cc=francesco.dolcini@toradex.com \
--cc=git@xilinx.com \
--cc=ilias.apalodimas@linaro.org \
--cc=martyn.welch@collabora.com \
--cc=max.krummenacher@toradex.com \
--cc=pbrobinson@gmail.com \
--cc=sjg@chromium.org \
--cc=tejas.arvind.bhumkar@amd.com \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=venkatesh.abbarapu@amd.com \
--cc=xypron.glpk@gmx.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox