linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Frank Wunderlich <frank-w@public-files.de>
To: Matthias Brugger <matthias.bgg@gmail.com>
Cc: Frank Wunderlich <linux@fw-web.de>,
	linux-mediatek@lists.infradead.org, CK Hu <ck.hu@mediatek.com>,
	Enric Balletbo i Serra <enric.balletbo@collabora.com>,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, dafna.hirschfeld@collabora.com,
	Chun-Kuang Hu <chunkuang.hu@kernel.org>,
	Hsin-Yi Wang <hsinyi@chromium.org>
Subject: Aw: Re: [PATCH v2] soc: mmsys: mediatek: add mask to mmsys routes
Date: Wed, 4 Aug 2021 17:59:46 +0200	[thread overview]
Message-ID: <trinity-7bda902b-2c2b-4b74-99fe-9258b7ebedcf-1628092786728@3c-app-gmx-bap67> (raw)
In-Reply-To: <e8c990b6-180d-9702-d8cc-fd1e98dfc744@gmail.com>

Hi,

> Gesendet: Mittwoch, 04. August 2021 um 17:17 Uhr
> Von: "Matthias Brugger" <matthias.bgg@gmail.com>

> My understanding is, that this does not break mt8173 and other SoCs that use the
> default routing table. Correct?

i took the mask values from CK Hu's Patch, mt7623 uses this table and with it hdmi works again (was broken by the array-commit). I'm not sure on which devices Chun-Kuang has tested it, he only suggests to add the mask again from his commit to fix mt7623.

https://patchwork.kernel.org/project/linux-mediatek/patch/20210710132431.265985-1-linux@fw-web.de/#24335233

I can only test on mt7623/BPI-R2...

there is a new patchset for mt8192 which adds a new routing-table, which needs to be extended with mask values (without it wil not work, but maybe duplicate values may work):

https://patchwork.kernel.org/project/linux-mediatek/patch/1627894773-23872-3-git-send-email-yongqiang.niu@mediatek.com/

regards Frank

> Added now to v5.14-next/soc
> Thanks.

Thanks too

      reply	other threads:[~2021-08-04 16:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-29  7:05 [PATCH v2] soc: mmsys: mediatek: add mask to mmsys routes Frank Wunderlich
2021-08-04 15:17 ` Matthias Brugger
2021-08-04 15:59   ` Frank Wunderlich [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=trinity-7bda902b-2c2b-4b74-99fe-9258b7ebedcf-1628092786728@3c-app-gmx-bap67 \
    --to=frank-w@public-files.de \
    --cc=chunkuang.hu@kernel.org \
    --cc=ck.hu@mediatek.com \
    --cc=dafna.hirschfeld@collabora.com \
    --cc=enric.balletbo@collabora.com \
    --cc=hsinyi@chromium.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=linux@fw-web.de \
    --cc=matthias.bgg@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 NNTP newsgroup(s).