From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: "Sharma, Shashank" <shashank.sharma@intel.com>
Cc: Hans Verkuil <hansverk@cisco.com>,
Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v3 3/4] drm/edid: Throw away the dummy VIC 0 cea mode
Date: Thu, 3 Oct 2019 17:16:05 +0300 [thread overview]
Message-ID: <20191003141605.GK1208@intel.com> (raw)
In-Reply-To: <3cad3f33-e402-1e44-6221-9de6a8324f3e@intel.com>
On Thu, Oct 03, 2019 at 01:59:42PM +0530, Sharma, Shashank wrote:
>
> On 9/25/2019 7:25 PM, Ville Syrjala wrote:
> > From: Ville Syrjälä <ville.syrjala@linux.intel.com>
> >
> > Now that the cea mode handling is not 100% tied to the single
> > array the dummy VIC 0 mode is pretty much pointles. Throw it
> > out.
> >
> > Cc: Hans Verkuil <hansverk@cisco.com>
> > Cc: Shashank Sharma <shashank.sharma@intel.com>
> > Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > ---
> > drivers/gpu/drm/drm_edid.c | 14 +++++---------
> > 1 file changed, 5 insertions(+), 9 deletions(-)
> >
> > diff --git a/drivers/gpu/drm/drm_edid.c b/drivers/gpu/drm/drm_edid.c
> > index 9f6996323efa..0007004d3221 100644
> > --- a/drivers/gpu/drm/drm_edid.c
> > +++ b/drivers/gpu/drm/drm_edid.c
> > @@ -709,11 +709,9 @@ static const struct minimode extra_modes[] = {
> > /*
> > * From CEA/CTA-861 spec.
> > *
> > - * Index with VIC.
> > + * Index with VIC-1.
>
> Do we want to really do this ? Till now, due to dummy VIC, indexing was
> pretty direct as per VIC, which was making the code easy to read and
> understand. I would still think that keeping the dummy VIC and adjusting
> the size of cea_modes_0[] in the size function, would be something
> neater to do, do you think so ?
I don't see the point of wasting that space. The access is now fully
abstraced so you *never* index this directly.
>
> - Shashank
>
> > */
> > -static const struct drm_display_mode edid_cea_modes_0[] = {
> > - /* 0 - dummy, VICs start at 1 */
> > - { },
> > +static const struct drm_display_mode edid_cea_modes_1[] = {
> > /* 1 - 640x480@60Hz 4:3 */
> > { DRM_MODE("640x480", DRM_MODE_TYPE_DRIVER, 25175, 640, 656,
> > 752, 800, 0, 480, 490, 492, 525, 0,
> > @@ -3211,10 +3209,8 @@ static u8 *drm_find_cea_extension(const struct edid *edid)
> >
> > static const struct drm_display_mode *cea_mode_for_vic(u8 vic)
> > {
> > - if (!vic)
> > - return NULL;
> > - if (vic < ARRAY_SIZE(edid_cea_modes_0))
> > - return &edid_cea_modes_0[vic];
> > + if (vic >= 1 && vic < 1 + ARRAY_SIZE(edid_cea_modes_1))
> > + return &edid_cea_modes_1[vic - 1];
> > if (vic >= 193 && vic < 193 + ARRAY_SIZE(edid_cea_modes_193))
> > return &edid_cea_modes_193[vic - 193];
> > return NULL;
> > @@ -3227,7 +3223,7 @@ static u8 cea_num_vics(void)
> >
> > static u8 cea_next_vic(u8 vic)
> > {
> > - if (++vic == ARRAY_SIZE(edid_cea_modes_0))
> > + if (++vic == 1 + ARRAY_SIZE(edid_cea_modes_1))
> > vic = 193;
> > return vic;
> > }
--
Ville Syrjälä
Intel
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2019-10-03 14:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190925135502.24055-1-ville.syrjala@linux.intel.com>
2019-09-25 13:54 ` [PATCH v3 1/4] drm/edid: Abstract away cea_edid_modes[] Ville Syrjala
2019-09-25 13:55 ` [PATCH v3 2/4] drm/edid: Add CTA-861-G modes with VIC >= 193 Ville Syrjala
2019-09-25 13:55 ` [PATCH v3 3/4] drm/edid: Throw away the dummy VIC 0 cea mode Ville Syrjala
2019-09-25 13:55 ` [PATCH v3 4/4] drm/edid: Make sure the CEA mode arrays have the correct amount of modes Ville Syrjala
2019-09-25 16:19 ` ✗ Fi.CI.CHECKPATCH: warning for drm/edid: Add new modes from CTA-861-G (rev2) Patchwork
2019-09-25 16:42 ` ✓ Fi.CI.BAT: success " Patchwork
2019-09-26 8:37 ` ✗ Fi.CI.IGT: failure " Patchwork
[not found] ` <20190925135502.24055-2-ville.syrjala@linux.intel.com>
2019-10-03 8:16 ` [PATCH v3 1/4] drm/edid: Abstract away cea_edid_modes[] Sharma, Shashank
2019-10-03 13:55 ` Ville Syrjälä
[not found] ` <20190925135502.24055-3-ville.syrjala@linux.intel.com>
2019-10-03 8:22 ` [PATCH v3 2/4] drm/edid: Add CTA-861-G modes with VIC >= 193 Sharma, Shashank
2019-10-03 14:15 ` Ville Syrjälä
[not found] ` <20190925135502.24055-4-ville.syrjala@linux.intel.com>
2019-10-03 8:29 ` [PATCH v3 3/4] drm/edid: Throw away the dummy VIC 0 cea mode Sharma, Shashank
2019-10-03 14:16 ` Ville Syrjälä [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=20191003141605.GK1208@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=hansverk@cisco.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=shashank.sharma@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