From: Rudraksha Gupta <guptarud@gmail.com>
To: Bartosz Golaszewski <brgl@bgdev.pl>,
Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: Elliot Berman <quic_eberman@quicinc.com>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Andrew Halaney <ahalaney@redhat.com>,
"Linux regression tracking (Thorsten Leemhuis)"
<regressions@leemhuis.info>,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Subject: Re: [PATCH 2/2] firmware: qcom: scm: fall back to kcalloc() for no SCM device bound
Date: Wed, 11 Sep 2024 11:01:16 -0700 [thread overview]
Message-ID: <8d9fde52-2582-499f-a971-e9aa46b23fa2@gmail.com> (raw)
In-Reply-To: <CAMRc=MefTjz=h6jzE5vE-yaHnyM601Ts8XYZqEYnOsidfQEavA@mail.gmail.com>
> I'm wondering about how to approach an eventual refactoring and I'm
> thinking that for platforms that are known to have DTs out there
> without the node, we could exceptionally instantiate the SCM device
> when the module is loaded? And then modify the driver to require the
> provider to have an actual struct device attached.
I'm happy to help test these changes if you'd like!
next prev parent reply other threads:[~2024-09-11 18:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-09 18:38 [PATCH 0/2] firmware: qcom: scm: fix SMC calls on ARM32 Bartosz Golaszewski
2024-09-09 18:38 ` [PATCH 1/2] firmware: qcom: scm: fix a NULL-pointer dereference Bartosz Golaszewski
2024-09-09 20:06 ` Konrad Dybcio
2024-09-10 6:45 ` Rudraksha Gupta
2024-09-09 18:38 ` [PATCH 2/2] firmware: qcom: scm: fall back to kcalloc() for no SCM device bound Bartosz Golaszewski
2024-09-09 20:10 ` Konrad Dybcio
2024-09-09 21:04 ` Elliot Berman
2024-09-10 8:37 ` Bartosz Golaszewski
2024-09-10 11:06 ` Dmitry Baryshkov
2024-09-11 11:41 ` Bartosz Golaszewski
2024-09-11 11:55 ` Dmitry Baryshkov
2024-09-11 18:01 ` Rudraksha Gupta [this message]
2024-09-11 19:44 ` Bartosz Golaszewski
2024-09-10 6:46 ` Rudraksha Gupta
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=8d9fde52-2582-499f-a971-e9aa46b23fa2@gmail.com \
--to=guptarud@gmail.com \
--cc=ahalaney@redhat.com \
--cc=andersson@kernel.org \
--cc=bartosz.golaszewski@linaro.org \
--cc=brgl@bgdev.pl \
--cc=dmitry.baryshkov@linaro.org \
--cc=konradybcio@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_eberman@quicinc.com \
--cc=regressions@leemhuis.info \
/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