From: John Garry <john.garry@huawei.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
<mika.westerberg@linux.intel.com>, <rafael@kernel.org>,
<lorenzo.pieralisi@arm.com>, <rjw@rjwysocki.net>,
<hanjun.guo@linaro.org>, <robh+dt@kernel.org>,
<bhelgaas@google.com>, <arnd@arndb.de>, <mark.rutland@arm.com>,
<olof@lixom.net>, <dann.frazier@canonical.com>,
<andy.shevchenko@gmail.com>, <robh@kernel.org>
Cc: <joe@perches.com>, <benh@kernel.crashing.org>,
<linux-pci@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-acpi@vger.kernel.org>, <linuxarm@huawei.com>,
<minyard@acm.org>, <devicetree@vger.kernel.org>,
<linux-arch@vger.kernel.org>, <rdunlap@infradead.org>,
<gregkh@linuxfoundation.org>, <akpm@linux-foundation.org>,
<frowand.list@gmail.com>, <agraf@suse.de>
Subject: Re: [PATCH v16 0/9] LPC: legacy ISA I/O support
Date: Tue, 6 Mar 2018 11:36:27 +0000 [thread overview]
Message-ID: <b4459d98-ebd4-7b13-07ec-613845579558@huawei.com> (raw)
In-Reply-To: <1520335317.10722.416.camel@linux.intel.com>
On 06/03/2018 11:21, Andy Shevchenko wrote:
> On Tue, 2018-03-06 at 18:47 +0800, John Garry wrote:
>> This patchset supports the IPMI-bt device attached to the Low-Pin-
>> Count
>> interface implemented on Hisilicon Hip06/Hip07 SoC.
>> -----------
>> | LPC host|
>> | |
>> -----------
>> |
>> _____________V_______________LPC
>> | |
>> V V
>> ------------
>> | BT(ipmi)|
>> ------------
>>
>> When master accesses those peripherals beneath the Hip06/Hip07 LPC, a
>> specific
>> LPC driver is needed to make LPC host generate the standard LPC I/O
>> cycles with
>> the target peripherals'I/O port addresses. But on curent arm64 world,
>> there is
>> no real I/O accesses. All the I/O operations through in/out accessors
>> are based
>> on MMIO ranges; on Hip06/Hip07 LPC the I/O accesses are performed
>> through driver
>> specific accessors rather than MMIO.
>> To solve this issue and keep the relevant existing peripherals'
>> drivers untouched,
>> this patchset:
>> - introduces a generic I/O space management framework, logical PIO,
>> to support
>> I/O operations on host controllers operating either on MMIO
>> buses or on buses
>> requiring specific driver I/O accessors;
>> - redefines the in/out accessors to provide a unified interface for
>> both MMIO
>> and driver specific I/O operations. Using logical PIO, th call of
>> in/out() from
>> the host children drivers, such as ipmi-si, will be redirected to
>> the
>> corresponding device-specific I/O hooks to perform the I/O
>> accesses.
>>
>> Based on this patch-set, all the I/O accesses to Hip06/Hip07 LPC
>> peripherals can
>> be supported without any changes on the existing ipmi-si driver.
>>
>> The whole patchset has been tested on Hip07 D05 board both using DTB
>> and ACPI.
>>
>
>> V15 thread here: https://lkml.org/lkml/2018/2/26/584
>
> Thanks for an update.
> Though I answered to previous thread.
>
> Summary: I'm fine with the series as long as maintainers are fine
> (Rafael et al.). On personal side I think that the handler approach is
> better. Details are in v15 thread.
Hi Andy,
Thanks for your input and continued support. As I mentioned in reply in
v15, the handler support would (or has) faced issues. And Rafael seems
fine with deferring the probe to the LLDD in Patch #7/9
Anyway, let's wait for any more input.
Much appreciated,
John
>
next prev parent reply other threads:[~2018-03-06 11:36 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-06 10:47 John Garry
2018-03-06 10:47 ` [PATCH v16 1/9] LIB: Introduce a generic PIO mapping method John Garry
2018-03-06 10:47 ` [PATCH v16 2/9] PCI: Remove unused __weak attribute in pci_register_io_range() John Garry
2018-03-06 10:47 ` [PATCH v16 3/9] PCI: Add fwnode handler as input param of pci_register_io_range() John Garry
2018-03-06 10:47 ` [PATCH v16 4/9] PCI: Apply the new generic I/O management on PCI IO hosts John Garry
2018-03-06 10:47 ` [PATCH v16 5/9] OF: Add missing I/O range exception for indirect-IO devices John Garry
2018-03-06 10:47 ` [PATCH v16 6/9] HISI LPC: Support the LPC host on Hip06/Hip07 with DT bindings John Garry
2018-03-06 10:47 ` [PATCH v16 7/9] ACPI / scan: do not enumerate Indirect IO host children John Garry
2018-03-06 10:47 ` [PATCH v16 8/9] HISI LPC: Add ACPI support John Garry
2018-03-06 10:47 ` [PATCH v16 9/9] MAINTAINERS: Add maintainer for HiSilicon LPC driver John Garry
2018-03-06 11:21 ` [PATCH v16 0/9] LPC: legacy ISA I/O support Andy Shevchenko
2018-03-06 11:36 ` John Garry [this message]
2018-03-06 15:30 ` Rafael J. Wysocki
2018-03-06 16:22 ` John Garry
2018-03-13 10:22 ` Rafael J. Wysocki
2018-03-13 10:42 ` John Garry
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=b4459d98-ebd4-7b13-07ec-613845579558@huawei.com \
--to=john.garry@huawei.com \
--cc=agraf@suse.de \
--cc=akpm@linux-foundation.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=andy.shevchenko@gmail.com \
--cc=arnd@arndb.de \
--cc=benh@kernel.crashing.org \
--cc=bhelgaas@google.com \
--cc=dann.frazier@canonical.com \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hanjun.guo@linaro.org \
--cc=joe@perches.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=lorenzo.pieralisi@arm.com \
--cc=mark.rutland@arm.com \
--cc=mika.westerberg@linux.intel.com \
--cc=minyard@acm.org \
--cc=olof@lixom.net \
--cc=rafael@kernel.org \
--cc=rdunlap@infradead.org \
--cc=rjw@rjwysocki.net \
--cc=robh+dt@kernel.org \
--cc=robh@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
all inboxes | Powered by JetHome®