Linux-remoteproc Archive mirror
 help / color / mirror / Atom feed
From: Bjorn Andersson <andersson@kernel.org>
To: Konrad Dybcio <konrad.dybcio@linaro.org>,
	Sibi Sankar <quic_sibis@quicinc.com>,
	Mathieu Poirier <mathieu.poirier@linaro.org>,
	Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-remoteproc@vger.kernel.org,
	Johan Hovold <johan+linaro@kernel.org>,
	Xilin Wu <wuxilin123@gmail.com>,
	Bryan O'Donoghue <bryan.odonoghue@linaro.org>,
	Steev Klimaszewski <steev@kali.org>,
	Alexey Minnekhanov <alexeymin@postmarketos.org>,
	Neil Armstrong <neil.armstrong@linaro.org>,
	Chris Lew <quic_clew@quicinc.com>
Subject: Re: (subset) [PATCH v9 0/5] soc: qcom: add in-kernel pd-mapper implementation
Date: Tue, 25 Jun 2024 09:45:13 -0700	[thread overview]
Message-ID: <171933390698.2418820.597257098896589015.b4-ty@kernel.org> (raw)
In-Reply-To: <20240622-qcom-pd-mapper-v9-0-a84ee3591c8e@linaro.org>


On Sat, 22 Jun 2024 01:03:39 +0300, Dmitry Baryshkov 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.
> 
> [...]

Applied, thanks!

[5/5] remoteproc: qcom: enable in-kernel PD mapper
      commit: 5b9f51b200dcb2c3924ecbff324fa52f1faa84d3

Best regards,
-- 
Bjorn Andersson <andersson@kernel.org>

      parent reply	other threads:[~2024-06-25 16:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-21 22:03 [PATCH v9 0/5] soc: qcom: add in-kernel pd-mapper implementation Dmitry Baryshkov
2024-06-21 22:03 ` [PATCH v9 1/5] soc: qcom: pdr: protect locator_addr with the main mutex Dmitry Baryshkov
2024-06-25  0:52   ` Chris Lew
2024-06-21 22:03 ` [PATCH v9 2/5] soc: qcom: pdr: fix parsing of domains lists Dmitry Baryshkov
2024-06-21 22:03 ` [PATCH v9 3/5] soc: qcom: pdr: extract PDR message marshalling data Dmitry Baryshkov
2024-06-21 22:03 ` [PATCH v9 4/5] soc: qcom: add pd-mapper implementation Dmitry Baryshkov
2024-06-21 22:03 ` [PATCH v9 5/5] remoteproc: qcom: enable in-kernel PD mapper Dmitry Baryshkov
2024-06-25  3:16 ` (subset) [PATCH v9 0/5] soc: qcom: add in-kernel pd-mapper implementation Bjorn Andersson
2024-06-25 16:45 ` Bjorn Andersson [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=171933390698.2418820.597257098896589015.b4-ty@kernel.org \
    --to=andersson@kernel.org \
    --cc=alexeymin@postmarketos.org \
    --cc=bryan.odonoghue@linaro.org \
    --cc=dmitry.baryshkov@linaro.org \
    --cc=johan+linaro@kernel.org \
    --cc=konrad.dybcio@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-remoteproc@vger.kernel.org \
    --cc=mathieu.poirier@linaro.org \
    --cc=neil.armstrong@linaro.org \
    --cc=quic_clew@quicinc.com \
    --cc=quic_sibis@quicinc.com \
    --cc=steev@kali.org \
    --cc=wuxilin123@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).