From: Heikki Krogerus <heikki.krogerus@linux.intel.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: "Rajmohan Mani" <rajmohan.mani@intel.com>,
"Darren Hart" <dvhart@infradead.org>,
"Andy Shevchenko" <andy@infradead.org>,
"Mika Westerberg" <mika.westerberg@linux.intel.com>,
"Dmitry Torokhov" <dmitry.torokhov@gmail.com>,
"Lee Jones" <lee.jones@linaro.org>,
"Ayman Bagabas" <ayman.bagabas@gmail.com>,
"Masahiro Yamada" <masahiroy@kernel.org>,
"Jithu Joseph" <jithu.joseph@intel.com>,
"Blaž Hrastnik" <blaz@mxxn.io>,
"Srinivas Pandruvada" <srinivas.pandruvada@linux.intel.com>,
linux-kernel@vger.kernel.org,
platform-driver-x86@vger.kernel.org, linux-usb@vger.kernel.org,
pmalani@chromium.org, bleung@chromium.org
Subject: Re: [PATCH v2 1/3] platform/x86: Add Intel Input Output Manager (IOM) driver
Date: Fri, 28 Aug 2020 12:08:32 +0300 [thread overview]
Message-ID: <20200828090832.GB174928@kuha.fi.intel.com> (raw)
In-Reply-To: <20200828074359.GC942935@kroah.com>
Hi Greg,
On Fri, Aug 28, 2020 at 09:43:59AM +0200, Greg Kroah-Hartman wrote:
> I still find this crazy that a whole separate driver is created just to
> read a single 32bit value.
>
> Why not put this logic in the driver that wants to read that value?
> That would be much simpler, smaller, and more obvious.
That would mean that we start maintaining something like DMI quirk
table in those drivers. Unfortunately the IOM device is not available
on every platform. Also, even on platforms that do have it, there is
no guarantee that the device is always going to be mapped to the same
address.
Nevertheless, I was originally hoping that we could hide the handling
of IOM somehow in ACPI without the need for an actual device object,
but it now turns out that the other features of the IOM chip have
created interest. At least our i915 guys probable have some use for it
(I don't know exactly what they are planning to use it for).
So the fact that we may later need the device for something else, on
top of the clumsiness and most importantly risks involved with using
ACPI to take care of extra tasks (ASL tends to have bugs - bugs that
may never ever get fixed), I think the IOM device object, and the
driver that binds to it, do have a valid reason for existing.
thanks,
--
heikki
next prev parent reply other threads:[~2020-08-28 9:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-22 4:05 [PATCH v2 0/3] Add Intel Input Output Manager driver Rajmohan Mani
2020-08-22 4:05 ` [PATCH v2 1/3] platform/x86: Add Intel Input Output Manager (IOM) driver Rajmohan Mani
2020-08-22 9:56 ` Prashant Malani
2020-08-24 22:19 ` Mani, Rajmohan
2020-08-24 22:47 ` Prashant Malani
2020-08-25 1:03 ` Mani, Rajmohan
2020-08-28 7:43 ` Greg Kroah-Hartman
2020-08-28 9:08 ` Heikki Krogerus [this message]
2020-08-28 10:03 ` Greg Kroah-Hartman
2020-08-28 11:55 ` Heikki Krogerus
2020-08-28 15:21 ` Mani, Rajmohan
2020-08-28 15:20 ` Mani, Rajmohan
2020-08-29 6:27 ` Greg Kroah-Hartman
2020-08-31 21:40 ` Mani, Rajmohan
2020-08-22 4:05 ` [PATCH v2 2/3] usb: typec: intel_pmc_mux: Check the port status before connect Rajmohan Mani
2020-08-22 4:05 ` [PATCH v2 3/3] usb: typec: intel_pmc_mux: Support for device role (UFP) Rajmohan Mani
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=20200828090832.GB174928@kuha.fi.intel.com \
--to=heikki.krogerus@linux.intel.com \
--cc=andy@infradead.org \
--cc=ayman.bagabas@gmail.com \
--cc=blaz@mxxn.io \
--cc=bleung@chromium.org \
--cc=dmitry.torokhov@gmail.com \
--cc=dvhart@infradead.org \
--cc=gregkh@linuxfoundation.org \
--cc=jithu.joseph@intel.com \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=pmalani@chromium.org \
--cc=rajmohan.mani@intel.com \
--cc=srinivas.pandruvada@linux.intel.com \
/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).