From: Ramalingam C <ramalingam.c@intel.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
gwan-gyeong.mun@intel.com
Subject: Re: [PATCH v4 05/13] drivers: create binary sysfs for class
Date: Fri, 5 Apr 2019 16:06:22 +0530 [thread overview]
Message-ID: <20190405103621.GA9459@intel.com> (raw)
In-Reply-To: <20190405092300.GB16788@kroah.com>
On 2019-04-05 at 11:23:00 +0200, Greg Kroah-Hartman wrote:
> On Fri, Apr 05, 2019 at 02:12:54PM +0530, Ramalingam C wrote:
> > Functions to create and remove the binary sysfs for class are added.
> >
> > These are getting introduced as DRM wants to create the common binary
> > sysfs across the drm subsystem to handle hdcp srm.
>
> Why do you need individual files? That's almost always a sign that you
> are going to race with userspace in a bad way. Why not just use an
> attribute group which provides automatic support for this?
Greg,
Reason behind this move is to have a common srm entry path across all drm
drivers. And the data fed into this is binary blob. So I am creating a
binary sysfs "hdcp_srm" at /sys/class/drm/
Thanks,
Ram.
>
> thanks,
>
> greg k-h
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-04-05 10:36 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-05 8:42 [PATCH v4 00/13] HDCP2.2 Phase II Ramalingam C
2019-04-05 8:42 ` [PATCH v4 01/13] drm: move content protection property to mode_config Ramalingam C
2019-04-05 8:42 ` [PATCH v4 02/13] drm/i915: debugfs: HDCP2.2 capability read Ramalingam C
2019-04-05 8:42 ` [PATCH v4 03/13] drm: Add Content protection type property Ramalingam C
2019-04-05 8:42 ` [PATCH v4 04/13] drm/i915: Attach content " Ramalingam C
2019-04-05 8:42 ` [PATCH v4 05/13] drivers: create binary sysfs for class Ramalingam C
2019-04-05 9:23 ` Greg Kroah-Hartman
2019-04-05 10:36 ` Ramalingam C [this message]
2019-04-05 12:32 ` Greg Kroah-Hartman
2019-04-15 12:41 ` Ramalingam C
2019-04-15 14:47 ` Greg Kroah-Hartman
2019-04-15 17:14 ` Ramalingam C
2019-04-15 18:01 ` Greg Kroah-Hartman
2019-04-15 19:14 ` Daniel Vetter
2019-04-16 9:04 ` Greg Kroah-Hartman
2019-04-16 9:25 ` Daniel Vetter
2019-04-05 8:42 ` [PATCH v4 06/13] drm: HDCP SRM binary sysfs for subsystem Ramalingam C
2019-04-05 8:42 ` [PATCH v4 07/13] drm/i915: SRM revocation check for HDCP1.4 and 2.2 Ramalingam C
2019-04-05 8:42 ` [PATCH v4 08/13] drm/hdcp: gathering hdcp related code into drm_hdcp.c Ramalingam C
2019-04-05 8:42 ` [PATCH v4 09/13] drm: uevent for connector status change Ramalingam C
2019-04-05 8:42 ` [PATCH v4 10/13] drm/hdcp: update content protection property with uevent Ramalingam C
2019-04-05 8:43 ` [PATCH v4 11/13] drm/i915: update the hdcp state " Ramalingam C
2019-04-05 8:43 ` [PATCH v4 12/13] drm: Add CP downstream_info property Ramalingam C
2019-04-05 8:43 ` [PATCH v4 13/13] drm/i915: Populate downstream info for HDCP Ramalingam C
2019-04-05 12:03 ` Ramalingam C
2019-04-05 11:16 ` ✗ Fi.CI.CHECKPATCH: warning for HDCP2.2 Phase II (rev5) Patchwork
2019-04-05 11:26 ` ✗ Fi.CI.SPARSE: " Patchwork
2019-04-05 11:41 ` ✓ Fi.CI.BAT: success " Patchwork
2019-04-06 7:11 ` ✓ Fi.CI.IGT: " Patchwork
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=20190405103621.GA9459@intel.com \
--to=ramalingam.c@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=gwan-gyeong.mun@intel.com \
--cc=intel-gfx@lists.freedesktop.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.