From: Ard Biesheuvel <ard.biesheuvel@linaro.org>
To: Marcin Wojtas <mw@semihalf.com>
Cc: edk2-devel-01 <edk2-devel@lists.01.org>,
"Tian, Feng" <feng.tian@intel.com>,
"Kinney, Michael D" <michael.d.kinney@intel.com>,
"Gao, Liming" <liming.gao@intel.com>,
"Leif Lindholm" <leif.lindholm@linaro.org>,
"Jan Dąbroś" <jsd@semihalf.com>
Subject: Re: [PATCH v2] MdeModulePkg/AtaAtapiPassThru: Ensure GHC.AE bit is always set in Ahci
Date: Thu, 24 Nov 2016 08:02:06 +0000 [thread overview]
Message-ID: <CAKv+Gu-ALTyv8EArMGGYr4+yb_hGm0ZwGZTZftHUx7gtpyrRBg@mail.gmail.com> (raw)
In-Reply-To: <CAPv3WKfzqTADmhdg81g6+h2Fh1W=Hk24a7_ptrP6f027RCoV-A@mail.gmail.com>
On 24 November 2016 at 08:01, Marcin Wojtas <mw@semihalf.com> wrote:
> Hi Ard,
>
> 2016-11-24 8:56 GMT+01:00 Ard Biesheuvel <ard.biesheuvel@linaro.org>:
>> On 24 November 2016 at 07:54, Marcin Wojtas <mw@semihalf.com> wrote:
>>> According to AHCI Spec 1.3 GHC.AE bit description:
>>> "The implementation of this bit is dependent upon the value of the
>>> CAP.SAM bit. If CAP.SAM is '0', then GHC.AE shall be read-write and shall
>>> have a reset value of '0'. If CAP.SAM is '1', then AE shall be read-only
>>> and shall have a reset value of '1'."
>>>
>>> Being in AhciMode, for proper operation it is required, that GHC.AE bit
>>> is always set, before any other AHCI registers are written to. Current
>>> AhciMode implementation, both in AhciReset() and AhciModeInitialization()
>>> functions, set GHC.AE bit only depending on 'CAP.SAM == 0' condition,
>>> assuming (according to the AHCI spec), that otherwise it has to be set
>>> anyway. It may however happen, that even if 'CAP.SAM == 1', GHC.AE
>>> requires updating by software.
>>>
>>> This patch enables in AhciMode setting GHC.AE in case its initial value
>>> is '0'. It fixes AHCI support for Marvell Armada 70x0 and 80x0 SoC
>>> families. The change is transparent to all other platforms.
>>>
>>> Contributed-under: TianoCore Contribution Agreement 1.0
>>> Signed-off-by: Marcin Wojtas <mw@semihalf.com>
>>> Signed-off-by: Jan Dabros <jsd@semihalf.com>
>>>
>>> ---
>>> Changelog:
>>> v1 -> v2
>>>
>>> * Instead of doing it uncoditionally, enable setting GHC.AE bit only in
>>> case its initial value is '0'
>>>
>>> ---
>>> MdeModulePkg/Bus/Ata/AtaAtapiPassThru/AhciMode.c | 21 ++++++++++-----------
>>> 1 file changed, 10 insertions(+), 11 deletions(-)
>>>
>>> diff --git a/MdeModulePkg/Bus/Ata/AtaAtapiPassThru/AhciMode.c b/MdeModulePkg/Bus/Ata/AtaAtapiPassThru/AhciMode.c
>>> index 533d201..4d01c1d 100644
>>> --- a/MdeModulePkg/Bus/Ata/AtaAtapiPassThru/AhciMode.c
>>> +++ b/MdeModulePkg/Bus/Ata/AtaAtapiPassThru/AhciMode.c
>>> @@ -1451,17 +1451,13 @@ AhciReset (
>>> {
>>> UINT64 Delay;
>>> UINT32 Value;
>>> - UINT32 Capability;
>>>
>>> //
>>> - // Collect AHCI controller information
>>> - //
>>> - Capability = AhciReadReg (PciIo, EFI_AHCI_CAPABILITY_OFFSET);
>>> -
>>> - //
>>> - // Enable AE before accessing any AHCI registers if Supports AHCI Mode Only is not set
>>> + // Make sure that GHC.AE bit is set before accessing any AHCI registers.
>>> //
>>> - if ((Capability & EFI_AHCI_CAP_SAM) == 0) {
>>> + Value = AhciReadReg(PciIo, EFI_AHCI_GHC_OFFSET);
>>> +
>>> + if ((Value & EFI_AHCI_GHC_ENABLE) == 0) {
>>> AhciOrReg (PciIo, EFI_AHCI_GHC_OFFSET, EFI_AHCI_GHC_ENABLE);
>>> }
>>>
>>
>> If we are ignoring the capability bits now, do we still need to read them?
>
> In the context above (AhciReset() function) reading capability is
> removed. In AhciModeInitialization() however, it has to remain,
> because of following lines:
>
> //
> // Enable 64-bit DMA support in the PCI layer if this controller
> // supports it.
> //
> if ((Capability & EFI_AHCI_CAP_S64A) != 0) {
>
> Which, I can see, were added by you:)
>
Ah, apologies, I misread the patch.
In that case
Reviewed-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
next prev parent reply other threads:[~2016-11-24 8:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-24 7:54 [PATCH v2] MdeModulePkg/AtaAtapiPassThru: Ensure GHC.AE bit is always set in Ahci Marcin Wojtas
2016-11-24 7:56 ` Ard Biesheuvel
2016-11-24 8:01 ` Marcin Wojtas
2016-11-24 8:02 ` Ard Biesheuvel [this message]
2016-11-24 8:35 ` Tian, Feng
2016-11-24 9:07 ` Marcin Wojtas
2016-11-24 15:57 ` Ard Biesheuvel
2016-11-24 16:06 ` Marcin Wojtas
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-list 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=CAKv+Gu-ALTyv8EArMGGYr4+yb_hGm0ZwGZTZftHUx7gtpyrRBg@mail.gmail.com \
--to=devel@edk2.groups.io \
/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