public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] arm64: to allow EFI_RTC can be selected on ARM64
Date: Mon, 28 Sep 2015 11:56:43 +0200	[thread overview]
Message-ID: <1493434.sLUZ1A9ljb@wuerfel> (raw)
In-Reply-To: <56090C08.8070003@huawei.com>

On Monday 28 September 2015 17:44:40 Leizhen wrote:
> >> No, on non-EFI platforms, they can still use RTC as before. As I mentioned above,
> >> RTC_LIB only controls whether to display some configs when run "make menuconfig".
> >> On ARM64, (in this patch) I only allowed EFI_RTC can be showed when RTC_LIB was
> >> not selected.
> >>
> > 
> > but that is the wrong driver that uses the legacy API, we cannot have that
> > on ARM because it conflicts with the normal RTC_CLASS drivers.
> 
> Yes, RTC_CLASS will automatically select RTC_LIB, and will not display EFI_RTC, because
> RTC_LIB=y now.
> 
> We can select EFI_RTC only when RTC_CLASS is not selected(meanwhile RTC_LIB=n)

I understood that, and my initial point was that we cannot allow
such a situation, all drivers that we might use must be able to coexist
in one kernel.

If you have any applications that are ported from Itanium and that rely on
specific behavior of the ia64 rtc driver, we should either enable those in the
normal rtc-efi driver, or you need to change your application to use the
portable RTC interfaces.

	Arnd

  reply	other threads:[~2015-09-28  9:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-28  5:34 [PATCH 0/2] to allow EFI_RTC can be selected on ARM64 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 [this message]
2015-10-08  9:07           ` Leizhen (ThunderTown)
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=1493434.sLUZ1A9ljb@wuerfel \
    --to=arnd@arndb.de \
    --cc=linux-arm-kernel@lists.infradead.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