From: "Leizhen (ThunderTown)" <thunder.leizhen@huawei.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: <linux-arm-kernel@lists.infradead.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will.deacon@arm.com>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Kefeng Wang <wangkefeng.wang@huawei.com>,
Xinwei Hu <huxinwei@huawei.com>, Zefan Li <lizefan@huawei.com>,
Tianhong Ding <dingtianhong@huawei.com>,
Hanjun Guo <guohanjun@huawei.com>
Subject: Re: [PATCH 2/2] arm64: to allow EFI_RTC can be selected on ARM64
Date: Thu, 8 Oct 2015 17:07:28 +0800 [thread overview]
Message-ID: <56163250.90207@huawei.com> (raw)
In-Reply-To: <56090C08.8070003@huawei.com>
On 2015/9/28 17:44, Leizhen (ThunderTown) wrote:
>> >
>>> >> --------------drivers/char/Kconfig--------------
>>> >> if RTC_LIB=n
>>> >>
>>> >> config RTC
>>> >> tristate "Enhanced Real Time Clock Support (legacy PC RTC driver)"
>>> >>
>>> >> .......
>>> >>
>>> >> config EFI_RTC
>>> >> bool "EFI Real Time Clock Services"
>>> >> depends on IA64 || ARM64
>>> >>
>>> >> .......
>>> >>
>>> >> endif # RTC_LIB
>> >
>> > The driver you want is RTC_DRV_EFI, not EFI_RTC.
> OK, I will try it tommorrow.
Sorry, the coach called me to learn to drive these days. I opened RTC_DRV_EFI and the RTC worked fine, thanks a lot.
>
>> >
>> > Arnd
>> >
>> > .
>> >
next prev parent reply other threads:[~2015-10-08 9:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-28 5:34 [PATCH 0/2] " Zhen Lei
2015-09-28 5:34 ` [PATCH 1/2] char/rtc: " Zhen Lei
2015-09-28 5:34 ` [PATCH 2/2] arm64: " Zhen Lei
2015-09-28 7:35 ` Arnd Bergmann
2015-09-28 8:29 ` Leizhen (ThunderTown)
2015-09-28 8:42 ` Arnd Bergmann
2015-09-28 9:44 ` Leizhen (ThunderTown)
2015-09-28 9:56 ` Arnd Bergmann
2015-10-08 9:07 ` Leizhen (ThunderTown) [this message]
2015-09-28 7:40 ` Ard Biesheuvel
2015-09-28 8:41 ` Leizhen (ThunderTown)
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=56163250.90207@huawei.com \
--to=thunder.leizhen@huawei.com \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=dingtianhong@huawei.com \
--cc=gregkh@linuxfoundation.org \
--cc=guohanjun@huawei.com \
--cc=huxinwei@huawei.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=wangkefeng.wang@huawei.com \
--cc=will.deacon@arm.com \
/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
Powered by JetHome