From: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
To: Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Mathieu Poirier <mathieu.poirier@linaro.org>
Cc: linux-arm-msm@vger.kernel.org, linux-remoteproc@vger.kernel.org
Subject: Re: [PATCH RFC v2 0/5] soc: qcom: add in-kernel pd-mapper implementation
Date: Fri, 1 Mar 2024 02:50:28 +0200 [thread overview]
Message-ID: <CAA8EJpo11gNRP1sYBXva4doOvuzuEsbR3pVgS1FdWqtwB0bNGA@mail.gmail.com> (raw)
In-Reply-To: <20240301-qcom-pd-mapper-v2-0-5d12a081d9d1@linaro.org>
On Fri, 1 Mar 2024 at 01:00, Dmitry Baryshkov
<dmitry.baryshkov@linaro.org> wrote:
>
> Protection domain mapper is a QMI service providing mapping between
> 'protection domains' and services supported / allowed in these domains.
> For example such mapping is required for loading of the WiFi firmware or
> for properly starting up the UCSI / altmode / battery manager support.
>
> The existing userspace implementation has several issue. It doesn't play
> well with CONFIG_EXTRA_FIRMWARE, it doesn't reread the JSON files if the
> firmware location is changed (or if the firmware was not available at
> the time pd-mapper was started but the corresponding directory is
> mounted later), etc.
>
> However this configuration is largely static and common between
> different platforms. Provide in-kernel service implementing static
> per-platform data.
>
> NOTE: this is an RFC / RFC, the domain mapping data might be inaccurate
> (especially for SM6xxx and SC7xxx platforms), which is reflected by
> several TODO and FIXME comments in the code.
>
> Changes since RFC v1:
> - Swapped num_domains / domains (Konrad)
> - Fixed an issue with battery not working on sc8280xp
After sending this RFC I have stumbled upon another issue on sc8280xp
/ X13s. I'll send v3 after finding a way to fix it.
> - Added missing configuration for QCS404
>> Best regards,
> --
> Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
>
--
With best wishes
Dmitry
prev parent reply other threads:[~2024-03-01 0:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-29 23:00 [PATCH RFC v2 0/5] soc: qcom: add in-kernel pd-mapper implementation Dmitry Baryshkov
2024-02-29 23:00 ` [PATCH RFC v2 1/5] soc: qcom: add " Dmitry Baryshkov
2024-02-29 23:00 ` [PATCH RFC v2 2/5] remoteproc: qcom: pas: correct data indentation Dmitry Baryshkov
2024-02-29 23:00 ` [PATCH RFC v2 3/5] remoteproc: qcom: adsp: add configuration for in-kernel pdm Dmitry Baryshkov
2024-02-29 23:04 ` Dmitry Baryshkov
2024-02-29 23:00 ` [PATCH RFC v2 4/5] remoteproc: qcom: mss: " Dmitry Baryshkov
2024-02-29 23:00 ` [PATCH RFC v2 5/5] remoteproc: qcom: pas: " Dmitry Baryshkov
2024-03-01 0:50 ` Dmitry Baryshkov [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=CAA8EJpo11gNRP1sYBXva4doOvuzuEsbR3pVgS1FdWqtwB0bNGA@mail.gmail.com \
--to=dmitry.baryshkov@linaro.org \
--cc=andersson@kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=mathieu.poirier@linaro.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 read-only IMAP folder(s) and NNTP newsgroup(s).