From: Guru Das Srinagesh <quic_gurus@quicinc.com>
To: Huang Yiwei <quic_hyiwei@quicinc.com>
Cc: <mani@kernel.org>, <agross@kernel.org>, <andersson@kernel.org>,
<konrad.dybcio@linaro.org>, <jassisinghbrar@gmail.com>,
<linux-arm-msm@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<quic_satyap@quicinc.com>, <quic_aiquny@quicinc.com>
Subject: Re: [PATCH] mailbox: qcom-ipcc: Support multiple channels for a given client
Date: Thu, 23 Feb 2023 19:27:39 -0800 [thread overview]
Message-ID: <20230224032739.GA15837@quicinc.com> (raw)
In-Reply-To: <20230223061318.1793-1-quic_hyiwei@quicinc.com>
On Feb 23 2023 14:13, Huang Yiwei wrote:
> Recently a new use case where two signals for the same protocol and
> client is needed, that means there will be more than one channel
> for a mbox node. Current driver only supports one channel, so need
> to remove the limitation and let the driver find every channel
> correctly.
>
> Signed-off-by: Huang Yiwei <quic_hyiwei@quicinc.com>
> ---
> drivers/mailbox/qcom-ipcc.c | 6 ++----
> 1 file changed, 2 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/mailbox/qcom-ipcc.c b/drivers/mailbox/qcom-ipcc.c
> index 7e27acf6c0cc..367658af089e 100644
> --- a/drivers/mailbox/qcom-ipcc.c
> +++ b/drivers/mailbox/qcom-ipcc.c
> @@ -226,11 +226,9 @@ static int qcom_ipcc_setup_mbox(struct qcom_ipcc *ipcc,
> for (j = 0; j < i; j++) {
> ret = of_parse_phandle_with_args(client_dn, "mboxes",
> "#mbox-cells", j, &curr_ph);
> - of_node_put(curr_ph.np);
> - if (!ret && curr_ph.np == controller_dn) {
> + if (!ret && curr_ph.np == controller_dn)
> ipcc->num_chans++;
> - break;
> - }
> + of_node_put(curr_ph.np);
of_node_put can stay where it is - the main change is the removal of the break,
is it not?
Guru Das.
prev parent reply other threads:[~2023-02-24 3:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-23 6:13 [PATCH] mailbox: qcom-ipcc: Support multiple channels for a given client Huang Yiwei
2023-02-24 3:27 ` Guru Das Srinagesh [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=20230224032739.GA15837@quicinc.com \
--to=quic_gurus@quicinc.com \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=jassisinghbrar@gmail.com \
--cc=konrad.dybcio@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mani@kernel.org \
--cc=quic_aiquny@quicinc.com \
--cc=quic_hyiwei@quicinc.com \
--cc=quic_satyap@quicinc.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