public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Ard Biesheuvel <ard.biesheuvel@linaro.org>
To: Leif Lindholm <leif.lindholm@linaro.org>
Cc: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: [PATCH edk2-platforms v2] Silicon/SynQuacer: enable coherent DMA for NETSEC and eMMC
Date: Fri, 1 Dec 2017 17:53:55 +0000	[thread overview]
Message-ID: <CAKv+Gu9_WrRZdRmQb9QKvq=yX7ntuRfQCvbEeOZ6knfwNV_9GA@mail.gmail.com> (raw)
In-Reply-To: <20171201125719.ffca5swpw5wajlwz@bivouac.eciton.net>

On 1 December 2017 at 12:57, Leif Lindholm <leif.lindholm@linaro.org> wrote:
> On Thu, Nov 30, 2017 at 06:53:55PM +0000, Ard Biesheuvel wrote:
>> As it turns out, it is surprisingly easy to configure both the NETSEC
>> and eMMC devices as cache coherent for DMA, given that they are both
>> behind the same SMMU which is already configured in passthrough mode
>> by the firmware running on the SCP.
>>
>> So update the static SMMU configuration to make memory accesses performed
>> by these devices inner shareable inner/outer writeback cacheable, which
>> makes them cache coherent with the CPUs.
>>
>> Contributed-under: TianoCore Contribution Agreement 1.1
>> Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
>
> Looks fine to me:
> Reviewed-by: Leif Lindholm <leif.lindholm@linaro.org>
> (If you want to hold back for Tested-by:s, feel free to.)
>

Thanks. It actually depends on the patch that adds the EMMC driver
stack, which depends on the SD/MMC override patches for EDK2, so it
needs to wait anyway.


  reply	other threads:[~2017-12-01 17:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-30 18:53 [PATCH edk2-platforms v2] Silicon/SynQuacer: enable coherent DMA for NETSEC and eMMC Ard Biesheuvel
2017-12-01 12:57 ` Leif Lindholm
2017-12-01 17:53   ` Ard Biesheuvel [this message]
2017-12-07 13:49     ` Ard Biesheuvel

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+Gu9_WrRZdRmQb9QKvq=yX7ntuRfQCvbEeOZ6knfwNV_9GA@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