From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Kuogee Hsieh <quic_khsieh@quicinc.com>
Cc: robdclark@gmail.com, sean@poorly.run, swboyd@chromium.org,
vkoul@kernel.org, daniel@ffwll.ch, airlied@linux.ie,
agross@kernel.org, dmitry.baryshkov@linaro.org,
quic_abhinavk@quicinc.com, aravindh@codeaurora.org,
freedreno@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drm/msm/dp: add wide bus support
Date: Mon, 31 Jan 2022 19:52:00 -0800 [thread overview]
Message-ID: <YfiuYFCONqRzv3Mk@ripper> (raw)
In-Reply-To: <1643390945-10813-1-git-send-email-quic_khsieh@quicinc.com>
On Fri 28 Jan 09:29 PST 2022, Kuogee Hsieh wrote:
> Normally, mdp will push one pixel of data per pixel clock to
> interface to display. Wide bus feature will increase bus
> width from 32 bits to 64 bits so that it can push two
> pixel of data per pixel clock to interface to display.
> This feature is pre requirement to support 4k resolution.
>
Can you please elaborate further how this is a requirement for 4k
resolution, given that I write you this question on a 4k monitor.
Regards,
Bjorn
WARNING: multiple messages have this Message-ID (diff)
From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Kuogee Hsieh <quic_khsieh@quicinc.com>
Cc: quic_abhinavk@quicinc.com, airlied@linux.ie,
freedreno@lists.freedesktop.org, vkoul@kernel.org,
dri-devel@lists.freedesktop.org, swboyd@chromium.org,
agross@kernel.org, linux-arm-msm@vger.kernel.org,
dmitry.baryshkov@linaro.org, aravindh@codeaurora.org,
sean@poorly.run, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drm/msm/dp: add wide bus support
Date: Mon, 31 Jan 2022 19:52:00 -0800 [thread overview]
Message-ID: <YfiuYFCONqRzv3Mk@ripper> (raw)
In-Reply-To: <1643390945-10813-1-git-send-email-quic_khsieh@quicinc.com>
On Fri 28 Jan 09:29 PST 2022, Kuogee Hsieh wrote:
> Normally, mdp will push one pixel of data per pixel clock to
> interface to display. Wide bus feature will increase bus
> width from 32 bits to 64 bits so that it can push two
> pixel of data per pixel clock to interface to display.
> This feature is pre requirement to support 4k resolution.
>
Can you please elaborate further how this is a requirement for 4k
resolution, given that I write you this question on a 4k monitor.
Regards,
Bjorn
next prev parent reply other threads:[~2022-02-01 3:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-28 17:29 [PATCH] drm/msm/dp: add wide bus support Kuogee Hsieh
2022-01-28 17:29 ` Kuogee Hsieh
2022-01-29 4:59 ` Dmitry Baryshkov
2022-01-29 4:59 ` Dmitry Baryshkov
2022-01-31 20:50 ` Kuogee Hsieh
2022-01-31 20:50 ` Kuogee Hsieh
2022-01-31 20:57 ` Dmitry Baryshkov
2022-01-31 20:57 ` Dmitry Baryshkov
2022-01-31 22:23 ` Kuogee Hsieh
2022-01-31 22:23 ` Kuogee Hsieh
2022-02-01 3:16 ` Dmitry Baryshkov
2022-02-01 3:16 ` Dmitry Baryshkov
2022-02-01 3:55 ` Dmitry Baryshkov
2022-02-01 3:55 ` Dmitry Baryshkov
2022-02-01 3:52 ` Bjorn Andersson [this message]
2022-02-01 3:52 ` 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=YfiuYFCONqRzv3Mk@ripper \
--to=bjorn.andersson@linaro.org \
--cc=agross@kernel.org \
--cc=airlied@linux.ie \
--cc=aravindh@codeaurora.org \
--cc=daniel@ffwll.ch \
--cc=dmitry.baryshkov@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_abhinavk@quicinc.com \
--cc=quic_khsieh@quicinc.com \
--cc=robdclark@gmail.com \
--cc=sean@poorly.run \
--cc=swboyd@chromium.org \
--cc=vkoul@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 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.