From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: John Garry <john.garry@huawei.com>,
xuwei5@huawei.com, mika.westerberg@linux.intel.com,
lee.jones@linaro.org
Cc: rjw@rjwysocki.net, linux-kernel@vger.kernel.org, arnd@arndb.de,
graeme.gregory@linaro.org, helgaas@kernel.org,
z.liuxinliang@hisilicon.com, linuxarm@huawei.com
Subject: Re: [PATCH v2 0/3] HISI LPC ACPI UART support
Date: Tue, 08 May 2018 14:17:40 +0300 [thread overview]
Message-ID: <1f8dd53826554a113b03b7c0fb2d131bb315eefd.camel@linux.intel.com> (raw)
In-Reply-To: <1525775252-239214-1-git-send-email-john.garry@huawei.com>
On Tue, 2018-05-08 at 18:27 +0800, John Garry wrote:
> This patchset adds ACPI FW support for the UART on
> the LPC bus on the Huawei D03 development board.
>
> It also drops MFD API usage. It's not right to use MFD
> APIs outside drivers/mfd. As the alternate solution, we
> use platform device APIs directly.
>
> The UART is 8250-compatible, and has the following
> profile:
> - IO space iotype
> - no interrupt, so polling mode required
> - 16550 type
>
> Currently no platform driver exists for the UART. Indeed,
> for PNP-compatible devices - like this UART - it would be
> better to create a PNP device so that we may use the
> existing PNP driver. Thus, we should use the 8250 PNP
> driver.
>
> However this host driver does not support PNP devices.
> An RFC was sent for PNP support in [1]. However it was
> deemed impractical to follow this path.
>
> So to provide this UART support we use the 8250 generic
> isa driver. For this, we need to set the UART platform
> device name to match the 8250 isa driver. This means
> passing the 8250 serial config in the child pdev platform
> data.
>
> 1. https://lkml.org/lkml/2018/4/20/278
>
I'm fine with this least invasive approach. It seems it has minimum
duplication of code, which is anyway unavoidable when we are speaking of
instantiating platform devices.
FWIW,
Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> Differences:
> v1 -> v2:
> - drop MFD API usage and use platform device APIs
> directly for ACPI support
>
> RFC -> v1:
> - drop PNP support
> - use static MFD cells
> - add 8250 setup
>
> John Garry (3):
> HISI LPC: Stop using MFD APIs
> HISI LPC: Re-Add ACPI child enumeration support
> HISI LPC: Add ACPI UART support
>
> drivers/bus/Kconfig | 1 -
> drivers/bus/hisi_lpc.c | 159 ++++++++++++++++++++++++++++++--------
> -----------
> 2 files changed, 97 insertions(+), 63 deletions(-)
>
--
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy
next prev parent reply other threads:[~2018-05-08 11:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-08 10:27 [PATCH v2 0/3] HISI LPC ACPI UART support John Garry
2018-05-08 10:27 ` [PATCH v2 1/3] HISI LPC: Stop using MFD APIs John Garry
2018-05-08 10:27 ` [PATCH v2 2/3] HISI LPC: Re-Add ACPI child enumeration support John Garry
2018-05-08 10:27 ` [PATCH v2 3/3] HISI LPC: Add ACPI UART support John Garry
2018-05-08 11:17 ` Andy Shevchenko [this message]
2018-05-09 14:48 ` [PATCH v2 0/3] HISI LPC " John Garry
2018-05-11 14:02 ` Wei Xu
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=1f8dd53826554a113b03b7c0fb2d131bb315eefd.camel@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=arnd@arndb.de \
--cc=graeme.gregory@linaro.org \
--cc=helgaas@kernel.org \
--cc=john.garry@huawei.com \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=mika.westerberg@linux.intel.com \
--cc=rjw@rjwysocki.net \
--cc=xuwei5@huawei.com \
--cc=z.liuxinliang@hisilicon.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