[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6012ec99-4246-41b6-adb2-1bcd4dd159ac@gmail.com>
Date: Fri, 9 Feb 2024 08:24:56 +0100
From: Rafał Miłecki <zajec5@...il.com>
To: AngeloGioacchino Del Regno <angelogioacchino.delregno@...labora.com>,
Rafał Miłecki <zajec5@...il.com>,
Mauro Carvalho Chehab <mchehab@...nel.org>, Rob Herring
<robh+dt@...nel.org>, Krzysztof Kozlowski
<krzysztof.kozlowski+dt@...aro.org>, Conor Dooley <conor+dt@...nel.org>
Cc: Matthias Brugger <matthias.bgg@...il.com>,
Sean Wang <sean.wang@...iatek.com>, linux-media@...r.kernel.org,
devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-mediatek@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] dt-bindings: media: convert Mediatek consumer IR to the
json-schema
On 24.01.2024 13:33, AngeloGioacchino Del Regno wrote:
> The driver says:
>
> ir->bus = devm_clk_get(dev, "bus");
> if (IS_ERR(ir->bus)) {
> /*
> * For compatibility with older device trees try unnamed
> * ir->bus uses the same clock as ir->clock.
> */
> ir->bus = ir->clk;
> }
>
> This makes me think that requiring *one* clock on MT7623 would be a mistake
> and the devicetree should use clk, bus - CLK_INFRA_IRRX_PD, CLK_TOP_F10M_REF_SEL.
Looking at mt2701-clk.h I can see CLK_INFRA_IRRX (which I guess you
meant above).
I can't find CLK_TOP_F10M_REF_SEL however. This seems to be available on
MT7622 and MT7629 only.
Could you take another look at it, please? Can you somehow verify what
clock should be used by IR on MT7623?
Powered by blists - more mailing lists