From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: "Luis R. Rodriguez" <mcgrof@kernel.org>,
Ingo Molnar <mingo@redhat.com>, "H . Peter Anvin" <hpa@zytor.com>,
linux-kernel@vger.kernel.org, x86@kernel.org
Subject: Re: [PATCH v2 1/1] x86/rtc: Allocate interrupt for platform device
Date: Tue, 17 Jan 2017 15:40:04 +0200 [thread overview]
Message-ID: <1484660404.2133.170.camel@linux.intel.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1701162131570.3923@nanos>
On Mon, 2017-01-16 at 22:00 +0100, Thomas Gleixner wrote:
> The early callback does not work, but we have one which is invoked
> later
> on: x86_init.wallclock_init(). That's invoked after the (IO/APIC)
> setup has
> been completed. See patch below.
Unfortunately it is till too early. Looks like descriptors are not
available yet and we still can't get an allocation:
[ 0.000000] intel_mid: Failed to allocate RTC interrupt. Disabling
RTC
...
[ 0.000000] NR_IRQS:4352 nr_irqs:512 0
> +static void __init intel_mid_legacy_rtc_init(void)
> +{
> + struct irq_alloc_info info;
> +
> + ioapic_set_alloc_attr(&info, NUMA_NO_NODE, 1, 0);
> + if (mp_map_gsi_to_irq(RTC_IRQ, IOAPIC_MAP_ALLOC, &info)) {
> + pr_info("Failed to allocate RTC interrupt. Disabling
> RTC\n");
> + x86_platform.legacy.rtc = 0;
> + }
> +}
> +
> static void intel_mid_arch_setup(void)
> {
> if (boot_cpu_data.x86 != 6) {
> @@ -151,6 +162,10 @@ static void intel_mid_arch_setup(void)
> if (intel_mid_ops->arch_setup)
> intel_mid_ops->arch_setup();
>
> + /* If the platform has an RTC make sure the APIC entry is
> allocated */
> + if (x86_platform.legacy.rtc)
> + x86_init.timers.wallclock_init =
> intel_mid_legacy_rtc_init;
--
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy
next prev parent reply other threads:[~2017-01-17 13:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-16 17:23 [PATCH v2 1/1] x86/rtc: Allocate interrupt for platform device Andy Shevchenko
2017-01-16 19:04 ` Luis R. Rodriguez
2017-01-16 19:21 ` Andy Shevchenko
2017-01-16 21:00 ` Thomas Gleixner
2017-01-16 22:44 ` Andy Shevchenko
2017-01-17 8:25 ` Thomas Gleixner
2017-01-17 13:40 ` Andy Shevchenko [this message]
2017-01-18 10:24 ` Thomas Gleixner
2017-01-18 10:56 ` Andy Shevchenko
2017-01-18 11:02 ` Thomas Gleixner
2017-01-18 11:54 ` Andy Shevchenko
2017-01-18 16:29 ` Andy Shevchenko
2017-01-18 16:48 ` Andy Shevchenko
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=1484660404.2133.170.camel@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@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;
as well as URLs for NNTP newsgroup(s).