From: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
To: "Nancy.Lin" <nancy.lin@mediatek.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
Philipp Zabel <p.zabel@pengutronix.de>,
CK Hu <ck.hu@mediatek.com>,
Chun-Kuang Hu <chunkuang.hu@kernel.org>
Cc: Nathan Chancellor <nathan@kernel.org>,
Nick Desaulniers <ndesaulniers@google.com>,
Tom Rix <trix@redhat.com>,
"Jason-JH . Lin" <jason-jh.lin@mediatek.com>,
Nathan Lu <nathan.lu@mediatek.com>,
Rex-BC Chen <rex-bc.chen@mediatek.com>,
Xinlei Lee <xinlei.lee@mediatek.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, llvm@lists.linux.dev,
singo.chang@mediatek.com,
Project_Global_Chrome_Upstream_Group@mediatek.com
Subject: Re: [PATCH v30 00/11] Add MediaTek SoC(vdosys1) support for mt8195
Date: Fri, 20 Jan 2023 12:10:59 +0100 [thread overview]
Message-ID: <91627ce5-1eb0-1a8d-3e73-4966cb7a817f@collabora.com> (raw)
In-Reply-To: <20230113104434.28023-1-nancy.lin@mediatek.com>
Il 13/01/23 11:44, Nancy.Lin ha scritto:
> The hardware path of vdosys1 with DPTx output need to go through by several modules, such as, OVL_ADAPTOR and MERGE.
>
> Add mmsys and mutex modules support by the patches below:
>
> Changes in v30:
Matthias, can you please pick this one?
It reached -> v30 <-.... I think that's way beyond being enough versions :-P
P.S.: We have MT8195 support and Tomato Chromebook support, but the display
doesn't work because of the VDOSYS1 soc+drm[1] not being there...
I'd really like to get this machine fully upstreamed.
[1]: https://patchwork.kernel.org/project/linux-mediatek/list/?series=707095
Also, CK, please can you coordinate with Matthias so that we get both series
merged in now?
Thanks,
Angelo
> - rebase to next-20230113
> - fix reviewer comment in v29
> - fix mmysy binding doc for vdosys1
>
next prev parent reply other threads:[~2023-01-20 11:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230113104434.28023-1-nancy.lin@mediatek.com>
[not found] ` <20230113104434.28023-2-nancy.lin@mediatek.com>
2023-01-13 11:19 ` [PATCH v30 01/11] dt-bindings: arm: mediatek: mmsys: add vdosys1 compatible for MT8195 Krzysztof Kozlowski
2023-01-20 11:10 ` AngeloGioacchino Del Regno [this message]
2023-01-25 15:05 ` [PATCH v30 00/11] Add MediaTek SoC(vdosys1) support for mt8195 Matthias Brugger
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=91627ce5-1eb0-1a8d-3e73-4966cb7a817f@collabora.com \
--to=angelogioacchino.delregno@collabora.com \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=chunkuang.hu@kernel.org \
--cc=ck.hu@mediatek.com \
--cc=devicetree@vger.kernel.org \
--cc=jason-jh.lin@mediatek.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=llvm@lists.linux.dev \
--cc=matthias.bgg@gmail.com \
--cc=nancy.lin@mediatek.com \
--cc=nathan.lu@mediatek.com \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=p.zabel@pengutronix.de \
--cc=rex-bc.chen@mediatek.com \
--cc=robh+dt@kernel.org \
--cc=singo.chang@mediatek.com \
--cc=trix@redhat.com \
--cc=xinlei.lee@mediatek.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 NNTP newsgroup(s).