All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sean Anderson <seanga2@gmail.com>
To: Tommaso Merciai <tommaso.merciai@amarulasolutions.com>,
	u-boot@lists.denx.de
Cc: Lukasz Majewski <lukma@denx.de>
Subject: Re: imx8mm eLCDIF clock
Date: Thu, 21 Apr 2022 20:09:59 -0400	[thread overview]
Message-ID: <d9827a78-a4d1-11f0-d145-edf02d8c2745@gmail.com> (raw)
In-Reply-To: <20220421064805.GA2335@tom-ThinkPad-T14s-Gen-2i>

On 4/21/22 2:48 AM, Tommaso Merciai wrote:
> Hi,
> I'm working on drivers/clk/imx/clk-imx8mm.c to port and bring up eLCDIF
> clocks. After port all necessary clocks needed by eLCDIF I found that
> IMX8MM_VIDEO_PLL1 clock is not enabled and need the following code to enable
> it at the end of the clk-imx8mm probe:
> 
> struct clk *clkp;
> 
> clk_get_by_id(IMX8MM_VIDEO_PLL1, &clkp);
> clk_set_rate(clkp, 594000000UL);
> clk_enable(clkp);
> 
> What do you think about this solution?
> There is a more standard way to do this?

PLL1 should be a parent of one of the clocks required by the eLCDIF. That clock
should call clk_enable() on PLL1 when it is enabled itself. If you want to set
a specific rate, you can do that with assigned-clock-rates in either the clock's
DT node, or the eLCDIF's DT node.

--Sean

  parent reply	other threads:[~2022-04-22  0:10 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-21  6:48 imx8mm eLCDIF clock Tommaso Merciai
2022-04-21 10:29 ` Tommaso Merciai
2022-04-21 11:14   ` Adam Ford
2022-04-21 11:20     ` Marek Vasut
2022-04-21 11:54       ` Tommaso Merciai
2022-04-21 12:01         ` Marek Vasut
2022-04-21 12:03           ` Stefano Babic
2022-04-21 12:05             ` Adam Ford
2022-04-21 12:08               ` Michael Nazzareno Trimarchi
2022-04-21 11:50     ` Tommaso Merciai
2022-04-22  0:09 ` Sean Anderson [this message]
2022-04-22  6:39   ` Tommaso Merciai
2022-05-27  3:41     ` Sean Anderson

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=d9827a78-a4d1-11f0-d145-edf02d8c2745@gmail.com \
    --to=seanga2@gmail.com \
    --cc=lukma@denx.de \
    --cc=tommaso.merciai@amarulasolutions.com \
    --cc=u-boot@lists.denx.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.