Received: by 2002:a05:6a10:8c0a:0:0:0:0 with SMTP id go10csp191896pxb; Fri, 5 Mar 2021 19:15:48 -0800 (PST) X-Google-Smtp-Source: ABdhPJx3X2cm1zRfRIUZI3QTFypzGUMa+R3wwgpJTABZqW+VlpTBsVCGNP8po+xekMlxYM7z3Atf X-Received: by 2002:a17:906:6047:: with SMTP id p7mr5236751ejj.400.1615000547889; Fri, 05 Mar 2021 19:15:47 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1615000547; cv=none; d=google.com; s=arc-20160816; b=I9kbfeRrxE1Weuj1TzYGmPHeSliG3EwnPbsbEdKsgGJZ/WwL2wnFFSxApUMH/HXhM9 Vy3VmpjPyUVmkyuB9KITWpQjNwNQ2GDYJwlV9/1Y6zqvYt5tLlGwDbezeBWo2v0dkmgd xfrr72YXQh10XB7z/xXr548rPge4/QBd9ZlaMnRXAzVuxmz4OoCm+9r5eMkGxYsSFTVq DDDNhvAlb1ASIKUHtFx7sl/qFA9CWBLrL9m4R15+q36BhZm2HgoCPa8XzFmy3noZmXt9 GGpkDN4aHO1NxhM9WwfhAz7L11dzpHyJKsLXfcu31KF3FHdKuZZywMsx4cfDQUt431Ip jXxA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:in-reply-to :mime-version:user-agent:date:message-id:from:cc:references:to :subject; bh=JDr7EelxEMI7UvQ0oUlf0Fr58RrC9q1SKt72fCkyqCs=; b=WOzYWLqibHPsB91RagyUM0ydy3ucxHpqFaqyxg3b9r9jyefok2xc81ogtkYWZxQovh 18uBGsbqb0J3sjKyfLSIGUwfPgag9KosfaLJR8hi4xUKnPWN5EvKLm4mh79e50Q/E8Er WsQuh2LKkbuGjVt1oX/TfK9a4eK1Nu/OSnjl/Tm+qRkkEEnG4/E+REVyPjkVwNnWaRos FkXcnKxi79iN97GQcRFr1+ahkl6cFROTWNIJN5LpwN0gveCqS3B0UZOd/5cLL9CwkpN1 5HPfnJSlyVvYuK7T52jeJ+25OUdqu93Q353CKO0eXz7MN1z7hoWCwRB2lciQxXDs/Epm KgKw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id gz5si2697246ejb.19.2021.03.05.19.15.25; Fri, 05 Mar 2021 19:15:47 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229637AbhCFDND (ORCPT + 99 others); Fri, 5 Mar 2021 22:13:03 -0500 Received: from mail.loongson.cn ([114.242.206.163]:59728 "EHLO loongson.cn" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S229597AbhCFDM2 (ORCPT ); Fri, 5 Mar 2021 22:12:28 -0500 Received: from [10.130.0.65] (unknown [113.200.148.30]) by mail.loongson.cn (Coremail) with SMTP id AQAAf9Dxb_EL80JgriAVAA--.9737S3; Sat, 06 Mar 2021 11:12:12 +0800 (CST) Subject: Re: [PATCH 2/2] MIPS: Loongson64: Move loongson_system_configuration to loongson.h To: =?UTF-8?Q?Philippe_Mathieu-Daud=c3=a9?= References: <20210304110057.22144-1-zhangqing@loongson.cn> <20210304110057.22144-3-zhangqing@loongson.cn> Cc: Huacai Chen , Jiaxun Yang , Thomas Bogendoerfer , Thomas Gleixner , Marc Zyngier , "open list:BROADCOM NVRAM DRIVER" , open list From: zhangqing Message-ID: Date: Sat, 6 Mar 2021 11:12:11 +0800 User-Agent: Mozilla/5.0 (X11; Linux mips64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-CM-TRANSID: AQAAf9Dxb_EL80JgriAVAA--.9737S3 X-Coremail-Antispam: 1UD129KBjvJXoWrZr1rWw1rWrWUtF13CrWrGrg_yoW8Jr4fpa 1Sg340ga1DGr1fuF1fKrW8uFyfA3WrtFsxGFy2q3WYkr9xXr18tF1Y9F4I93W7Arn5CF9r Z34I9r1xKan8CF7anT9S1TB71UUUUUUqnTZGkaVYY2UrUUUUjbIjqfuFe4nvWSU5nxnvy2 9KBjDU0xBIdaVrnRJUUUvqb7Iv0xC_Cr1lb4IE77IF4wAFF20E14v26r4j6ryUM7CY07I2 0VC2zVCF04k26cxKx2IYs7xG6rWj6s0DM7CIcVAFz4kK6r1j6r18M28lY4IEw2IIxxk0rw A2F7IY1VAKz4vEj48ve4kI8wA2z4x0Y4vE2Ix0cI8IcVAFwI0_Ar0_tr1l84ACjcxK6xII jxv20xvEc7CjxVAFwI0_Gr1j6F4UJwA2z4x0Y4vEx4A2jsIE14v26r4UJVWxJr1l84ACjc xK6I8E87Iv6xkF7I0E14v26F4UJVW0owAS0I0E0xvYzxvE52x082IY62kv0487Mc02F40E FcxC0VAKzVAqx4xG6I80ewAv7VC0I7IYx2IY67AKxVWUXVWUAwAv7VC2z280aVAFwI0_Gr 0_Cr1lOx8S6xCaFVCjc4AY6r1j6r4UM4x0Y48IcVAKI48JMxk0xIA0c2IEe2xFo4CEbIxv r21lc2xSY4AK67AK6r48MxAIw28IcxkI7VAKI48JMxC20s026xCaFVCjc4AY6r1j6r4UMI 8I3I0E5I8CrVAFwI0_Jr0_Jr4lx2IqxVCjr7xvwVAFwI0_JrI_JrWlx4CE17CEb7AF67AK xVWUtVW8ZwCIc40Y0x0EwIxGrwCI42IY6xIIjxv20xvE14v26r1j6r1xMIIF0xvE2Ix0cI 8IcVCY1x0267AKxVWUJVW8JwCI42IY6xAIw20EY4v20xvaj40_Zr0_Wr1UMIIF0xvEx4A2 jsIE14v26r4j6F4UMIIF0xvEx4A2jsIEc7CjxVAFwI0_Gr0_Gr1UYxBIdaVFxhVjvjDU0x ZFpf9x07j7xhLUUUUU= X-CM-SenderInfo: x2kd0wptlqwqxorr0wxvrqhubq/ Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 03/05/2021 06:01 PM, Philippe Mathieu-Daudé wrote: > Hi, > > On Thu, Mar 4, 2021 at 5:35 PM Qing Zhang wrote: >> The purpose of separating loongson_system_configuration from boot_param.h >> is to keep the other structure consistent with the firmware. > This is supposed to be a trivial patch, but the description actually > confuses me. > > Why is the move out of "boot_param.h" keeping it consistent with fw? Hi, PhilippeMathieu-Daudé Thank you for your reply. The boot_param.h file must be consistent in the kernel and the firmware pmon/cmds/bootparam.h In env.c, the loongson_system_configuration structure member gets the value passed to the firmware. eg: struct boot_params *boot_p; loongson_sysconf.restart_addr = boot_p->reset_system.ResetWarm; loongson_sysconf.poweroff_addr = boot_p->reset_system.Shutdown; loongson_sysconf.suspend_addr = boot_p->reset_system.DoSuspend; The boot_params structure is consistent with the firmware, The loongson_system_configuration is filled in the kernel, and there is no such structure in pmon-loongson3, it is actually defined in the kernel. So, remove its definition from boot_param.h. Thanks, Qing