From: Florian Fainelli <f.fainelli@gmail.com>
To: Matthew Hagan <mnhagan88@gmail.com>
Cc: Florian Fainelli <f.fainelli@gmail.com>,
Vladimir Oltean <olteanv@gmail.com>, Andrew Lunn <andrew@lunn.ch>,
Vivek Unune <npcomplete13@gmail.com>,
Rob Herring <robh+dt@kernel.org>, Ray Jui <rjui@broadcom.com>,
Scott Branden <sbranden@broadcom.com>,
bcm-kernel-feedback-list@broadcom.com,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/4] ARM: dts: NSP: disable sp804 ccbtimers by default
Date: Sun, 13 Jun 2021 09:22:49 -0700 [thread overview]
Message-ID: <89d2a415-a9a3-f778-bd40-e39e01e219ef@gmail.com> (raw)
In-Reply-To: <20210613094639.3242151-2-mnhagan88@gmail.com>
On 6/13/2021 2:46 AM, Matthew Hagan wrote:
> The sp804 ccbtimers are enabled by default, however they may or may not
> be present on the board. This patch disables them by default, requiring
> them to be enabled only where applicable.
The timers are always part of the SoC, so they should always be enabled,
and if there was some board specific wiring, in that maybe one of the
times was fed a different clock source than iprocslow, we could deal
with that on a per-board basis.
If someone does not want a specific timer to be used, it could be
unbound once the kernel has booted for instance.
--
Florian
next prev parent reply other threads:[~2021-06-13 16:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-13 9:46 [PATCH 1/4] ARM: dts: NSP: disable qspi node by default Matthew Hagan
2021-06-13 9:46 ` [PATCH 2/4] ARM: dts: NSP: disable sp804 ccbtimers " Matthew Hagan
2021-06-13 16:22 ` Florian Fainelli [this message]
2021-06-13 19:46 ` Matthew Hagan
2021-06-13 9:46 ` [PATCH 3/4] ARM: dts: NSP: add MDIO bus controller node Matthew Hagan
2021-06-24 22:34 ` Florian Fainelli
2021-06-13 9:46 ` [PATCH 4/4] ARM: dts: NSP: Move USB3 PHY to internal MDIO bus Matthew Hagan
2021-06-24 22:34 ` Florian Fainelli
2021-06-24 22:33 ` [PATCH 1/4] ARM: dts: NSP: disable qspi node by default 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=89d2a415-a9a3-f778-bd40-e39e01e219ef@gmail.com \
--to=f.fainelli@gmail.com \
--cc=andrew@lunn.ch \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mnhagan88@gmail.com \
--cc=npcomplete13@gmail.com \
--cc=olteanv@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).