From: Florian Fainelli <f.fainelli@gmail.com>
To: Jim Quinlan <jim2101024@gmail.com>,
Philipp Zabel <p.zabel@pengutronix.de>,
Hans de Goede <hdegoede@redhat.com>, Jens Axboe <axboe@kernel.dk>,
bcm-kernel-feedback-list@broadcom.com,
james.quinlan@broadcom.com
Cc: "moderated list:BROADCOM BCM2711/BCM2835 ARM ARCHITECTURE"
<linux-arm-kernel@lists.infradead.org>,
"open list:LIBATA SUBSYSTEM (Serial and Parallel ATA drivers)"
<linux-ide@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
"open list:PCI NATIVE HOST BRIDGE AND ENDPOINT DRIVERS"
<linux-pci@vger.kernel.org>,
"moderated list:BROADCOM BCM2711/BCM2835 ARM ARCHITECTURE"
<linux-rpi-kernel@lists.infradead.org>,
Rob Herring <robh@kernel.org>
Subject: Re: [RESEND PATCH v3 0/2] ata: ahci_brcm: Fix use of BCM7216 reset controller
Date: Tue, 5 Jan 2021 13:22:11 -0800 [thread overview]
Message-ID: <ece90017-4b7d-d5bb-e868-9b63909be5f3@gmail.com> (raw)
In-Reply-To: <92084293-d2fd-1663-0f6a-a10f01e23066@gmail.com>
On 12/23/20 4:05 PM, Florian Fainelli wrote:
>
>
> On 12/16/2020 1:41 PM, Jim Quinlan wrote:
>> v3 -- discard commit from v2; instead rely on the new function
>> reset_control_rearm provided in a recent commit [1] applied
>> to reset/next.
>> -- New commit to correct pcie-brcmstb.c usage of a reset controller
>> to use reset/rearm verses deassert/assert.
>>
>> v2 -- refactor rescal-reset driver to implement assert/deassert rather than
>> reset because the reset call only fires once per lifetime and we need
>> to reset after every resume from S2 or S3.
>> -- Split the use of "ahci" and "rescal" controllers in separate fields
>> to keep things simple.
>>
>> v1 -- original
>>
>>
>> [1] Applied commit "reset: make shared pulsed reset controls re-triggerable"
>> found at git://git.pengutronix.de/git/pza/linux.git
>> branch reset/shared-retrigger
>
> The changes in that branch above have now landed in Linus' tree with:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=557acb3d2cd9c82de19f944f6cc967a347735385
>
> It would be good if we could get both patches applied via the same tree
> or within the same cycle to avoid having either PCIe or SATA broken on
> these platforms.
Ping? Can someone apply those patches if you are happy with them? Thank you.
--
Florian
next prev parent reply other threads:[~2021-01-05 21:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-16 21:41 [RESEND PATCH v3 0/2] ata: ahci_brcm: Fix use of BCM7216 reset controller Jim Quinlan
2020-12-16 21:41 ` [RESEND PATCH v3 1/2] " Jim Quinlan
2020-12-16 21:59 ` Florian Fainelli
2020-12-16 21:41 ` [RESEND PATCH v3 2/2] PCI: brcmstb: use reset/rearm instead of deassert/assert Jim Quinlan
2020-12-16 22:02 ` Florian Fainelli
2020-12-24 0:05 ` [RESEND PATCH v3 0/2] ata: ahci_brcm: Fix use of BCM7216 reset controller Florian Fainelli
2021-01-05 21:22 ` Florian Fainelli [this message]
2021-01-14 20:46 ` Florian Fainelli
2021-01-21 20:48 ` Florian Fainelli
2021-01-22 0:20 ` Bjorn Helgaas
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=ece90017-4b7d-d5bb-e868-9b63909be5f3@gmail.com \
--to=f.fainelli@gmail.com \
--cc=axboe@kernel.dk \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=hdegoede@redhat.com \
--cc=james.quinlan@broadcom.com \
--cc=jim2101024@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=p.zabel@pengutronix.de \
--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;
as well as URLs for NNTP newsgroup(s).