Obviously the MODULE_PARM_DESC documentation for
drm_kms_helper.edid_firmware needs some updating before we could
consider this.
Signed-off-by: Jani Nikula <jani.nik...@intel.com>
---
Documentation/admin-guide/kernel-parameters.txt | 18 ---------------
.../admin-guide/module-parameters/drm.rst | 26 ++++++++++++++++++++++
.../module-parameters/drm_kms_helper.rst | 23 +++++++++++++++++++
3 files changed, 49 insertions(+), 18 deletions(-)
create mode 100644 Documentation/admin-guide/module-parameters/drm.rst
create mode 100644
Documentation/admin-guide/module-parameters/drm_kms_helper.rst
diff --git a/Documentation/admin-guide/kernel-parameters.txt
b/Documentation/admin-guide/kernel-parameters.txt
index 4e731b44db95..f0cee38beef2 100644
--- a/Documentation/admin-guide/kernel-parameters.txt
+++ b/Documentation/admin-guide/kernel-parameters.txt
@@ -854,24 +854,6 @@
The filter can be disabled or changed to another
driver later using sysfs.
- drm_kms_helper.edid_firmware=[<connector>:]<file>[,[<connector>:]<file>]
- Broken monitors, graphic adapters, KVMs and EDIDless
- panels may send no or incorrect EDID data sets.
- This parameter allows to specify an EDID data sets
- in the /lib/firmware directory that are used instead.
- Generic built-in EDID data sets are used, if one of
- edid/1024x768.bin, edid/1280x1024.bin,
- edid/1680x1050.bin, or edid/1920x1080.bin is given
- and no file with the same name exists. Details and
- instructions how to build your own EDID data are
- available in Documentation/EDID/HOWTO.txt. An EDID
- data set will only be used for a particular connector,
- if its name and a colon are prepended to the EDID
- name. Each connector may use a unique EDID data
- set by separating the files with a comma. An EDID
- data set with no connector name will be used for
- any connectors not explicitly specified.
-
dscc4.setup= [NET]
dt_cpu_ftrs= [PPC]
diff --git a/Documentation/admin-guide/module-parameters/drm.rst
b/Documentation/admin-guide/module-parameters/drm.rst
new file mode 100644
index 000000000000..8b03a54f844c
--- /dev/null
+++ b/Documentation/admin-guide/module-parameters/drm.rst
@@ -0,0 +1,26 @@
+.. Autogenerated from drm.ko using modinfo(8) and modinfo-to-rst
+
+drm
+===
+
+debug (int)
+ Enable debug output, where each bit enables a debug category.
+ Bit 0 (0x01) will enable CORE messages (drm core code)
+ Bit 1 (0x02) will enable DRIVER messages (drm controller code)
+ Bit 2 (0x04) will enable KMS messages (modesetting code)
+ Bit 3 (0x08) will enable PRIME messages (prime code)
+ Bit 4 (0x10) will enable ATOMIC messages (atomic code)
+ Bit 5 (0x20) will enable VBL messages (vblank code)
+
+edid_fixup (int)
+ Minimum number of valid EDID header bytes (0-8, default 6)
+
+timestamp_monotonic (int)
+ Use monotonic timestamps
+
+timestamp_precision_usec (int)
+ Max. error on timestamps [usecs]
+
+vblankoffdelay (int)
+ Delay until vblank irq auto-disable [msecs] (0: never disable, <0: disable
immediately)
+
diff --git a/Documentation/admin-guide/module-parameters/drm_kms_helper.rst
b/Documentation/admin-guide/module-parameters/drm_kms_helper.rst
new file mode 100644
index 000000000000..8940951d75da
--- /dev/null
+++ b/Documentation/admin-guide/module-parameters/drm_kms_helper.rst
@@ -0,0 +1,23 @@
+.. Autogenerated from drm_kms_helper.ko using modinfo(8) and modinfo-to-rst
+
+drm_kms_helper
+==============
+
+dp_aux_i2c_speed_khz (int)
+ Assumed speed of the i2c bus in kHz, (1-400, default 10)
+
+dp_aux_i2c_transfer_size (int)
+ Number of bytes to transfer in a single I2C over DP AUX CH message, (1-16,
default 16)
+
+drm_fbdev_overalloc (int)
+ Overallocation of the fbdev buffer (%) [default=100]
+
+edid_firmware (string)
+ Do not probe monitor, use specified EDID blob from built-in data or
/lib/firmware instead.
+
+fbdev_emulation (bool)
+ Enable legacy fbdev emulation [default=true]
+
+poll (bool)
+
+
--
2.11.0
--
To unsubscribe from this list: send the line "unsubscribe linux-doc" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
