From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Ingo Molnar <mingo@redhat.com>, "H . Peter Anvin" <hpa@zytor.com>,
linux-kernel@vger.kernel.org, x86@kernel.org,
"Luis R . Rodriguez" <mcgrof@kernel.org>
Subject: Re: [PATCH v3 2/3] x86/platform/intel-mid: Allocate RTC interrupt for Merrifield
Date: Thu, 19 Jan 2017 19:02:12 +0200 [thread overview]
Message-ID: <1484845332.2133.247.camel@linux.intel.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1701191746580.3428@nanos>
On Thu, 2017-01-19 at 17:54 +0100, Thomas Gleixner wrote:
> On Wed, 18 Jan 2017, Andy Shevchenko wrote:
> > +#include <linux/init.h>
> > +
> > +#include <asm/hw_irq.h>
> > +#include <asm/intel-mid.h>
> > +#include <asm/io_apic.h>
> > +#include <asm/time.h>
> > +#include <asm/x86_init.h>
> > +
> > +static int __init mrfld_legacy_rtc_alloc_irq(void)
> > +{
> > + struct irq_alloc_info info;
> > + int ret;
> > +
> > + if (!x86_platform.legacy.rtc)
> > + return -ENODEV;
> > +
> > + ioapic_set_alloc_attr(&info, NUMA_NO_NODE, 1, 0);
> > + ret = mp_map_gsi_to_irq(RTC_IRQ, IOAPIC_MAP_ALLOC, &info);
> > + if (ret < 0) {
> > + pr_info("Failed to allocate RTC interrupt.
> > Disabling RTC\n");
> > + x86_platform.legacy.rtc = 0;
> > + return ret;
> > + }
> > +
> > + return 0;
> > +}
> > +
> > +static int __init mrfld_legacy_rtc_init(void)
> > +{
> > + if (intel_mid_identify_cpu() != INTEL_MID_CPU_CHIP_TANGIER)
> > + return -ENODEV;
> > +
> > + return mrfld_legacy_rtc_alloc_irq();
> > +}
> > +rootfs_initcall(mrfld_legacy_rtc_init);
>
> rootfs_initcall???? That does not make any sense at all. I know you
> need it
> before the device initcalls, but just using a random initcall level
> before
> device_initcall is wrong.
I copied watchdog approach, would you like me to move watchdog there as
well?
>
> arch_initcall is much more suitable.
So, I think I need to send v4, but I would wait for answer for the
above.
Thanks for review!
--
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy
next prev parent reply other threads:[~2017-01-19 17:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-18 17:42 [PATCH v3 0/3] x86/platform/intel-mid: Fix RTC handling Andy Shevchenko
2017-01-18 17:42 ` [PATCH v3 1/3] x86/ioapic: Return suitable error code in mp_map_gsi_to_irq() Andy Shevchenko
2017-01-18 17:42 ` [PATCH v3 2/3] x86/platform/intel-mid: Allocate RTC interrupt for Merrifield Andy Shevchenko
2017-01-19 16:54 ` Thomas Gleixner
2017-01-19 17:02 ` Andy Shevchenko [this message]
2017-01-18 17:42 ` [PATCH v3 3/3] x86/platform/intel-mid: Don't shadow error code of mp_map_gsi_to_irq() 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=1484845332.2133.247.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
Powered by JetHome