Linux clock framework development
 help / color / mirror / Atom feed
From: maxime@cerno.tech
To: Dom Cobley <dom@raspberrypi.com>
Cc: Stefan Wahren <stefan.wahren@i2se.com>,
	Mike Turquette <mturquette@baylibre.com>,
	Stephen Boyd <sboyd@kernel.org>,
	Florian Fainelli <f.fainelli@gmail.com>,
	Broadcom internal kernel review list 
	<bcm-kernel-feedback-list@broadcom.com>,
	linux-clk@vger.kernel.org,
	Dave Stevenson <dave.stevenson@raspberrypi.com>,
	Phil Elwell <phil@raspberrypi.com>,
	Tim Gover <tim.gover@raspberrypi.com>
Subject: Re: BCM2835 clock driver, power domains and CLK_SET_RATE_GATE
Date: Mon, 24 Oct 2022 11:44:56 +0200	[thread overview]
Message-ID: <20221024094456.yz7thvtbsqb57c3h@houat> (raw)
In-Reply-To: <CANUESCHbXTC3Z6JgZLq6Em=1ftK0nJuryVRcK=kWVnRE1Zy1Vw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 653 bytes --]

Hi Dom,

On Fri, Oct 21, 2022 at 03:26:23PM +0100, Dom Cobley wrote:
> I believe our view is that clk-bcm2835 is fundamentally unsafe, as it
> writes to registers the firmware is in control of, and any calls should be
> migrated to clk-raspberrypi which should be safe.
> 
> If there are any missing features of clk-raspberrypi, then we can support
> them.

Thanks for your input. I'm inclined to send a patch switching over to
the firmware clocks for the HDMI controller then.

There's one thing that isn't really clear to me, is there any difference
in terms of firmware capabilities between all the RPi0-3 versions?

Thanks!
Maxime

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

      parent reply	other threads:[~2022-10-24  9:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-21 14:05 BCM2835 clock driver, power domains and CLK_SET_RATE_GATE maxime
2022-10-21 18:51 ` Stefan Wahren
     [not found] ` <CANUESCHbXTC3Z6JgZLq6Em=1ftK0nJuryVRcK=kWVnRE1Zy1Vw@mail.gmail.com>
2022-10-24  9:44   ` maxime [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=20221024094456.yz7thvtbsqb57c3h@houat \
    --to=maxime@cerno.tech \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=dave.stevenson@raspberrypi.com \
    --cc=dom@raspberrypi.com \
    --cc=f.fainelli@gmail.com \
    --cc=linux-clk@vger.kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=phil@raspberrypi.com \
    --cc=sboyd@kernel.org \
    --cc=stefan.wahren@i2se.com \
    --cc=tim.gover@raspberrypi.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