From: Alan Cox <alan@linux.intel.com>
To: hpa@zytor.com, Thomas Gleixner <tglx@linutronix.de>,
Rajneesh Bhardwaj <rajneesh.bhardwaj@intel.com>
Cc: Anshuman Gupta <anshuman.gupta@intel.com>,
glx@linutronix.de, x86@kernel.org, mingo@redhat.com,
rjw@rjwysocki.net, andriy.shevchenko@linux.intel.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] x86: i8237: Register based on FADT legacy boot flag
Date: Mon, 26 Mar 2018 15:55:16 +0100 [thread overview]
Message-ID: <1522076116.16723.13.camel@linux.intel.com> (raw)
In-Reply-To: <8A68406D-B05E-4953-89D1-D2AB49904644@zytor.com>
> Can we probe safely for this device?
99% of the time yes the inb gives us a straight answer. However (and
we've hit this with port 0x81 for real) there are concerns that some
systems will trap those addresses into SMM and do weirdness that makes
the 0xFF check fail.
Alan
next prev parent reply other threads:[~2018-03-26 14:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-14 5:17 [PATCH v2] x86: i8237: Register based on FADT legacy boot flag Rajneesh Bhardwaj
2018-03-14 12:48 ` Andy Shevchenko
2018-03-14 15:07 ` Thomas Gleixner
[not found] ` <20180319104627.GA2959@anshuman.gupta@intel.com>
2018-03-19 10:57 ` Thomas Gleixner
2018-03-22 10:21 ` [PATCH v3] " Anshuman Gupta
2018-03-22 11:05 ` Rajneesh Bhardwaj
2018-03-22 11:17 ` Thomas Gleixner
2018-03-25 11:50 ` Thomas Gleixner
2018-03-26 5:48 ` Rajneesh Bhardwaj
2018-03-26 9:11 ` Thomas Gleixner
2018-03-26 10:34 ` hpa
2018-03-26 10:51 ` Rajneesh Bhardwaj
2018-03-26 14:55 ` Alan Cox [this message]
2018-03-29 15:06 ` [PATCH v4] " Anshuman Gupta
2018-04-27 15:06 ` [tip:x86/dma] x86/i8237: Register device " tip-bot for Rajneesh Bhardwaj
2018-03-26 14:52 ` [PATCH v3] x86: i8237: Register " Alan Cox
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=1522076116.16723.13.camel@linux.intel.com \
--to=alan@linux.intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=anshuman.gupta@intel.com \
--cc=glx@linutronix.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rajneesh.bhardwaj@intel.com \
--cc=rjw@rjwysocki.net \
--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