From: Jani Nikula <jani.nikula@linux.intel.com>
To: Angus Ainslie <angus@akkea.ca>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>
Cc: kernel@puri.sm, David Airlie <airlied@linux.ie>,
Angus Ainslie <angus@akkea.ca>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
ville.syrjala@linux.intel.com
Subject: Re: [PATCH] drm: drm_probe_helper: add modes upto 1920x1080
Date: Tue, 16 Nov 2021 10:44:14 +0200 [thread overview]
Message-ID: <87czn01odd.fsf@intel.com> (raw)
In-Reply-To: <20211115160135.25451-1-angus@akkea.ca>
Cc: Ville
On Mon, 15 Nov 2021, Angus Ainslie <angus@akkea.ca> wrote:
> Lots of monitors nowdays support more than 1024x768 so if the EDID is
> unknown then add resolutions upto 1920x1080.
IIUC it's supposed to be the fallback that's pretty much guaranteed to
work. What's going to happen if we add 1920x1080 and it fails?
BR,
Jani.
>
> Signed-off-by: Angus Ainslie <angus@akkea.ca>
> ---
> drivers/gpu/drm/drm_probe_helper.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/drm_probe_helper.c b/drivers/gpu/drm/drm_probe_helper.c
> index e7e1ee2aa352..5ad66ae9916e 100644
> --- a/drivers/gpu/drm/drm_probe_helper.c
> +++ b/drivers/gpu/drm/drm_probe_helper.c
> @@ -517,7 +517,7 @@ int drm_helper_probe_single_connector_modes(struct drm_connector *connector,
>
> if (count == 0 && (connector->status == connector_status_connected ||
> connector->status == connector_status_unknown))
> - count = drm_add_modes_noedid(connector, 1024, 768);
> + count = drm_add_modes_noedid(connector, 1920, 1080);
> count += drm_helper_probe_add_cmdline_mode(connector);
> if (count == 0)
> goto prune;
--
Jani Nikula, Intel Open Source Graphics Center
next prev parent reply other threads:[~2021-11-16 8:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-15 16:01 [PATCH] drm: drm_probe_helper: add modes upto 1920x1080 Angus Ainslie
2021-11-16 8:44 ` Jani Nikula [this message]
2021-11-16 8:50 ` Daniel Vetter
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=87czn01odd.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=airlied@linux.ie \
--cc=angus@akkea.ca \
--cc=dri-devel@lists.freedesktop.org \
--cc=kernel@puri.sm \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=tzimmermann@suse.de \
--cc=ville.syrjala@linux.intel.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