public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Xuyang Dong" <dongxuyang@eswincomputing.com>
To: "Bo Gan" <ganboing@gmail.com>,
	mturquette@baylibre.com, sboyd@kernel.org, robh@kernel.org,
	krzk+dt@kernel.org, conor+dt@kernel.org,
	linux-clk@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, troy.mitchell@linux.dev,
	bmasney@redhat.com
Cc: ningyu@eswincomputing.com, linmin@eswincomputing.com,
	huangyifeng@eswincomputing.com, pinkesh.vaghela@einfochips.com,
	marcel@ziswiler.com
Subject: Re: Re: [PATCH v13 0/3] Add driver support for ESWIN eic700 SoC clock controller
Date: Tue, 24 Feb 2026 17:09:42 +0800 (GMT+08:00)	[thread overview]
Message-ID: <41d3bf12.387f.19c8ee9570e.Coremail.dongxuyang@eswincomputing.com> (raw)
In-Reply-To: <ae2358d7-7e82-49fe-8a03-195487a7b010@gmail.com>

> Hi ESWIN folks,
> 
> I'm testing your patchset on
> https://github.com/ganboing/linux-eic77/tree/eic77-integration-test-clk-v13
> 
> It's applied on top of Samuel's PMA v3 patshset, plus device-tree patches
> from your integration test branch. It's pretty similar to what Marcel did,
> but I just want to have a separate verification. What I found is that the
> kernel can successfully boot with clk_ignore_unused (eMMC/eth working),
> but hangs without. It stuck at
> 
> [    3.257141] clk: Disabling unused clocks
> 
> I'm pretty sure that some clocks that weren't supposed to get disabled got
> turned off. Can you validate if that's a bug in the clock driver, or my
> device-tree just didn't link all clocks. One thing I noticed is that there
> is no CLK_IS_CRITICAL in your code, so it's highly likely that DDR PLL or
> others were turned off unintentionally. Not a clock driver expert, but I'd
> expect the kernel should work fine without clk_ignore_unused.
> 

Hi Bo,

Thanks for your reply. I also got the same result without clk_ignore_unused. 
This is a bug, and I will address it in v14.

Regards,
Xuyang Dong

  reply	other threads:[~2026-02-24  9:09 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-14 10:14 [PATCH v13 0/3] Add driver support for ESWIN eic700 SoC clock controller dongxuyang
2026-02-14 10:15 ` [PATCH v13 1/3] dt-bindings: clock: eswin: Documentation for eic7700 SoC dongxuyang
2026-02-14 10:15 ` [PATCH v13 2/3] clk: eswin: Add eic7700 clock driver dongxuyang
2026-02-16 17:17   ` Brian Masney
2026-02-17  1:09     ` Brian Masney
2026-02-19 13:14     ` Marcel Ziswiler
2026-02-25  6:55     ` Xuyang Dong
2026-02-25 13:29       ` Brian Masney
2026-02-14 10:15 ` [PATCH v13 3/3] MAINTAINERS: Add entry for ESWIN EIC7700 " dongxuyang
2026-02-24  8:46 ` [PATCH v13 0/3] Add driver support for ESWIN eic700 SoC clock controller Bo Gan
2026-02-24  9:09   ` Xuyang Dong [this message]
2026-02-24 11:33     ` Brian Masney

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=41d3bf12.387f.19c8ee9570e.Coremail.dongxuyang@eswincomputing.com \
    --to=dongxuyang@eswincomputing.com \
    --cc=bmasney@redhat.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=ganboing@gmail.com \
    --cc=huangyifeng@eswincomputing.com \
    --cc=krzk+dt@kernel.org \
    --cc=linmin@eswincomputing.com \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcel@ziswiler.com \
    --cc=mturquette@baylibre.com \
    --cc=ningyu@eswincomputing.com \
    --cc=pinkesh.vaghela@einfochips.com \
    --cc=robh@kernel.org \
    --cc=sboyd@kernel.org \
    --cc=troy.mitchell@linux.dev \
    /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