From: Jean Delvare <jdelvare@suse.de>
To: Hans de Goede <hdegoede@redhat.com>
Cc: Wolfram Sang <wsa@the-dreams.de>,
linux-i2c@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] i2c: i801: Fix Failed to allocate irq -2147483648 error
Date: Mon, 27 Nov 2017 11:04:27 +0100 [thread overview]
Message-ID: <20171127110427.624a8b3c@endymion> (raw)
In-Reply-To: <5ba5b26d-18d9-6f07-d9a9-52cde30ea5ee@redhat.com>
On Sat, 25 Nov 2017 14:43:08 +0100, Hans de Goede wrote:
> On 11/24/2017 02:49 PM, Jean Delvare wrote:
> > Isn't it a BIOS bug?
>
> No, as mentioned in:
>
> >> BugLink: https://communities.intel.com/thread/114759
>
> The BIOS deliberately does not contain IRQ routing issues because some
> variants of the Windows driver for this falling over if their is
> any IRQ routing set, so this is a "feature" not a bug :|
What I do not understand is how Apollo Lake systems are different from
any other Intel system, which already had a compatible SMBus controller
and apparently having an IRQ configured was never an issue?
> > (...)
> > However if this is considered a BIOS bug then a pr_err(FW_BUG...) would
> > be good to add IMHO.
>
> See above, that would just replace one error message with another on all
> Apollo Lake systems.
Turning a cryptic error message into a meaningful error message isn't
necessarily a bad thing.
--
Jean Delvare
SUSE L3 Support
next prev parent reply other threads:[~2017-11-27 10:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-22 11:28 [PATCH] i2c: i801: Fix Failed to allocate irq -2147483648 error Hans de Goede
2017-11-24 13:49 ` Jean Delvare
2017-11-25 13:43 ` Hans de Goede
2017-11-27 10:04 ` Jean Delvare [this message]
2017-11-27 15:38 ` Hans de Goede
2017-11-28 13:37 ` Jean Delvare
2017-11-28 13:42 ` Hans de Goede
2017-11-27 18:11 ` Wolfram Sang
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=20171127110427.624a8b3c@endymion \
--to=jdelvare@suse.de \
--cc=hdegoede@redhat.com \
--cc=linux-i2c@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=wsa@the-dreams.de \
/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.