From: Sudeep Holla <sudeep.holla@arm.com>
To: Rishabh Bhatnagar <rishabhb@codeaurora.org>, cristian.marussi@arm.com
Cc: Sudeep Holla <sudeep.holla@arm.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, adharmap@codeaurora.org,
avajid@codeaurora.org
Subject: Re: [PATCH v3] firmware: arm_scmi: Free mailbox channels if probe fails
Date: Mon, 9 Aug 2021 06:00:57 +0100 [thread overview]
Message-ID: <162848516052.232525.343233021782950735.b4-ty@arm.com> (raw)
In-Reply-To: <1628111999-21595-1-git-send-email-rishabhb@codeaurora.org>
On Wed, 4 Aug 2021 14:19:59 -0700, Rishabh Bhatnagar wrote:
> Mailbox channels for the base protocol are setup during probe.
> There can be a scenario where probe fails to acquire the base
> protocol due to a timeout leading to cleaning up of all device
> managed memory including the scmi_mailbox structure setup during
> mailbox_chan_setup function.
> [ 12.735104]arm-scmi soc:qcom,scmi: timed out in resp(caller: version_get+0x84/0x140)
> [ 12.735224]arm-scmi soc:qcom,scmi: unable to communicate with SCMI
> [ 12.735947]arm-scmi: probe of soc:qcom,scmi failed with error -110
>
> [...]
Applied to sudeep.holla/linux (for-next/scmi), thanks!
[1/1] firmware: arm_scmi: Free mailbox channels if probe fails
https://git.kernel.org/sudeep.holla/c/1e7cbfaa66
--
Regards,
Sudeep
prev parent reply other threads:[~2021-08-09 5:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-04 21:19 [PATCH v3] firmware: arm_scmi: Free mailbox channels if probe fails Rishabh Bhatnagar
2021-08-05 10:54 ` Cristian Marussi
2021-08-30 21:09 ` rishabhb
2021-08-31 5:48 ` Cristian Marussi
2021-09-01 9:35 ` Cristian Marussi
2021-11-01 16:35 ` rishabhb
2021-11-02 11:32 ` Sudeep Holla
2021-11-04 23:40 ` rishabhb
2021-11-05 9:43 ` Cristian Marussi
2021-11-05 17:40 ` rishabhb
2021-11-07 10:34 ` Cristian Marussi
2021-11-07 18:22 ` Cristian Marussi
2021-11-08 17:58 ` rishabhb
2021-11-09 14:38 ` Cristian Marussi
2021-08-09 5:00 ` Sudeep Holla [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=162848516052.232525.343233021782950735.b4-ty@arm.com \
--to=sudeep.holla@arm.com \
--cc=adharmap@codeaurora.org \
--cc=avajid@codeaurora.org \
--cc=cristian.marussi@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rishabhb@codeaurora.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;
as well as URLs for NNTP newsgroup(s).