From: Alexander Stein <alexander.stein@ew.tq-group.com>
To: Aisheng Dong <aisheng.dong@nxp.com>,
"andi.shyti@kernel.org" <andi.shyti@kernel.org>,
"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-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Carlos Song <carlos.song@nxp.com>
Cc: "linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>,
"imx@lists.linux.dev" <imx@lists.linux.dev>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 5/5] i2c: imx-lpi2c: increase PM timeout to avoid operate clk frequently
Date: Fri, 30 Aug 2024 11:07:10 +0200 [thread overview]
Message-ID: <3775392.MHq7AAxBmi@steina-w> (raw)
In-Reply-To: <DB7PR04MB500383BFE3957B1E422270AEE8972@DB7PR04MB5003.eurprd04.prod.outlook.com>
Hi,
Am Freitag, 30. August 2024, 10:53:16 CEST schrieb Carlos Song:
> > -----Original Message-----
> > From: Alexander Stein <alexander.stein@ew.tq-group.com>
> > Sent: Thursday, August 29, 2024 6:55 PM
> > To: Aisheng Dong <aisheng.dong@nxp.com>; andi.shyti@kernel.org;
> > shawnguo@kernel.org; s.hauer@pengutronix.de; kernel@pengutronix.de;
> > festevam@gmail.com; linux-arm-kernel@lists.infradead.org
> > Cc: linux-i2c@vger.kernel.org; imx@lists.linux.dev;
> > linux-arm-kernel@lists.infradead.org; linux-kernel@vger.kernel.org; Carlos Song
> > <carlos.song@nxp.com>
> > Subject: [EXT] Re: [PATCH 5/5] i2c: imx-lpi2c: increase PM timeout to avoid
> > operate clk frequently
> >
> > Caution: This is an external email. Please take care when clicking links or
> > opening attachments. When in doubt, report the message using the 'Report this
> > email' button
> >
> >
> > Hi,
> >
> > Am Donnerstag, 29. August 2024, 11:37:22 CEST schrieb carlos.song@nxp.com:
> > > From: Clark Wang <xiaoning.wang@nxp.com>
> > >
> > > Switching the clock frequently will affect the data transmission
> > > efficiency, and prolong the timeout to reduce autosuspend times for
> > > lpi2c.
> >
> > Efficiency as in throughput or total time per transfer? Do you have any numbers?
> >
>
> Hi, Thank your for your quick ack!
>
> Apologies for the unclear explanation. The efficiency I'm referring to isn't just for I2C. For platforms with SC firmware
> like the 8X series, every i2c transfer to enable or disable the clock notifies the SC firmware to perform a clock operation.
> So if the autosuspend time is short, i2c may enable and disable clock frequently, it will occupy resources of the SC firmware.
>
> Therefore, we add this patch to minimize the excessive sc firmware resource waste caused by frequent I2C clock enable/disable operations.
Thanks for the explanation. So this delay only occurs on systems using an SC (imx8qm/qxp) or SM (imx95), right?
Is there a chance to detect this kind of clock provider and make this timeout configurable?
Best regards,
Alexander
--
TQ-Systems GmbH | Mühlstraße 2, Gut Delling | 82229 Seefeld, Germany
Amtsgericht München, HRB 105018
Geschäftsführer: Detlef Schneider, Rüdiger Stahl, Stefan Schneider
http://www.tq-group.com/
prev parent reply other threads:[~2024-08-30 9:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-29 9:37 [PATCH 1/5] i2c: imx-lpi2c: add target mode support carlos.song
2024-08-29 9:37 ` [PATCH 2/5] i2c: imx-lpi2c: add IRQF_NO_SUSPEND IRQ flag carlos.song
2024-08-29 10:52 ` Stefan Wahren
2024-08-30 8:53 ` [EXT] " Carlos Song
2024-08-29 9:37 ` [PATCH 3/5] i2c: imx-lpi2c: manage IRQ request/release in runtime pm carlos.song
2024-08-29 9:37 ` [PATCH 4/5] i2c: imx-lpi2c: improve i2c driver probe priority carlos.song
2024-08-29 10:16 ` Stefan Wahren
2024-08-30 8:53 ` [EXT] " Carlos Song
2024-08-29 9:37 ` [PATCH 5/5] i2c: imx-lpi2c: increase PM timeout to avoid operate clk frequently carlos.song
2024-08-29 10:55 ` Alexander Stein
2024-08-30 8:53 ` [EXT] " Carlos Song
2024-08-30 9:07 ` Alexander Stein [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=3775392.MHq7AAxBmi@steina-w \
--to=alexander.stein@ew.tq-group.com \
--cc=aisheng.dong@nxp.com \
--cc=andi.shyti@kernel.org \
--cc=carlos.song@nxp.com \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=s.hauer@pengutronix.de \
--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