From: Andy Shevchenko <andy.shevchenko@gmail.com>
To: Wolfram Sang <wsa@kernel.org>,
Terry Bowman <Terry.Bowman@amd.com>,
Andy Shevchenko <andy.shevchenko@gmail.com>,
Guenter Roeck <linux@roeck-us.net>,
Jean Delvare <jdelvare@suse.de>,
linux-i2c <linux-i2c@vger.kernel.org>,
linux-watchdog@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Tom Lendacky <thomas.lendacky@amd.com>,
Robert Richter <rrichter@amd.com>
Subject: Re: [PATCH] i2c: piix4: Replace piix4_smbus driver's cd6h/cd7h port io accesses with mmio accesses
Date: Thu, 13 Jan 2022 12:24:41 +0200 [thread overview]
Message-ID: <CAHp75VeR4sL1URhf+Vj6_fUjw3wgG98nZd8Mu20NzH1zM590SQ@mail.gmail.com> (raw)
In-Reply-To: <Yd/X6DlWjACLODe2@ninjato>
On Thu, Jan 13, 2022 at 9:42 AM Wolfram Sang <wsa@kernel.org> wrote:
>
>
> > > On top of that I'm wondering why slow I/O is used? Do we have anything
> > > that really needs that or is it simply a cargo-cult?
> >
> > The efch SMBUS & WDT previously only supported a port I/O interface
> > (until recently) and thus dictated the HW access method.
>
> Is this enough information to start v2 of this series? Or does the
> approach need more discussion?
I dunno why slow I/O is chosen, but it only affects design (read:
ugliness) of the new code.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2022-01-13 10:26 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-15 22:18 [PATCH] i2c: piix4: Replace piix4_smbus driver's cd6h/cd7h port io accesses with mmio accesses Terry Bowman
2021-09-07 16:37 ` Jean Delvare
2021-11-05 16:05 ` Jean Delvare
2021-12-13 17:48 ` Terry Bowman
2022-01-04 19:34 ` Terry Bowman
2022-01-06 13:01 ` Wolfram Sang
2022-01-06 18:18 ` Guenter Roeck
2022-01-08 21:49 ` Wolfram Sang
2022-01-10 10:29 ` Andy Shevchenko
2022-01-11 12:39 ` Wolfram Sang
2022-01-11 14:13 ` Terry Bowman
2022-01-11 14:53 ` Andy Shevchenko
2022-01-11 14:54 ` Andy Shevchenko
2022-01-11 15:50 ` Terry Bowman
2022-01-11 16:17 ` Andy Shevchenko
2022-01-12 0:40 ` Terry Bowman
2022-01-13 7:42 ` Wolfram Sang
2022-01-13 10:24 ` Andy Shevchenko [this message]
2022-01-18 13:09 ` Jean Delvare
2022-01-18 14:22 ` Jean Delvare
[not found] <20210715221828.244536-1-Terry.Bowman () amd ! com>
2021-08-16 16:55 ` Terry Bowman
2021-08-16 17:03 ` Terry Bowman
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=CAHp75VeR4sL1URhf+Vj6_fUjw3wgG98nZd8Mu20NzH1zM590SQ@mail.gmail.com \
--to=andy.shevchenko@gmail.com \
--cc=Terry.Bowman@amd.com \
--cc=jdelvare@suse.de \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=rrichter@amd.com \
--cc=thomas.lendacky@amd.com \
--cc=wsa@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;
as well as URLs for NNTP newsgroup(s).