From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Ramalingam C <ramalingam.c@intel.com>
Cc: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v4] drm: Fix downstream dev count read
Date: Thu, 5 Apr 2018 16:56:41 -0700 [thread overview]
Message-ID: <20180405235641.GN4181@intel.com> (raw)
In-Reply-To: <afea456a-c438-523f-e167-5f144b77d4ee@intel.com>
On Thu, Apr 05, 2018 at 04:04:14AM +0530, Ramalingam C wrote:
>
>
> On Thursday 05 April 2018 12:53 AM, Sean Paul wrote:
> > On Wed, Apr 04, 2018 at 12:07:41PM -0700, Rodrigo Vivi wrote:
> > > On Wed, Apr 04, 2018 at 11:57:42PM +0530, Ramalingam C wrote:
> > > > In both HDMI and DP, device count is represented by 6:0 bits of a
> > > > register(BInfo/Bstatus)
> > > >
> > > > So macro for bitmasking the device_count is fixed(0x3F->0x7F).
> > > >
> > > > v3:
> > > > Retained the Rb-ed.
> > > > v4:
> > > > %s/drm\/i915/drm [rodrigo]
> > > >
> > > Shouldn't this patch have a "Fixes:" ?
> > Yes, I think that'd be good.
> Will add
> Fixes: 495eb7f877ab drm: Add some HDCP related #defines
> >
> > > cc: stable?
> > It couldn't hurt.
> Sorry what is needed here?
nothing actually...
$ dim fixes 495eb7f877ab3
Fixes: 495eb7f877ab ("drm: Add some HDCP related #defines")
Cc: Daniel Vetter <daniel.vetter@intel.com>
Cc: Ramalingam C <ramalingm.c@intel.com>
Cc: Sean Paul <seanpaul@chromium.org>
Cc: Gustavo Padovan <gustavo@padovan.org>
Cc: David Airlie <airlied@linux.ie>
Cc: dri-devel@lists.freedesktop.org
CC: Stable wasn't returned here so it is not needed.
> >
> > > I pushed first 3 patches on the series to dinq.
> > > I believe this one here could be there with Dave's ack or
> > > maybe on drm-misc-fixes?
> > Meh. The severity of this isn't too big, given that I doubt people care _too_
> > much about plugging in more than 64 HDCP-enabled devices. If you want to drop it
> > in -misc-next-fixes, I can send it out next week.
> >
> > While we're asking for a respin, could we add HDCP somewhere in the subject?
> will change the sub to
> drm: Fix HDCP downstream dev count read
>
> --Ram
> >
> > Sean
> >
> > > > Signed-off-by: Ramalingam C <ramalingam.c@intel.com>
> > > > cc: Sean Paul <seanpaul@chromium.org>
> > > > Reviewed-by: Sean Paul <seanpaul@chromium.org>
> > > > ---
> > > > include/drm/drm_hdcp.h | 2 +-
> > > > 1 file changed, 1 insertion(+), 1 deletion(-)
> > > >
> > > > diff --git a/include/drm/drm_hdcp.h b/include/drm/drm_hdcp.h
> > > > index 562fa7df2637..98e63d870139 100644
> > > > --- a/include/drm/drm_hdcp.h
> > > > +++ b/include/drm/drm_hdcp.h
> > > > @@ -19,7 +19,7 @@
> > > > #define DRM_HDCP_RI_LEN 2
> > > > #define DRM_HDCP_V_PRIME_PART_LEN 4
> > > > #define DRM_HDCP_V_PRIME_NUM_PARTS 5
> > > > -#define DRM_HDCP_NUM_DOWNSTREAM(x) (x & 0x3f)
> > > > +#define DRM_HDCP_NUM_DOWNSTREAM(x) (x & 0x7f)
> > > > #define DRM_HDCP_MAX_CASCADE_EXCEEDED(x) (x & BIT(3))
> > > > #define DRM_HDCP_MAX_DEVICE_EXCEEDED(x) (x & BIT(7))
> > > > --
> > > > 2.7.4
> > > >
>
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-04-05 23:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-02 10:10 [PATCH v3 0/4] HDCP1.4 fixes Ramalingam C
2018-04-02 10:10 ` [PATCH v3 1/4] drm/i915: Read HDCP R0 thrice in case of mismatch Ramalingam C
2018-04-02 11:50 ` [PATCH v4 " Ramalingam C
2018-04-02 13:49 ` Sean Paul
2018-04-02 10:10 ` [PATCH v3 2/4] drm/i915: Read Vprime thrice incase " Ramalingam C
2018-04-02 13:50 ` Sean Paul
2018-04-02 10:10 ` [PATCH v3 3/4] drm/i915: Check hdcp key loadability Ramalingam C
2018-04-02 10:10 ` [PATCH v3 4/4] drm/i915: Fix reading downstream dev count Ramalingam C
2018-04-04 18:27 ` [PATCH v4] drm: Fix downstream dev count read Ramalingam C
2018-04-04 19:07 ` Rodrigo Vivi
2018-04-04 19:23 ` Sean Paul
2018-04-04 22:34 ` Ramalingam C
2018-04-05 23:56 ` Rodrigo Vivi [this message]
2018-04-05 12:03 ` [PATCH v5] drm: Fix HDCP " Ramalingam C
2018-04-16 16:11 ` Sean Paul
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=20180405235641.GN4181@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=ramalingam.c@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