From: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
To: Daniel Golle <daniel@makrotopia.org>
Cc: "Qii Wang" <qii.wang@mediatek.com>,
"Andi Shyti" <andi.shyti@kernel.org>,
"Matthias Brugger" <matthias.bgg@gmail.com>,
linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, 郭小桥 <joe@gainstrong.cn>
Subject: Re: [PATCH] i2c: mt65xx: allow optional pmic clock
Date: Thu, 14 Sep 2023 11:37:49 +0200 [thread overview]
Message-ID: <dc2cf86a-abf2-b372-29f9-3bfedeb24a97@collabora.com> (raw)
In-Reply-To: <ZQLNWHKlIZNd7x4l@makrotopia.org>
Il 14/09/23 11:07, Daniel Golle ha scritto:
> On Wed, Sep 13, 2023 at 04:00:53PM +0200, AngeloGioacchino Del Regno wrote:
>> Il 27/08/23 04:13, Daniel Golle ha scritto:
>>> Using the I2C host controller on the MT7981 SoC requires 4 clocks to
>>> be enabled. One of them, the pmic clk, is only enabled in case
>>> 'mediatek,have-pmic' is also set which has other consequences which
>>> are not desired in this case.
>>>
>>> Allow defining a pmic clk even in case the 'mediatek,have-pmic' propterty
>>> is not present and the bus is not used to connect to a pmic, but may
>>> still require to enable the pmic clock.
>>>
>>> Signed-off-by: Daniel Golle <daniel@makrotopia.org>
>>> ---
>>> drivers/i2c/busses/i2c-mt65xx.c | 12 ++++++++----
>>> 1 file changed, 8 insertions(+), 4 deletions(-)
>>>
>>> diff --git a/drivers/i2c/busses/i2c-mt65xx.c b/drivers/i2c/busses/i2c-mt65xx.c
>>> index 1a9b5a068ef1b..a8b5719c33729 100644
>>> --- a/drivers/i2c/busses/i2c-mt65xx.c
>>> +++ b/drivers/i2c/busses/i2c-mt65xx.c
>>> @@ -1442,15 +1442,19 @@ static int mtk_i2c_probe(struct platform_device *pdev)
>>> if (IS_ERR(i2c->clocks[I2C_MT65XX_CLK_ARB].clk))
>>> return PTR_ERR(i2c->clocks[I2C_MT65XX_CLK_ARB].clk);
>>> + i2c->clocks[I2C_MT65XX_CLK_PMIC].clk = devm_clk_get_optional(&pdev->dev, "pmic");
>>> + if (IS_ERR(i2c->clocks[I2C_MT65XX_CLK_PMIC].clk)) {
>>> + dev_err(&pdev->dev, "cannot get pmic clock\n");
>>> + return PTR_ERR(i2c->clocks[I2C_MT65XX_CLK_PMIC].clk);
>>> + }
>>> +
>>> if (i2c->have_pmic) {
>>
>> ...but you're not changing speed_clk if !i2c->have_pmic, I'm not sure that
>> this will work correctly. Perhaps you wanted to also set speed_clk if the
>> clock is present?
>
> No, if I wanted that I could have used the existing 'mediatek,have-pmic'
> property -- however, all needed e.g. on MT7981 is to make sure the
> clock is enabled, but still use I2C_MT65XX_CLK_MAIN as speed_clk.
>
Sorry, I've misunderstood the intention and yes, I understand now.
Reviewed-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
next prev parent reply other threads:[~2023-09-14 9:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-27 2:13 [PATCH] i2c: mt65xx: allow optional pmic clock Daniel Golle
2023-09-02 23:49 ` Andi Shyti
2023-09-13 14:00 ` AngeloGioacchino Del Regno
2023-09-14 9:07 ` Daniel Golle
2023-09-14 9:37 ` AngeloGioacchino Del Regno [this message]
2025-08-07 5:42 ` 回复: " Qii Wang (王琪)
2023-09-19 20:00 ` Wolfram Sang
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=dc2cf86a-abf2-b372-29f9-3bfedeb24a97@collabora.com \
--to=angelogioacchino.delregno@collabora.com \
--cc=andi.shyti@kernel.org \
--cc=daniel@makrotopia.org \
--cc=joe@gainstrong.cn \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=qii.wang@mediatek.com \
/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