From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Mahadevan P <mahadevan.p@oss.qualcomm.com>,
Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Cc: Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64: dts: qcom: lemans: add DT changes to enable MDSS1 and DPU
Date: Fri, 26 Sep 2025 12:43:14 +0200 [thread overview]
Message-ID: <57be4253-485f-4a24-afc0-a25a3c33caa4@oss.qualcomm.com> (raw)
In-Reply-To: <d451f8f0-d2ab-44eb-bfcc-ec1e9dbba060@oss.qualcomm.com>
On 9/26/25 11:24 AM, Mahadevan P wrote:
>
> On 9/26/2025 3:11 AM, Dmitry Baryshkov wrote:
>> On Thu, Sep 25, 2025 at 02:28:07PM +0530, Mahadevan wrote:
>>> Add devicetree changes to enable second Mobile Display
>>> Subsystem (MDSS1) and its Display Processing Unit(DPU) for
>>> Qualcomm LEMANS platform.
>> No outputs? Should it be enabled on any of the devices?
>
> Outputs and enablement are include as part of this series:
> https://lore.kernel.org/all/20250926085956.2346179-1-quic_mkuntuma@quicinc.com/
Why send two very related and interdependent series separately?
It only makes it harder for the recipients to manage and track your
patches (there are ~100 emails flowing in daily, now more because
of recent SoC announcements)
Konrad
next prev parent reply other threads:[~2025-09-26 10:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-25 8:58 Mahadevan
2025-09-25 10:49 ` Konrad Dybcio
2025-09-25 21:45 ` Dmitry Baryshkov
2025-09-25 21:41 ` Dmitry Baryshkov
2025-09-26 9:24 ` Mahadevan P
2025-09-26 10:43 ` Konrad Dybcio [this message]
2025-10-17 22:50 ` Bjorn Andersson
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=57be4253-485f-4a24-afc0-a25a3c33caa4@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mahadevan.p@oss.qualcomm.com \
--cc=robh@kernel.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®