From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: Yuan Tan <tanyuan@tinylab.org>,
Christophe Leroy <christophe.leroy@csgroup.eu>,
"mpe@ellerman.id.au" <mpe@ellerman.id.au>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"mingo@redhat.com" <mingo@redhat.com>,
"tsbogend@alpha.franken.de" <tsbogend@alpha.franken.de>,
"hdegoede@redhat.com" <hdegoede@redhat.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"x86@kernel.org" <x86@kernel.org>,
"linux-mips@vger.kernel.org" <linux-mips@vger.kernel.org>,
"linux@weissschuh.net" <linux@weissschuh.net>,
"falcon@tinylab.org" <falcon@tinylab.org>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
"w@1wt.eu" <w@1wt.eu>
Subject: Re: [PATCH v2 1/3] kconfig: add dependencies of POWER_RESET for mips malta
Date: Mon, 4 Sep 2023 21:08:45 +0200 [thread overview]
Message-ID: <2841ec8c-f07b-307e-de03-6e8a4dd88775@linaro.org> (raw)
In-Reply-To: <8464A5F00EFC8C59+502c989a-3814-4686-8c6f-0a8f814e1c39@tinylab.org>
On 4/9/23 19:40, Yuan Tan wrote:
>
> On 9/4/2023 6:58 PM, Christophe Leroy wrote:
>>
>> Le 04/09/2023 à 12:51, Philippe Mathieu-Daudé a écrit :
>>> On 4/9/23 11:24, Yuan Tan wrote:
>>>> Hi,
>>>>
>>>> On 9/4/2023 3:40 PM, Philippe Mathieu-Daudé wrote:
>>>>> Hi,
>>>>>
>>>>> On 1/9/23 04:42, Yuan Tan wrote:
>>>>>> MIPS Malta's power off depends on PCI, PCI_QUIRKS, and
>>>>>> POWER_RESET_PIIX4_POWEROFF to work. Enable them when POWER_RESET
>>>>>> is set
>>>>>> for convenience.
>>>>>>
>>>>>> Suggested-by: Zhangjin Wu <falcon@tinylab.org>
>>>>>> Signed-off-by: Yuan Tan <tanyuan@tinylab.org>
>>>>>> ---
>>>>>> arch/mips/Kconfig | 3 +++
>>>>>> 1 file changed, 3 insertions(+)
>>>>>>
>>>>>> diff --git a/arch/mips/Kconfig b/arch/mips/Kconfig
>>>>>> index bc8421859006..13bacbd05125 100644
>>>>>> --- a/arch/mips/Kconfig
>>>>>> +++ b/arch/mips/Kconfig
>>>>>> @@ -547,6 +547,9 @@ config MIPS_MALTA
>>>>>> select MIPS_L1_CACHE_SHIFT_6
>>>>>> select MIPS_MSC
>>>>>> select PCI_GT64XXX_PCI0
>>>>>> + select PCI if POWER_RESET
>>>>>> + select PCI_QUIRKS if POWER_RESET
>>>>>> + select POWER_RESET_PIIX4_POWEROFF if POWER_RESET
>>>>>> select SMP_UP if SMP
>>>>>> select SWAP_IO_SPACE
>>>>>> select SYS_HAS_CPU_MIPS32_R1
>>>>> Shouldn't we also update the _defconfig files?
>>>>>
>>>> Sorry, in my last email, I forgot to reply to all. So I am now
>>>> resending this email.
>>>>
>>>> In malta_defconfig, PCI and POWER_RESET_PIIX4_POWEROFF have already
>>>> been set and PCI_QUIRKS is also selected by FSL_PCI [=n].
>>>>
>>>> So shutdown and reboot with malta_defconfig is working and there is no
>>>> need to update the malta_defconfig 🙂
>>> Since the dependency is now enforced by Kconfig, the defconfig can
>>> be simplified:
>>>
>>> --- a/arch/mips/configs/malta_defconfig
>>> +++ b/arch/mips/configs/malta_defconfig
>>> @@ -306,3 +306,2 @@ CONFIG_SERIAL_8250_CONSOLE=y
>>> CONFIG_POWER_RESET=y
>>> -CONFIG_POWER_RESET_PIIX4_POWEROFF=y
>>> CONFIG_POWER_RESET_SYSCON=y
>>>
>>> But maybe we don't care, I don't know.
>> I understand from what you say that you update malta_defconfig manually ?
>>
>> defconfigs shouldn't be updated manually.
>>
>> Once you have the new .config you should use "make savedefconfig" then
>> replace your file by the newly generated defconfig file.
>>
>> Christophe
>
> To do so, I just unset CONFIG_POWER_RESET and set it again in
> menuconfig, then "make savedefconfig". The POWER_RESET part is simplified.
>
> CONFIG_POWER_RESET=y
> -CONFIG_POWER_RESET_PIIX4_POWEROFF=y
> -CONFIG_POWER_RESET_SYSCON=y
>
> However, I found that there's other changes in this new
> malta_defconfig, for example
>
> CONFIG_NLS_KOI8_U=m CONFIG_CRYPTO_CRYPTD=m -CONFIG_CRYPTO_LRW=m
> -CONFIG_CRYPTO_PCBC=m -CONFIG_CRYPTO_HMAC=y -CONFIG_CRYPTO_XCBC=m
> -CONFIG_CRYPTO_MD4=m -CONFIG_CRYPTO_SHA512=m -CONFIG_CRYPTO_WP512=m
> -CONFIG_CRYPTO_ANUBIS=m CONFIG_CRYPTO_BLOWFISH=m CONFIG_CRYPTO_CAMELLIA=m
>
> Should I import all these changes in a commit? Or only POWER_RESET part.
I'd first update the defconfigs with mainline (as a cleanup)
then apply your series on top, re-running 'make savedefconfig'
you should get only the changes relevant to your work.
next prev parent reply other threads:[~2023-09-04 19:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-01 2:42 [PATCH v2 0/3] Add dependencies of POWER_RESET for MIPS Malta, x86, and PowerMac Yuan Tan
2023-09-01 2:42 ` [PATCH v2 1/3] kconfig: add dependencies of POWER_RESET for mips malta Yuan Tan
2023-09-04 7:40 ` Philippe Mathieu-Daudé
2023-09-04 9:24 ` Yuan Tan
2023-09-04 10:51 ` Philippe Mathieu-Daudé
2023-09-04 10:58 ` Christophe Leroy
2023-09-04 17:40 ` Yuan Tan
2023-09-04 19:08 ` Philippe Mathieu-Daudé [this message]
2023-09-14 7:28 ` Yuan Tan
2023-09-01 2:43 ` [PATCH v2 2/3] kconfig: add dependencies of POWER_RESET for x86 Yuan Tan
2023-09-01 2:43 ` [PATCH v2 3/3] kconfig: add dependencies of POWER_RESET for PowerMac Yuan Tan
2023-09-01 6:10 ` Christophe Leroy
2023-09-01 18:02 ` Yuan Tan
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=2841ec8c-f07b-307e-de03-6e8a4dd88775@linaro.org \
--to=philmd@linaro.org \
--cc=christophe.leroy@csgroup.eu \
--cc=falcon@tinylab.org \
--cc=hdegoede@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux@weissschuh.net \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mingo@redhat.com \
--cc=mpe@ellerman.id.au \
--cc=tanyuan@tinylab.org \
--cc=tglx@linutronix.de \
--cc=tsbogend@alpha.franken.de \
--cc=w@1wt.eu \
--cc=x86@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).