From: Florian Fainelli <f.fainelli@gmail.com>
To: bcm-kernel-feedback-list@broadcom.com,
Matthew Hagan <mnhagan88@gmail.com>
Cc: Rob Herring <robh+dt@kernel.org>, Ray Jui <rjui@broadcom.com>,
Scott Branden <sbranden@broadcom.com>,
Viresh Kumar <viresh.kumar@linaro.org>,
Krzysztof Kozlowski <krzk@kernel.org>,
Geert Uytterhoeven <geert+renesas@glider.be>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 3/3] ARM: dts: NSP: enable DMA on bcm988312hr
Date: Thu, 24 Jun 2021 15:31:17 -0700 [thread overview]
Message-ID: <20210624223117.1315078-1-f.fainelli@gmail.com> (raw)
In-Reply-To: <20210610203524.2215918-3-mnhagan88@gmail.com>
On Thu, 10 Jun 2021 21:35:12 +0100, Matthew Hagan <mnhagan88@gmail.com> wrote:
> The previous patch "ARM: dts: NSP: Disable PL330 by default, add
> dma-coherent property" set the DMAC to disabled by default, requiring it
> to be manually enabled on each device. The bcm988312hr was mistakenly
> omitted. This patch adds it back.
>
> Signed-off-by: Matthew Hagan <mnhagan88@gmail.com>
> ---
Applied to https://github.com/Broadcom/stblinux/commits/devicetree/next, thanks!
--
Florian
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-06-24 22:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-10 20:35 [PATCH 1/3] ARM: dts: NSP: add device names to compatible Matthew Hagan
2021-06-10 20:35 ` [PATCH 2/3] dt-bindings: arm: bcm: add NSP devices to SoCs Matthew Hagan
2021-06-24 19:01 ` Rob Herring
2021-06-24 22:30 ` Florian Fainelli
2021-06-10 20:35 ` [PATCH 3/3] ARM: dts: NSP: enable DMA on bcm988312hr Matthew Hagan
2021-06-24 22:31 ` Florian Fainelli [this message]
2021-06-24 22:29 ` [PATCH 1/3] ARM: dts: NSP: add device names to compatible Florian Fainelli
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=20210624223117.1315078-1-f.fainelli@gmail.com \
--to=f.fainelli@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mnhagan88@gmail.com \
--cc=rjui@broadcom.com \
--cc=robh+dt@kernel.org \
--cc=sbranden@broadcom.com \
--cc=viresh.kumar@linaro.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).