From: Thierry Reding <thierry.reding@avionic-design.de>
To: Sebastian Andrzej Siewior <sebastian@breakpoint.cc>
Cc: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
Grant Likely <grant.likely@secretlab.ca>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86/dt: use linear irq domain for ioapic(s).
Date: Sun, 12 Aug 2012 08:48:03 +0200 [thread overview]
Message-ID: <20120812064803.GA5950@avionic-0098.mockup.avionic-design.de> (raw)
In-Reply-To: <20120811172638.GA9440@kibibi>
[-- Attachment #1: Type: text/plain, Size: 1052 bytes --]
On Sat, Aug 11, 2012 at 07:26:38PM +0200, Sebastian Andrzej Siewior wrote:
> * Thierry Reding | 2012-08-08 14:07:37 [+0200]:
>
> >With that in place, the driver code can match on "intel,hpet" to catch
> >all implementations and use the more specific entries if quirks are
> >required for the specific hardware.
>
> from http://lkml.org/lkml/2011/2/16/350:
>
> |"intel,ioapic" is probably too generic and can be dropped. Newer
> |devices can claim compatibility with "intel,ioapic-ce4100" if they are
> |indeed compatible so that device drivers don't need to be modified.
> |It is better to anchor compatible values to real implementations that
> |try to come up with 'generic' or wildcard strings. Ditto through the
> |rest of the file.
Oh well. I've seen just the opposite used on ARM, where you start from a
generic implementation and compatible value and use more specific
compatible values for device-specific quirks.
But okay, the hardware that I use seems to work fine anyway, so I'll
just leave it as-is.
Thierry
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-08-12 6:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-02 6:51 [PATCH] x86/ioapic: Fix fallout from IRQ domain conversion Thierry Reding
2012-08-06 7:38 ` [PATCH] x86/dt: use linear irq domain for ioapic(s) Sebastian Andrzej Siewior
2012-08-06 16:04 ` Thierry Reding
2012-08-08 10:46 ` Thierry Reding
2012-08-08 11:51 ` Sebastian Andrzej Siewior
2012-08-08 12:07 ` Thierry Reding
2012-08-11 17:26 ` Sebastian Andrzej Siewior
2012-08-12 6:48 ` Thierry Reding [this message]
2012-10-19 11:36 ` Florian Fainelli
2012-10-19 13:40 ` Florian Fainelli
2012-10-26 15:52 ` Sebastian Andrzej Siewior
2012-08-13 20:23 ` [PATCH v2] " Sebastian Andrzej Siewior
2012-08-21 20:25 ` [tip:x86/apic] x86: dt: Use " tip-bot for Sebastian Andrzej Siewior
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=20120812064803.GA5950@avionic-0098.mockup.avionic-design.de \
--to=thierry.reding@avionic-design.de \
--cc=bigeasy@linutronix.de \
--cc=grant.likely@secretlab.ca \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=sebastian@breakpoint.cc \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.