From: Sourab Gupta
The drmfs filesystem will not be registered standalone during kernel init time,
instead it is intended to be initialized/registered during drm initialization.
This again is dependent on CONFIG_DRMFS being defined.
Signed-off-by: Sourab Gupta
Signed-off-by: Swati Dhingra
ments and catering to the needs to DRM subsystem components
Signed-off-by: Sourab Gupta
Signed-off-by: Swati Dhingra
---
Documentation/gpu/drm-uapi.rst | 76 ++
drivers/gpu/drm/Kconfig| 9 +
drivers/gpu/drm/Makefile | 1 +
drivers/gpu
at '/sys/kernel/drm/i915'.
Signed-off-by: Sourab Gupta
Signed-off-by: Swati Dhingra
---
drivers/gpu/drm/drm_drv.c | 6 ++
include/drm/drm_drv.h | 3 +++
2 files changed, 9 insertions(+)
diff --git a/drivers/gpu/drm/drm_drv.c b/drivers/gpu/drm/drm_drv.c
index 298013c..4c32
using the drmfs api's to create the requisite files.
Signed-off-by: Sourab Gupta
Signed-off-by: Swati Dhingra
---
drivers/gpu/drm/i915/i915_guc_submission.c | 33 +++---
1 file changed, 12 insertions(+), 21 deletions(-)
diff --git a/drivers/gpu/drm/i915/i915_guc_
From: Swati Dhingra
Currently, we don't have a stable ABI which can be used for the purpose of
providing output debug/loggging/crc and other such data from DRM.
The ABI in current use (filesystems, ioctls, et al.) have their own
constraints and are intended to output a particular type of
ments and catering to the needs to DRM subsystem components
Signed-off-by: Sourab Gupta
Signed-off-by: Swati Dhingra
---
drivers/gpu/drm/Kconfig| 9 +
drivers/gpu/drm/Makefile | 1 +
drivers/gpu/drm/drmfs.c| 555 +
include
From: Sourab Gupta
The drmfs filesystem will not be registered standalone during kernel init time,
instead it is intended to be initialized/registered during drm initialization.
Signed-off-by: Sourab Gupta
Signed-off-by: Swati Dhingra
---
drivers/gpu/drm/drm_drv.c | 6 ++
1 file changed
using the drmfs api's to create the requisite files.
Signed-off-by: Sourab Gupta
Signed-off-by: Swati Dhingra
---
drivers/gpu/drm/i915/i915_guc_submission.c | 33 +++---
1 file changed, 12 insertions(+), 21 deletions(-)
diff --git a/drivers/gpu/drm/i915/i915_guc_
at '/sys/kernel/drm/i915'.
Signed-off-by: Sourab Gupta
Signed-off-by: Swati Dhingra
---
drivers/gpu/drm/drm_drv.c | 6 ++
include/drm/drm_drv.h | 3 +++
2 files changed, 9 insertions(+)
diff --git a/drivers/gpu/drm/drm_drv.c b/drivers/gpu/drm/drm_drv.c
index 298013c..4c32
From: Swati Dhingra
Currently, we don't have a stable ABI which can be used for the purpose of
providing output debug/loggging/crc and other such data from DRM.
The ABI in current use (filesystems, ioctls, et al.) have their own
constraints and are intended to output a particular type of
From: Swati Dhingra
In the current scenario, the relay API fit well only with debugfs, due to
availability of parent dentry. Any other existing filesystem was not feasible
for
holding guc logs, due to incompatibility with relay. But this makes the guc_log
file unavailable on the production
From: Swati Dhingra
The patch introduces a new pseudo filesystem type, named 'drmfs' which is
intended to house the files for the data generated by drm subsystem that
cannot be accommodated by any of the existing filesystems.
The filesystem is modelled on the lines of existing pseudo-f
From: Swati Dhingra
Currently, for the purpose of providing output debug/loggging/crc and various
other kinds of data from DRM layer to userspace, we don't have a standard
filesystem, which would suffice for all the usecases. The filesystems used
currently such as debugfs/sysfs have thei
From: Swati Dhingra
During drm module initialization, drm_core_init initializes the drmfs
filesystem and register this with kernel. A driver specific directory is created
inside drmfs root, and dentry of this directory is saved for subsequent use
by the driver (e.g. i915). The driver can then
From: Swati Dhingra
During drm module initialization, drm_core_init initializes the drmfs
filesystem and register this with kernel. A driver specific directory is created
inside drmfs root, and dentry of this directory is saved for subsequent use
by the driver (e.g. i915). The driver can then
From: Swati Dhingra
In the current scenario, the relay API fit well only with debugfs, due to
availability of parent dentry. Any other existing filesystem was not feasible
for
holding guc logs, due to incompatibility with relay. But this makes the guc_log
file unavailable on the production
From: Swati Dhingra
The patch introduces a new pseudo filesystem type, named 'drmfs' which is
intended to house the files for the data generated by drm subsystem that
cannot be accommodated by any of the existing filesystems.
The filesystem is modelled on the lines of existing pseudo-f
From: Swati Dhingra
Currently, for the purpose of providing output debug/loggging/crc and various
other kinds of data from DRM layer to userspace, we don't have a standard
filesystem, which would suffice for all the usecases. The filesystems used
currently such as debugfs/sysfs have thei
18 matches
Mail list logo
