public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jean Delvare <jdelvare@suse.de>
To: Tiezhu Yang <yangtiezhu@loongson.cn>
Cc: Paul Burton <paulburton@kernel.org>,
	Ralf Baechle <ralf@linux-mips.org>,
	Huacai Chen <chenhc@lemote.com>,
	Xuefeng Li <lixuefeng@loongson.cn>, <linux-mips@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>,
	Yinglu Yang <yangyinglu@loongson.cn>,
	Jiaxun Yang <jiaxun.yang@flygoat.com>
Subject: Re: [PATCH v2,RESEND] MIPS: Scan the DMI system information
Date: Mon, 3 Feb 2020 13:14:22 +0100	[thread overview]
Message-ID: <20200203131422.384cd168@endymion> (raw)
In-Reply-To: <a267161f-c8b3-a11c-7416-3ab9ba19aa82@loongson.cn>

Hi Tiezhun,

On Mon, 3 Feb 2020 16:32:03 +0800, Tiezhu Yang wrote:
> On 1/16/20 9:26 PM, Tiezhu Yang wrote:
> > Enable DMI scanning on the MIPS architecture, this setups DMI identifiers
> > (dmi_system_id) for printing it out on task dumps and prepares DIMM entry
> > information (dmi_memdev_info) from the SMBIOS table. With this patch, the
> > driver can easily match various of mainboards.
> >
> > In the SMBIOS reference specification, the table anchor string "_SM_" is
> > present in the address range 0xF0000 to 0xFFFFF on a 16-byte boundary,
> > but there exists a special case for Loongson platform, when call function
> > dmi_early_remap, it should specify the start address to 0xFFFE000 due to
> > it is reserved for SMBIOS and can be normally access in the BIOS.
> >
> > This patch works fine on the Loongson 3A3000 platform which belongs to
> > MIPS architecture and has no influence on the other architectures such
> > as x86 and ARM.
> >
> > Co-developed-by: Yinglu Yang <yangyinglu@loongson.cn>
> > Signed-off-by: Yinglu Yang <yangyinglu@loongson.cn>
> > [jiaxun.yang@flygoat.com: Refine definitions and Kconfig]
> > Signed-off-by: Jiaxun Yang <jiaxun.yang@flygoat.com>
> > Signed-off-by: Tiezhu Yang <yangtiezhu@loongson.cn>
> > Reviewed-by: Huacai Chen <chenhc@lemote.com>
> > ---
> >
> > v2:
> >    - add SMBIOS_ENTRY_POINT_SCAN_START suggested by Jean
> >    - refine definitions and Kconfig by Jiaxun
> >
> >   arch/mips/Kconfig           | 10 ++++++++++
> >   arch/mips/include/asm/dmi.h | 20 ++++++++++++++++++++
> >   arch/mips/kernel/setup.c    |  2 ++
> >   drivers/firmware/dmi_scan.c |  6 +++++-
> >   4 files changed, 37 insertions(+), 1 deletion(-)
> >   create mode 100644 arch/mips/include/asm/dmi.h  
> 
> 
> Hi Paul and Jean,
> 
> How do you think this patch?

Looks good to me and you can add:

Reviewed-by: Jean Delvare <jdelvare@suse.de>

for the dmi subsystem part.

> 
> Should I split it into the following two patches?
> [PATCH v3 1/2] firmware: dmi: Add macro SMBIOS_ENTRY_POINT_SCAN_START
> [PATCH v3 2/2] MIPS: Add support for Desktop Management Interface (DMI)
> 
> The first patch is only related with the common dmi code
> drivers/firmware/dmi_scan.c, the other patch is only related
> with the mips code under arch/mips.
> 
> If you have any questions or suggestions, please let me know.
> I am looking forward to your early reply.

I'm fine either way. I you do not split it, as most changes are in the
mips arch files and I do not expect any conflict in the dmi subsystem
part, I believe that the patch should be merged by the mips arch
maintainer.

Thanks,
-- 
Jean Delvare
SUSE L3 Support

  reply	other threads:[~2020-02-03 12:14 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-16 13:26 [PATCH v2,RESEND] MIPS: Scan the DMI system information Tiezhu Yang
2020-02-03  8:32 ` Tiezhu Yang
2020-02-03 12:14   ` Jean Delvare [this message]
2020-02-05  2:28     ` Tiezhu Yang
2020-02-05  2:55       ` Jiaxun Yang
2020-02-05  5:01         ` Tiezhu Yang
2020-02-05  9:11         ` Jean Delvare
2020-02-06  7:04           ` Jiaxun Yang
2020-02-03 14:46 ` Jonas Gorski
2020-02-05  2:13   ` Tiezhu Yang

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=20200203131422.384cd168@endymion \
    --to=jdelvare@suse.de \
    --cc=chenhc@lemote.com \
    --cc=jiaxun.yang@flygoat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=lixuefeng@loongson.cn \
    --cc=paulburton@kernel.org \
    --cc=ralf@linux-mips.org \
    --cc=yangtiezhu@loongson.cn \
    --cc=yangyinglu@loongson.cn \
    /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