From: Mukesh Kumar Savaliya <quic_msavaliy@quicinc.com>
To: Konrad Dybcio <konrad.dybcio@linaro.org>, <andersson@kernel.org>,
<vkoul@kernel.org>, <andi.shyti@kernel.org>, <wsa@kernel.org>,
<linux-arm-msm@vger.kernel.org>, <dmaengine@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <linux-i2c@vger.kernel.org>
Cc: <quic_vdadhani@quicinc.com>
Subject: Re: [PATCH v1] i2c: i2c-qcom-geni: Add support to share an I2C SE from two subsystem
Date: Fri, 19 Apr 2024 00:31:51 +0530 [thread overview]
Message-ID: <9a18b752-c13a-4b46-ae71-59b8372dd953@quicinc.com> (raw)
In-Reply-To: <f4cbacca-c2e7-42e7-8ed9-dbc6bb59f1ce@linaro.org>
Hi Konrad, Thanks for confirming your preferences.
On 4/16/2024 5:14 AM, Konrad Dybcio wrote:
>
>
> On 4/2/24 08:21, Mukesh Kumar Savaliya wrote:
>> Thanks Konrad for detailed review. For dt-bindings sending a separate
>> patch soon, rest comments tried to address and updated patch V2.
>
> [...]
>
>>>> + if (of_property_read_bool(pdev->dev.of_node, "qcom,shared-se")) {
>>>> + gi2c->is_shared = true;
>>>> + dev_info(&pdev->dev, "Multi-EE usecase with shared SE\n");
>>>
>>> How would this line be useful in my kernel log?
>>>
>> It informs that particular SE is shared between SEs from two
>> subsystems, hence respective debug can happen accordingly in case of
>> the issue.
>
> This amounts to "not very useful". As an end user, I couldn't care less
> about the nitty-gritty of firmware-hardware interactions, so long as the
> thing works. You must not spam the kernel log with debug messages, as it
> slows things down and makes actually useful messages harder to spot. If
> you want to keep it, use dev_dbg.
>
Sure, will go with the dev_dbg. I am uploading a separate patches for
i2c and GSI DMA sub system.
> Konrad
prev parent reply other threads:[~2024-04-18 19:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-27 10:18 [PATCH v1] i2c: i2c-qcom-geni: Add support to share an I2C SE from two subsystem Mukesh Kumar Savaliya
2024-03-27 21:05 ` Konrad Dybcio
2024-04-02 6:21 ` Mukesh Kumar Savaliya
2024-04-15 23:44 ` Konrad Dybcio
2024-04-18 19:01 ` Mukesh Kumar Savaliya [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=9a18b752-c13a-4b46-ae71-59b8372dd953@quicinc.com \
--to=quic_msavaliy@quicinc.com \
--cc=andersson@kernel.org \
--cc=andi.shyti@kernel.org \
--cc=dmaengine@vger.kernel.org \
--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_vdadhani@quicinc.com \
--cc=vkoul@kernel.org \
--cc=wsa@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