public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Abel Vesa <abel.vesa@linaro.org>
To: Stephen Boyd <sboyd@kernel.org>,
	LI Qingwu <qing-wu.li@leica-geosystems.com.cn>
Cc: LI Qingwu <qing-wu.li@leica-geosystems.com.cn>,
	Peng Fan <peng.fan@nxp.com>,
	"abelvesa@kernel.org" <abelvesa@kernel.org>,
	"mturquette@baylibre.com" <mturquette@baylibre.com>,
	"shawnguo@kernel.org" <shawnguo@kernel.org>,
	"s.hauer@pengutronix.de" <s.hauer@pengutronix.de>,
	"kernel@pengutronix.de" <kernel@pengutronix.de>,
	"festevam@gmail.com" <festevam@gmail.com>,
	"linux-imx@nxp.com" <linux-imx@nxp.com>,
	"linux-clk@vger.kernel.org" <linux-clk@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"18701859600@163.com" <18701859600@163.com>,
	GEO-CHHER-bsp-development 
	<bsp-development.geo@leica-geosystems.com>,
	Marco Felsch <m.felsch@pengutronix.de>
Subject: Re: [PATCH V5 1/1] clk: imx8mp: Alias M7 SRC/DIV to M7 CORE
Date: Mon, 13 Feb 2023 09:41:58 +0200	[thread overview]
Message-ID: <Y+npxisKxJaaSrul@linaro.org> (raw)
In-Reply-To: <911ff831eaa686c87682d8e95e90326c.sboyd@kernel.org>

On 23-01-30 14:34:30, Stephen Boyd wrote:
> Quoting LI Qingwu (2023-01-29 23:44:22)
> > 
> > > > Is it needed for clk-fixes? When did the system start hanging?
> > > 
> > > Li, Peng, can you provide some details here?
> > 
> > Since IMX8MP_CLK_M7_SRC and IMX8MP_CLK_M7_DIV were not assigned,
> > if using any one of them in device tree, Linux system hanging after start M7 core.
> 
>  $ git grep -e IMX8MP_CLK_M7_SRC -o -e IMX8MP_CLK_M7_DIV
>  include/dt-bindings/clock/imx8mp-clock.h:IMX8MP_CLK_M7_SRC
>  include/dt-bindings/clock/imx8mp-clock.h:IMX8MP_CLK_M7_DIV
> 
> so we're OK to let Abel apply this?

Replying here as the CC emails in Li's next-in-thread email are all messed up and
the reply I sent there bounced back.

As Stephen pointed out, in upstream, there is no current user for those
two clock IDs. So I suppose we can keep the Fixes tag, but currently,
on upstream, there is no chance a consumer could hang as there is no
consumer yet for these clocks.

Stephen, I'll add this to my 6.4 material, again, since there is no
actual comsumer yet, if that's OK with you.


      parent reply	other threads:[~2023-02-13  7:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-11 10:10 [PATCH V5 0/1] clk: imx8mp: Alias M7 SRC/DIV to M7 CORE LI Qingwu
2023-01-11 10:10 ` [PATCH V5 1/1] " LI Qingwu
2023-01-16 14:28   ` Abel Vesa
2023-01-18 19:00     ` Stephen Boyd
2023-01-28 18:38       ` Abel Vesa
2023-01-30  7:44         ` LI Qingwu
     [not found]           ` <911ff831eaa686c87682d8e95e90326c.sboyd@kernel.org>
     [not found]             ` <AS8PR06MB7432D9E3D31FAF8087338548D7DD9@AS8PR06MB7432.eurprd06.prod.outlook.com>
2023-02-13  5:44               ` LI Qingwu
2023-02-13  7:41             ` Abel Vesa [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=Y+npxisKxJaaSrul@linaro.org \
    --to=abel.vesa@linaro.org \
    --cc=18701859600@163.com \
    --cc=abelvesa@kernel.org \
    --cc=bsp-development.geo@leica-geosystems.com \
    --cc=festevam@gmail.com \
    --cc=kernel@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-imx@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m.felsch@pengutronix.de \
    --cc=mturquette@baylibre.com \
    --cc=peng.fan@nxp.com \
    --cc=qing-wu.li@leica-geosystems.com.cn \
    --cc=s.hauer@pengutronix.de \
    --cc=sboyd@kernel.org \
    --cc=shawnguo@kernel.org \
    /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