From: Thierry Reding <thierry.reding@gmail.com>
To: Kunihiko Hayashi <hayashi.kunihiko@socionext.com>,
Tejun Heo <tj@kernel.org>,
Patrice Chotard <patrice.chotard@st.com>,
Matthias Brugger <matthias.bgg@gmail.com>
Cc: Hans de Goede <hdegoede@redhat.com>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
linux-ide@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-mediatek@lists.infradead.org
Subject: Re: [PATCH] ata: ahci-platform: add reset control support
Date: Thu, 5 Apr 2018 11:54:29 +0200 [thread overview]
Message-ID: <20180405095429.GA7506@ulmo> (raw)
In-Reply-To: <1521768653-11824-1-git-send-email-hayashi.kunihiko@socionext.com>
[-- Attachment #1: Type: text/plain, Size: 1469 bytes --]
On Fri, Mar 23, 2018 at 10:30:53AM +0900, Kunihiko Hayashi wrote:
> Add support to get and control a list of resets for the device
> as optional and shared. These resets must be kept de-asserted until
> the device is enabled.
>
> This is specified as shared because some SoCs like UniPhier series
> have common reset controls with all ahci controller instances.
>
> Signed-off-by: Kunihiko Hayashi <hayashi.kunihiko@socionext.com>
> ---
> .../devicetree/bindings/ata/ahci-platform.txt | 1 +
> drivers/ata/ahci.h | 1 +
> drivers/ata/libahci_platform.c | 24 +++++++++++++++++++---
> 3 files changed, 23 insertions(+), 3 deletions(-)
This causes a regression on Tegra because we explicitly request the
resets after the call to ahci_platform_get_resources().
From a quick look, ahci_mtk and ahci_st are in the same boat, adding the
corresponding maintainers to Cc.
Patrice, Matthias: does SATA still work for you after this patch? This
has been in linux-next since next-20180327.
Given how this is one of the more hardware-specific bits, perhaps a
better way to do this is to move reset handling into a Uniphier driver
much like Tegra, Mediatek and ST?
That said, I don't see SATA support for any of the Socionext hardware
either in the DT bindings or drivers/ata, so perhaps it'd be best to
back this out again until we have something that's more well tested?
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-04-05 9:54 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-23 1:30 [PATCH] ata: ahci-platform: add reset control support Kunihiko Hayashi
2018-03-23 8:19 ` Hans de Goede
2018-03-26 22:24 ` Rob Herring
2018-04-05 9:54 ` Thierry Reding [this message]
2018-04-05 9:59 ` Thierry Reding
2018-04-05 11:23 ` Kunihiko Hayashi
2018-04-05 11:30 ` Hans de Goede
2018-04-05 13:17 ` Patrice CHOTARD
2018-04-05 13:27 ` Hans de Goede
2018-04-05 13:54 ` Thierry Reding
2018-04-05 14:00 ` Hans de Goede
2018-04-05 14:08 ` Hans de Goede
2018-04-06 4:48 ` Kunihiko Hayashi
2018-04-06 8:29 ` Hans de Goede
2018-04-06 9:36 ` Kunihiko Hayashi
2018-04-06 10:12 ` Hans de Goede
2018-04-09 11:59 ` Thierry Reding
[not found] ` <1f7d0738-1963-21c5-c293-e46fb0214ecf-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2018-04-05 14:00 ` Patrice CHOTARD
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=20180405095429.GA7506@ulmo \
--to=thierry.reding@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=hayashi.kunihiko@socionext.com \
--cc=hdegoede@redhat.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=matthias.bgg@gmail.com \
--cc=patrice.chotard@st.com \
--cc=robh+dt@kernel.org \
--cc=tj@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).