From: Florian Fainelli <f.fainelli@gmail.com>
To: Matthew Hagan <mnhagan88@gmail.com>
Cc: devicetree@vger.kernel.org,
Florian Fainelli <f.fainelli@gmail.com>,
Scott Branden <sbranden@broadcom.com>,
Ray Jui <rjui@broadcom.com>, Russell King <linux@armlinux.org.uk>,
Rob Herring <robh+dt@kernel.org>,
bcm-kernel-feedback-list@broadcom.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/3] ARM: dts: NSP: Disable PL330 by default, add dma-coherent property
Date: Sun, 14 Jun 2020 15:17:43 -0700 [thread overview]
Message-ID: <9e83df99-fae3-107d-3983-1e79d9591e00@gmail.com> (raw)
In-Reply-To: <c19be985a3e7abc8ac05fc30678475aeadb73c50.1591719237.git.mnhagan88@gmail.com>
On 6/9/2020 9:58 AM, Matthew Hagan wrote:
> Currently the PL330 is enabled by default. However if left in IDM reset, as is
> the case with the Meraki and Synology NSP devices, the system will hang when
> probing for the PL330's AMBA peripheral ID. We therefore should be able to
> disable it in these cases.
>
> The PL330 is also included among of the list of peripherals put into coherent
> mode, so "dma-coherent" has been added here as well.
>
> Signed-off-by: Matthew Hagan <mnhagan88@gmail.com>
Applied to devicetree/fixes with:
Fixes: 5fa1026a3e4d ("ARM: dts: NSP: Add PL330 support")
Thanks!
--
Florian
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2020-06-14 22:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-09 16:58 [PATCH 1/3] ARM: dts: NSP: Disable PL330 by default, add dma-coherent property Matthew Hagan
2020-06-09 16:58 ` [PATCH 2/3] ARM: dts: NSP: Correct amac_base lengths, mailbox reg and add amac3 Matthew Hagan
2020-06-14 22:28 ` Florian Fainelli
2020-06-16 20:19 ` Matthew Hagan
2020-06-17 21:54 ` Florian Fainelli
2020-06-09 16:58 ` [PATCH 3/3] ARM: bcm: Select ARM_TIMER_SP804 for ARCH_BCM_NSP Matthew Hagan
2020-06-14 22:15 ` Florian Fainelli
2020-06-14 22:17 ` 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=9e83df99-fae3-107d-3983-1e79d9591e00@gmail.com \
--to=f.fainelli@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux@armlinux.org.uk \
--cc=mnhagan88@gmail.com \
--cc=rjui@broadcom.com \
--cc=robh+dt@kernel.org \
--cc=sbranden@broadcom.com \
/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).