From: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
To: Chen-Yu Tsai <wenst@chromium.org>,
Bjorn Andersson <andersson@kernel.org>,
Mathieu Poirier <mathieu.poirier@linaro.org>,
Matthias Brugger <matthias.bgg@gmail.com>
Cc: Tinghan Shen <tinghan.shen@mediatek.com>,
linux-remoteproc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org,
Laura Nao <laura.nao@collabora.com>
Subject: Re: [PATCH] remoteproc: mediatek: Detect single/multi core SCP with rpmsg-name property
Date: Tue, 19 Sep 2023 11:26:09 +0200 [thread overview]
Message-ID: <13843095-0906-804e-ffbe-36625ebe05cf@collabora.com> (raw)
In-Reply-To: <20230919050305.3817347-1-wenst@chromium.org>
Il 19/09/23 07:03, Chen-Yu Tsai ha scritto:
> In the just landed multi-core SCP work, detection of single/multi core
> SCP is done by checking the immediate child node of the SCP complex
> device node. In the original work this was done by matching the child
> node's name. However the name wasn't previously standardized. This
> resulted in breakage on MT8183 and MT8192 Chromebooks while the driver
> side changes were picked up and the device tree changes were not picked
> up.
>
> Instead, match against the "mediatek,rpmsg-name" property, which is
> required to be present in the rpmsg sub-node. This makes the
> aforementioned devices running old device trees working again.
>
> Reported-by: Laura Nao <laura.nao@collabora.com>
> Fixes: 1fdbf0cdde98 ("remoteproc: mediatek: Probe SCP cluster on multi-core SCP")
> Signed-off-by: Chen-Yu Tsai <wenst@chromium.org>
> ---
> The patch is based on next-20230918 with a whole bunch of local patches
> stacked on top. None of my local patches are related to remoteproc, so
> it should be fine.
>
> I tested on both MT8183 Juniper and MT8192 Hayato and on both systems
> the SCP successfully probed again.
Instead of checking "mediatek,rpmsg-name", I think that a better way of checking if
this is single or multi core is to count the number of cores...
I've sent my own version of this, please check [1].
[1]:
https://lore.kernel.org/linux-remoteproc/20230919092336.51007-1-angelogioacchino.delregno@collabora.com/
Cheers,
Angelo
next prev parent reply other threads:[~2023-09-19 9:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-19 5:03 Chen-Yu Tsai
2023-09-19 9:26 ` AngeloGioacchino Del Regno [this message]
2023-09-19 9:39 ` Chen-Yu Tsai
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=13843095-0906-804e-ffbe-36625ebe05cf@collabora.com \
--to=angelogioacchino.delregno@collabora.com \
--cc=andersson@kernel.org \
--cc=laura.nao@collabora.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=matthias.bgg@gmail.com \
--cc=tinghan.shen@mediatek.com \
--cc=wenst@chromium.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
all inboxes | Powered by JetHome®