From: Frank Wunderlich <frank-w@public-files.de>
To: linux-mediatek@lists.infradead.org,
Chun-Kuang Hu <chunkuang.hu@kernel.org>
Cc: devicetree@vger.kernel.org, Ryder Lee <ryder.lee@mediatek.com>,
chunkuang Hu <chunkuang.hu@kernel.org>,
Sean Wang <sean.wang@mediatek.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
Rob Herring <robh+dt@kernel.org>,
"moderated list:ARM/Mediatek SoC support"
<linux-mediatek@lists.infradead.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
Frank Wunderlich <linux@fw-web.de>,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 1/2] arm: dts: mt7623: move more display-related nodes to mt7623n.dtsi
Date: Sun, 09 Aug 2020 09:21:37 +0200 [thread overview]
Message-ID: <81DFA743-B455-498F-B2F2-161DD9D51F57@public-files.de> (raw)
In-Reply-To: <CAAOTY_9o_hBWxWBdDoeeJ6zuV4rb4R_yEoN5+L0uHBGMw4Kduw@mail.gmail.com>
Am 9. August 2020 02:16:59 MESZ schrieb Chun-Kuang Hu <chunkuang.hu@kernel.org>:
>
>I would like to put all device in mt7623.dtsi with some device's
>status is "disabled" and change its status in platform dtsi.
>I would like to see all device in mt7623.dtsi because of its name. If
>you move some device to platform dtsi, we would trace all platform
>dtsi to find out how many device in mt7623. One day a new platform
>enable different devices, you would reorganize all these platform
>dtsi?
Ok,then i change the dts-patch from hdmi-series to disable all nodes and enabling them in bpi-r2 dts. Do they need to be in alphabetical order (or any other)?
Is the tmds Patch ok? (because review missing) https://patchwork.kernel.org/patch/11700679/
Just to know before reposting series as v5 :)
regards Frank
WARNING: multiple messages have this Message-ID (diff)
From: Frank Wunderlich <frank-w@public-files.de>
To: linux-mediatek@lists.infradead.org,
Chun-Kuang Hu <chunkuang.hu@kernel.org>
Cc: devicetree@vger.kernel.org, Ryder Lee <ryder.lee@mediatek.com>,
chunkuang Hu <chunkuang.hu@kernel.org>,
Sean Wang <sean.wang@mediatek.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
Rob Herring <robh+dt@kernel.org>,
"moderated list:ARM/Mediatek SoC support"
<linux-mediatek@lists.infradead.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
Frank Wunderlich <linux@fw-web.de>,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 1/2] arm: dts: mt7623: move more display-related nodes to mt7623n.dtsi
Date: Sun, 09 Aug 2020 09:21:37 +0200 [thread overview]
Message-ID: <81DFA743-B455-498F-B2F2-161DD9D51F57@public-files.de> (raw)
In-Reply-To: <CAAOTY_9o_hBWxWBdDoeeJ6zuV4rb4R_yEoN5+L0uHBGMw4Kduw@mail.gmail.com>
Am 9. August 2020 02:16:59 MESZ schrieb Chun-Kuang Hu <chunkuang.hu@kernel.org>:
>
>I would like to put all device in mt7623.dtsi with some device's
>status is "disabled" and change its status in platform dtsi.
>I would like to see all device in mt7623.dtsi because of its name. If
>you move some device to platform dtsi, we would trace all platform
>dtsi to find out how many device in mt7623. One day a new platform
>enable different devices, you would reorganize all these platform
>dtsi?
Ok,then i change the dts-patch from hdmi-series to disable all nodes and enabling them in bpi-r2 dts. Do they need to be in alphabetical order (or any other)?
Is the tmds Patch ok? (because review missing) https://patchwork.kernel.org/patch/11700679/
Just to know before reposting series as v5 :)
regards Frank
_______________________________________________
Linux-mediatek mailing list
Linux-mediatek@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-mediatek
WARNING: multiple messages have this Message-ID (diff)
From: Frank Wunderlich <frank-w@public-files.de>
To: linux-mediatek@lists.infradead.org,
Chun-Kuang Hu <chunkuang.hu@kernel.org>
Cc: devicetree@vger.kernel.org, Ryder Lee <ryder.lee@mediatek.com>,
chunkuang Hu <chunkuang.hu@kernel.org>,
Sean Wang <sean.wang@mediatek.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
Rob Herring <robh+dt@kernel.org>,
"moderated list:ARM/Mediatek SoC support"
<linux-mediatek@lists.infradead.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
Frank Wunderlich <linux@fw-web.de>,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 1/2] arm: dts: mt7623: move more display-related nodes to mt7623n.dtsi
Date: Sun, 09 Aug 2020 09:21:37 +0200 [thread overview]
Message-ID: <81DFA743-B455-498F-B2F2-161DD9D51F57@public-files.de> (raw)
In-Reply-To: <CAAOTY_9o_hBWxWBdDoeeJ6zuV4rb4R_yEoN5+L0uHBGMw4Kduw@mail.gmail.com>
Am 9. August 2020 02:16:59 MESZ schrieb Chun-Kuang Hu <chunkuang.hu@kernel.org>:
>
>I would like to put all device in mt7623.dtsi with some device's
>status is "disabled" and change its status in platform dtsi.
>I would like to see all device in mt7623.dtsi because of its name. If
>you move some device to platform dtsi, we would trace all platform
>dtsi to find out how many device in mt7623. One day a new platform
>enable different devices, you would reorganize all these platform
>dtsi?
Ok,then i change the dts-patch from hdmi-series to disable all nodes and enabling them in bpi-r2 dts. Do they need to be in alphabetical order (or any other)?
Is the tmds Patch ok? (because review missing) https://patchwork.kernel.org/patch/11700679/
Just to know before reposting series as v5 :)
regards Frank
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-08-09 7:22 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-07 8:27 Frank Wunderlich
2020-08-07 8:27 ` Frank Wunderlich
2020-08-07 8:27 ` Frank Wunderlich
2020-08-07 8:27 ` [PATCH 1/2] arm: dts: mt7623: move more display-related nodes to mt7623n.dtsi Frank Wunderlich
2020-08-07 8:27 ` Frank Wunderlich
2020-08-07 8:27 ` Frank Wunderlich
2020-08-08 12:27 ` Aw: " Frank Wunderlich
2020-08-08 12:27 ` Frank Wunderlich
2020-08-08 12:27 ` Frank Wunderlich
2020-08-09 0:16 ` Chun-Kuang Hu
2020-08-09 0:16 ` Chun-Kuang Hu
2020-08-09 0:16 ` Chun-Kuang Hu
2020-08-09 7:21 ` Frank Wunderlich [this message]
2020-08-09 7:21 ` Frank Wunderlich
2020-08-09 7:21 ` Frank Wunderlich
2020-08-10 0:06 ` Chun-Kuang Hu
2020-08-10 0:06 ` Chun-Kuang Hu
2020-08-10 0:06 ` Chun-Kuang Hu
2020-08-10 5:39 ` Frank Wunderlich
2020-08-10 5:39 ` Frank Wunderlich
2020-08-10 5:39 ` Frank Wunderlich
2020-08-10 7:48 ` David Woodhouse
2020-08-10 7:48 ` David Woodhouse
2020-08-10 7:48 ` David Woodhouse
2020-08-10 23:28 ` Chun-Kuang Hu
2020-08-10 23:28 ` Chun-Kuang Hu
2020-08-10 23:28 ` Chun-Kuang Hu
2020-08-11 8:41 ` Frank Wunderlich
2020-08-11 8:41 ` Frank Wunderlich
2020-08-11 8:41 ` Frank Wunderlich
2020-08-11 9:35 ` David Woodhouse
2020-08-11 9:35 ` David Woodhouse
2020-08-11 9:35 ` David Woodhouse
2020-08-18 7:16 ` Aw: " Frank Wunderlich
2020-08-18 7:16 ` Frank Wunderlich
2020-08-18 7:36 ` David Woodhouse
2020-08-18 7:36 ` David Woodhouse
2020-08-18 7:45 ` Aw: " Frank Wunderlich
2020-08-18 7:45 ` Frank Wunderlich
2020-08-07 8:27 ` [PATCH 2/2] arm: dts: mt7623: add display subsystem related device nodes Frank Wunderlich
2020-08-07 8:27 ` Frank Wunderlich
2020-08-07 8:27 ` Frank Wunderlich
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=81DFA743-B455-498F-B2F2-161DD9D51F57@public-files.de \
--to=frank-w@public-files.de \
--cc=chunkuang.hu@kernel.org \
--cc=devicetree@vger.kernel.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 \
--cc=robh+dt@kernel.org \
--cc=ryder.lee@mediatek.com \
--cc=sean.wang@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.