linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Florian Fainelli <f.fainelli@gmail.com>
To: Florian Fainelli <f.fainelli@gmail.com>,
	linux-kernel@vger.kernel.org, axboe@kernel.dk
Cc: bcm-kernel-feedback-list@broadcom.com,
	Hans de Goede <hdegoede@redhat.com>,
	"open list:LIBATA SUBSYSTEM (Serial and Parallel ATA drivers)" 
	<linux-ide@vger.kernel.org>
Subject: Re: [PATCH] ata: ahci_brcm: Add back regulators management
Date: Thu, 21 Jan 2021 12:47:30 -0800	[thread overview]
Message-ID: <1cc0cacd-7ab2-c11e-db5c-363c69991f1e@gmail.com> (raw)
In-Reply-To: <057c3619-022f-1d79-6c9d-51f9085ea963@gmail.com>



On 1/14/2021 12:46 PM, Florian Fainelli wrote:
> On 12/23/20 2:41 PM, Florian Fainelli wrote:
>> While reworking the resources management and departing from using
>> ahci_platform_enable_resources() which did not allow a proper step
>> separation like we need, we unfortunately lost the ability to control
>> AHCI regulators. This broke some Broadcom STB systems that do expect
>> regulators to be turned on to link up with attached hard drives.
>>
>> Fixes: c0cdf2ac4b5b ("ata: ahci_brcm: Fix AHCI resources management")
>> Signed-off-by: Florian Fainelli <f.fainelli@gmail.com>
>> ---
>> Jens,
>>
>> This is based on your for-next branch, let me know if you need me to
>> rebase to a different branch. Thanks!
> 
> Jens, this is a bug fix so it would be nice to get this applied at some> point. Thank you

Jens, can you apply this patch or let me know if you need me to change
something? Thanks
-- 
Florian

      reply	other threads:[~2021-01-21 20:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-23 22:41 [PATCH] ata: ahci_brcm: Add back regulators management Florian Fainelli
2021-01-14 20:46 ` Florian Fainelli
2021-01-21 20:47   ` Florian Fainelli [this message]

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=1cc0cacd-7ab2-c11e-db5c-363c69991f1e@gmail.com \
    --to=f.fainelli@gmail.com \
    --cc=axboe@kernel.dk \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=hdegoede@redhat.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.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).