All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marek Vasut <marex@denx.de>
To: Adam Ford <aford173@gmail.com>,
	Tommaso Merciai <tommaso.merciai@amarulasolutions.com>
Cc: U-Boot Mailing List <u-boot@lists.denx.de>,
	Lukasz Majewski <lukma@denx.de>,
	Sean Anderson <seanga2@gmail.com>,
	Fabio Estevam <festevam@gmail.com>,
	Tim Harvey <tharvey@gateworks.com>,
	Michael Trimarchi <michael@amarulasolutions.com>
Subject: Re: imx8mm eLCDIF clock
Date: Thu, 21 Apr 2022 13:20:58 +0200	[thread overview]
Message-ID: <b96ddda9-0c21-49bb-824a-dedc506d9708@denx.de> (raw)
In-Reply-To: <CAHCN7xJZMLq3C29Pp_bVH8RuQyNgCBqiqFOPACoMnEoyh7CrNA@mail.gmail.com>

On 4/21/22 13:14, Adam Ford wrote:
> On Thu, Apr 21, 2022 at 5:29 AM Tommaso Merciai
> <tommaso.merciai@amarulasolutions.com> wrote:
>>
>> On Thu, Apr 21, 2022 at 08:48:05AM +0200, Tommaso Merciai wrote:
>>
>> + Fabio
>> + Tim
>> + Michael
>> + Marek
>> + Adam
>>
>>> 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 clk_enable 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?
>>> I'm missing somethings?
> 
> I think the LCD driver should request the clock and clock rate based
> on settings the device tree.  However, I think the bigger issues is
> that you might run into issues with the lack of a disp-blkctrl driver.
> Marek enable the GPC driver fairly recently, but the blkctrl driver
> will be needed to enable the LCD and DSI portions or the system may
> hang.

Just boot quickly and init the graphics pipeline in Linux ?

  reply	other threads:[~2022-04-21 11:21 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 [this message]
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
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=b96ddda9-0c21-49bb-824a-dedc506d9708@denx.de \
    --to=marex@denx.de \
    --cc=aford173@gmail.com \
    --cc=festevam@gmail.com \
    --cc=lukma@denx.de \
    --cc=michael@amarulasolutions.com \
    --cc=seanga2@gmail.com \
    --cc=tharvey@gateworks.com \
    --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.