From: Mukesh Kumar Savaliya <quic_msavaliy@quicinc.com>
To: Bjorn Andersson <bjorn.andersson@oss.qualcomm.com>
Cc: <andi.shyti@kernel.org>, <quic_bjorande@quicinc.com>,
<linux-arm-msm@vger.kernel.org>, <linux-i2c@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <konrad.dybcio@linaro.org>,
<quic_vdadhani@quicinc.com>, <vkoul@kernel.org>
Subject: Re: [PATCH v2] i2c: i2c-qcom-geni: Serve transfer during early resume stage
Date: Sat, 23 Nov 2024 17:43:09 +0530 [thread overview]
Message-ID: <f96fbfc5-ed5a-4def-a7e0-df4098dea4b3@quicinc.com> (raw)
In-Reply-To: <CADLxj5RD5syLXdVnfsMpEso9VOhWiwdP8_iV12R=mvhKwUY_bA@mail.gmail.com>
Thanks Bjorn.
On 11/19/2024 8:29 PM, Bjorn Andersson wrote:
> On Tue, Nov 19, 2024 at 8:29 AM Mukesh Kumar Savaliya
> <quic_msavaliy@quicinc.com> wrote:
>> On 10/11/2024 11:28 PM, Bjorn Andersson wrote:
>>> On Fri, Oct 11, 2024 at 05:47:57PM +0530, Mukesh Kumar Savaliya wrote:
> [..]
>>>> pm_runtime_get_sync() function fails during PM early resume and returning
>>>> -EACCES because runtime PM for the device is disabled at the early stage
>>>> causing i2c transfer to fail. Make changes to serve transfer with forced
>>>> resume.
>>>>
>>>> Few i2c clients like PCI OR touch may request i2c transfers during early
>>>> resume stage. In order to serve transfer request do :
>>>>
>>>
>>> This problem description is too generic. I am not aware of any use case
>>> upstream where PCI or touch might need to perform i2c transfers during
>>> early resume; your commit message should educate me.
>>>
>> yes, it's generic as of now since we have an internal usecase with PCI
>> is yet to be enabled in upstream. Not tied up with any usecase in
>> upstream, i just heard recently.
>>
>> Provided the scenario is generic and possible by any client, can this
>> code change be reviewed or shall be kept on halt till PCI usecase gets
>> enabled ?
>>
>
> If this is a valid scenario in the upstream kernel, yes. If it solves
> a problem only manifesting itself based on a downstream design then
> you need to exactly describe that scenario so that reviewers can
> decide if this is a problem with the upstream kernel or your
> downstream design.
>
The exact scenario from PCIe switch is as below. Hope it describes the
usecase at high level to understand PCIe client -> PCIe Driver -> I2C
driver.
PCIe switch needs certain configurations through i2c after powering on
the switch, as part of suspend we are using suspend_noirq() to turn off
the switch because some PCIe clients do some transfers till
suspend_noirq() phase. And as part of resume_noirq(), we will enable the
power to the switch and configures the switch again through i2c.
> Regards,
> Bjonr
>
next prev parent reply other threads:[~2024-11-23 12:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-11 12:17 [PATCH v2] i2c: i2c-qcom-geni: Serve transfer during early resume stage Mukesh Kumar Savaliya
2024-10-11 17:58 ` Bjorn Andersson
2024-11-19 14:29 ` Mukesh Kumar Savaliya
2024-11-19 14:59 ` Bjorn Andersson
2024-11-23 12:13 ` Mukesh Kumar Savaliya [this message]
2024-10-13 13:41 ` kernel test robot
2024-10-13 14:23 ` kernel test robot
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=f96fbfc5-ed5a-4def-a7e0-df4098dea4b3@quicinc.com \
--to=quic_msavaliy@quicinc.com \
--cc=andi.shyti@kernel.org \
--cc=bjorn.andersson@oss.qualcomm.com \
--cc=konrad.dybcio@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_bjorande@quicinc.com \
--cc=quic_vdadhani@quicinc.com \
--cc=vkoul@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