Skip to content

feat[DSS7]: Document SELF_REFRESH and ALWAYS_ON_DISPLAY properties - #760

Open
devarsht wants to merge 1 commit into
TexasInstruments:masterfrom
devarsht:dss_aod_sr
Open

feat[DSS7]: Document SELF_REFRESH and ALWAYS_ON_DISPLAY properties#760
devarsht wants to merge 1 commit into
TexasInstruments:masterfrom
devarsht:dss_aod_sr

Conversation

@devarsht

Copy link
Copy Markdown
Collaborator

Add the SELF_REFRESH (plane) and ALWAYS_ON_DISPLAY (crtc) DRM properties to the tidss properties table, along with usage sections describing their behaviour and modetest examples, following the format used for the other documented properties.

@StaticRocket StaticRocket left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There's also some unnecessary use of passive voice in here

Comment thread source/linux/Foundational_Components/Kernel/Kernel_Drivers/Display/DSS7.rst Outdated
Comment thread source/linux/Foundational_Components/Kernel/Kernel_Drivers/Display/DSS7.rst Outdated
Comment thread source/linux/Foundational_Components/Kernel/Kernel_Drivers/Display/DSS7.rst Outdated
Comment thread source/linux/Foundational_Components/Kernel/Kernel_Drivers/Display/DSS7.rst Outdated
Comment thread source/linux/Foundational_Components/Kernel/Kernel_Drivers/Display/DSS7.rst Outdated
Comment thread source/linux/Foundational_Components/Kernel/Kernel_Drivers/Display/DSS7.rst Outdated
Comment thread source/linux/Foundational_Components/Kernel/Kernel_Drivers/Display/DSS7.rst Outdated
@SenWang125

Copy link
Copy Markdown
Contributor

Don't have any comments, looks good to me.

Add the SELF_REFRESH (plane) and ALWAYS_ON_DISPLAY (crtc) DRM
properties to the tidss properties table, along with usage
sections describing their behaviour and modetest examples,
following the format used for the other documented properties.

Signed-off-by: Devarsh Thakkar <devarsht@ti.com>
@devarsht

Copy link
Copy Markdown
Collaborator Author

There's also some unnecessary use of passive voice in here

@StaticRocket Yeah but re-reading those sentences which vale reported, those sentences look very much understandable/readable to me and I would prefer to keep that way. But if it's a more popular opinion to always use active voice I can always modify.

@StaticRocket

Copy link
Copy Markdown
Member

Technical documentation is normally declarative and uses active voice. As an example of what I mean: We are dictating the way something behaves under optimal conditions. We are not writing to a friend about something that may or may not happen due to circumstance.

It makes it dry, but brief, easier to translate, and usually easier to understand.

@StaticRocket

Copy link
Copy Markdown
Member

You're also bugging commit-check with that patch formatting

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants