From: Randy Dunlap <rdunlap@infradead.org>
To: "Anand K. Mistry" <amistry@google.com>
Cc: x86@kernel.org, Borislav Petkov <bp@alien8.de>,
"H. Peter Anvin" <hpa@zytor.com>, Ingo Molnar <mingo@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86: Add a prompt for HPET_EMULATE_RTC
Date: Wed, 3 Feb 2021 22:29:55 -0800 [thread overview]
Message-ID: <507e5062-f575-e034-d6fa-f1dca4bbbcc9@infradead.org> (raw)
In-Reply-To: <CAATStaMRHai=jWr4x1cZVs2MrME+1QSqoXD75xAOQfxb723hQQ@mail.gmail.com>
On 2/3/21 10:13 PM, Anand K. Mistry wrote:
>> Hi,
>>
>> When you run "make olddefconfig", should this "depends on"
>> line evaluate to true or false?
>
> True. RTC_DRV_CMOS=y by default on x86 systems and HPET_TIMER also
> appears to default yes (on x86-64 if I'm reading this right).
>
> Oddly, the RTC config option doesn't appear to exist. Probably a separate issue.
Yes, just a separate simple patch.
>> I.e., what are the settings of these symbols in the old .config file?
>>
>>
>> depends on HPET_TIMER && (RTC=y || RTC=m || RTC_DRV_CMOS=m || RTC_DRV_CMOS=y)
>
> Actually, none of these options are set in the old config.
> RTC_DRV_CMOS and HPET_TIMER appear to default to yes.
>
> % grep HPET .config
> CONFIG_HPET=y
> # CONFIG_HPET_EMULATE_RTC is not set
> # CONFIG_HPET_MMAP is not set
> % grep RTC .config
> CONFIG_RTC_CLASS=y
> # CONFIG_HPET_EMULATE_RTC is not set
> CONFIG_PM_TRACE_RTC=y
> # CONFIG_RTC_HCTOSYS is not set
>
>>
>> If not, is there some out-of-tree driver involved?
>
> No out of tree drivers involved. I tried this on a vanilla 5.11-rc6.
>
>> I'm having a little trouble seeing why this is needed.
>
> So am I. But this is the magic that lets me keep
> CONFIG_HPET_EMULATE_RTC from the old config. I did manage to trace
> where the option is being overridden in the conf tool, but the
> reasoning why is beyond my knowledge.
Can you post the .config that you are feeding to 'make olddefconfig', please.
I'll take a look (or the x86 guys can do so).
thanks.
--
~Randy
next prev parent reply other threads:[~2021-02-04 6:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-04 2:21 Anand K Mistry
2021-02-04 3:47 ` Randy Dunlap
2021-02-04 6:13 ` Anand K. Mistry
2021-02-04 6:29 ` Randy Dunlap [this message]
2021-02-04 6:55 ` Anand K. Mistry
2021-02-04 17:37 ` Randy Dunlap
2021-02-04 17:59 ` Randy Dunlap
2021-02-04 20:53 ` Anand K. Mistry
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=507e5062-f575-e034-d6fa-f1dca4bbbcc9@infradead.org \
--to=rdunlap@infradead.org \
--cc=amistry@google.com \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--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
all inboxes | Powered by JetHome®