dri-devel October 2019

dri-devel@lists.freedesktop.org

359 participants
1833 discussions

[PULL] drm-misc-fixes
by Maxime Ripard 07 Oct '19

07 Oct '19

Hi Dave, Daniel, I hope that you enjoy XDC if you could make it this year :) Here's the first round of fixes for drm-misc Maxime drm-misc-fixes-2019-10-02: - One include fix for tilcdc - A memory leak fix for Komeda - Some fixes for resources cleanups with writeback The following changes since commit 54ecb8f7028c5eb3d740bb82b0f1d90f2df63c5c: Linux 5.4-rc1 (2019-09-30 10:35:40 -0700) are available in the Git repository at: git://anongit.freedesktop.org/drm/drm-misc tags/drm-misc-… [View More]

2 2

[PULL] drm-intel-next
by Joonas Lahtinen 07 Oct '19

07 Oct '19

Hi Dave & Daniel, Back from XDC, so here comes the first bunch of features. For uAPI: immutable zpos plane property added, disallow userptr import of GGTT mmapped buffer and disallow tiling Other than that loads of early Tigerlake enabling and many Icelake fixups. DP MST and PSR fixes as well as audio tweaks. Gen7 and Cherryview are back to aliasing ppGTT from full, for being too fragile with the timing of the flush calls. And yeah, we eliminated struct_mutex as BKL, now only used for … [View More]execbuffer and working towards dma_resv replacing it. (perf and GVT corner cases are to be cleaned up). So that is an end to 2 year journey. Regards, Joonas *** drm-intel-next-2019-10-07: UAPI Changes: - Never allow userptr into the mappable GGTT (Chris) No existing users. Avoid anyone from even trying to spare a deadlock scenario. Cross-subsystem Changes: Core Changes: Driver Changes: - Eliminate struct_mutex use as BKL! (Chris) Only used for execbuf serialisation. - Initialize DDI TC and TBT ports (D-I) on Tigerlake (Lucas) - Fix DKL link training for 2.7GHz and 1.62GHz (Jose) - Add Tigerlake DKL PHY programming sequences (Clinton) - Add Tigerlake Thunderbolt PLL divider values (Imre) - drm/i915: Use helpers for drm_mm_node booleans (Chris) - Restrict L3 remapping sysfs interface to dwords (Chris) - Fix audio power up sequence for gen10+ display (Kai) - Skip redundant execlist resubmission (Chris) - Only unwedge if we can reset GPU first (Chris) - Initialise breadcrumb lists on the virtual engine (Chris) - Don't rely on kernel context existing during early errors (Matt A) - Update Icelake+ MG_DP_MODE programming table (Clinton) - Update DMC firmware for Icelake (Anusha) - Downgrade DP MST error after unplugging TypeC cable (Srinivasan) - Limit MST modes based on plane size too (Ville) - Polish intel_tv_mode_valid() (Ville) - Fix g4x sprite scaling stride check with GTT remapping (Ville) - Don't advertize non-exisiting crtcs (Ville) - Clean up encoder->crtc_mask setup (Ville) - Use tc_port instead of port parameter to MG registers (Jose) - Remove static variable for aux last status (Jani) - Implement a better i945gm vblank irq vs. C-states workaround (Ville) - Make the object creation interface consistent (CQ) - Rename intel_vga_msr_write() to intel_vga_reset_io_mem() (Jani, Ville) - Eliminate previous drm_dbg/drm_err usage (Jani) - Move gmbus setup down to intel_modeset_init() (Jani) - Abstract all vgaarb access to intel_vga.[ch] (Jani) - Split out i915_switcheroo.[ch] from i915_drv.c (Jani) - Use intel_gt in has_reset* (Chris) - Eliminate return value for i915_gem_init_early (Matt A) - Selftest improvements (Chris) - Update HuC firmware header version number format (Daniele) drm-intel-next-2019-09-27: UAPI Changes: - Revert "drm/i915: Fix DP-MST crtc_mask" to avoid MST regressions (Ville) - Disable set/get_tiling ioctl on Gen12+ as hardware is gone (Daniel) - Add immutable zpos plane properties (Ville) - Report dual-subslice count as subslices for Tigerlake (Daniele) Driver Changes: <TIGERLAKE ENABLING> - Enable HDCP 1.4 and 2.2 on Gen12+ (Ramalingam) - Enable display state buffer (DSB) batch-programming (Animesh) - Add 12 BPC support for Tigerlake (Anusha) - Add maximum resolution supported by PSR2 HW for Tigerlake (Jose) - Only allow PSR2 on supporting transcoders (Jose) - Disable pipes in reverse order to comply with MST for Tigerlake+ (Jose) - Implement Tigerlake DisplayPort training sequence (Jose) - Do not apply WaIncreaseDefaultTLBEntries from Gen12 onwards (Michel) - Reuse Icelake OA context logic for Tigerlake (Michel) - Enable VD HCP/MFX sub-pipe power gating (Michel) - Use separate context for relocations to deal with Tigerlake pre-parser (Daniele) - Enabling DSC on Pipe A for Tigerlake (Madhumitha) - Remove Yf tiling and legacy CCS support starting Tigerlake (Dhinakaran) - Remove PSR link standby support starting Tigerlake (Jose) - Access the right register when handling PSR interruptions (Jose) - Move DP_TP_* registers from port to transcoder for Tigerlake (Lucas) - Disable SAGV for Tigerlake (Lucas) - Reuse Gen11 stolen initialization for Gen12 (Lucas) - Apply FBC WA for Tigerlake too (Jose) - Use engine relative LRIs on context setup for Tigerlake (Mika, Daniele) - Register state context definition for Gen12 (Michel) - Extend MI_SEMAPHORE_WAIT instruction for Tigerlake (Chris) - Disable various Tigerlake features in attempt to have stable CI results (Chris) - Add Tigerlake W/A to disable CPS aware color pipe by setting chicken bit (Radhakrishna) - Add Tigerlake W/A to Enable Small PL for power benefit (Michel) - Add missing DDI clock select during DP init sequence for Tigerlake (Clinton) - Add missing update_active_dpll callback on Tigerlake (Clinton) - Finish modular FIA support on registers for Tigerlake (Jose) - Unify disable and enable phy clock gating functions on Tigerlake (Jose) - Check the UC health of TC controllers after power on (Jose) - Add TigerLake bandwidth checking (Stanislav) - Add Pipe D cursor ctrl register for Gen12 (Ankit) - Add DKL PHY PLL calculations (Lucas, Vandita, Jose) - Add memory type decoding for bandwidth checking (James) </TIGERLAKE ENABLING> - Downgrade Gen7 and Cherryview back to aliasing-ppGTT (Chris) - Limit MST to <= 8bpc once again (Ville) - Restrict the aliasing-ppgtt to the size of the ggtt (Chris) - Restore relaxed padding (OCL_OOB_SUPPRES_ENABLE) for SKL+ (Chris, Jason) - Whitelist COMMON_SLICE_CHICKEN2 (Kenneth) - Include GTT page-size info in error state (Matt A) - Clear STOP_RING bit on reset (Chris) - Ignore lost CSB completion events (Chris) - Use a high priority wq for nonblocking plane updates (Ville) - Bump up Skylake/Icelake+ display/plane/fb size restrictions (Manasi, Ville) - Update Gen11/Gen12 forcewake ranges from BSpec (Mika, Daniele, Michel) - Allow downscale factor of <3.0 on GLK+ for all formats (Ville) - Add missing Comet Lake PCH PCI ID (Matt) - Fix Gen11 SFC reset flow (Daniele) - Fix YCbCr programming for ILK-IVB,HSW+ (Ville) - Save audio frequency programming state at audio domain suspend (Kai) - Fix DisplayPort DSC BPP calculations (Maarten) - Add hardware readout for FEC (Maarten) - Do not add all planes when checking scalers on GLK+ (Maarten) - Make small joiner RAM buffer size platform-specific (Matt R) - Use per-process HWSP as scratch (Michal Wi) - Match allowed Gen11+ CDCLK values to BSpec (Matt R) - Rework CDCLK code for clarity and table format (Matt R) - Unify CDCLK code to reuse functions (Ville) - Enhance CDCLK sanitization (Matt R) - Preallocate Braswell top-level page directory (Chris) - Make vgpu ppgtt notificaiton as atomic operation (Xiaolin) - Use NOEVICT for first pass on attemping to pin a GGTT mmap (Chris) - Disable PSR if more than one eDP panel is present (Jose) - Make breadcrumb flushes more robust (Chris) - Extend non readable MCR range (Mika) - Protect our local workers against I915_FENCE_TIMEOUT (Chris) - Allow stolen memory (and future local memory) addresses in sg_table (Matt A) - Better organize the disable sequence in atomic_commit_tail() (Manasi) - Fix regression with crtc disable ordering (Maarten) - Add HW Gamma LUT readout (Swati) - Hook up power management code to use intel_gt (Andi) - Rework codebase towards use of intel_gt (Tvrtko) - Remove incorrect BUG_ON for schedule-out (Chris, Vinay) - Cleanup cache coloring code (Matt A) - Flush writes before RING_TAIL update on SNB (Chris) - Perform GGTT restore much earlier during resume (Chris) - Make shrink pinning atomic (Chris) - Make i915_vma.flags atomic for mutex reduction (Chris) - Make sure the gen6 ppgtt is bound before first use without struct mutex (Chris) - Report IOMMU status in debugfs (Chris) - Disable FBC if BIOS reserved memory (stolen) is unavailable (Chris) - Add a paranoid flushes and context reload around GPU reset (Chris) - Skip engine busyness sampling when and where not needed (Tvrtko) - Use GT parked time for estimating RC6 while asleep (Chris) - Get the correct wakeref for reading hotplug registers from debugfs (Arkadiusz) - Only apply a rmw mmio update if the value changes (Chris, Daniele) - Extend Haswell GT1 PSMI workaround to all HSW (Chris) - Only enqueue already completed requests (Chris) - Fix preempt-to-busy interactions of virtual requests (Chris) - Prevent bonded requests from overtaking each other on preemption (Chris) - Mark contents as dirty on a write fault (Chris) - Adjust length of MI_LOAD_REGISTER_REG (Michal Wi) - Don't disable interrupts for intel_engine_breadcrumbs_irq() (Sebastian) - Extract GT render sleep (rc6) management (Andi) - Rework SSEU reporting code (Stuart) - Use correct DSC registers in intel_configure_pps_for_dsc_encoder (Manasi) - Use enum pipe instead of crtc index to track active pipes (Ville) - Enforce irq-off lockdep check for for timeline locks (Chris) - Flush the existing fence before GGTT read/write (Chris) - Keep drm_i915_file_private around under RCU (Chris) - Call dma_set_max_seg_size() to silence spurious warnings (Lyude) - Make engine's batch pool safe for use with virtual engines (Chris) - Align power domain names with port names (Imre) - Parameterize and unify HPD code (Lucas) - Use RCU for unlocked vm_idr lookup (Chris) - Replace obj->pin_global with obj->frontbuffer (Chris) - Rework code to use INTEL_NUM_PIPES() (Jani) - Convert device info num_pipes to pipe_mask (Jani) - Introduce INTEL_DISPLAY_ENABLED() (Jani) - Stop conflating HAS_DISPLAY() and disabled display (Jani) - Modularize i915 modesetting probing/init code (Jani) - Use drm_format_info_is_yuv_semiplanar() instead of rolling own (Ville) - Other display codebase cleanups (Ville) - Other GEM codebase cleanup, lockdep and selftest improvements (Chris) - Future-proof DDC pin mapping to reuse ICP variant (Matt R) - Rewrite timeline handling to be RCU based (Chris) - Define explicit wedged on init reset state (Michal Wi) - Add GuC firmware for Elkhartlake (Daniele) - Update HuC firmware naming convention and bump versions (Anusha) - Extract common code from GuC stop/disable comm (Fernando) - Fix perf kernel-doc formatting for struct members (Anna) - Documentation fixes (Joonas) The following changes since commit be91233b1053d9725d3a437e3da44ccff2639477: drm/i915: Update DRIVER_DATE to 20190822 (2019-08-22 05:46:28 -0700) are available in the Git repository at: git://anongit.freedesktop.org/drm/drm-intel tags/drm-intel-next-2019-10-07 for you to fetch changes up to 9445ad17109b6fe7864acc33f0c62bd9d866b722: drm/i915: Update DRIVER_DATE to 20191007 (2019-10-07 15:24:47 +0300) ---------------------------------------------------------------- UAPI Changes: - Never allow userptr into the mappable GGTT (Chris) No existing users. Avoid anyone from even trying to spare a deadlock scenario. Cross-subsystem Changes: Core Changes: Driver Changes: - Eliminate struct_mutex use as BKL! (Chris) Only used for execbuf serialisation. - Initialize DDI TC and TBT ports (D-I) on Tigerlake (Lucas) - Fix DKL link training for 2.7GHz and 1.62GHz (Jose) - Add Tigerlake DKL PHY programming sequences (Clinton) - Add Tigerlake Thunderbolt PLL divider values (Imre) - drm/i915: Use helpers for drm_mm_node booleans (Chris) - Restrict L3 remapping sysfs interface to dwords (Chris) - Fix audio power up sequence for gen10+ display (Kai) - Skip redundant execlist resubmission (Chris) - Only unwedge if we can reset GPU first (Chris) - Initialise breadcrumb lists on the virtual engine (Chris) - Don't rely on kernel context existing during early errors (Matt A) - Update Icelake+ MG_DP_MODE programming table (Clinton) - Update DMC firmware for Icelake (Anusha) - Downgrade DP MST error after unplugging TypeC cable (Srinivasan) - Limit MST modes based on plane size too (Ville) - Polish intel_tv_mode_valid() (Ville) - Fix g4x sprite scaling stride check with GTT remapping (Ville) - Don't advertize non-exisiting crtcs (Ville) - Clean up encoder->crtc_mask setup (Ville) - Use tc_port instead of port parameter to MG registers (Jose) - Remove static variable for aux last status (Jani) - Implement a better i945gm vblank irq vs. C-states workaround (Ville) - Make the object creation interface consistent (CQ) - Rename intel_vga_msr_write() to intel_vga_reset_io_mem() (Jani, Ville) - Eliminate previous drm_dbg/drm_err usage (Jani) - Move gmbus setup down to intel_modeset_init() (Jani) - Abstract all vgaarb access to intel_vga.[ch] (Jani) - Split out i915_switcheroo.[ch] from i915_drv.c (Jani) - Use intel_gt in has_reset* (Chris) - Eliminate return value for i915_gem_init_early (Matt A) - Selftest improvements (Chris) - Update HuC firmware header version number format (Daniele) ---------------------------------------------------------------- Andi Shyti (2): drm/i915: Hook up GT power management drm/i915: Extract GT render sleep (rc6) management Animesh Manna (9): drm/i915/dsb: feature flag added for display state buffer. drm/i915/dsb: DSB context creation. drm/i915/dsb: Indexed register write function for DSB. drm/i915/dsb: Check DSB engine status. drm/i915/dsb: functions to enable/disable DSB engine. drm/i915/dsb: function to trigger workload execution of DSB. drm/i915/dsb: Enable gamma lut programming using DSB. drm/i915/dsb: Enable DSB for gen12. drm/i915/dsb: Documentation for DSB. Ankit Nautiyal (1): drm/i915: Add Pipe D cursor ctrl register for Gen12 Anna Karas (1): drm/i915/perf: Fix use of kernel-doc format in structure members Anusha Srivatsa (3): drm/dp/dsc: Add Support for all BPCs supported by TGL drm/i915/uc: Update HuC firmware naming convention and load latest HuC drm/i915/dmc: Update ICL DMC version to v1.09 Arkadiusz Hiler (1): drm/i915: Get the correct wakeref for reading HOTPLUG_EN et al. CQ Tang (1): drm/i915/stolen: make the object creation interface consistent Chris Wilson (108): drm/i915: Hold irq-off for the entire fake lock period drm/i915/gtt: Preallocate Braswell top-level page directory drm/i915: Flush the existing fence before GGTT read/write drm/i915: Keep drm_i915_file_private around under RCU drm/i915/selftests: Teach igt_gpu_fill_dw() to take intel_context drm/i915/selftests: Add the usual batch vma managements to st_workarounds drm/i915: Use NOEVICT for first pass on attemping to pin a GGTT mmap drm/i915/selftests: Markup impossible error pointers drm/i915: Only activate i915_active debugobject once drm/i915: Make engine's batch pool safe for use with virtual engines drm/i915/selftests: Remove accidental serialization between gpu_fill drm/i915/selftests: Try to recycle context allocations drm/i915/execlists: Flush the post-sync breadcrumb write harder drm/i915/selftests: Ignore coherency failures on Broadwater drm/i915: Protect our local workers against I915_FENCE_TIMEOUT drm/i915/selftests: cond_resched() within the longer buddy tests drm/i915/execlists: Try rearranging breadcrumb flush drm/i915/gtt: Downgrade gen7 (ivb, byt, hsw) back to aliasing-ppgtt drm/i915/gtt: Downgrade Cherryview back to aliasing-ppgtt drm/i915: Remove ppgtt->dirty_engines drm/i915: Use RCU for unlocked vm_idr lookup drm/i915/perf: Assert locking for i915_init_oa_perf_state() drm/i915: Restrict the aliasing-ppgtt to the size of the ggtt drm/i915: Report aliasing ppgtt size as ggtt size drm/i915: Replace obj->pin_global with obj->frontbuffer drm/i915/selftests: Remove unused __engines_name() drm/i915: Refresh the errno to vmf_fault translations drm/i915: Restore relaxed padding (OCL_OOB_SUPPRES_ENABLE) for skl+ drm/i915: Protect debugfs per_file_stats with RCU lock drm/i915/execlists: Remove incorrect BUG_ON for schedule-out drm/i915/execlists: Clear STOP_RING bit on reset drm/i915/execlists: Ignore lost completion events drm/i915/ringbuffer: Flush writes before RING_TAIL update drm/i915: Perform GGTT restore much earlier during resume drm/i915/selftests: Take runtime wakeref for igt_ggtt_lowlevel drm/i915/selftests: Tighten the timeout testing for partial mmaps drm/i915/tgl: Disable rc6 for debugging drm/i915: Make shrink/unshrink be atomic drm/i915: Make i915_vma.flags atomic_t for mutex reduction drm/i915/display: Add glk_cdclk_table drm/i915/tgl: Disable read-only ppgtt support drm/i915: Squeeze iommu status into debugfs/i915_capabilities drm/i915: Disable FBC if BIOS reserved memory (stolen) is unavailable drm/i915/execlists: Add a paranoid flush of the CSB pointers upon reset drm/i915/execlists: Ensure the context is reloaded after a GPU reset drm/i915/pmu: Use GT parked for estimating RC6 while asleep drm/i915/tgl: Disable preemption while being debugged drm/i915/selftests: Keep the engine awake while we keep for preemption drm/i915/gtt: Make sure the gen6 ppgtt is bound before first use drm/i915: Don't mix srcu tag and negative error codes drm/i915/tgl: Limit ourselves to just rcs0 drm/i915: Show the logical context ring state on dumping drm/i915: Only apply a rmw mmio update if the value changes drm/i915/tgl: Extend MI_SEMAPHORE_WAIT drm/i915: Extend Haswell GT1 PSMI workaround to all drm/i915: Verify the engine after acquiring the active.lock drm/i915/selftests: Exercise CS TLB invalidation drm/i915/tgl: Suspend pre-parser across GTT invalidations drm/i915: Mark i915_request.timeline as a volatile, rcu pointer drm/i915: Lock signaler timeline while navigating drm/i915: Protect timeline->hwsp dereferencing Revert "drm/i915/tgl: Implement Wa_1406941453" drm/i915/execlists: Relax assertion for a pinned context image on reset drm/i915/execlists: Drop redundant list_del_init(&rq->sched.link) drm/i915: Only enqueue already completed requests drm/i915/execlists: Refactor -EIO markup of hung requests drm/i915: Fixup preempt-to-busy vs resubmission of a virtual request drm/i915: Fixup preempt-to-busy vs reset of a virtual request drm/i915: Prevent bonded requests from overtaking each other on preemption drm/i915: Mark contents as dirty on a write fault drm/i915/selftests: Verify the LRC register layout between init and HW drm/i915/tgl: Swap engines for no rps (gpu reclocking) drm/i915/execlists: Simplify gen12_csb_parse drm/i915/selftests: Exercise concurrent submission to all engines drm/i915/selftests: Do not try to sanitize mock HW drm/i915: Pass intel_gt to has-reset? drm/i915/selftests: Distinguish mock device from no wakeref drm/i915/selftests: Provide a mock GPU reset routine drm/i915/selftests: Exercise context switching in parallel drm/i915/gt: Only unwedge if we can reset first drm/i915: Initialise breadcrumb lists on the virtual engine drm/i915/userptr: Never allow userptr into the mappable GGTT drm/i915/selftests: Extract random_offset() for use with a prng drm/i915/gem: Refactor tests on obj->ops->flags drm/i915/selftests: Exercise potential false lite-restore drm/i915/execlists: Skip redundant resubmission drm/i915: Restrict L3 remapping sysfs interface to dwords drm/i915: Use helpers for drm_mm_node booleans drm/i915: Only track bound elements of the GTT drm/i915: Mark up address spaces that may need to allocate drm/i915: Pull i915_vma_pin under the vm->mutex drm/i915: Push the i915_active.retire into a worker drm/i915: Coordinate i915_active with its own mutex drm/i915: Move idle barrier cleanup into engine-pm drm/i915: Drop struct_mutex from around i915_retire_requests() drm/i915: Remove the GEM idle worker drm/i915: Merge wait_for_timelines with retire_request drm/i915/gem: Retire directly for mmap-offset shrinking drm/i915: Move request runtime management onto gt drm/i915: Move global activity tracking from GEM to GT drm/i915: Remove logical HW ID drm/i915: Move context management under GEM drm/i915/overlay: Drop struct_mutex guard drm/i915: Drop struct_mutex guard from debugfs/framebuffer_info drm/i915: Remove struct_mutex guard for debugfs/opregion drm/i915: Drop struct_mutex from suspend state save/restore drm/i915/selftests: Drop vestigal struct_mutex guards drm/i915: Drop struct_mutex from around GEM initialisation Clinton A Taylor (4): drm/i915/tgl: Add missing ddi clock select during DP init sequence drm/i915/tgl/pll: Set update_active_dpll drm/i915/tc: Update DP_MODE programming drm/i915/tgl: Add dkl phy programming sequences Daniel Vetter (1): drm/i915: disable set/get_tiling ioctl on gen12+ Daniele Ceraolo Spurio (5): drm/i915/uc: define GuC and HuC FWs for EHL drm/i915: use a separate context for gpu relocs drm/i915: fix SFC reset flow drm/i915/tgl: s/ss/eu fuse reading support drm/i915/huc: fix version parsing from CSS header Dhinakaran Pandiyan (1): drm/i915/tgl: Gen-12 display loses Yf tiling and legacy CCS support Fernando Pacheco (1): drm/i915/uc: Extract common code from GuC stop/disable comm Imre Deak (2): drm/i915: Align power domain names with port names drm/i915/tgl: Add the Thunderbolt PLL divider values James Ausmus (1): drm/i915/tgl: Add memory type decoding for bandwidth checking Jani Nikula (18): drm/i915: add INTEL_NUM_PIPES() and use it drm/i915: convert device info num_pipes to pipe_mask drm/i915: introduce INTEL_DISPLAY_ENABLED() drm/i915: stop conflating HAS_DISPLAY() and disabled display drm/i915/dsb: single register write function for DSB. drm/i915: add i915_driver_modeset_remove() drm/i915: pass i915 to i915_driver_modeset_probe() drm/i915: pass i915 to intel_modeset_driver_remove() drm/i915: abstract intel_panel_sanitize_ssc() from intel_modeset_init() drm/i915: abstract intel_mode_config_init() from intel_modeset_init() drm/i915: pass i915 to intel_modeset_init() and intel_modeset_init_hw() drm/i915/display: abstract all vgaarb access to intel_vga.[ch] drm/i915: use DRM_ERROR() instead of drm_err() drm/i915: use DRM_DEBUG_KMS() instead of drm_dbg(DRM_UT_KMS, ...) drm/i915/dp: remove static variable for aux last status drm/i915/vga: rename intel_vga_msr_write() to intel_vga_reset_io_mem() drm/i915: split out i915_switcheroo.[ch] from i915_drv.c drm/i915: move gmbus setup down to intel_modeset_init() Joonas Lahtinen (4): drm/i915: Remove link to missing "Batchbuffer Pools" documentation drm/i915: Indent GuC/WOPCM documentation sections drm/i915: Update DRIVER_DATE to 20190927 drm/i915: Update DRIVER_DATE to 20191007 José Roberto de Souza (21): drm/i915/psr: Make PSR registers relative to transcoders drm/i915: Add transcoder restriction to PSR2 drm/i915: Do not unmask PSR interruption in IRQ postinstall drm/i915/tgl: Guard and warn if more than one eDP panel is present drm/i915: Do not read PSR2 register in transcoders without PSR2 drm/i915/tgl: Add maximum resolution supported by PSR2 HW drm: Add for_each_oldnew_intel_crtc_in_state_reverse() drm/i915: Disable pipes in reverse order drm/i915/tgl: Implement TGL DisplayPort training sequence drm/i915/tgl: PSR link standby is not supported anymore drm/i915/psr: Only handle interruptions of the transcoder in use drm/i915/tgl: Access the right register when handling PSR interruptions drm/i915: Apply FBC WA for TGL too drm/i915/mst: Do not hardcoded the crtcs that encoder can connect drm/i915/tgl: Finish modular FIA support on registers drm/i915/icl: Unify disable and enable phy clock gating functions drm/i915/tgl: Check the UC health of tc controllers after power on drm/i915/tgl: Add dkl phy pll calculations drm/i915/tgl: Return the mg/dkl pll as DDI clock for new TC ports drm/i915/tgl: Fix dkl link training drm/i915/mg: Use tc_port instead of port parameter to MG registers Kai Vehmanen (3): drm/i915: save AUD_FREQ_CNTRL state at audio domain suspend drm/i915: Fix audio power up sequence for gen10+ display drm/i915: extend audio CDCLK>=2*BCLK constraint to more platforms Kenneth Graunke (1): drm/i915: Whitelist COMMON_SLICE_CHICKEN2 Lucas De Marchi (11): drm/i915: parameterize south hpd macros drm/i915: unify icp, tgp and mcc irq handling drm/i915: parameterize SDE hotplug registers drm/i915: unify icp, tgp and mcc irq setup drm/i915: protect access to DP_TP_* on non-dp drm/i915/tgl: move DP_TP_* to transcoder drm/i915/tgl: disable SAGV temporarily drm/i915/tgl: add gen12 to stolen initialization drm/i915/tgl: Add initial dkl pll support drm/i915/tgl: re-indent code to prepare for DKL changes drm/i915/tgl: initialize TC and TBT ports Lyude Paul (1): drm/i915: Call dma_set_max_seg_size() in i915_driver_hw_probe() Maarten Lankhorst (6): drm/i915: Fix regression with crtc disable ordering drm/i915/dp: Fix dsc bpp calculations, v5. drm/i915: Add hardware readout for FEC drm/i915: Get rid of crtc_state->fb_changed drm/i915: Rename planar linked plane variables drm/i915: Do not add all planes when checking scalers on glk+ Madhumitha Tolakanahalli Pradeep (1): drm/i915/tgl: Enabling DSC on Pipe A for TGL Manasi Navare (5): drm/i915/dp: Fix DSC enable code to use cpu_transcoder instead of encoder->type drm/i915/display: Rename update_crtcs() to commit_modeset_enables() drm/i915/display: Move the commit_tail() disable sequence to separate function drm/i915/display/icl: Bump up the hdisplay and vdisplay as per transcoder limits drm/i915/display/icl: Bump up the plane/fb height Matt Roper (15): drm/i915: Allow /2 CD2X divider on gen11+ drm/i915: Add 324mhz and 326.4mhz cdclks for gen11+ drm/i915/tgl: Use refclk/2 as bypass frequency drm/i915: Consolidate bxt/cnl/icl cdclk readout drm/i915: Use literal representation of cdclk tables drm/i915: Combine bxt_set_cdclk and cnl_set_cdclk drm/i915: Kill cnl_sanitize_cdclk() drm/i915: Consolidate {bxt,cnl,icl}_uninit_cdclk drm/i915: Add calc_voltage_level display vfunc drm/i915: Enhance cdclk sanitization drm/i915: Consolidate {bxt,cnl,icl}_init_cdclk drm/i915/cml: Add second PCH ID for CMP drm/i915: Future-proof DDC pin mapping drm/i915: Unify ICP and MCC hotplug pin tables drm/i915: Small joiner RAM buffer size is platform-specific Matthew Auld (8): drm/i915: s/for_each_sgt_dma/for_each_sgt_daddr/ drm/i915/buddy: add missing call to i915_global_register drm/i915: export color_differs drm/i915: s/i915_gtt_color_adjust/i915_ggtt_color_adjust drm/i915: cleanup cache-coloring drm/i915: include GTT page-size info in error state drm/i915: check for kernel_context drm/i915: simplify i915_gem_init_early Michał Winiarski (4): drm/i915: Define explicit wedged on init reset state drm/i915/execlists: Use per-process HWSP as scratch drm/i915: Adjust length of MI_LOAD_REGISTER_REG drm/i915: Add definitions for MI_MATH command Michel Thierry (7): drm/i915/tgl: Move GTCR register to cope with GAM MMIO address remap drm/i915/tgl: Enable VD HCP/MFX sub-pipe power gating drm/i915/tgl: Do not apply WaIncreaseDefaultTLBEntries from GEN12 onwards drm/i915/tgl/perf: use the same oa ctx_id format as icl drm/i915/tgl: Register state context definition for Gen12 drm/i915/tgl: Introduce gen12 forcewake ranges drm/i915/tgl: Implement Wa_1406941453 Mika Kuoppala (4): drm/i915: Extend non readable mcr range drm/i915: Use engine relative LRIs on context setup drm/i915: Update Gen11 forcewake ranges drm/i915/tgl: Re-enable rc6 Radhakrishna Sripada (1): drm/i915/tgl: Implement Wa_1409142259 Ramalingam C (6): drm/i915: mei_hdcp: I915 sends ddi index as per ME FW drm: Move port definition back to i915 header drm: Extend I915 mei interface for transcoder info misc/mei/hdcp: Fill transcoder index in port info drm/i915/hdcp: update current transcoder into intel_hdcp drm/i915/hdcp: Enable HDCP 1.4 and 2.2 on Gen12+ Sebastian Andrzej Siewior (2): drm/i915: Drop the IRQ-off asserts drm/i915: Don't disable interrupts for intel_engine_breadcrumbs_irq() Srinivasan S (1): drm/i915/dp: Fix DP MST error after unplugging TypeC cable Stanislav Lisovskiy (1): drm/i915: Add TigerLake bandwidth checking Stuart Summers (11): drm/i915: Use variable for debugfs device status drm/i915: Add function to set SSEU info per platform drm/i915: Add subslice stride runtime parameter drm/i915: Add EU stride runtime parameter drm/i915: Use local variables for subslice_mask for device info drm/i915: Add function to set subslices drm/i915: Use subslice stride to set subslices for a given slice drm/i915: Add function to determine if a slice has a subslice drm/i915: Refactor instdone loops on new subslice functions drm/i915: Add new function to copy subslices for a slice drm/i915: Expand subslice mask Swati Sharma (13): drm/i915/display: Add debug log for color parameters drm/i915/display: Add func to get gamma bit precision drm/i915/display: Add func to compare hw/sw gamma lut drm/i915/display: Add macro to compare gamma hw/sw lut drm/i915/display: Extract i9xx_read_luts() drm/i915/display: Extract ilk_read_luts() drm/i915/display: Extract glk_read_luts() drm/i915/display: Add gamma precision function for CHV drm/i915/display: Extract i965_read_luts() drm/i915/display: Extract chv_read_luts() drm/i915/color: Fix formatting issues drm/i915/color: Extract icl_read_luts() Revert "drm/i915/color: Extract icl_read_luts()" Tvrtko Ursulin (5): drm/i915: Move GT init to intel_gt.c drm/i915: Make wait_for_timelines take struct intel_gt drm/i915: Avoid round-trip via i915 in intel_gt_park drm/i915: Make pm_notify take intel_gt drm/i915/pmu: Skip busyness sampling when and where not needed Vandita Kulkarni (2): drm/i915/tgl: Add dkl phy registers drm/i915/tgl: Add support for dkl pll write Ville Syrjälä (38): drm/i915: Use enum pipe instead of crtc index to track active pipes drm/i915: Unconfuse pipe vs. crtc->index in i915_get_crtc_scanoutpos() drm/i915: Use enum pipe consistently drm/i915: s/num_active_crtcs/num_active_pipes/ drm/i915: Use hweight8() for 8bit masks drm/i915: Limit MST to <= 8bpc once again drm/i915: Prefer encoder->name over port_name() drm/i915: Clean up HDMI deep color handling a bit Revert "drm/i915: Fix DP-MST crtc_mask" drm/i915: add immutable zpos plane properties drm/i915: Use a high priority wq for nonblocking plane updates drm/i915: Remove pointless planes_changed=true assignment drm/i915: Fix cdclk bypass freq readout for tgl/bxt/glk drm/i915: Fix CD2X pipe select masking during cdclk sanitation drm/i915: Reuse cnl_modeset_calc_cdclk() on icl+ drm/i915: Remove duplicated bxt/cnl/icl .modeset_calc_cdclk() funcs drm/i915: Replace is_planar_yuv_format() with drm_format_info_is_yuv_semiplanar() drm/i915: Allow downscale factor of <3.0 on glk+ for all formats drm/i915: Extract intel_modeset_calc_cdclk() drm/i915: s/pipe_config/crtc_state/ in intel_crtc_atomic_check() drm/i915: Bump skl+ max plane width to 5k for linear/x-tiled drm/i915: Don't advertise modes that exceed the max plane size drm/i915: Fix HSW+ DP MSA YCbCr colorspace indication drm/i915: Fix AVI infoframe quantization range for YCbCr output drm/i915: Extract intel_hdmi_limited_color_range() drm/i915: Never set limited_color_range=true for YCbCr output drm/i915: Don't look at unrelated PIPECONF bits for interlaced readout drm/i915: Simplify intel_get_crtc_ycbcr_config() drm/i915: Add PIPECONF YCbCr 4:4:4 programming for HSW drm/i915: Document ILK+ pipe csc matrix better drm/i915: Set up ILK/SNB csc unit properly for YCbCr output drm/i915: Add PIPECONF YCbCr 4:4:4 programming for ILK-IVB drm/i915: Limit MST modes based on plane size too drm/i915: Polish intel_tv_mode_valid() drm/i915: Fix g4x sprite scaling stride check with GTT remapping drm/i915: Populate possible_crtcs correctly drm/i915: Clean up encoder->crtc_mask setup drm/i915: Implement a better i945gm vblank irq vs. C-states workaround Xiaolin Zhang (1): drm/i915: to make vgpu ppgtt notificaiton as atomic operation Documentation/gpu/i915.rst | 32 +- drivers/gpu/drm/i915/Makefile | 7 +- drivers/gpu/drm/i915/display/intel_atomic.c | 24 +- drivers/gpu/drm/i915/display/intel_atomic_plane.c | 9 +- drivers/gpu/drm/i915/display/intel_audio.c | 36 +- drivers/gpu/drm/i915/display/intel_bios.c | 2 +- drivers/gpu/drm/i915/display/intel_bios.h | 3 +- drivers/gpu/drm/i915/display/intel_bw.c | 81 +- drivers/gpu/drm/i915/display/intel_cdclk.c | 1264 ++++++++------------ drivers/gpu/drm/i915/display/intel_cdclk.h | 13 +- drivers/gpu/drm/i915/display/intel_color.c | 529 +++++++- drivers/gpu/drm/i915/display/intel_color.h | 7 + drivers/gpu/drm/i915/display/intel_crt.c | 4 +- drivers/gpu/drm/i915/display/intel_ddi.c | 642 +++++++--- drivers/gpu/drm/i915/display/intel_display.c | 1101 +++++++++-------- drivers/gpu/drm/i915/display/intel_display.h | 51 +- drivers/gpu/drm/i915/display/intel_display_power.c | 398 +++--- drivers/gpu/drm/i915/display/intel_display_power.h | 40 +- drivers/gpu/drm/i915/display/intel_display_types.h | 36 +- drivers/gpu/drm/i915/display/intel_dp.c | 408 ++++--- drivers/gpu/drm/i915/display/intel_dp.h | 7 +- drivers/gpu/drm/i915/display/intel_dp_mst.c | 30 +- drivers/gpu/drm/i915/display/intel_dpll_mgr.c | 364 +++++- drivers/gpu/drm/i915/display/intel_dsb.c | 332 +++++ drivers/gpu/drm/i915/display/intel_dsb.h | 52 + drivers/gpu/drm/i915/display/intel_dsi.c | 3 +- drivers/gpu/drm/i915/display/intel_dvo.c | 4 +- drivers/gpu/drm/i915/display/intel_fbc.c | 7 +- drivers/gpu/drm/i915/display/intel_fbdev.c | 14 +- drivers/gpu/drm/i915/display/intel_frontbuffer.c | 19 +- drivers/gpu/drm/i915/display/intel_gmbus.c | 2 +- drivers/gpu/drm/i915/display/intel_hdcp.c | 214 +++- drivers/gpu/drm/i915/display/intel_hdcp.h | 4 + drivers/gpu/drm/i915/display/intel_hdmi.c | 229 ++-- drivers/gpu/drm/i915/display/intel_hdmi.h | 1 + drivers/gpu/drm/i915/display/intel_hotplug.c | 3 +- drivers/gpu/drm/i915/display/intel_hotplug.h | 1 + drivers/gpu/drm/i915/display/intel_lpe_audio.c | 2 +- drivers/gpu/drm/i915/display/intel_lvds.c | 8 +- drivers/gpu/drm/i915/display/intel_overlay.c | 31 +- drivers/gpu/drm/i915/display/intel_psr.c | 299 +++-- drivers/gpu/drm/i915/display/intel_psr.h | 1 - drivers/gpu/drm/i915/display/intel_sdvo.c | 2 +- drivers/gpu/drm/i915/display/intel_sdvo.h | 1 + drivers/gpu/drm/i915/display/intel_sprite.c | 122 +- drivers/gpu/drm/i915/display/intel_sprite.h | 1 - drivers/gpu/drm/i915/display/intel_tc.c | 87 +- drivers/gpu/drm/i915/display/intel_tc.h | 1 + drivers/gpu/drm/i915/display/intel_tv.c | 10 +- drivers/gpu/drm/i915/display/intel_vdsc.c | 2 +- drivers/gpu/drm/i915/display/intel_vga.c | 160 +++ drivers/gpu/drm/i915/display/intel_vga.h | 18 + drivers/gpu/drm/i915/display/vlv_dsi.c | 2 +- drivers/gpu/drm/i915/gem/i915_gem_client_blt.c | 9 +- drivers/gpu/drm/i915/gem/i915_gem_context.c | 390 ++---- drivers/gpu/drm/i915/gem/i915_gem_context.h | 42 +- drivers/gpu/drm/i915/gem/i915_gem_context_types.h | 20 +- drivers/gpu/drm/i915/gem/i915_gem_domain.c | 56 +- drivers/gpu/drm/i915/gem/i915_gem_execbuffer.c | 83 +- drivers/gpu/drm/i915/gem/i915_gem_mman.c | 101 +- drivers/gpu/drm/i915/gem/i915_gem_object.c | 33 +- drivers/gpu/drm/i915/gem/i915_gem_object.h | 29 +- drivers/gpu/drm/i915/gem/i915_gem_object_blt.c | 4 +- drivers/gpu/drm/i915/gem/i915_gem_object_types.h | 8 +- drivers/gpu/drm/i915/gem/i915_gem_pages.c | 1 + drivers/gpu/drm/i915/gem/i915_gem_pm.c | 150 +-- drivers/gpu/drm/i915/gem/i915_gem_shrinker.c | 124 +- drivers/gpu/drm/i915/gem/i915_gem_stolen.c | 62 +- drivers/gpu/drm/i915/gem/i915_gem_throttle.c | 4 +- drivers/gpu/drm/i915/gem/i915_gem_tiling.c | 34 +- drivers/gpu/drm/i915/gem/i915_gem_userptr.c | 31 +- drivers/gpu/drm/i915/gem/selftests/huge_pages.c | 163 +-- .../drm/i915/gem/selftests/i915_gem_coherency.c | 40 +- .../gpu/drm/i915/gem/selftests/i915_gem_context.c | 540 ++++++--- drivers/gpu/drm/i915/gem/selftests/i915_gem_mman.c | 268 ++++- .../drm/i915/gem/selftests/i915_gem_object_blt.c | 4 - drivers/gpu/drm/i915/gem/selftests/i915_gem_phys.c | 2 - drivers/gpu/drm/i915/gem/selftests/igt_gem_utils.c | 33 +- drivers/gpu/drm/i915/gem/selftests/igt_gem_utils.h | 13 +- drivers/gpu/drm/i915/gem/selftests/mock_context.c | 15 +- drivers/gpu/drm/i915/gt/intel_breadcrumbs.c | 19 +- drivers/gpu/drm/i915/gt/intel_context.c | 22 +- drivers/gpu/drm/i915/gt/intel_context_types.h | 1 + drivers/gpu/drm/i915/gt/intel_engine.h | 1 - drivers/gpu/drm/i915/gt/intel_engine_cs.c | 73 +- drivers/gpu/drm/i915/gt/intel_engine_pm.c | 44 +- drivers/gpu/drm/i915/gt/intel_engine_pool.c | 15 +- drivers/gpu/drm/i915/gt/intel_engine_pool.h | 4 +- drivers/gpu/drm/i915/gt/intel_engine_types.h | 35 +- drivers/gpu/drm/i915/gt/intel_gpu_commands.h | 30 +- drivers/gpu/drm/i915/gt/intel_gt.c | 149 ++- drivers/gpu/drm/i915/gt/intel_gt.h | 12 +- drivers/gpu/drm/i915/gt/intel_gt_pm.c | 85 +- drivers/gpu/drm/i915/gt/intel_gt_pm.h | 11 + drivers/gpu/drm/i915/gt/intel_gt_requests.c | 123 ++ drivers/gpu/drm/i915/gt/intel_gt_requests.h | 24 + drivers/gpu/drm/i915/gt/intel_gt_types.h | 18 +- drivers/gpu/drm/i915/gt/intel_hangcheck.c | 5 +- drivers/gpu/drm/i915/gt/intel_lrc.c | 1240 +++++++++++++------ drivers/gpu/drm/i915/gt/intel_lrc.h | 14 + drivers/gpu/drm/i915/gt/intel_lrc_reg.h | 66 +- drivers/gpu/drm/i915/gt/intel_rc6.c | 712 +++++++++++ drivers/gpu/drm/i915/gt/intel_rc6.h | 25 + drivers/gpu/drm/i915/gt/intel_rc6_types.h | 28 + drivers/gpu/drm/i915/gt/intel_reset.c | 140 ++- drivers/gpu/drm/i915/gt/intel_reset.h | 16 +- drivers/gpu/drm/i915/gt/intel_reset_types.h | 6 + drivers/gpu/drm/i915/gt/intel_ringbuffer.c | 99 +- drivers/gpu/drm/i915/gt/intel_sseu.c | 37 +- drivers/gpu/drm/i915/gt/intel_sseu.h | 37 +- drivers/gpu/drm/i915/gt/intel_timeline.c | 56 +- drivers/gpu/drm/i915/gt/intel_timeline_types.h | 10 +- drivers/gpu/drm/i915/gt/intel_workarounds.c | 18 +- drivers/gpu/drm/i915/gt/selftest_context.c | 62 +- drivers/gpu/drm/i915/gt/selftest_gt_pm.c | 50 + drivers/gpu/drm/i915/gt/selftest_hangcheck.c | 155 +-- drivers/gpu/drm/i915/gt/selftest_lrc.c | 513 +++++--- drivers/gpu/drm/i915/gt/selftest_reset.c | 4 +- drivers/gpu/drm/i915/gt/selftest_timeline.c | 97 +- drivers/gpu/drm/i915/gt/selftest_workarounds.c | 63 +- drivers/gpu/drm/i915/gt/selftests/mock_timeline.c | 2 +- drivers/gpu/drm/i915/gt/uc/intel_guc_reg.h | 3 + drivers/gpu/drm/i915/gt/uc/intel_uc.c | 30 +- drivers/gpu/drm/i915/gt/uc/intel_uc_fw.c | 51 +- drivers/gpu/drm/i915/gt/uc/intel_uc_fw_abi.h | 8 +- drivers/gpu/drm/i915/gt/uc/selftest_guc.c | 4 - drivers/gpu/drm/i915/gvt/aperture_gm.c | 12 +- drivers/gpu/drm/i915/gvt/handlers.c | 2 +- drivers/gpu/drm/i915/gvt/kvmgt.c | 17 - drivers/gpu/drm/i915/gvt/scheduler.c | 27 +- drivers/gpu/drm/i915/i915_active.c | 340 ++++-- drivers/gpu/drm/i915/i915_active.h | 328 ++--- drivers/gpu/drm/i915/i915_active_types.h | 33 +- drivers/gpu/drm/i915/i915_buddy.c | 1 + drivers/gpu/drm/i915/i915_debugfs.c | 274 +++-- drivers/gpu/drm/i915/i915_drv.c | 212 ++-- drivers/gpu/drm/i915/i915_drv.h | 119 +- drivers/gpu/drm/i915/i915_gem.c | 317 +---- drivers/gpu/drm/i915/i915_gem_evict.c | 58 +- drivers/gpu/drm/i915/i915_gem_fence_reg.c | 9 +- drivers/gpu/drm/i915/i915_gem_gtt.c | 259 ++-- drivers/gpu/drm/i915/i915_gem_gtt.h | 67 +- drivers/gpu/drm/i915/i915_getparam.c | 4 +- drivers/gpu/drm/i915/i915_gpu_error.c | 28 +- drivers/gpu/drm/i915/i915_gpu_error.h | 3 +- drivers/gpu/drm/i915/i915_irq.c | 322 ++--- drivers/gpu/drm/i915/i915_irq.h | 4 +- drivers/gpu/drm/i915/i915_pci.c | 44 +- drivers/gpu/drm/i915/i915_perf.c | 116 +- drivers/gpu/drm/i915/i915_perf.h | 5 +- drivers/gpu/drm/i915/i915_pmu.c | 247 ++-- drivers/gpu/drm/i915/i915_pmu.h | 4 +- drivers/gpu/drm/i915/i915_query.c | 10 +- drivers/gpu/drm/i915/i915_reg.h | 636 +++++++--- drivers/gpu/drm/i915/i915_request.c | 276 ++--- drivers/gpu/drm/i915/i915_request.h | 32 +- drivers/gpu/drm/i915/i915_scatterlist.h | 8 +- drivers/gpu/drm/i915/i915_suspend.c | 11 +- drivers/gpu/drm/i915/i915_switcheroo.c | 67 ++ drivers/gpu/drm/i915/i915_switcheroo.h | 14 + drivers/gpu/drm/i915/i915_sysfs.c | 88 +- drivers/gpu/drm/i915/i915_trace.h | 40 +- drivers/gpu/drm/i915/i915_vgpu.c | 1 + drivers/gpu/drm/i915/i915_vma.c | 590 ++++++--- drivers/gpu/drm/i915/i915_vma.h | 132 +- drivers/gpu/drm/i915/intel_csr.c | 4 +- drivers/gpu/drm/i915/intel_device_info.c | 217 ++-- drivers/gpu/drm/i915/intel_device_info.h | 3 +- drivers/gpu/drm/i915/intel_pch.c | 1 + drivers/gpu/drm/i915/intel_pch.h | 1 + drivers/gpu/drm/i915/intel_pm.c | 906 ++------------ drivers/gpu/drm/i915/intel_pm.h | 3 - drivers/gpu/drm/i915/intel_runtime_pm.c | 1 - drivers/gpu/drm/i915/intel_uncore.c | 94 +- drivers/gpu/drm/i915/intel_uncore.h | 20 +- drivers/gpu/drm/i915/selftests/i915_active.c | 42 +- drivers/gpu/drm/i915/selftests/i915_buddy.c | 4 + drivers/gpu/drm/i915/selftests/i915_gem.c | 12 +- drivers/gpu/drm/i915/selftests/i915_gem_evict.c | 55 +- drivers/gpu/drm/i915/selftests/i915_gem_gtt.c | 395 +++++- .../gpu/drm/i915/selftests/i915_live_selftests.h | 2 + drivers/gpu/drm/i915/selftests/i915_random.c | 20 + drivers/gpu/drm/i915/selftests/i915_random.h | 4 + drivers/gpu/drm/i915/selftests/i915_request.c | 251 ++-- drivers/gpu/drm/i915/selftests/i915_selftest.c | 8 +- drivers/gpu/drm/i915/selftests/i915_vma.c | 19 +- drivers/gpu/drm/i915/selftests/igt_flush_test.c | 33 +- drivers/gpu/drm/i915/selftests/igt_flush_test.h | 2 +- drivers/gpu/drm/i915/selftests/igt_live_test.c | 14 +- drivers/gpu/drm/i915/selftests/igt_spinner.c | 2 +- drivers/gpu/drm/i915/selftests/intel_uncore.c | 2 + drivers/gpu/drm/i915/selftests/mock_gem_device.c | 36 +- drivers/gpu/drm/i915/selftests/mock_gtt.c | 6 +- drivers/misc/mei/hdcp/mei_hdcp.c | 45 +- drivers/misc/mei/hdcp/mei_hdcp.h | 17 +- include/drm/i915_drm.h | 18 - include/drm/i915_mei_hdcp_interface.h | 42 +- include/uapi/drm/i915_drm.h | 6 +- 198 files changed, 12046 insertions(+), 8192 deletions(-) create mode 100644 drivers/gpu/drm/i915/display/intel_dsb.c create mode 100644 drivers/gpu/drm/i915/display/intel_dsb.h create mode 100644 drivers/gpu/drm/i915/display/intel_vga.c create mode 100644 drivers/gpu/drm/i915/display/intel_vga.h create mode 100644 drivers/gpu/drm/i915/gt/intel_gt_requests.c create mode 100644 drivers/gpu/drm/i915/gt/intel_gt_requests.h create mode 100644 drivers/gpu/drm/i915/gt/intel_rc6.c create mode 100644 drivers/gpu/drm/i915/gt/intel_rc6.h create mode 100644 drivers/gpu/drm/i915/gt/intel_rc6_types.h create mode 100644 drivers/gpu/drm/i915/gt/selftest_gt_pm.c create mode 100644 drivers/gpu/drm/i915/i915_switcheroo.c create mode 100644 drivers/gpu/drm/i915/i915_switcheroo.h [View Less]

1 0

[PATCH v2 RESEND] drm/bridge: dw-hdmi: Restore audio when setting a mode
by Cheng-Yi Chiang 07 Oct '19

07 Oct '19

From: Daniel Kurtz <djkurtz(a)chromium.org> When setting a new display mode, dw_hdmi_setup() calls dw_hdmi_enable_video_path(), which disables all hdmi clocks, including the audio clock. We should only (re-)enable the audio clock if audio was already enabled when setting the new mode. Without this patch, on RK3288, there will be HDMI audio on some monitors if i2s was played to headphone when the monitor was plugged. ACER H277HU and ASUS PB278 are two of the monitors showing this issue. … [View More]

3 2

Re: drm_sched with panfrost crash on T820
by Koenig, Christian 07 Oct '19

07 Oct '19

Am 04.10.2019 18:02 schrieb Steven Price <steven.price(a)arm.com>: On 04/10/2019 16:34, Koenig, Christian wrote: > Am 04.10.19 um 17:27 schrieb Steven Price: >> On 04/10/2019 16:03, Neil Armstrong wrote: >>> On 04/10/2019 16:53, Grodzovsky, Andrey wrote: >>>> On 10/3/19 4:34 AM, Neil Armstrong wrote: >>>>> Hi Andrey, >>>>> >>>>> Le 02/10/2019 à 16:40, Grodzovsky, Andrey a écrit : >>>>>> On 9/30/19 … [View More]10:52 AM, Hillf Danton wrote: >>>>>>> On Mon, 30 Sep 2019 11:17:45 +0200 Neil Armstrong wrote: >>>>>>>> Did a new run from 5.3: >>>>>>>> >>>>>>>> [ 35.971972] Call trace: >>>>>>>> [ 35.974391] drm_sched_increase_karma+0x5c/0xf0 >>>>>>>> ffff000010667f38 FFFF000010667F94 >>>>>>>> drivers/gpu/drm/scheduler/sched_main.c:335 >>>>>>>> >>>>>>>> The crashing line is : >>>>>>>> if (bad->s_fence->scheduled.context == >>>>>>>> entity->fence_context) { >>>>>>>> >>>>>>>> Doesn't seem related to guilty job. >>>>>>> Bail out if s_fence is no longer fresh. >>>>>>> >>>>>>> --- a/drivers/gpu/drm/scheduler/sched_main.c >>>>>>> +++ b/drivers/gpu/drm/scheduler/sched_main.c >>>>>>> @@ -333,6 +333,10 @@ void drm_sched_increase_karma(struct drm >>>>>>> >>>>>>> spin_lock(&rq->lock); >>>>>>> list_for_each_entry_safe(entity, tmp, &rq->entities, list) { >>>>>>> + if (!smp_load_acquire(&bad->s_fence)) { >>>>>>> + spin_unlock(&rq->lock); >>>>>>> + return; >>>>>>> + } >>>>>>> if (bad->s_fence->scheduled.context == >>>>>>> entity->fence_context) { >>>>>>> if (atomic_read(&bad->karma) > >>>>>>> @@ -543,7 +547,7 @@ EXPORT_SYMBOL(drm_sched_job_init); >>>>>>> void drm_sched_job_cleanup(struct drm_sched_job *job) >>>>>>> { >>>>>>> dma_fence_put(&job->s_fence->finished); >>>>>>> - job->s_fence = NULL; >>>>>>> + smp_store_release(&job->s_fence, 0); >>>>>>> } >>>>>>> EXPORT_SYMBOL(drm_sched_job_cleanup); >>>>> This fixed the problem on the 10 CI runs. >>>>> >>>>> Neil >>>> >>>> These are good news but I still fail to see how this fixes the problem - >>>> Hillf, do you mind explaining how you came up with this particular fix - >>>> what was the bug you saw ? >>> As Steven explained, seems the same job was submitted on both HW slots, >>> and then when timeout occurs each thread calls panfrost_job_timedout >>> which leads to drm_sched_stop() on the first call and on the >>> second call the job was already freed. >>> >>> Steven proposed a working fix, and this one does the same but on >>> the drm_sched side. This one looks cleaner, but panfrost should >>> not call drm_sched_stop() twice for the same job. >> I'm not sure that Hillf's fix is sufficient. In particular in >> drm_sched_increase_karma() I don't understand how the smp_load_acquire() >> call prevents bad->s_fence becoming NULL immediately afterwards (but >> admittedly the window is much smaller). But really this is just a >> Panfrost bug (calling drm_sched_stop() twice on the same job). >> >> The part of my change that I'd welcome feedback on is changing >> cancel_delayed_work() to cancel_delayed_work_sync() in drm_sched_stop() >> when called on different scheduler to the bad job. It's not clear to me >> exactly what the semantics of the function should be, and I haven't >> tested the effect of the change on drivers other than Panfrost. > > Yeah, at least of hand that change doesn't seem to make sense to me. We need to ensure that any other timeouts that might have started processing are complete before actually resetting the hardware. Otherwise after the reset another thread could come along and attempt to reset the hardware again (and cause a double free of a job). This is intentional behaviour. If you don't want the double reset in Panfrost you should probably call the cancel_sync yourself. Regards, Christian. My change to use the _sync() variant prevents this happening. > Multiple timeout workers can perfectly run in parallel, Panfrost needs > to make sure that they don't affect each other. > > The simplest way of doing this is to have a mutex you trylock when > starting the reset. > > The first one grabbing it wins, all other just silently return. Ah that would simplify my change removing the need for the new variable. I hadn't thought to use trylock. I'll give that a spin and post a new simpler version. Thanks, Steve > Regards, > Christian. > >> >> Steve >> >>> Neil >>> >>>> Andrey >>>> >>>>>> Does this change help the problem ? Note that drm_sched_job_cleanup is >>>>>> called from scheduler thread which is stopped at all times when work_tdr >>>>>> thread is running and anyway the 'bad' job is still in the >>>>>> ring_mirror_list while it's being accessed from >>>>>> drm_sched_increase_karma so I don't think drm_sched_job_cleanup can be >>>>>> called for it BEFORE or while drm_sched_increase_karma is executed. >>>>>> >>>>>> Andrey >>>>>> >>>>>> >>>>>>> >>>>>>> -- >>>>>>> >>> _______________________________________________ >>> dri-devel mailing list >>> dri-devel(a)lists.freedesktop.org >>> https://lists.freedesktop.org/mailman/listinfo/dri-devel >>> > > _______________________________________________ > dri-devel mailing list > dri-devel(a)lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/dri-devel > [View Less]

2 1

[PATCH v2] drm/bridge: dw-hdmi: Refuse DDC/CI transfers on the internal I2C controller
by Matthias Kaehlcke 07 Oct '19

07 Oct '19

The DDC/CI protocol involves sending a multi-byte request to the display via I2C, which is typically followed by a multi-byte response. The internal I2C controller only allows single byte reads/writes or reads of 8 sequential bytes, hence DDC/CI is not supported when the internal I2C controller is used. The I2C transfers complete without errors, however the data in the response is garbage. Abort transfers to/from slave address 0x37 (DDC) with -EOPNOTSUPP, to make it evident that the … [View More]

2 1

[PATCH 1/3] drm/atomic-helper: Extract drm_atomic_helper_calc_timestamping_constants()
by Ville Syrjala 07 Oct '19

07 Oct '19

From: Ville Syrjälä <ville.syrjala(a)linux.intel.com> Put the vblank timestamping constants update loop into its own function. It has no business living inside drm_atomic_helper_update_legacy_modeset_state() so we'll be wanting to move it out entirely. As a first step we'll still call it from drm_atomic_helper_update_legacy_modeset_state(). Signed-off-by: Ville Syrjälä <ville.syrjala(a)linux.intel.com> --- drivers/gpu/drm/drm_atomic_helper.c | 26 ++++++++++++++++++++++---- … [View More]include/drm/drm_atomic_helper.h | 3 +++ 2 files changed, 25 insertions(+), 4 deletions(-) diff --git a/drivers/gpu/drm/drm_atomic_helper.c b/drivers/gpu/drm/drm_atomic_helper.c index 587052751b48..3773d74877e7 100644 --- a/drivers/gpu/drm/drm_atomic_helper.c +++ b/drivers/gpu/drm/drm_atomic_helper.c @@ -1080,9 +1080,7 @@ disable_outputs(struct drm_device *dev, struct drm_atomic_state *old_state) * @old_state: atomic state object with old state structures * * This function updates all the various legacy modeset state pointers in - * connectors, encoders and crtcs. It also updates the timestamping constants - * used for precise vblank timestamps by calling - * drm_calc_timestamping_constants(). + * connectors, encoders and crtcs. * * Drivers can use this for building their own atomic commit if they don't have * a pure helper-based modeset implementation. @@ -1151,13 +1149,33 @@ drm_atomic_helper_update_legacy_modeset_state(struct drm_device *dev, crtc->x = new_plane_state->src_x >> 16; crtc->y = new_plane_state->src_y >> 16; } + } + + drm_atomic_helper_calc_timestamping_constants(old_state); +} +EXPORT_SYMBOL(drm_atomic_helper_update_legacy_modeset_state); +/** + * drm_atomic_helper_calc_timestamping_constants - update vblank timestamping constants + * @state: atomic state object + * + * Updates the timestamping constants used for precise vblank timestamps + * by calling drm_calc_timestamping_constants() for all enabled crtcs in @state. + */ +void drm_atomic_helper_calc_timestamping_constants(struct drm_atomic_state *state) +{ + struct drm_crtc_state *new_crtc_state; + struct drm_crtc *crtc; + int i; + + /* set legacy state in the crtc structure */ + for_each_new_crtc_in_state(state, crtc, new_crtc_state, i) { if (new_crtc_state->enable) drm_calc_timestamping_constants(crtc, &new_crtc_state->adjusted_mode); } } -EXPORT_SYMBOL(drm_atomic_helper_update_legacy_modeset_state); +EXPORT_SYMBOL(drm_atomic_helper_calc_timestamping_constants); static void crtc_set_mode(struct drm_device *dev, struct drm_atomic_state *old_state) diff --git a/include/drm/drm_atomic_helper.h b/include/drm/drm_atomic_helper.h index bf4e07141d81..a60ea2cf36f0 100644 --- a/include/drm/drm_atomic_helper.h +++ b/include/drm/drm_atomic_helper.h @@ -74,6 +74,9 @@ void drm_atomic_helper_update_legacy_modeset_state(struct drm_device *dev, struct drm_atomic_state *old_state); +void +drm_atomic_helper_calc_timestamping_constants(struct drm_atomic_state *state); + void drm_atomic_helper_commit_modeset_disables(struct drm_device *dev, struct drm_atomic_state *state); void drm_atomic_helper_commit_modeset_enables(struct drm_device *dev, -- 2.21.0 [View Less]

1 2

[PATCH v11 0/7] drm/sun4i: dsi: Fixes/updates (A33 reworked!)
by Jagan Teki 07 Oct '19

07 Oct '19

This is v11 version changes for previous series[1]. This series dropped the tcon->dclk_min_div and tcon->dclk_max_div patches, since the discussion on the respective threads[2][3] not finalized or not agree on both the ends. This series mostly the commit messages changes suggested by Chen-Yu. Most of these issues are reproduced while supporting Allwinner A64 MIPI-DSI [4] but to confirm it with other SoC this series is reworked on A33 since the controller tested it A33 as of now. … [View More]Since we don't have proper evidence and documentation for dsi controller in Allwinner, these changes are more likely to rely on new working BSP codes (even the initial driver written as per this rule). All these fixes/updates are tested in "bananapi,s070wv20-ct16" panel on Allwinner A33, the same panel timings are available in panel-simple in mainline tree. Changes for v11: - Drop DCLK dividers patches - Updated the commit message changes suggested by Chen-Yu - rebased on linux-next Changes for v10: - reworked previous "Fixes/updates" patches on A33 - reworked previous A64 DSI fixes on A33 - added proper detailed commit messages with logs - tested on BPI-M2M board. Changes for v9: - rebase on drm-misc - update commit messages - add hsync_porch overflow patch Changes for v8: - rebase on master - rework on commit messages - rework video start delay - include drq changes from previous version Changes for v7: - rebase on master - collect Merlijn Wajer Tested-by credits. Changes for v6: - fixed all burst mode patches as per previous version comments - rebase on master - update proper commit message - dropped unneeded comments - order the patches that make review easy Changes for v5, v4, v3, v2: - use existing driver code construct for hblk computation - create separate function for vblk computation - cleanup commit messages - update proper commit messages - fixed checkpatch warnings/errors - use proper return value for tcon0 probe - add logic to get tcon0 divider values - simplify timings code to support burst mode - fix drq computation return values - rebase on master Any inputs? Jagan. [1] https://patchwork.freedesktop.org/series/60847/ [2] https://patchwork.freedesktop.org/patch/305923/?series=60847&rev=1 [3] https://patchwork.kernel.org/patch/10779937/ [4] https://patchwork.freedesktop.org/series/57834/ Jagan Teki (7): drm/sun4i: dsi: Fix TCON DRQ set bits drm/sun4i: dsi: Update start value in video start delay drm/sun4i: dsi: Fix video start delay computation dt-bindings: sun6i-dsi: Add VCC-DSI supply property drm/sun4i: sun6i_mipi_dsi: Add VCC-DSI regulator support [DO NOT MERGE] drm/panel: Add Bananapi S070WV20-CT16 ICN6211 MIPI-DSI to RGB bridge [DO NOT MERGE] ARM: dts: sun8i: bananapi-m2m: Enable Bananapi S070WV20-CT16 DSI panel .../display/allwinner,sun6i-a31-mipi-dsi.yaml | 3 + arch/arm/boot/dts/sun8i-r16-bananapi-m2m.dts | 40 +++ drivers/gpu/drm/panel/Kconfig | 9 + drivers/gpu/drm/panel/Makefile | 1 + .../panel/panel-bananapi-s070wv20-icn6211.c | 293 ++++++++++++++++++ drivers/gpu/drm/sun4i/sun6i_mipi_dsi.c | 32 +- drivers/gpu/drm/sun4i/sun6i_mipi_dsi.h | 2 + 7 files changed, 376 insertions(+), 4 deletions(-) create mode 100644 drivers/gpu/drm/panel/panel-bananapi-s070wv20-icn6211.c -- 2.18.0.321.gffc6fa0e3 [View Less]

4 21

[PATCH] cec: add cec_adapter to cec_notifier_cec_adap_unregister()
by Hans Verkuil 07 Oct '19

07 Oct '19

It is possible for one HDMI connector to have multiple CEC adapters. The typical real-world scenario is that where one adapter is used when the device is in standby, and one that's better/smarter when the device is powered up. The cec-notifier changes were made with that in mind, but I missed that in order to support this you need to tell cec_notifier_cec_adap_unregister() which adapter you are unregistering from the notifier. Add this additional argument. It is currently unused, but once all … [View More]drivers use this, the CEC core will be adapted for these use-cases. Signed-off-by: Hans Verkuil <hverkuil-cisco(a)xs4all.nl> --- This patch should go in via the drm subsystem since all CEC adapters in the drm subsystem have been converted to use cec_notifier_cec_adap_unregister(). The media subsystem still has older drm drivers that weren't converted to use cec_notifier_cec_adap_unregister(). This will only be a problem if a new CEC adapter driver is added to the media subsystem for v5.5, but I am not aware of any plans for that. Should it happen, then that just means that the media subsystem needs to resolve a fairly trivial merge conflict. Ville, Mauro, can you review/ack? --- diff --git a/drivers/gpu/drm/bridge/synopsys/dw-hdmi-cec.c b/drivers/gpu/drm/bridge/synopsys/dw-hdmi-cec.c index ac1e001d0882..70ab4fbdc23e 100644 --- a/drivers/gpu/drm/bridge/synopsys/dw-hdmi-cec.c +++ b/drivers/gpu/drm/bridge/synopsys/dw-hdmi-cec.c @@ -285,7 +285,7 @@ static int dw_hdmi_cec_probe(struct platform_device *pdev) ret = cec_register_adapter(cec->adap, pdev->dev.parent); if (ret < 0) { - cec_notifier_cec_adap_unregister(cec->notify); + cec_notifier_cec_adap_unregister(cec->notify, cec->adap); return ret; } @@ -302,7 +302,7 @@ static int dw_hdmi_cec_remove(struct platform_device *pdev) { struct dw_hdmi_cec *cec = platform_get_drvdata(pdev); - cec_notifier_cec_adap_unregister(cec->notify); + cec_notifier_cec_adap_unregister(cec->notify, cec->adap); cec_unregister_adapter(cec->adap); return 0; diff --git a/drivers/gpu/drm/i2c/tda9950.c b/drivers/gpu/drm/i2c/tda9950.c index a5a75bdeb7a5..5b03fdd1eaa4 100644 --- a/drivers/gpu/drm/i2c/tda9950.c +++ b/drivers/gpu/drm/i2c/tda9950.c @@ -465,7 +465,7 @@ static int tda9950_probe(struct i2c_client *client, ret = cec_register_adapter(priv->adap, priv->hdmi); if (ret < 0) { - cec_notifier_cec_adap_unregister(priv->notify); + cec_notifier_cec_adap_unregister(priv->notify, priv->adap); return ret; } @@ -482,7 +482,7 @@ static int tda9950_remove(struct i2c_client *client) { struct tda9950_priv *priv = i2c_get_clientdata(client); - cec_notifier_cec_adap_unregister(priv->notify); + cec_notifier_cec_adap_unregister(priv->notify, priv->adap); cec_unregister_adapter(priv->adap); return 0; diff --git a/drivers/media/cec/cec-notifier.c b/drivers/media/cec/cec-notifier.c index 4d82a5522072..7cf42b133dbc 100644 --- a/drivers/media/cec/cec-notifier.c +++ b/drivers/media/cec/cec-notifier.c @@ -153,13 +153,14 @@ cec_notifier_cec_adap_register(struct device *hdmi_dev, const char *conn_name, } EXPORT_SYMBOL_GPL(cec_notifier_cec_adap_register); -void cec_notifier_cec_adap_unregister(struct cec_notifier *n) +void cec_notifier_cec_adap_unregister(struct cec_notifier *n, + struct cec_adapter *adap) { if (!n) return; mutex_lock(&n->lock); - n->cec_adap->notifier = NULL; + adap->notifier = NULL; n->cec_adap = NULL; n->callback = NULL; mutex_unlock(&n->lock); diff --git a/drivers/media/platform/cros-ec-cec/cros-ec-cec.c b/drivers/media/platform/cros-ec-cec/cros-ec-cec.c index 4a3b3810fd89..f048e8994785 100644 --- a/drivers/media/platform/cros-ec-cec/cros-ec-cec.c +++ b/drivers/media/platform/cros-ec-cec/cros-ec-cec.c @@ -314,7 +314,8 @@ static int cros_ec_cec_probe(struct platform_device *pdev) return 0; out_probe_notify: - cec_notifier_cec_adap_unregister(cros_ec_cec->notify); + cec_notifier_cec_adap_unregister(cros_ec_cec->notify, + cros_ec_cec->adap); out_probe_adapter: cec_delete_adapter(cros_ec_cec->adap); return ret; @@ -335,7 +336,8 @@ static int cros_ec_cec_remove(struct platform_device *pdev) return ret; } - cec_notifier_cec_adap_unregister(cros_ec_cec->notify); + cec_notifier_cec_adap_unregister(cros_ec_cec->notify, + cros_ec_cec->adap); cec_unregister_adapter(cros_ec_cec->adap); return 0; diff --git a/drivers/media/platform/meson/ao-cec-g12a.c b/drivers/media/platform/meson/ao-cec-g12a.c index 3b39e875292e..70f875b4a01e 100644 --- a/drivers/media/platform/meson/ao-cec-g12a.c +++ b/drivers/media/platform/meson/ao-cec-g12a.c @@ -736,7 +736,7 @@ static int meson_ao_cec_g12a_probe(struct platform_device *pdev) clk_disable_unprepare(ao_cec->core); out_probe_notify: - cec_notifier_cec_adap_unregister(ao_cec->notify); + cec_notifier_cec_adap_unregister(ao_cec->notify, ao_cec->adap); out_probe_adapter: cec_delete_adapter(ao_cec->adap); @@ -752,7 +752,7 @@ static int meson_ao_cec_g12a_remove(struct platform_device *pdev) clk_disable_unprepare(ao_cec->core); - cec_notifier_cec_adap_unregister(ao_cec->notify); + cec_notifier_cec_adap_unregister(ao_cec->notify, ao_cec->adap); cec_unregister_adapter(ao_cec->adap); diff --git a/drivers/media/platform/meson/ao-cec.c b/drivers/media/platform/meson/ao-cec.c index 64ed549bf012..92859a6d006f 100644 --- a/drivers/media/platform/meson/ao-cec.c +++ b/drivers/media/platform/meson/ao-cec.c @@ -688,7 +688,7 @@ static int meson_ao_cec_probe(struct platform_device *pdev) clk_disable_unprepare(ao_cec->core); out_probe_notify: - cec_notifier_cec_adap_unregister(ao_cec->notify); + cec_notifier_cec_adap_unregister(ao_cec->notify, ao_cec->adap); out_probe_adapter: cec_delete_adapter(ao_cec->adap); @@ -704,7 +704,7 @@ static int meson_ao_cec_remove(struct platform_device *pdev) clk_disable_unprepare(ao_cec->core); - cec_notifier_cec_adap_unregister(ao_cec->notify); + cec_notifier_cec_adap_unregister(ao_cec->notify, ao_cec->adap); cec_unregister_adapter(ao_cec->adap); return 0; diff --git a/drivers/media/platform/s5p-cec/s5p_cec.c b/drivers/media/platform/s5p-cec/s5p_cec.c index 6ddcc35b0bbd..2a3e7ffefe0a 100644 --- a/drivers/media/platform/s5p-cec/s5p_cec.c +++ b/drivers/media/platform/s5p-cec/s5p_cec.c @@ -239,7 +239,7 @@ static int s5p_cec_probe(struct platform_device *pdev) return 0; err_notifier: - cec_notifier_cec_adap_unregister(cec->notifier); + cec_notifier_cec_adap_unregister(cec->notifier, cec->adap); err_delete_adapter: cec_delete_adapter(cec->adap); @@ -250,7 +250,7 @@ static int s5p_cec_remove(struct platform_device *pdev) { struct s5p_cec_dev *cec = platform_get_drvdata(pdev); - cec_notifier_cec_adap_unregister(cec->notifier); + cec_notifier_cec_adap_unregister(cec->notifier, cec->adap); cec_unregister_adapter(cec->adap); pm_runtime_disable(&pdev->dev); return 0; diff --git a/drivers/media/platform/seco-cec/seco-cec.c b/drivers/media/platform/seco-cec/seco-cec.c index 9cd60fe1867c..54b0d51e9c55 100644 --- a/drivers/media/platform/seco-cec/seco-cec.c +++ b/drivers/media/platform/seco-cec/seco-cec.c @@ -671,7 +671,7 @@ static int secocec_probe(struct platform_device *pdev) return ret; err_notifier: - cec_notifier_cec_adap_unregister(secocec->notifier); + cec_notifier_cec_adap_unregister(secocec->notifier, secocec->cec_adap); err_delete_adapter: cec_delete_adapter(secocec->cec_adap); err: @@ -692,7 +692,7 @@ static int secocec_remove(struct platform_device *pdev) dev_dbg(&pdev->dev, "IR disabled"); } - cec_notifier_cec_adap_unregister(secocec->notifier); + cec_notifier_cec_adap_unregister(secocec->notifier, secocec->cec_adap); cec_unregister_adapter(secocec->cec_adap); release_region(BRA_SMB_BASE_ADDR, 7); diff --git a/drivers/media/platform/sti/cec/stih-cec.c b/drivers/media/platform/sti/cec/stih-cec.c index 8118c7365d3f..f0c73e64b586 100644 --- a/drivers/media/platform/sti/cec/stih-cec.c +++ b/drivers/media/platform/sti/cec/stih-cec.c @@ -359,7 +359,7 @@ static int stih_cec_probe(struct platform_device *pdev) return 0; err_notifier: - cec_notifier_cec_adap_unregister(cec->notifier); + cec_notifier_cec_adap_unregister(cec->notifier, cec->adap); err_delete_adapter: cec_delete_adapter(cec->adap); @@ -370,7 +370,7 @@ static int stih_cec_remove(struct platform_device *pdev) { struct stih_cec *cec = platform_get_drvdata(pdev); - cec_notifier_cec_adap_unregister(cec->notifier); + cec_notifier_cec_adap_unregister(cec->notifier, cec->adap); cec_unregister_adapter(cec->adap); return 0; diff --git a/drivers/media/platform/tegra-cec/tegra_cec.c b/drivers/media/platform/tegra-cec/tegra_cec.c index a632602131f2..a99caac59f44 100644 --- a/drivers/media/platform/tegra-cec/tegra_cec.c +++ b/drivers/media/platform/tegra-cec/tegra_cec.c @@ -409,7 +409,7 @@ static int tegra_cec_probe(struct platform_device *pdev) return 0; err_notifier: - cec_notifier_cec_adap_unregister(cec->notifier); + cec_notifier_cec_adap_unregister(cec->notifier, cec->adap); err_adapter: cec_delete_adapter(cec->adap); err_clk: @@ -423,7 +423,7 @@ static int tegra_cec_remove(struct platform_device *pdev) clk_disable_unprepare(cec->clk); - cec_notifier_cec_adap_unregister(cec->notifier); + cec_notifier_cec_adap_unregister(cec->notifier, cec->adap); cec_unregister_adapter(cec->adap); return 0; diff --git a/include/media/cec-notifier.h b/include/media/cec-notifier.h index f161f8a493ac..985afea1ee36 100644 --- a/include/media/cec-notifier.h +++ b/include/media/cec-notifier.h @@ -93,8 +93,10 @@ cec_notifier_cec_adap_register(struct device *hdmi_dev, const char *conn_name, * cec_notifier_cec_adap_unregister - decrease refcount and delete when the * refcount reaches 0. * @n: notifier. If NULL, then this function does nothing. + * @adap: the cec adapter that registered this notifier. */ -void cec_notifier_cec_adap_unregister(struct cec_notifier *n); +void cec_notifier_cec_adap_unregister(struct cec_notifier *n, + struct cec_adapter *adap); /** * cec_notifier_set_phys_addr - set a new physical address. @@ -160,7 +162,8 @@ cec_notifier_cec_adap_register(struct device *hdmi_dev, const char *conn_name, return (struct cec_notifier *)0xdeadfeed; } -static inline void cec_notifier_cec_adap_unregister(struct cec_notifier *n) +static inline void cec_notifier_cec_adap_unregister(struct cec_notifier *n, + struct cec_adapter *adap) { } [View Less]

3 2

RE: [PATCH] drm/i915: customize DPCD brightness control for specific panel
by Lee, Shawn C 07 Oct '19

07 Oct '19

On Mon, 07 Oct 2019, "Jani Nikula" <jani.nikula(a)intel.com> wrote: >On Mon, 07 Oct 2019, "Lee, Shawn C" <shawn.c.lee(a)intel.com> wrote: >> On Fri, 04 Oct 2019, Jani Nikula <jani.nikula(a)intel.com> wrote: >>>On Fri, 04 Oct 2019, Adam Jackson <ajax(a)redhat.com> wrote: >>>> On Sat, 2019-10-05 at 05:58 +0800, Lee Shawn C wrote: >>>>> This panel (manufacturer is SDC, product ID is 0x4141) used >>>>> manufacturer … [View More]defined DPCD register to control brightness that not >>>>> defined in eDP spec so far. This change follow panel vendor's >>>>> instruction to support brightness adjustment. >>>> >>>> I'm sure this works, but this smells a little funny to me. >>> >>>That was kindly put. ;) >>> >>>>> + /* Samsung eDP panel */ >>>>> + { "SDC", 0x4141, EDID_QUIRK_NON_STD_BRIGHTNESS_CONTROL }, >>>> >>>> It feels a bit like a layering violation to identify eDP behavior >>>> changes based on EDID. But I'm not sure there's any obvious way to >>>> identify this device by its DPCD. The Sink OUI (from the linked >>>> bugzilla) seems to be 0011F8, which doesn't match up to anything in my >>>> oui.txt... >>> >>>We have the DPCD quirk stuff in drm_dp_helper.c, but IIUC in this case >>>there's only the OUI, and the device id etc. are all zeros. Otherwise I >>>think that would be the natural thing to do, and all this could be >>>better hidden away in i915. >>> >> >> Below is what we dumped from this panel. Only sink OUI (ba-41-59) in it >> and nothing else. >> 00000400 ba 41 59 00 00 00 00 00 00 00 00 00 00 00 00 00 |.AY.............| >> 00000410 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................ >> >> That's why the patch to identify EDID's manufacturer and product ID >> to make sure this method applied on specific panel. >> >>>> >>>>> @@ -1953,6 +1956,7 @@ static u32 edid_get_quirks(const struct edid >>>>> *edid) >>>>> >>>>> return 0; >>>>> } >>>>> +EXPORT_SYMBOL(edid_get_quirks); >>>> >>>> If we're going to export this it should probably get a drm_ prefix. >> >> Yes! It will be better to have drm_ prefix for export funciton. >> >>>> >>>>> +#define DPCD_EDP_GETSET_CTRL_PARAMS 0x344 >>>>> +#define DPCD_EDP_CONTENT_LUMINANCE 0x346 >>>>> +#define DPCD_EDP_PANEL_LUMINANCE_OVERRIDE 0x34a >>>>> +#define DPCD_EDP_BRIGHTNESS_NITS 0x354 >>>>> +#define DPCD_EDP_BRIGHTNESS_OPTIMIZATION 0x358 >>>>> + >>>>> +#define EDP_CUSTOMIZE_MAX_BRIGHTNESS_LEVEL (512) >>>> >>>> This also seems a bit weird, the 0x300-0x3FF registers belong to the >>>> _source_ DP device. But then later... >>>> >>>>> + /* write source OUI */ >>>>> + write_val[0] = 0x00; >>>>> + write_val[1] = 0xaa; >>>>> + write_val[2] = 0x01; >>>> >>>> Oh hey, you're writing (an) Intel OUI to the Source OUI, so now it >>>> makes sense that you're writing to registers whose behavior the source >>>> defines. But this does raise the question: is this just a convention >>>> between Intel and this particular panel? Would we expect this to work >>>> with other similar panels? Is there any way to know to expect this >>>> convention from DPCD instead? >> >> TCON would reply on source OUI to configure its capability. And these >> DPCD registers were defined by vendor and Intel. This change should works >> with similar panels (with same TCON). Seems there is another issue so >> vendor decide to use non standard way to setup brightness. >> >>>For one thing, it's not standard. I honestly don't know, but I'd assume >>>you wouldn't find behaviour with Intel OUI in non-Intel designs... and a >>>quirk of some sort seems like the only way to make this work. >>> >>>I suppose we could start off with a DPCD quirk that only looks at the >>>sink OUI, and then, if needed, limit by DMI matching or by checking for >>>some DPCD registers (what, I am not sure, perhaps write the source OUI >>>and see how it behaves). >>> >>>That would avoid the mildly annoying change in the EDID quirk interface >>>and how it's being used. >>> >>>Thoughts? >>> >>> >>>BR, >>>Jani. >>> >> >> To be honest. Panel vendor did not provide enough sink info in DPCD. >> That's why hard to recognize it and we have to confirm EDID instead of DPCD. >> >> Do you mean just confirm sink OUI only from DPCD quirk? I'm afraid it >> may impact the other panels with the same TCON. Any suggestion? > >The problem with the EDID quirks is that exposing the quirks sticks out >like a sore thumb. Thus far all of it has been contained in drm_edid.c >and they affect how the EDID gets parsed, for all drivers. Obviously >this could be changed, but is it the right thing to do? > >What I suggested was, check the OUI only, and if it matches, do >more. Perhaps there's something in the 0x300 range of DPCD offsets that >you can read? Or perhaps you need to write the source OUI first, and >then do that. > >BR, >Jani. > These bytes are RO. Seems we can used it to identify this panel as well. I will use DPCD quirk and renew this patch again. > >> >>> >>>-- >>>Jani Nikula, Intel Open Source Graphics Center >>> [View Less]

1 1

[RESEND TRIVIAL 1/3] treewide: drivers: Fix Kconfig indentation
by Krzysztof Kozlowski 07 Oct '19

07 Oct '19

Adjust indentation from spaces to tab (+optional two spaces) as in coding style with command like: $ sed -e 's/^ /\t/' -i */Kconfig Signed-off-by: Krzysztof Kozlowski <krzk(a)kernel.org> --- drivers/acpi/Kconfig | 8 +- drivers/ata/Kconfig | 12 +-- drivers/auxdisplay/Kconfig | 14 +-- drivers/base/firmware_loader/Kconfig | 2 +- drivers/block/Kconfig | 28 +++--- drivers/… [View More]block/mtip32xx/Kconfig | 2 +- drivers/char/Kconfig | 6 +- drivers/char/agp/Kconfig | 2 +- drivers/char/hw_random/Kconfig | 10 +- drivers/char/ipmi/Kconfig | 20 ++-- drivers/clk/Kconfig | 2 +- drivers/clk/mediatek/Kconfig | 10 +- drivers/clk/versatile/Kconfig | 2 +- drivers/clocksource/Kconfig | 20 ++-- drivers/cpufreq/Kconfig.x86 | 6 +- drivers/cpuidle/Kconfig | 8 +- drivers/cpuidle/Kconfig.arm | 16 ++-- drivers/crypto/Kconfig | 4 +- drivers/crypto/caam/Kconfig | 14 +-- drivers/crypto/chelsio/Kconfig | 30 +++--- drivers/crypto/stm32/Kconfig | 6 +- drivers/crypto/ux500/Kconfig | 16 ++-- drivers/devfreq/Kconfig | 6 +- drivers/dma/Kconfig | 46 ++++----- drivers/edac/Kconfig | 2 +- drivers/firmware/Kconfig | 4 +- drivers/firmware/efi/Kconfig | 2 +- drivers/hid/Kconfig | 2 +- drivers/hwmon/Kconfig | 14 +-- drivers/i2c/busses/Kconfig | 16 ++-- drivers/i2c/muxes/Kconfig | 18 ++-- drivers/iio/gyro/Kconfig | 8 +- drivers/infiniband/hw/bnxt_re/Kconfig | 12 +-- drivers/input/keyboard/Kconfig | 8 +- drivers/input/mouse/Kconfig | 6 +- drivers/input/tablet/Kconfig | 20 ++-- drivers/input/touchscreen/Kconfig | 2 +- drivers/iommu/Kconfig | 2 +- drivers/irqchip/Kconfig | 10 +- drivers/isdn/hardware/mISDN/Kconfig | 2 +- drivers/macintosh/Kconfig | 6 +- drivers/md/Kconfig | 54 +++++------ drivers/media/Kconfig | 6 +- drivers/media/radio/si470x/Kconfig | 4 +- drivers/memstick/core/Kconfig | 18 ++-- drivers/memstick/host/Kconfig | 4 +- drivers/misc/Kconfig | 16 ++-- drivers/mtd/nand/onenand/Kconfig | 12 +-- drivers/nfc/nfcmrvl/Kconfig | 2 +- drivers/pci/Kconfig | 24 ++--- drivers/pci/controller/dwc/Kconfig | 6 +- drivers/pci/hotplug/Kconfig | 2 +- drivers/perf/Kconfig | 14 +-- drivers/phy/hisilicon/Kconfig | 6 +- drivers/pinctrl/Kconfig | 18 ++-- drivers/pinctrl/freescale/Kconfig | 12 +-- drivers/pinctrl/qcom/Kconfig | 34 +++---- drivers/platform/chrome/Kconfig | 6 +- drivers/platform/mellanox/Kconfig | 4 +- drivers/platform/x86/Kconfig | 48 +++++----- drivers/power/avs/Kconfig | 12 +-- drivers/power/supply/Kconfig | 30 +++--- drivers/regulator/Kconfig | 8 +- drivers/rpmsg/Kconfig | 2 +- drivers/rtc/Kconfig | 6 +- drivers/scsi/Kconfig | 22 ++--- drivers/scsi/aic7xxx/Kconfig.aic7xxx | 14 +-- drivers/scsi/pcmcia/Kconfig | 2 +- drivers/scsi/qedf/Kconfig | 4 +- drivers/scsi/smartpqi/Kconfig | 8 +- drivers/soc/fsl/Kconfig | 8 +- drivers/soc/qcom/Kconfig | 22 ++--- drivers/soc/rockchip/Kconfig | 18 ++-- drivers/spi/Kconfig | 18 ++-- drivers/staging/fbtft/Kconfig | 12 +-- drivers/staging/fwserial/Kconfig | 6 +- drivers/staging/most/Kconfig | 8 +- drivers/staging/nvec/Kconfig | 10 +- drivers/staging/pi433/Kconfig | 24 ++--- drivers/staging/uwb/Kconfig | 42 ++++---- .../vc04_services/bcm2835-audio/Kconfig | 12 +-- drivers/staging/wusbcore/Kconfig | 2 +- drivers/tty/Kconfig | 26 ++--- drivers/tty/hvc/Kconfig | 4 +- drivers/tty/serial/8250/Kconfig | 2 +- drivers/tty/serial/Kconfig | 96 +++++++++---------- drivers/video/backlight/Kconfig | 8 +- drivers/video/console/Kconfig | 76 +++++++-------- drivers/virt/Kconfig | 10 +- drivers/virtio/Kconfig | 10 +- drivers/w1/slaves/Kconfig | 4 +- drivers/xen/Kconfig | 22 ++--- 92 files changed, 631 insertions(+), 631 deletions(-) diff --git a/drivers/acpi/Kconfig b/drivers/acpi/Kconfig index ebe1e9e5fd81..1fbe7e3d57b3 100644 --- a/drivers/acpi/Kconfig +++ b/drivers/acpi/Kconfig @@ -104,9 +104,9 @@ config ACPI_PROCFS_POWER depends on X86 && PROC_FS help For backwards compatibility, this option allows - deprecated power /proc/acpi/ directories to exist, even when - they have been replaced by functions in /sys. - The deprecated directories (and their replacements) include: + deprecated power /proc/acpi/ directories to exist, even when + they have been replaced by functions in /sys. + The deprecated directories (and their replacements) include: /proc/acpi/battery/* (/sys/class/power_supply/*) and /proc/acpi/ac_adapter/* (sys/class/power_supply/*). This option has no effect on /proc/acpi/ directories @@ -454,7 +454,7 @@ config ACPI_CUSTOM_METHOD config ACPI_BGRT bool "Boottime Graphics Resource Table support" depends on EFI && (X86 || ARM64) - help + help This driver adds support for exposing the ACPI Boottime Graphics Resource Table, which allows the operating system to obtain data from the firmware boot splash. It will appear under diff --git a/drivers/ata/Kconfig b/drivers/ata/Kconfig index a6beb2c5a692..86e35c9a9ac6 100644 --- a/drivers/ata/Kconfig +++ b/drivers/ata/Kconfig @@ -695,7 +695,7 @@ config PATA_IMX depends on ARCH_MXC help This option enables support for the PATA host available on Freescale - iMX SoCs. + iMX SoCs. If unsure, say N. @@ -704,7 +704,7 @@ config PATA_IT8213 depends on PCI help This option enables support for the ITE 821 PATA - controllers via the new ATA layer. + controllers via the new ATA layer. If unsure, say N. @@ -732,9 +732,9 @@ config PATA_MACIO depends on PPC_PMAC help Most IDE capable PowerMacs have IDE busses driven by a variant - of this controller which is part of the Apple chipset used on - most PowerMac models. Some models have multiple busses using - different chipsets, though generally, MacIO is one of them. + of this controller which is part of the Apple chipset used on + most PowerMac models. Some models have multiple busses using + different chipsets, though generally, MacIO is one of them. config PATA_MARVELL tristate "Marvell PATA support via legacy mode" @@ -915,7 +915,7 @@ config PATA_PXA This option enables support for harddrive attached to PXA CPU's bus. NOTE: This driver utilizes PXA DMA controller, in case your hardware - is not capable of doing MWDMA, use pata_platform instead. + is not capable of doing MWDMA, use pata_platform instead. If unsure, say N. diff --git a/drivers/auxdisplay/Kconfig b/drivers/auxdisplay/Kconfig index b8313a04422d..a92be39825f6 100644 --- a/drivers/auxdisplay/Kconfig +++ b/drivers/auxdisplay/Kconfig @@ -329,7 +329,7 @@ config PANEL_LCD_PROTO config PANEL_LCD_PIN_E depends on PANEL_PROFILE="0" && PANEL_LCD="1" && PANEL_LCD_PROTO="0" - int "Parallel port pin number & polarity connected to the LCD E signal (-17...17) " + int "Parallel port pin number & polarity connected to the LCD E signal (-17...17) " range -17 17 default 14 ---help--- @@ -344,7 +344,7 @@ config PANEL_LCD_PIN_E config PANEL_LCD_PIN_RS depends on PANEL_PROFILE="0" && PANEL_LCD="1" && PANEL_LCD_PROTO="0" - int "Parallel port pin number & polarity connected to the LCD RS signal (-17...17) " + int "Parallel port pin number & polarity connected to the LCD RS signal (-17...17) " range -17 17 default 17 ---help--- @@ -359,7 +359,7 @@ config PANEL_LCD_PIN_RS config PANEL_LCD_PIN_RW depends on PANEL_PROFILE="0" && PANEL_LCD="1" && PANEL_LCD_PROTO="0" - int "Parallel port pin number & polarity connected to the LCD RW signal (-17...17) " + int "Parallel port pin number & polarity connected to the LCD RW signal (-17...17) " range -17 17 default 16 ---help--- @@ -374,7 +374,7 @@ config PANEL_LCD_PIN_RW config PANEL_LCD_PIN_SCL depends on PANEL_PROFILE="0" && PANEL_LCD="1" && PANEL_LCD_PROTO!="0" - int "Parallel port pin number & polarity connected to the LCD SCL signal (-17...17) " + int "Parallel port pin number & polarity connected to the LCD SCL signal (-17...17) " range -17 17 default 1 ---help--- @@ -389,7 +389,7 @@ config PANEL_LCD_PIN_SCL config PANEL_LCD_PIN_SDA depends on PANEL_PROFILE="0" && PANEL_LCD="1" && PANEL_LCD_PROTO!="0" - int "Parallel port pin number & polarity connected to the LCD SDA signal (-17...17) " + int "Parallel port pin number & polarity connected to the LCD SDA signal (-17...17) " range -17 17 default 2 ---help--- @@ -404,12 +404,12 @@ config PANEL_LCD_PIN_SDA config PANEL_LCD_PIN_BL depends on PANEL_PROFILE="0" && PANEL_LCD="1" - int "Parallel port pin number & polarity connected to the LCD backlight signal (-17...17) " + int "Parallel port pin number & polarity connected to the LCD backlight signal (-17...17) " range -17 17 default 0 ---help--- This describes the number of the parallel port pin to which the LCD 'BL' signal - has been connected. It can be : + has been connected. It can be : 0 : no connection (eg: connected to ground) 1..17 : directly connected to any of these pins on the DB25 plug diff --git a/drivers/base/firmware_loader/Kconfig b/drivers/base/firmware_loader/Kconfig index 3f9e274e2ed3..e4cd11135785 100644 --- a/drivers/base/firmware_loader/Kconfig +++ b/drivers/base/firmware_loader/Kconfig @@ -148,7 +148,7 @@ config FW_LOADER_USER_HELPER_FALLBACK to be used for all firmware requests which explicitly do not disable a a fallback mechanism. Firmware calls which do prohibit a fallback mechanism is request_firmware_direct(). This option is kept for - backward compatibility purposes given this precise mechanism can also + backward compatibility purposes given this precise mechanism can also be enabled by setting the proc sysctl value to true: /proc/sys/kernel/firmware_config/force_sysfs_fallback diff --git a/drivers/block/Kconfig b/drivers/block/Kconfig index 1bb8ec575352..fa0cd072f5a1 100644 --- a/drivers/block/Kconfig +++ b/drivers/block/Kconfig @@ -142,10 +142,10 @@ config BLK_DEV_UBD bool "Virtual block device" depends on UML ---help--- - The User-Mode Linux port includes a driver called UBD which will let - you access arbitrary files on the host computer as block devices. - Unless you know that you do not need such virtual block devices say - Y here. + The User-Mode Linux port includes a driver called UBD which will let + you access arbitrary files on the host computer as block devices. + Unless you know that you do not need such virtual block devices say + Y here. config BLK_DEV_UBD_SYNC bool "Always do synchronous disk IO for UBD" @@ -156,16 +156,16 @@ config BLK_DEV_UBD_SYNC Linux 'Virtual Machine' uses a journalling filesystem and the host computer crashes. - Synchronous operation (i.e. always writing data to the host's disk - immediately) is configurable on a per-UBD basis by using a special - kernel command line option. Alternatively, you can say Y here to - turn on synchronous operation by default for all block devices. + Synchronous operation (i.e. always writing data to the host's disk + immediately) is configurable on a per-UBD basis by using a special + kernel command line option. Alternatively, you can say Y here to + turn on synchronous operation by default for all block devices. - If you're running a journalling file system (like reiserfs, for - example) in your virtual machine, you will want to say Y here. If - you care for the safety of the data in your virtual machine, Y is a - wise choice too. In all other cases (for example, if you're just - playing around with User-Mode Linux) you can choose N. + If you're running a journalling file system (like reiserfs, for + example) in your virtual machine, you will want to say Y here. If + you care for the safety of the data in your virtual machine, Y is a + wise choice too. In all other cases (for example, if you're just + playing around with User-Mode Linux) you can choose N. config BLK_DEV_COW_COMMON bool @@ -430,7 +430,7 @@ config VIRTIO_BLK depends on VIRTIO ---help--- This is the virtual block driver for virtio. It can be used with - QEMU based VMMs (like KVM or Xen). Say Y or M. + QEMU based VMMs (like KVM or Xen). Say Y or M. config VIRTIO_BLK_SCSI bool "SCSI passthrough request for the Virtio block driver" diff --git a/drivers/block/mtip32xx/Kconfig b/drivers/block/mtip32xx/Kconfig index bf221358567e..a469dc72e67a 100644 --- a/drivers/block/mtip32xx/Kconfig +++ b/drivers/block/mtip32xx/Kconfig @@ -7,4 +7,4 @@ config BLK_DEV_PCIESSD_MTIP32XX tristate "Block Device Driver for Micron PCIe SSDs" depends on PCI help - This enables the block driver for Micron PCIe SSDs. + This enables the block driver for Micron PCIe SSDs. diff --git a/drivers/char/Kconfig b/drivers/char/Kconfig index df0fc997dc3e..26956c006987 100644 --- a/drivers/char/Kconfig +++ b/drivers/char/Kconfig @@ -439,8 +439,8 @@ config RAW_DRIVER Once bound, I/O against /dev/raw/rawN uses efficient zero-copy I/O. See the raw(8) manpage for more details. - Applications should preferably open the device (eg /dev/hda1) - with the O_DIRECT flag. + Applications should preferably open the device (eg /dev/hda1) + with the O_DIRECT flag. config MAX_RAW_DEVS int "Maximum number of RAW devices to support (1-65536)" @@ -559,4 +559,4 @@ config RANDOM_TRUST_BOOTLOADER device randomness. Say Y here to assume the entropy provided by the booloader is trustworthy so it will be added to the kernel's entropy pool. Otherwise, say N here so it will be regarded as device input that - only mixes the entropy pool. \ No newline at end of file + only mixes the entropy pool. diff --git a/drivers/char/agp/Kconfig b/drivers/char/agp/Kconfig index 812d6aa6e013..bc54235a7022 100644 --- a/drivers/char/agp/Kconfig +++ b/drivers/char/agp/Kconfig @@ -63,7 +63,7 @@ config AGP_AMD64 This option gives you AGP support for the GLX component of X using the on-CPU northbridge of the AMD Athlon64/Opteron CPUs. You still need an external AGP bridge like the AMD 8151, VIA - K8T400M, SiS755. It may also support other AGP bridges when loaded + K8T400M, SiS755. It may also support other AGP bridges when loaded with agp_try_unsupported=1. config AGP_INTEL diff --git a/drivers/char/hw_random/Kconfig b/drivers/char/hw_random/Kconfig index 59f25286befe..5011eb673ab4 100644 --- a/drivers/char/hw_random/Kconfig +++ b/drivers/char/hw_random/Kconfig @@ -377,13 +377,13 @@ config HW_RANDOM_CAVIUM depends on HW_RANDOM && PCI && (ARM64 || (COMPILE_TEST && 64BIT)) default HW_RANDOM ---help--- - This driver provides kernel-side support for the Random Number - Generator hardware found on Cavium SoCs. + This driver provides kernel-side support for the Random Number + Generator hardware found on Cavium SoCs. - To compile this driver as a module, choose M here: the - module will be called cavium_rng. + To compile this driver as a module, choose M here: the + module will be called cavium_rng. - If unsure, say Y. + If unsure, say Y. config HW_RANDOM_MTK tristate "Mediatek Random Number Generator support" diff --git a/drivers/char/ipmi/Kconfig b/drivers/char/ipmi/Kconfig index 4bad0614109b..cc4bea773ded 100644 --- a/drivers/char/ipmi/Kconfig +++ b/drivers/char/ipmi/Kconfig @@ -8,13 +8,13 @@ menuconfig IPMI_HANDLER depends on HAS_IOMEM select IPMI_DMI_DECODE if DMI help - This enables the central IPMI message handler, required for IPMI + This enables the central IPMI message handler, required for IPMI to work. - IPMI is a standard for managing sensors (temperature, - voltage, etc.) in a system. + IPMI is a standard for managing sensors (temperature, + voltage, etc.) in a system. - See <file:Documentation/IPMI.txt> for more details on the driver. + See <file:Documentation/IPMI.txt> for more details on the driver. If unsure, say N. @@ -56,14 +56,14 @@ config IPMI_PANIC_STRING config IPMI_DEVICE_INTERFACE tristate 'Device interface for IPMI' help - This provides an IOCTL interface to the IPMI message handler so + This provides an IOCTL interface to the IPMI message handler so userland processes may use IPMI. It supports poll() and select(). config IPMI_SI tristate 'IPMI System Interface handler' select IPMI_PLAT_DATA help - Provides a driver for System Interfaces (KCS, SMIC, BT). + Provides a driver for System Interfaces (KCS, SMIC, BT). Currently, only KCS and SMIC are supported. If you are using IPMI, you should probably say "y" here. @@ -71,7 +71,7 @@ config IPMI_SSIF tristate 'IPMI SMBus handler (SSIF)' select I2C help - Provides a driver for a SMBus interface to a BMC, meaning that you + Provides a driver for a SMBus interface to a BMC, meaning that you have a driver that must be accessed over an I2C bus instead of a standard interface. This module requires I2C support. @@ -79,17 +79,17 @@ config IPMI_POWERNV depends on PPC_POWERNV tristate 'POWERNV (OPAL firmware) IPMI interface' help - Provides a driver for OPAL firmware-based IPMI interfaces. + Provides a driver for OPAL firmware-based IPMI interfaces. config IPMI_WATCHDOG tristate 'IPMI Watchdog Timer' help - This enables the IPMI watchdog timer. + This enables the IPMI watchdog timer. config IPMI_POWEROFF tristate 'IPMI Poweroff' help - This enables a function to power off the system with IPMI if + This enables a function to power off the system with IPMI if the IPMI management controller is capable of this. endif # IPMI_HANDLER diff --git a/drivers/clk/Kconfig b/drivers/clk/Kconfig index c44247d0b83e..0bea0363142e 100644 --- a/drivers/clk/Kconfig +++ b/drivers/clk/Kconfig @@ -27,7 +27,7 @@ config COMMON_CLK_WM831X tristate "Clock driver for WM831x/2x PMICs" depends on MFD_WM831X ---help--- - Supports the clocking subsystem of the WM831x/2x series of + Supports the clocking subsystem of the WM831x/2x series of PMICs from Wolfson Microelectronics. source "drivers/clk/versatile/Kconfig" diff --git a/drivers/clk/mediatek/Kconfig b/drivers/clk/mediatek/Kconfig index 7efc3617bbd5..5ddd813521e7 100644 --- a/drivers/clk/mediatek/Kconfig +++ b/drivers/clk/mediatek/Kconfig @@ -179,31 +179,31 @@ config COMMON_CLK_MT6797 select COMMON_CLK_MEDIATEK default ARCH_MEDIATEK && ARM64 ---help--- - This driver supports MediaTek MT6797 basic clocks. + This driver supports MediaTek MT6797 basic clocks. config COMMON_CLK_MT6797_MMSYS bool "Clock driver for MediaTek MT6797 mmsys" depends on COMMON_CLK_MT6797 ---help--- - This driver supports MediaTek MT6797 mmsys clocks. + This driver supports MediaTek MT6797 mmsys clocks. config COMMON_CLK_MT6797_IMGSYS bool "Clock driver for MediaTek MT6797 imgsys" depends on COMMON_CLK_MT6797 ---help--- - This driver supports MediaTek MT6797 imgsys clocks. + This driver supports MediaTek MT6797 imgsys clocks. config COMMON_CLK_MT6797_VDECSYS bool "Clock driver for MediaTek MT6797 vdecsys" depends on COMMON_CLK_MT6797 ---help--- - This driver supports MediaTek MT6797 vdecsys clocks. + This driver supports MediaTek MT6797 vdecsys clocks. config COMMON_CLK_MT6797_VENCSYS bool "Clock driver for MediaTek MT6797 vencsys" depends on COMMON_CLK_MT6797 ---help--- - This driver supports MediaTek MT6797 vencsys clocks. + This driver supports MediaTek MT6797 vencsys clocks. config COMMON_CLK_MT7622 bool "Clock driver for MediaTek MT7622" diff --git a/drivers/clk/versatile/Kconfig b/drivers/clk/versatile/Kconfig index ac766855ba16..c2618f1477a2 100644 --- a/drivers/clk/versatile/Kconfig +++ b/drivers/clk/versatile/Kconfig @@ -9,7 +9,7 @@ config COMMON_CLK_VERSATILE COMPILE_TEST select REGMAP_MMIO ---help--- - Supports clocking on ARM Reference designs: + Supports clocking on ARM Reference designs: - Integrator/AP and Integrator/CP - RealView PB1176, EB, PB11MP and PBX - Versatile Express diff --git a/drivers/clocksource/Kconfig b/drivers/clocksource/Kconfig index f35a53ce8988..f2342cb58e08 100644 --- a/drivers/clocksource/Kconfig +++ b/drivers/clocksource/Kconfig @@ -470,7 +470,7 @@ config OXNAS_RPS_TIMER This enables support for the Oxford Semiconductor OXNAS RPS timers. config SYS_SUPPORTS_SH_CMT - bool + bool config MTK_TIMER bool "Mediatek timer driver" if COMPILE_TEST @@ -490,13 +490,13 @@ config SPRD_TIMER Enables support for the Spreadtrum timer driver. config SYS_SUPPORTS_SH_MTU2 - bool + bool config SYS_SUPPORTS_SH_TMU - bool + bool config SYS_SUPPORTS_EM_STI - bool + bool config CLKSRC_JCORE_PIT bool "J-Core PIT timer driver" if COMPILE_TEST @@ -590,21 +590,21 @@ config CLKSRC_PXA platforms. config H8300_TMR8 - bool "Clockevent timer for the H8300 platform" if COMPILE_TEST - depends on HAS_IOMEM + bool "Clockevent timer for the H8300 platform" if COMPILE_TEST + depends on HAS_IOMEM help This enables the 8 bits timer for the H8300 platform. config H8300_TMR16 - bool "Clockevent timer for the H83069 platform" if COMPILE_TEST - depends on HAS_IOMEM + bool "Clockevent timer for the H83069 platform" if COMPILE_TEST + depends on HAS_IOMEM help This enables the 16 bits timer for the H8300 platform with the H83069 cpu. config H8300_TPU - bool "Clocksource for the H8300 platform" if COMPILE_TEST - depends on HAS_IOMEM + bool "Clocksource for the H8300 platform" if COMPILE_TEST + depends on HAS_IOMEM help This enables the clocksource for the H8300 platform with the H8S2678 cpu. diff --git a/drivers/cpufreq/Kconfig.x86 b/drivers/cpufreq/Kconfig.x86 index dfa6457deaf6..6eec6ccb14cb 100644 --- a/drivers/cpufreq/Kconfig.x86 +++ b/drivers/cpufreq/Kconfig.x86 @@ -9,12 +9,12 @@ config X86_INTEL_PSTATE select ACPI_PROCESSOR if ACPI select ACPI_CPPC_LIB if X86_64 && ACPI && SCHED_MC_PRIO help - This driver provides a P state for Intel core processors. + This driver provides a P state for Intel core processors. The driver implements an internal governor and will become - the scaling driver and governor for Sandy bridge processors. + the scaling driver and governor for Sandy bridge processors. When this driver is enabled it will become the preferred - scaling driver for Sandy bridge processors. + scaling driver for Sandy bridge processors. If in doubt, say N. diff --git a/drivers/cpuidle/Kconfig b/drivers/cpuidle/Kconfig index 88727b7c0d59..1b8614d1c696 100644 --- a/drivers/cpuidle/Kconfig +++ b/drivers/cpuidle/Kconfig @@ -16,7 +16,7 @@ config CPU_IDLE if CPU_IDLE config CPU_IDLE_MULTIPLE_DRIVERS - bool + bool config CPU_IDLE_GOV_LADDER bool "Ladder governor (for periodic timer tick)" @@ -67,9 +67,9 @@ config HALTPOLL_CPUIDLE depends on X86 && KVM_GUEST default y help - This option enables halt poll cpuidle driver, which allows to poll - before halting in the guest (more efficient than polling in the - host via halt_poll_ns for some scenarios). + This option enables halt poll cpuidle driver, which allows to poll + before halting in the guest (more efficient than polling in the + host via halt_poll_ns for some scenarios). endif diff --git a/drivers/cpuidle/Kconfig.arm b/drivers/cpuidle/Kconfig.arm index d8530475493c..e91ab792d14d 100644 --- a/drivers/cpuidle/Kconfig.arm +++ b/drivers/cpuidle/Kconfig.arm @@ -3,15 +3,15 @@ # ARM CPU Idle drivers # config ARM_CPUIDLE - bool "Generic ARM/ARM64 CPU idle Driver" - select DT_IDLE_STATES + bool "Generic ARM/ARM64 CPU idle Driver" + select DT_IDLE_STATES select CPU_IDLE_MULTIPLE_DRIVERS - help - Select this to enable generic cpuidle driver for ARM. - It provides a generic idle driver whose idle states are configured - at run-time through DT nodes. The CPUidle suspend backend is - initialized by calling the CPU operations init idle hook - provided by architecture code. + help + Select this to enable generic cpuidle driver for ARM. + It provides a generic idle driver whose idle states are configured + at run-time through DT nodes. The CPUidle suspend backend is + initialized by calling the CPU operations init idle hook + provided by architecture code. config ARM_PSCI_CPUIDLE bool "PSCI CPU idle Driver" diff --git a/drivers/crypto/Kconfig b/drivers/crypto/Kconfig index 1fb622f2a87d..390f0d652cb1 100644 --- a/drivers/crypto/Kconfig +++ b/drivers/crypto/Kconfig @@ -353,7 +353,7 @@ config CRYPTO_DEV_OMAP depends on ARCH_OMAP2PLUS help OMAP processors have various crypto HW accelerators. Select this if - you want to use the OMAP modules for any of the crypto algorithms. + you want to use the OMAP modules for any of the crypto algorithms. if CRYPTO_DEV_OMAP @@ -635,7 +635,7 @@ config CRYPTO_DEV_QCOM_RNG Generator hardware found on Qualcomm SoCs. To compile this driver as a module, choose M here. The - module will be called qcom-rng. If unsure, say N. + module will be called qcom-rng. If unsure, say N. config CRYPTO_DEV_VMX bool "Support for VMX cryptographic acceleration instructions" diff --git a/drivers/crypto/caam/Kconfig b/drivers/crypto/caam/Kconfig index 137ed3df0c74..2a0fa8dcae3c 100644 --- a/drivers/crypto/caam/Kconfig +++ b/drivers/crypto/caam/Kconfig @@ -130,13 +130,13 @@ config CRYPTO_DEV_FSL_CAAM_AHASH_API scatterlist crypto API to the SEC4 via job ring. config CRYPTO_DEV_FSL_CAAM_PKC_API - bool "Register public key cryptography implementations with Crypto API" - default y - select CRYPTO_RSA - help - Selecting this will allow SEC Public key support for RSA. - Supported cryptographic primitives: encryption, decryption, - signature and verification. + bool "Register public key cryptography implementations with Crypto API" + default y + select CRYPTO_RSA + help + Selecting this will allow SEC Public key support for RSA. + Supported cryptographic primitives: encryption, decryption, + signature and verification. config CRYPTO_DEV_FSL_CAAM_RNG_API bool "Register caam device for hwrng API" diff --git a/drivers/crypto/chelsio/Kconfig b/drivers/crypto/chelsio/Kconfig index 250150560e68..2786b497437c 100644 --- a/drivers/crypto/chelsio/Kconfig +++ b/drivers/crypto/chelsio/Kconfig @@ -23,22 +23,22 @@ config CRYPTO_DEV_CHELSIO will be called chcr. config CHELSIO_IPSEC_INLINE - bool "Chelsio IPSec XFRM Tx crypto offload" - depends on CHELSIO_T4 + bool "Chelsio IPSec XFRM Tx crypto offload" + depends on CHELSIO_T4 depends on CRYPTO_DEV_CHELSIO - depends on XFRM_OFFLOAD - depends on INET_ESP_OFFLOAD || INET6_ESP_OFFLOAD - default n - ---help--- - Enable support for IPSec Tx Inline. + depends on XFRM_OFFLOAD + depends on INET_ESP_OFFLOAD || INET6_ESP_OFFLOAD + default n + ---help--- + Enable support for IPSec Tx Inline. config CRYPTO_DEV_CHELSIO_TLS - tristate "Chelsio Crypto Inline TLS Driver" - depends on CHELSIO_T4 - depends on TLS - select CRYPTO_DEV_CHELSIO - ---help--- - Support Chelsio Inline TLS with Chelsio crypto accelerator. + tristate "Chelsio Crypto Inline TLS Driver" + depends on CHELSIO_T4 + depends on TLS + select CRYPTO_DEV_CHELSIO + ---help--- + Support Chelsio Inline TLS with Chelsio crypto accelerator. - To compile this driver as a module, choose M here: the module - will be called chtls. + To compile this driver as a module, choose M here: the module + will be called chtls. diff --git a/drivers/crypto/stm32/Kconfig b/drivers/crypto/stm32/Kconfig index 1aba9372cd23..4ef3eb11361c 100644 --- a/drivers/crypto/stm32/Kconfig +++ b/drivers/crypto/stm32/Kconfig @@ -4,7 +4,7 @@ config CRYPTO_DEV_STM32_CRC depends on ARCH_STM32 select CRYPTO_HASH help - This enables support for the CRC32 hw accelerator which can be found + This enables support for the CRC32 hw accelerator which can be found on STMicroelectronics STM32 SOC. config CRYPTO_DEV_STM32_HASH @@ -17,7 +17,7 @@ config CRYPTO_DEV_STM32_HASH select CRYPTO_SHA256 select CRYPTO_ENGINE help - This enables support for the HASH hw accelerator which can be found + This enables support for the HASH hw accelerator which can be found on STMicroelectronics STM32 SOC. config CRYPTO_DEV_STM32_CRYP @@ -27,5 +27,5 @@ config CRYPTO_DEV_STM32_CRYP select CRYPTO_ENGINE select CRYPTO_LIB_DES help - This enables support for the CRYP (AES/DES/TDES) hw accelerator which + This enables support for the CRYP (AES/DES/TDES) hw accelerator which can be found on STMicroelectronics STM32 SOC. diff --git a/drivers/crypto/ux500/Kconfig b/drivers/crypto/ux500/Kconfig index b1c6f739f77b..5a48497989ad 100644 --- a/drivers/crypto/ux500/Kconfig +++ b/drivers/crypto/ux500/Kconfig @@ -11,18 +11,18 @@ config CRYPTO_DEV_UX500_CRYP select CRYPTO_BLKCIPHER select CRYPTO_LIB_DES help - This selects the crypto driver for the UX500_CRYP hardware. It supports - AES-ECB, CBC and CTR with keys sizes of 128, 192 and 256 bit sizes. + This selects the crypto driver for the UX500_CRYP hardware. It supports + AES-ECB, CBC and CTR with keys sizes of 128, 192 and 256 bit sizes. config CRYPTO_DEV_UX500_HASH - tristate "UX500 crypto driver for HASH block" - depends on CRYPTO_DEV_UX500 - select CRYPTO_HASH + tristate "UX500 crypto driver for HASH block" + depends on CRYPTO_DEV_UX500 + select CRYPTO_HASH select CRYPTO_SHA1 select CRYPTO_SHA256 - help - This selects the hash driver for the UX500_HASH hardware. - Depends on UX500/STM DMA if running in DMA mode. + help + This selects the hash driver for the UX500_HASH hardware. + Depends on UX500/STM DMA if running in DMA mode. config CRYPTO_DEV_UX500_DEBUG bool "Activate ux500 platform debug-mode for crypto and hash block" diff --git a/drivers/devfreq/Kconfig b/drivers/devfreq/Kconfig index defe1d438710..0ccfd68f5cc2 100644 --- a/drivers/devfreq/Kconfig +++ b/drivers/devfreq/Kconfig @@ -123,9 +123,9 @@ config ARM_RK3399_DMC_DEVFREQ select PM_DEVFREQ_EVENT select PM_OPP help - This adds the DEVFREQ driver for the RK3399 DMC(Dynamic Memory Controller). - It sets the frequency for the memory controller and reads the usage counts - from hardware. + This adds the DEVFREQ driver for the RK3399 DMC(Dynamic Memory Controller). + It sets the frequency for the memory controller and reads the usage counts + from hardware. source "drivers/devfreq/event/Kconfig" diff --git a/drivers/dma/Kconfig b/drivers/dma/Kconfig index 7af874b69ffb..e068677947d2 100644 --- a/drivers/dma/Kconfig +++ b/drivers/dma/Kconfig @@ -15,19 +15,19 @@ menuconfig DMADEVICES be empty in some cases. config DMADEVICES_DEBUG - bool "DMA Engine debugging" - depends on DMADEVICES != n - help - This is an option for use by developers; most people should - say N here. This enables DMA engine core and driver debugging. + bool "DMA Engine debugging" + depends on DMADEVICES != n + help + This is an option for use by developers; most people should + say N here. This enables DMA engine core and driver debugging. config DMADEVICES_VDEBUG - bool "DMA Engine verbose debugging" - depends on DMADEVICES_DEBUG != n - help - This is an option for use by developers; most people should - say N here. This enables deeper (more verbose) debugging of - the DMA engine core and drivers. + bool "DMA Engine verbose debugging" + depends on DMADEVICES_DEBUG != n + help + This is an option for use by developers; most people should + say N here. This enables deeper (more verbose) debugging of + the DMA engine core and drivers. if DMADEVICES @@ -222,21 +222,21 @@ config FSL_QDMA select DMA_ENGINE_RAID select ASYNC_TX_ENABLE_CHANNEL_SWITCH help - Support the NXP Layerscape qDMA engine with command queue and legacy mode. - Channel virtualization is supported through enqueuing of DMA jobs to, - or dequeuing DMA jobs from, different work queues. - This module can be found on NXP Layerscape SoCs. + Support the NXP Layerscape qDMA engine with command queue and legacy mode. + Channel virtualization is supported through enqueuing of DMA jobs to, + or dequeuing DMA jobs from, different work queues. + This module can be found on NXP Layerscape SoCs. The qdma driver only work on SoCs with a DPAA hardware block. config FSL_RAID - tristate "Freescale RAID engine Support" - depends on FSL_SOC && !ASYNC_TX_ENABLE_CHANNEL_SWITCH - select DMA_ENGINE - select DMA_ENGINE_RAID - ---help--- - Enable support for Freescale RAID Engine. RAID Engine is - available on some QorIQ SoCs (like P5020/P5040). It has - the capability to offload memcpy, xor and pq computation + tristate "Freescale RAID engine Support" + depends on FSL_SOC && !ASYNC_TX_ENABLE_CHANNEL_SWITCH + select DMA_ENGINE + select DMA_ENGINE_RAID + ---help--- + Enable support for Freescale RAID Engine. RAID Engine is + available on some QorIQ SoCs (like P5020/P5040). It has + the capability to offload memcpy, xor and pq computation for raid5/6. config IMG_MDC_DMA diff --git a/drivers/edac/Kconfig b/drivers/edac/Kconfig index 417dad635526..c49f6bc39716 100644 --- a/drivers/edac/Kconfig +++ b/drivers/edac/Kconfig @@ -492,7 +492,7 @@ config EDAC_TI depends on ARCH_KEYSTONE || SOC_DRA7XX help Support for error detection and correction on the - TI SoCs. + TI SoCs. config EDAC_QCOM tristate "QCOM EDAC Controller" diff --git a/drivers/firmware/Kconfig b/drivers/firmware/Kconfig index e40a77bfe821..312c27876b60 100644 --- a/drivers/firmware/Kconfig +++ b/drivers/firmware/Kconfig @@ -86,8 +86,8 @@ config EDD BIOS tries boot from. This information is then exported via sysfs. This option is experimental and is known to fail to boot on some - obscure configurations. Most disk controller BIOS vendors do - not yet implement this feature. + obscure configurations. Most disk controller BIOS vendors do + not yet implement this feature. config EDD_OFF bool "Sets default behavior for EDD detection to off" diff --git a/drivers/firmware/efi/Kconfig b/drivers/firmware/efi/Kconfig index 178ee8106828..b6a4afcec75a 100644 --- a/drivers/firmware/efi/Kconfig +++ b/drivers/firmware/efi/Kconfig @@ -80,7 +80,7 @@ config EFI_PARAMS_FROM_FDT help Select this config option from the architecture Kconfig if the EFI runtime support gets system table address, memory - map address, and other parameters from the device tree. + map address, and other parameters from the device tree. config EFI_RUNTIME_WRAPPERS bool diff --git a/drivers/hid/Kconfig b/drivers/hid/Kconfig index 1ecb5124421c..04c2c4a9ffd9 100644 --- a/drivers/hid/Kconfig +++ b/drivers/hid/Kconfig @@ -107,7 +107,7 @@ config HID_ACCUTOUCH The driver works around a problem in the reported device capabilities which causes userspace to detect the device as a mouse rather than - a touchscreen. + a touchscreen. Say Y here if you have a Accutouch 2216 touch controller. diff --git a/drivers/hwmon/Kconfig b/drivers/hwmon/Kconfig index 13a6b4afb4b3..af92974abbae 100644 --- a/drivers/hwmon/Kconfig +++ b/drivers/hwmon/Kconfig @@ -495,10 +495,10 @@ config SENSORS_F75375S will be called f75375s. config SENSORS_MC13783_ADC - tristate "Freescale MC13783/MC13892 ADC" - depends on MFD_MC13XXX - help - Support for the A/D converter on MC13783 and MC13892 PMIC. + tristate "Freescale MC13783/MC13892 ADC" + depends on MFD_MC13XXX + help + Support for the A/D converter on MC13783 and MC13892 PMIC. config SENSORS_FSCHMD tristate "Fujitsu Siemens Computers sensor chips" @@ -1287,10 +1287,10 @@ config SENSORS_NPCM7XX imply THERMAL help This driver provides support for Nuvoton NPCM750/730/715/705 PWM - and Fan controllers. + and Fan controllers. - This driver can also be built as a module. If so, the module - will be called npcm750-pwm-fan. + This driver can also be built as a module. If so, the module + will be called npcm750-pwm-fan. config SENSORS_NSA320 tristate "ZyXEL NSA320 and compatible fan speed and temperature sensors" diff --git a/drivers/i2c/busses/Kconfig b/drivers/i2c/busses/Kconfig index 146ce40d8e0a..9b2a478fc90a 100644 --- a/drivers/i2c/busses/Kconfig +++ b/drivers/i2c/busses/Kconfig @@ -292,7 +292,7 @@ config I2C_VIA select I2C_ALGOBIT help If you say yes to this option, support will be included for the VIA - 82C586B I2C interface + 82C586B I2C interface This driver can also be built as a module. If so, the module will be called i2c-via. @@ -677,11 +677,11 @@ config I2C_IMX_LPI2C tristate "IMX Low Power I2C interface" depends on ARCH_MXC || COMPILE_TEST help - Say Y here if you want to use the Low Power IIC bus controller - on the Freescale i.MX processors. + Say Y here if you want to use the Low Power IIC bus controller + on the Freescale i.MX processors. - This driver can also be built as a module. If so, the module - will be called i2c-imx-lpi2c. + This driver can also be built as a module. If so, the module + will be called i2c-imx-lpi2c. config I2C_IOP3XX tristate "Intel IOPx3xx and IXP4xx on-chip I2C interface" @@ -1283,9 +1283,9 @@ config I2C_VIPERBOARD help Say yes here to access the I2C part of the Nano River Technologies Viperboard as I2C master. - See viperboard API specification and Nano - River Tech's viperboard.h for detailed meaning - of the module parameters. + See viperboard API specification and Nano + River Tech's viperboard.h for detailed meaning + of the module parameters. comment "Other I2C/SMBus bus drivers" diff --git a/drivers/i2c/muxes/Kconfig b/drivers/i2c/muxes/Kconfig index c6040aa839ac..1708b1a82da2 100644 --- a/drivers/i2c/muxes/Kconfig +++ b/drivers/i2c/muxes/Kconfig @@ -109,14 +109,14 @@ config I2C_DEMUX_PINCTRL want to change the I2C master at run-time depending on features. config I2C_MUX_MLXCPLD - tristate "Mellanox CPLD based I2C multiplexer" - help - If you say yes to this option, support will be included for a - CPLD based I2C multiplexer. This driver provides access to - I2C busses connected through a MUX, which is controlled - by a CPLD register. - - This driver can also be built as a module. If so, the module - will be called i2c-mux-mlxcpld. + tristate "Mellanox CPLD based I2C multiplexer" + help + If you say yes to this option, support will be included for a + CPLD based I2C multiplexer. This driver provides access to + I2C busses connected through a MUX, which is controlled + by a CPLD register. + + This driver can also be built as a module. If so, the module + will be called i2c-mux-mlxcpld. endmenu diff --git a/drivers/iio/gyro/Kconfig b/drivers/iio/gyro/Kconfig index 95e6f96d4529..f91af3b8e4da 100644 --- a/drivers/iio/gyro/Kconfig +++ b/drivers/iio/gyro/Kconfig @@ -82,11 +82,11 @@ config FXAS21002C select FXAS21002C_SPI if (SPI) depends on (I2C || SPI_MASTER) help - Say yes here to build support for NXP FXAS21002C Tri-axis Gyro - Sensor driver connected via I2C or SPI. + Say yes here to build support for NXP FXAS21002C Tri-axis Gyro + Sensor driver connected via I2C or SPI. - This driver can also be built as a module. If so, the module - will be called fxas21002c_i2c or fxas21002c_spi. + This driver can also be built as a module. If so, the module + will be called fxas21002c_i2c or fxas21002c_spi. config FXAS21002C_I2C tristate diff --git a/drivers/infiniband/hw/bnxt_re/Kconfig b/drivers/infiniband/hw/bnxt_re/Kconfig index ab8779d23382..b83f1cc38c52 100644 --- a/drivers/infiniband/hw/bnxt_re/Kconfig +++ b/drivers/infiniband/hw/bnxt_re/Kconfig @@ -1,11 +1,11 @@ # SPDX-License-Identifier: GPL-2.0-only config INFINIBAND_BNXT_RE - tristate "Broadcom Netxtreme HCA support" - depends on 64BIT - depends on ETHERNET && NETDEVICES && PCI && INET && DCB - select NET_VENDOR_BROADCOM - select BNXT - ---help--- + tristate "Broadcom Netxtreme HCA support" + depends on 64BIT + depends on ETHERNET && NETDEVICES && PCI && INET && DCB + select NET_VENDOR_BROADCOM + select BNXT + ---help--- This driver supports Broadcom NetXtreme-E 10/25/40/50 gigabit RoCE HCAs. To compile this driver as a module, choose M here: the module will be called bnxt_re. diff --git a/drivers/input/keyboard/Kconfig b/drivers/input/keyboard/Kconfig index 8911bc2ec42a..f553adae8eb4 100644 --- a/drivers/input/keyboard/Kconfig +++ b/drivers/input/keyboard/Kconfig @@ -171,11 +171,11 @@ config KEYBOARD_QT1070 tristate "Atmel AT42QT1070 Touch Sensor Chip" depends on I2C help - Say Y here if you want to use Atmel AT42QT1070 QTouch - Sensor chip as input device. + Say Y here if you want to use Atmel AT42QT1070 QTouch + Sensor chip as input device. - To compile this driver as a module, choose M here: - the module will be called qt1070 + To compile this driver as a module, choose M here: + the module will be called qt1070 config KEYBOARD_QT2160 tristate "Atmel AT42QT2160 Touch Sensor Chip" diff --git a/drivers/input/mouse/Kconfig b/drivers/input/mouse/Kconfig index 652c38e3c0b5..e1ca0dd737c9 100644 --- a/drivers/input/mouse/Kconfig +++ b/drivers/input/mouse/Kconfig @@ -96,10 +96,10 @@ config MOUSE_PS2_CYPRESS default y depends on MOUSE_PS2 help - Say Y here if you have a Cypress PS/2 Trackpad connected to - your system. + Say Y here if you have a Cypress PS/2 Trackpad connected to + your system. - If unsure, say Y. + If unsure, say Y. config MOUSE_PS2_LIFEBOOK bool "Fujitsu Lifebook PS/2 mouse protocol extension" if EXPERT diff --git a/drivers/input/tablet/Kconfig b/drivers/input/tablet/Kconfig index e4c0d9a055b9..51c339182017 100644 --- a/drivers/input/tablet/Kconfig +++ b/drivers/input/tablet/Kconfig @@ -39,16 +39,16 @@ config TABLET_USB_AIPTEK module will be called aiptek. config TABLET_USB_GTCO - tristate "GTCO CalComp/InterWrite USB Support" - depends on USB && INPUT - help - Say Y here if you want to use the USB version of the GTCO - CalComp/InterWrite Tablet. Make sure to say Y to "Mouse support" - (CONFIG_INPUT_MOUSEDEV) and/or "Event interface support" - (CONFIG_INPUT_EVDEV) as well. - - To compile this driver as a module, choose M here: the - module will be called gtco. + tristate "GTCO CalComp/InterWrite USB Support" + depends on USB && INPUT + help + Say Y here if you want to use the USB version of the GTCO + CalComp/InterWrite Tablet. Make sure to say Y to "Mouse support" + (CONFIG_INPUT_MOUSEDEV) and/or "Event interface support" + (CONFIG_INPUT_EVDEV) as well. + + To compile this driver as a module, choose M here: the + module will be called gtco. config TABLET_USB_HANWANG tristate "Hanwang Art Master III tablet support (USB)" diff --git a/drivers/input/touchscreen/Kconfig b/drivers/input/touchscreen/Kconfig index 46ad9090493b..69d210e1175c 100644 --- a/drivers/input/touchscreen/Kconfig +++ b/drivers/input/touchscreen/Kconfig @@ -633,7 +633,7 @@ config TOUCHSCREEN_HP600 depends on SH_HP6XX && SH_ADC help Say Y here if you have a HP Jornada 620/660/680/690 and want to - support the built-in touchscreen. + support the built-in touchscreen. To compile this driver as a module, choose M here: the module will be called hp680_ts_input. diff --git a/drivers/iommu/Kconfig b/drivers/iommu/Kconfig index e3842eabcfdd..0388d10e6e3c 100644 --- a/drivers/iommu/Kconfig +++ b/drivers/iommu/Kconfig @@ -78,7 +78,7 @@ config IOMMU_DEBUGFS config IOMMU_DEFAULT_PASSTHROUGH bool "IOMMU passthrough by default" depends on IOMMU_API - help + help Enable passthrough by default, removing the need to pass in iommu.passthrough=on or iommu=pt through command line. If this is enabled, you can still disable with iommu.passthrough=off diff --git a/drivers/irqchip/Kconfig b/drivers/irqchip/Kconfig index ccbb8973a324..542ddc11fe87 100644 --- a/drivers/irqchip/Kconfig +++ b/drivers/irqchip/Kconfig @@ -328,7 +328,7 @@ config INGENIC_TCU_IRQ If unsure, say N. config RENESAS_H8300H_INTC - bool + bool select IRQ_DOMAIN config RENESAS_H8S_INTC @@ -368,7 +368,7 @@ config MVEBU_PIC bool config MVEBU_SEI - bool + bool config LS_SCFG_MSI def_bool y if SOC_LS1021A || ARCH_LAYERSCAPE @@ -410,15 +410,15 @@ config MESON_IRQ_GPIO depends on ARCH_MESON select IRQ_DOMAIN_HIERARCHY help - Support Meson SoC Family GPIO Interrupt Multiplexer + Support Meson SoC Family GPIO Interrupt Multiplexer config GOLDFISH_PIC bool "Goldfish programmable interrupt controller" depends on MIPS && (GOLDFISH || COMPILE_TEST) select IRQ_DOMAIN help - Say yes here to enable Goldfish interrupt controller driver used - for Goldfish based virtual platforms. + Say yes here to enable Goldfish interrupt controller driver used + for Goldfish based virtual platforms. config QCOM_PDC bool "QCOM PDC" diff --git a/drivers/isdn/hardware/mISDN/Kconfig b/drivers/isdn/hardware/mISDN/Kconfig index 304f50c08da2..078eeadf707a 100644 --- a/drivers/isdn/hardware/mISDN/Kconfig +++ b/drivers/isdn/hardware/mISDN/Kconfig @@ -10,7 +10,7 @@ config MISDN_HFCPCI depends on PCI help Enable support for cards with Cologne Chip AG's - HFC PCI chip. + HFC PCI chip. config MISDN_HFCMULTI tristate "Support for HFC multiport cards (HFC-4S/8S/E1)" diff --git a/drivers/macintosh/Kconfig b/drivers/macintosh/Kconfig index 574e122ae105..cbd46c1c5bf7 100644 --- a/drivers/macintosh/Kconfig +++ b/drivers/macintosh/Kconfig @@ -178,7 +178,7 @@ config THERM_ADT746X depends on I2C && I2C_POWERMAC && PPC_PMAC && !PPC_PMAC64 help This driver provides some thermostat and fan control for the - iBook G4, and the ATI based aluminium PowerBooks, allowing slightly + iBook G4, and the ATI based aluminium PowerBooks, allowing slightly better fan behaviour by default, and some manual control. config WINDFARM @@ -214,7 +214,7 @@ config WINDFARM_PM91 select I2C_POWERMAC help This driver provides thermal control for the PowerMac9,1 - which is the recent (SMU based) single CPU desktop G5 + which is the recent (SMU based) single CPU desktop G5 config WINDFARM_PM112 tristate "Support for thermal management on PowerMac11,2" @@ -242,7 +242,7 @@ config PMAC_RACKMETER depends on PPC_PMAC help This driver provides some support to control the front panel - blue LEDs "vu-meter" of the XServer macs. + blue LEDs "vu-meter" of the XServer macs. config SENSORS_AMS tristate "Apple Motion Sensor driver" diff --git a/drivers/md/Kconfig b/drivers/md/Kconfig index aa98953f4462..d6d5ab23c088 100644 --- a/drivers/md/Kconfig +++ b/drivers/md/Kconfig @@ -38,9 +38,9 @@ config MD_AUTODETECT default y ---help--- If you say Y here, then the kernel will try to autodetect raid - arrays as part of its boot process. + arrays as part of its boot process. - If you don't use raid and say Y, this autodetection can cause + If you don't use raid and say Y, this autodetection can cause a several-second delay in the boot time due to various synchronisation steps that are part of this step. @@ -290,7 +290,7 @@ config DM_SNAPSHOT depends on BLK_DEV_DM select DM_BUFIO ---help--- - Allow volume managers to take writable snapshots of a device. + Allow volume managers to take writable snapshots of a device. config DM_THIN_PROVISIONING tristate "Thin provisioning target" @@ -298,7 +298,7 @@ config DM_THIN_PROVISIONING select DM_PERSISTENT_DATA select DM_BIO_PRISON ---help--- - Provides thin provisioning and snapshots that share a data store. + Provides thin provisioning and snapshots that share a data store. config DM_CACHE tristate "Cache target (EXPERIMENTAL)" @@ -307,23 +307,23 @@ config DM_CACHE select DM_PERSISTENT_DATA select DM_BIO_PRISON ---help--- - dm-cache attempts to improve performance of a block device by - moving frequently used data to a smaller, higher performance - device. Different 'policy' plugins can be used to change the - algorithms used to select which blocks are promoted, demoted, - cleaned etc. It supports writeback and writethrough modes. + dm-cache attempts to improve performance of a block device by + moving frequently used data to a smaller, higher performance + device. Different 'policy' plugins can be used to change the + algorithms used to select which blocks are promoted, demoted, + cleaned etc. It supports writeback and writethrough modes. config DM_CACHE_SMQ tristate "Stochastic MQ Cache Policy (EXPERIMENTAL)" depends on DM_CACHE default y ---help--- - A cache policy that uses a multiqueue ordered by recent hits - to select which blocks should be promoted and demoted. - This is meant to be a general purpose policy. It prioritises - reads over writes. This SMQ policy (vs MQ) offers the promise - of less memory utilization, improved performance and increased - adaptability in the face of changing workloads. + A cache policy that uses a multiqueue ordered by recent hits + to select which blocks should be promoted and demoted. + This is meant to be a general purpose policy. It prioritises + reads over writes. This SMQ policy (vs MQ) offers the promise + of less memory utilization, improved performance and increased + adaptability in the face of changing workloads. config DM_WRITECACHE tristate "Writecache target" @@ -343,9 +343,9 @@ config DM_ERA select DM_PERSISTENT_DATA select DM_BIO_PRISON ---help--- - dm-era tracks which parts of a block device are written to - over time. Useful for maintaining cache coherency when using - vendor snapshots. + dm-era tracks which parts of a block device are written to + over time. Useful for maintaining cache coherency when using + vendor snapshots. config DM_CLONE tristate "Clone target (EXPERIMENTAL)" @@ -353,20 +353,20 @@ config DM_CLONE default n select DM_PERSISTENT_DATA ---help--- - dm-clone produces a one-to-one copy of an existing, read-only source - device into a writable destination device. The cloned device is - visible/mountable immediately and the copy of the source device to the - destination device happens in the background, in parallel with user - I/O. + dm-clone produces a one-to-one copy of an existing, read-only source + device into a writable destination device. The cloned device is + visible/mountable immediately and the copy of the source device to the + destination device happens in the background, in parallel with user + I/O. - If unsure, say N. + If unsure, say N. config DM_MIRROR tristate "Mirror target" depends on BLK_DEV_DM ---help--- - Allow volume managers to mirror logical volumes, also - needed for live data migration tools such as 'pvmove'. + Allow volume managers to mirror logical volumes, also + needed for live data migration tools such as 'pvmove'. config DM_LOG_USERSPACE tristate "Mirror userspace logging" @@ -483,7 +483,7 @@ config DM_FLAKEY tristate "Flakey target" depends on BLK_DEV_DM ---help--- - A target that intermittently fails I/O for debugging purposes. + A target that intermittently fails I/O for debugging purposes. config DM_VERITY tristate "Verity target support" diff --git a/drivers/media/Kconfig b/drivers/media/Kconfig index b36a41332867..9dfea5c4b6ab 100644 --- a/drivers/media/Kconfig +++ b/drivers/media/Kconfig @@ -208,9 +208,9 @@ config MEDIA_SUBDRV_AUTOSELECT If unsure say Y. config MEDIA_HIDE_ANCILLARY_SUBDRV - bool - depends on MEDIA_SUBDRV_AUTOSELECT && !COMPILE_TEST && !EXPERT - default y + bool + depends on MEDIA_SUBDRV_AUTOSELECT && !COMPILE_TEST && !EXPERT + default y config MEDIA_ATTACH bool diff --git a/drivers/media/radio/si470x/Kconfig b/drivers/media/radio/si470x/Kconfig index 537f8e1601f3..a1ba8bc54b62 100644 --- a/drivers/media/radio/si470x/Kconfig +++ b/drivers/media/radio/si470x/Kconfig @@ -1,7 +1,7 @@ # SPDX-License-Identifier: GPL-2.0-only config RADIO_SI470X - tristate "Silicon Labs Si470x FM Radio Receiver support" - depends on VIDEO_V4L2 + tristate "Silicon Labs Si470x FM Radio Receiver support" + depends on VIDEO_V4L2 help This is a driver for devices with the Silicon Labs SI470x chip (either via USB or I2C buses). diff --git a/drivers/memstick/core/Kconfig b/drivers/memstick/core/Kconfig index 516f454fde14..08192fd70eb4 100644 --- a/drivers/memstick/core/Kconfig +++ b/drivers/memstick/core/Kconfig @@ -6,16 +6,16 @@ comment "MemoryStick drivers" config MEMSTICK_UNSAFE_RESUME - bool "Allow unsafe resume (DANGEROUS)" - help - If you say Y here, the MemoryStick layer will assume that all - cards stayed in their respective slots during the suspend. The - normal behaviour is to remove them at suspend and - redetecting them at resume. Breaking this assumption will - in most cases result in data corruption. + bool "Allow unsafe resume (DANGEROUS)" + help + If you say Y here, the MemoryStick layer will assume that all + cards stayed in their respective slots during the suspend. The + normal behaviour is to remove them at suspend and + redetecting them at resume. Breaking this assumption will + in most cases result in data corruption. - This option is usually just for embedded systems which use - a MemoryStick card for rootfs. Most people should say N here. + This option is usually just for embedded systems which use + a MemoryStick card for rootfs. Most people should say N here. config MSPRO_BLOCK tristate "MemoryStick Pro block device driver" diff --git a/drivers/memstick/host/Kconfig b/drivers/memstick/host/Kconfig index 446c93ecef8f..4113343da056 100644 --- a/drivers/memstick/host/Kconfig +++ b/drivers/memstick/host/Kconfig @@ -18,7 +18,7 @@ config MEMSTICK_TIFM_MS 'Misc devices: TI Flash Media PCI74xx/PCI76xx host adapter support (TIFM_7XX1)'. - To compile this driver as a module, choose M here: the + To compile this driver as a module, choose M here: the module will be called tifm_ms. config MEMSTICK_JMICRON_38X @@ -29,7 +29,7 @@ config MEMSTICK_JMICRON_38X Say Y here if you want to be able to access MemoryStick cards with the JMicron(R) JMB38X MemoryStick card reader. - To compile this driver as a module, choose M here: the + To compile this driver as a module, choose M here: the module will be called jmb38x_ms. config MEMSTICK_R592 diff --git a/drivers/misc/Kconfig b/drivers/misc/Kconfig index 3ce00bf5cfe3..1772a6dfefb4 100644 --- a/drivers/misc/Kconfig +++ b/drivers/misc/Kconfig @@ -339,14 +339,14 @@ config SENSORS_TSL2550 will be called tsl2550. config SENSORS_BH1770 - tristate "BH1770GLC / SFH7770 combined ALS - Proximity sensor" - depends on I2C - ---help--- - Say Y here if you want to build a driver for BH1770GLC (ROHM) or + tristate "BH1770GLC / SFH7770 combined ALS - Proximity sensor" + depends on I2C + ---help--- + Say Y here if you want to build a driver for BH1770GLC (ROHM) or SFH7770 (Osram) combined ambient light and proximity sensor chip. - To compile this driver as a module, choose M here: the - module will be called bh1770glc. If unsure, say N here. + To compile this driver as a module, choose M here: the + module will be called bh1770glc. If unsure, say N here. config SENSORS_APDS990X tristate "APDS990X combined als and proximity sensors" @@ -451,8 +451,8 @@ config PCI_ENDPOINT_TEST select CRC32 tristate "PCI Endpoint Test driver" ---help--- - Enable this configuration option to enable the host side test driver - for PCI Endpoint. + Enable this configuration option to enable the host side test driver + for PCI Endpoint. config XILINX_SDFEC tristate "Xilinx SDFEC 16" diff --git a/drivers/mtd/nand/onenand/Kconfig b/drivers/mtd/nand/onenand/Kconfig index ae0b8fe5b990..ea382fc48432 100644 --- a/drivers/mtd/nand/onenand/Kconfig +++ b/drivers/mtd/nand/onenand/Kconfig @@ -33,12 +33,12 @@ config MTD_ONENAND_OMAP2 Enable dmaengine and gpiolib for better performance. config MTD_ONENAND_SAMSUNG - tristate "OneNAND on Samsung SOC controller support" - depends on ARCH_S3C64XX || ARCH_S5PV210 || ARCH_EXYNOS4 - help - Support for a OneNAND flash device connected to an Samsung SOC. - S3C64XX uses command mapping method. - S5PC110/S5PC210 use generic OneNAND method. + tristate "OneNAND on Samsung SOC controller support" + depends on ARCH_S3C64XX || ARCH_S5PV210 || ARCH_EXYNOS4 + help + Support for a OneNAND flash device connected to an Samsung SOC. + S3C64XX uses command mapping method. + S5PC110/S5PC210 use generic OneNAND method. config MTD_ONENAND_OTP bool "OneNAND OTP Support" diff --git a/drivers/nfc/nfcmrvl/Kconfig b/drivers/nfc/nfcmrvl/Kconfig index 06f34fb4e0b0..ded0d03c0015 100644 --- a/drivers/nfc/nfcmrvl/Kconfig +++ b/drivers/nfc/nfcmrvl/Kconfig @@ -15,7 +15,7 @@ config NFC_MRVL_USB Marvell NFC-over-USB driver. This driver provides support for Marvell NFC-over-USB devices: - 8897. + 8897. Say Y here to compile support for Marvell NFC-over-USB driver into the kernel or say M to compile it as module. diff --git a/drivers/pci/Kconfig b/drivers/pci/Kconfig index a304f5ea11b9..bd50765f30cd 100644 --- a/drivers/pci/Kconfig +++ b/drivers/pci/Kconfig @@ -106,14 +106,14 @@ config PCI_PF_STUB When in doubt, say N. config XEN_PCIDEV_FRONTEND - tristate "Xen PCI Frontend" - depends on X86 && XEN - select PCI_XEN + tristate "Xen PCI Frontend" + depends on X86 && XEN + select PCI_XEN select XEN_XENBUS_FRONTEND - default y - help - The PCI device frontend driver allows the kernel to import arbitrary - PCI devices from a PCI backend to support PCI driver domains. + default y + help + The PCI device frontend driver allows the kernel to import arbitrary + PCI devices from a PCI backend to support PCI driver domains. config PCI_ATS bool @@ -180,12 +180,12 @@ config PCI_LABEL select NLS config PCI_HYPERV - tristate "Hyper-V PCI Frontend" - depends on X86_64 && HYPERV && PCI_MSI && PCI_MSI_IRQ_DOMAIN && SYSFS + tristate "Hyper-V PCI Frontend" + depends on X86_64 && HYPERV && PCI_MSI && PCI_MSI_IRQ_DOMAIN && SYSFS select PCI_HYPERV_INTERFACE - help - The PCI device frontend driver allows the kernel to import arbitrary - PCI devices from a PCI backend to support PCI driver domains. + help + The PCI device frontend driver allows the kernel to import arbitrary + PCI devices from a PCI backend to support PCI driver domains. source "drivers/pci/hotplug/Kconfig" source "drivers/pci/controller/Kconfig" diff --git a/drivers/pci/controller/dwc/Kconfig b/drivers/pci/controller/dwc/Kconfig index 0ba988b5b5bc..625a031b2193 100644 --- a/drivers/pci/controller/dwc/Kconfig +++ b/drivers/pci/controller/dwc/Kconfig @@ -7,9 +7,9 @@ config PCIE_DW bool config PCIE_DW_HOST - bool + bool depends on PCI_MSI_IRQ_DOMAIN - select PCIE_DW + select PCIE_DW config PCIE_DW_EP bool @@ -224,7 +224,7 @@ config PCIE_HISI_STB depends on PCI_MSI_IRQ_DOMAIN select PCIE_DW_HOST help - Say Y here if you want PCIe controller support on HiSilicon STB SoCs + Say Y here if you want PCIe controller support on HiSilicon STB SoCs config PCI_MESON bool "MESON PCIe controller" diff --git a/drivers/pci/hotplug/Kconfig b/drivers/pci/hotplug/Kconfig index e7b493c22bf3..32455a79372d 100644 --- a/drivers/pci/hotplug/Kconfig +++ b/drivers/pci/hotplug/Kconfig @@ -83,7 +83,7 @@ config HOTPLUG_PCI_CPCI_ZT5550 depends on HOTPLUG_PCI_CPCI && X86 help Say Y here if you have an Performance Technologies (formerly Intel, - formerly just Ziatech) Ziatech ZT5550 CompactPCI system card. + formerly just Ziatech) Ziatech ZT5550 CompactPCI system card. To compile this driver as a module, choose M here: the module will be called cpcihp_zt5550. diff --git a/drivers/perf/Kconfig b/drivers/perf/Kconfig index 09ae8a970880..288c1b3589e7 100644 --- a/drivers/perf/Kconfig +++ b/drivers/perf/Kconfig @@ -83,8 +83,8 @@ config HISI_PMU bool "HiSilicon SoC PMU" depends on ARM64 && ACPI help - Support for HiSilicon SoC uncore performance monitoring - unit (PMU), such as: L3C, HHA and DDRC. + Support for HiSilicon SoC uncore performance monitoring + unit (PMU), such as: L3C, HHA and DDRC. config QCOM_L2_PMU bool "Qualcomm Technologies L2-cache PMU" @@ -115,11 +115,11 @@ config THUNDERX2_PMU in the DDR4 Memory Controller (DMC). config XGENE_PMU - depends on ARCH_XGENE - bool "APM X-Gene SoC PMU" - default n - help - Say y if you want to use APM X-Gene SoC performance monitors. + depends on ARCH_XGENE + bool "APM X-Gene SoC PMU" + default n + help + Say y if you want to use APM X-Gene SoC performance monitors. config ARM_SPE_PMU tristate "Enable support for the ARMv8.2 Statistical Profiling Extension" diff --git a/drivers/phy/hisilicon/Kconfig b/drivers/phy/hisilicon/Kconfig index 534e393a09b3..6a591bb84031 100644 --- a/drivers/phy/hisilicon/Kconfig +++ b/drivers/phy/hisilicon/Kconfig @@ -38,9 +38,9 @@ config PHY_HISI_INNO_USB2 select GENERIC_PHY select MFD_SYSCON help - Support for INNO USB2 PHY on HiSilicon SoCs. This Phy supports - USB 1.5Mb/s, USB 12Mb/s, USB 480Mb/s speeds. It supports one - USB host port to accept one USB device. + Support for INNO USB2 PHY on HiSilicon SoCs. This Phy supports + USB 1.5Mb/s, USB 12Mb/s, USB 480Mb/s speeds. It supports one + USB host port to accept one USB device. config PHY_HIX5HD2_SATA tristate "HIX5HD2 SATA PHY Driver" diff --git a/drivers/pinctrl/Kconfig b/drivers/pinctrl/Kconfig index b372419d61f2..25b6c830f2f1 100644 --- a/drivers/pinctrl/Kconfig +++ b/drivers/pinctrl/Kconfig @@ -32,15 +32,15 @@ config DEBUG_PINCTRL Say Y here to add some extra checks and diagnostics to PINCTRL calls. config PINCTRL_ARTPEC6 - bool "Axis ARTPEC-6 pin controller driver" - depends on MACH_ARTPEC6 - select PINMUX - select GENERIC_PINCONF - help - This is the driver for the Axis ARTPEC-6 pin controller. This driver - supports pin function multiplexing as well as pin bias and drive - strength configuration. Device tree integration instructions can be - found in Documentation/devicetree/bindings/pinctrl/axis,artpec6-pinctrl.txt + bool "Axis ARTPEC-6 pin controller driver" + depends on MACH_ARTPEC6 + select PINMUX + select GENERIC_PINCONF + help + This is the driver for the Axis ARTPEC-6 pin controller. This driver + supports pin function multiplexing as well as pin bias and drive + strength configuration. Device tree integration instructions can be + found in Documentation/devicetree/bindings/pinctrl/axis,artpec6-pinctrl.txt config PINCTRL_AS3722 tristate "Pinctrl and GPIO driver for ams AS3722 PMIC" diff --git a/drivers/pinctrl/freescale/Kconfig b/drivers/pinctrl/freescale/Kconfig index 5f4058033ec6..3ea9ce3e0cd9 100644 --- a/drivers/pinctrl/freescale/Kconfig +++ b/drivers/pinctrl/freescale/Kconfig @@ -39,12 +39,12 @@ config PINCTRL_IMX27 config PINCTRL_IMX25 - bool "IMX25 pinctrl driver" - depends on OF - depends on SOC_IMX25 - select PINCTRL_IMX - help - Say Y here to enable the imx25 pinctrl driver + bool "IMX25 pinctrl driver" + depends on OF + depends on SOC_IMX25 + select PINCTRL_IMX + help + Say Y here to enable the imx25 pinctrl driver config PINCTRL_IMX35 bool "IMX35 pinctrl driver" diff --git a/drivers/pinctrl/qcom/Kconfig b/drivers/pinctrl/qcom/Kconfig index 32fc2458b8eb..8ad0d3cc3bf6 100644 --- a/drivers/pinctrl/qcom/Kconfig +++ b/drivers/pinctrl/qcom/Kconfig @@ -141,10 +141,10 @@ config PINCTRL_QCOM_SPMI_PMIC select GPIOLIB_IRQCHIP select IRQ_DOMAIN_HIERARCHY help - This is the pinctrl, pinmux, pinconf and gpiolib driver for the - Qualcomm GPIO and MPP blocks found in the Qualcomm PMIC's chips, - which are using SPMI for communication with SoC. Example PMIC's - devices are pm8841, pm8941 and pma8084. + This is the pinctrl, pinmux, pinconf and gpiolib driver for the + Qualcomm GPIO and MPP blocks found in the Qualcomm PMIC's chips, + which are using SPMI for communication with SoC. Example PMIC's + devices are pm8841, pm8941 and pma8084. config PINCTRL_QCOM_SSBI_PMIC tristate "Qualcomm SSBI PMIC pin controller driver" @@ -154,10 +154,10 @@ config PINCTRL_QCOM_SSBI_PMIC select GENERIC_PINCONF select IRQ_DOMAIN_HIERARCHY help - This is the pinctrl, pinmux, pinconf and gpiolib driver for the - Qualcomm GPIO and MPP blocks found in the Qualcomm PMIC's chips, - which are using SSBI for communication with SoC. Example PMIC's - devices are pm8058 and pm8921. + This is the pinctrl, pinmux, pinconf and gpiolib driver for the + Qualcomm GPIO and MPP blocks found in the Qualcomm PMIC's chips, + which are using SSBI for communication with SoC. Example PMIC's + devices are pm8058 and pm8921. config PINCTRL_SC7180 tristate "Qualcomm Technologies Inc SC7180 pin controller driver" @@ -173,26 +173,26 @@ config PINCTRL_SDM660 depends on GPIOLIB && OF select PINCTRL_MSM help - This is the pinctrl, pinmux, pinconf and gpiolib driver for the - Qualcomm Technologies Inc TLMM block found on the Qualcomm - Technologies Inc SDM660 platform. + This is the pinctrl, pinmux, pinconf and gpiolib driver for the + Qualcomm Technologies Inc TLMM block found on the Qualcomm + Technologies Inc SDM660 platform. config PINCTRL_SDM845 tristate "Qualcomm Technologies Inc SDM845 pin controller driver" depends on GPIOLIB && (OF || ACPI) select PINCTRL_MSM help - This is the pinctrl, pinmux, pinconf and gpiolib driver for the - Qualcomm Technologies Inc TLMM block found on the Qualcomm - Technologies Inc SDM845 platform. + This is the pinctrl, pinmux, pinconf and gpiolib driver for the + Qualcomm Technologies Inc TLMM block found on the Qualcomm + Technologies Inc SDM845 platform. config PINCTRL_SM8150 tristate "Qualcomm Technologies Inc SM8150 pin controller driver" depends on GPIOLIB && OF select PINCTRL_MSM help - This is the pinctrl, pinmux, pinconf and gpiolib driver for the - Qualcomm Technologies Inc TLMM block found on the Qualcomm - Technologies Inc SM8150 platform. + This is the pinctrl, pinmux, pinconf and gpiolib driver for the + Qualcomm Technologies Inc TLMM block found on the Qualcomm + Technologies Inc SM8150 platform. endif diff --git a/drivers/platform/chrome/Kconfig b/drivers/platform/chrome/Kconfig index ee5f08ea57b6..b66cc7182287 100644 --- a/drivers/platform/chrome/Kconfig +++ b/drivers/platform/chrome/Kconfig @@ -132,9 +132,9 @@ config CROS_EC_LPC module will be called cros_ec_lpcs. config CROS_EC_PROTO - bool - help - ChromeOS EC communication protocol helpers. + bool + help + ChromeOS EC communication protocol helpers. config CROS_KBD_LED_BACKLIGHT tristate "Backlight LED support for Chrome OS keyboards" diff --git a/drivers/platform/mellanox/Kconfig b/drivers/platform/mellanox/Kconfig index 530fe7e31397..a4746bba7e9f 100644 --- a/drivers/platform/mellanox/Kconfig +++ b/drivers/platform/mellanox/Kconfig @@ -41,7 +41,7 @@ config MLXBF_TMFIFO depends on VIRTIO_CONSOLE && VIRTIO_NET help Say y here to enable TmFifo support. The TmFifo driver provides - platform driver support for the TmFifo which supports console - and networking based on the virtio framework. + platform driver support for the TmFifo which supports console + and networking based on the virtio framework. endif # MELLANOX_PLATFORM diff --git a/drivers/platform/x86/Kconfig b/drivers/platform/x86/Kconfig index ae21d08c65e8..5c356e4c7d4b 100644 --- a/drivers/platform/x86/Kconfig +++ b/drivers/platform/x86/Kconfig @@ -28,7 +28,7 @@ config ACER_WMI depends on ACPI_WMI select INPUT_SPARSEKMAP # Acer WMI depends on ACPI_VIDEO when ACPI is enabled - select ACPI_VIDEO if ACPI + select ACPI_VIDEO if ACPI ---help--- This is a driver for newer Acer (and Wistron) laptops. It adds wireless radio and bluetooth control, and on some laptops, @@ -38,18 +38,18 @@ config ACER_WMI here. config ACER_WIRELESS - tristate "Acer Wireless Radio Control Driver" - depends on ACPI - depends on INPUT - ---help--- - The Acer Wireless Radio Control handles the airplane mode hotkey - present on new Acer laptops. + tristate "Acer Wireless Radio Control Driver" + depends on ACPI + depends on INPUT + ---help--- + The Acer Wireless Radio Control handles the airplane mode hotkey + present on new Acer laptops. - Say Y or M here if you have an Acer notebook with an airplane mode - hotkey. + Say Y or M here if you have an Acer notebook with an airplane mode + hotkey. - If you choose to compile this driver as a module the module will be - called acer-wireless. + If you choose to compile this driver as a module the module will be + called acer-wireless. config ACERHDF tristate "Acer Aspire One temperature and fan driver" @@ -286,17 +286,17 @@ config FUJITSU_TABLET depends on ACPI depends on INPUT ---help--- - This is a driver for tablets built by Fujitsu: + This is a driver for tablets built by Fujitsu: - * Lifebook P1510/P1610/P1620/Txxxx - * Stylistic ST5xxx - * Possibly other Fujitsu tablet models + * Lifebook P1510/P1610/P1620/Txxxx + * Stylistic ST5xxx + * Possibly other Fujitsu tablet models - It adds support for the panel buttons, docking station detection, - tablet/notebook mode detection for convertible and - orientation detection for docked slates. + It adds support for the panel buttons, docking station detection, + tablet/notebook mode detection for convertible and + orientation detection for docked slates. - If you have a Fujitsu convertible or slate, say Y or M here. + If you have a Fujitsu convertible or slate, say Y or M here. config AMILO_RFKILL tristate "Fujitsu-Siemens Amilo rfkill support" @@ -1013,8 +1013,8 @@ config INTEL_MFLD_THERMAL tristate "Thermal driver for Intel Medfield platform" depends on MFD_INTEL_MSIC && THERMAL help - Say Y here to enable thermal driver support for the Intel Medfield - platform. + Say Y here to enable thermal driver support for the Intel Medfield + platform. config INTEL_IPS tristate "Intel Intelligent Power Sharing" @@ -1121,7 +1121,7 @@ config MXM_WMI tristate "WMI support for MXM Laptop Graphics" depends on ACPI_WMI ---help--- - MXM is a standard for laptop graphics cards, the WMI interface + MXM is a standard for laptop graphics cards, the WMI interface is required for switchable nvidia graphics machines config INTEL_OAKTRAIL @@ -1156,7 +1156,7 @@ config APPLE_GMUX control is supported by the driver. config INTEL_RST - tristate "Intel Rapid Start Technology Driver" + tristate "Intel Rapid Start Technology Driver" depends on ACPI ---help--- This driver provides support for modifying paramaters on systems @@ -1168,7 +1168,7 @@ config INTEL_RST as usual. config INTEL_SMARTCONNECT - tristate "Intel Smart Connect disabling driver" + tristate "Intel Smart Connect disabling driver" depends on ACPI ---help--- Intel Smart Connect is a technology intended to permit devices to diff --git a/drivers/power/avs/Kconfig b/drivers/power/avs/Kconfig index b5a217b828dc..089b6244b716 100644 --- a/drivers/power/avs/Kconfig +++ b/drivers/power/avs/Kconfig @@ -13,9 +13,9 @@ menuconfig POWER_AVS Say Y here to enable Adaptive Voltage Scaling class support. config ROCKCHIP_IODOMAIN - tristate "Rockchip IO domain support" - depends on POWER_AVS && ARCH_ROCKCHIP && OF - help - Say y here to enable support io domains on Rockchip SoCs. It is - necessary for the io domain setting of the SoC to match the - voltage supplied by the regulators. + tristate "Rockchip IO domain support" + depends on POWER_AVS && ARCH_ROCKCHIP && OF + help + Say y here to enable support io domains on Rockchip SoCs. It is + necessary for the io domain setting of the SoC to match the + voltage supplied by the regulators. diff --git a/drivers/power/supply/Kconfig b/drivers/power/supply/Kconfig index c84a7b1caeb6..f6995eaa5640 100644 --- a/drivers/power/supply/Kconfig +++ b/drivers/power/supply/Kconfig @@ -73,10 +73,10 @@ config WM831X_POWER provided by Wolfson Microelectronics WM831x PMICs. config WM8350_POWER - tristate "WM8350 PMU support" - depends on MFD_WM8350 - help - Say Y here to enable support for the power management unit + tristate "WM8350 PMU support" + depends on MFD_WM8350 + help + Say Y here to enable support for the power management unit provided by the Wolfson Microelectronics WM8350 PMIC. config TEST_POWER @@ -209,16 +209,16 @@ config BATTERY_WM97XX Say Y to enable support for battery measured by WM97xx aux port. config BATTERY_SBS - tristate "SBS Compliant gas gauge" - depends on I2C - help + tristate "SBS Compliant gas gauge" + depends on I2C + help Say Y to include support for SBS battery driver for SBS-compliant gas gauges. config CHARGER_SBS - tristate "SBS Compliant charger" - depends on I2C - help + tristate "SBS Compliant charger" + depends on I2C + help Say Y to include support for SBS compliant battery chargers. config MANAGER_SBS @@ -484,11 +484,11 @@ config CHARGER_MANAGER depends on REGULATOR select EXTCON help - Say Y to enable charger-manager support, which allows multiple - chargers attached to a battery and multiple batteries attached to a - system. The charger-manager also can monitor charging status in - runtime and in suspend-to-RAM by waking up the system periodically - with help of suspend_again support. + Say Y to enable charger-manager support, which allows multiple + chargers attached to a battery and multiple batteries attached to a + system. The charger-manager also can monitor charging status in + runtime and in suspend-to-RAM by waking up the system periodically + with help of suspend_again support. config CHARGER_LT3651 tristate "Analog Devices LT3651 charger" diff --git a/drivers/regulator/Kconfig b/drivers/regulator/Kconfig index 3ee63531f6d5..74eb5af7295f 100644 --- a/drivers/regulator/Kconfig +++ b/drivers/regulator/Kconfig @@ -841,10 +841,10 @@ config REGULATOR_SKY81452 will be called sky81452-regulator. config REGULATOR_SLG51000 - tristate "Dialog Semiconductor SLG51000 regulators" - depends on I2C - select REGMAP_I2C - help + tristate "Dialog Semiconductor SLG51000 regulators" + depends on I2C + select REGMAP_I2C + help Say y here to support for the Dialog Semiconductor SLG51000. The SLG51000 is seven compact and customizable low dropout regulators. diff --git a/drivers/rpmsg/Kconfig b/drivers/rpmsg/Kconfig index d0322b41eca5..709276540ef1 100644 --- a/drivers/rpmsg/Kconfig +++ b/drivers/rpmsg/Kconfig @@ -21,7 +21,7 @@ config RPMSG_QCOM_GLINK_NATIVE config RPMSG_QCOM_GLINK_RPM tristate "Qualcomm RPM Glink driver" - select RPMSG_QCOM_GLINK_NATIVE + select RPMSG_QCOM_GLINK_NATIVE depends on HAS_IOMEM depends on MAILBOX help diff --git a/drivers/rtc/Kconfig b/drivers/rtc/Kconfig index 1adf9f815652..bc95038457c8 100644 --- a/drivers/rtc/Kconfig +++ b/drivers/rtc/Kconfig @@ -1510,9 +1510,9 @@ config RTC_DRV_PXA depends on ARCH_PXA select RTC_DRV_SA1100 help - If you say Y here you will get access to the real time clock - built into your PXA27x or PXA3xx CPU. This RTC is actually 2 RTCs - consisting of an SA1100 compatible RTC and the extended PXA RTC. + If you say Y here you will get access to the real time clock + built into your PXA27x or PXA3xx CPU. This RTC is actually 2 RTCs + consisting of an SA1100 compatible RTC and the extended PXA RTC. This RTC driver uses PXA RTC registers available since pxa27x series (RDxR, RYxR) instead of legacy RCNR, RTAR. diff --git a/drivers/scsi/Kconfig b/drivers/scsi/Kconfig index 1b92f3c19ff3..23678311b51c 100644 --- a/drivers/scsi/Kconfig +++ b/drivers/scsi/Kconfig @@ -1166,8 +1166,8 @@ config SCSI_LPFC depends on NVME_FC || NVME_FC=n select CRC_T10DIF ---help--- - This lpfc driver supports the Emulex LightPulse - Family of Fibre Channel PCI host adapters. + This lpfc driver supports the Emulex LightPulse + Family of Fibre Channel PCI host adapters. config SCSI_LPFC_DEBUG_FS bool "Emulex LightPulse Fibre Channel debugfs Support" @@ -1480,14 +1480,14 @@ config ZFCP depends on S390 && QDIO && SCSI depends on SCSI_FC_ATTRS help - If you want to access SCSI devices attached to your IBM eServer - zSeries by means of Fibre Channel interfaces say Y. - For details please refer to the documentation provided by IBM at - <http://oss.software.ibm.com/developerworks/opensource/linux390> + If you want to access SCSI devices attached to your IBM eServer + zSeries by means of Fibre Channel interfaces say Y. + For details please refer to the documentation provided by IBM at + <http://oss.software.ibm.com/developerworks/opensource/linux390> - This driver is also available as a module. This module will be - called zfcp. If you want to compile it as a module, say M here - and read <file:Documentation/kbuild/modules.rst>. + This driver is also available as a module. This module will be + called zfcp. If you want to compile it as a module, say M here + and read <file:Documentation/kbuild/modules.rst>. config SCSI_PMCRAID tristate "PMC SIERRA Linux MaxRAID adapter support" @@ -1518,8 +1518,8 @@ config SCSI_VIRTIO tristate "virtio-scsi support" depends on VIRTIO help - This is the virtual HBA driver for virtio. If the kernel will - be used in a virtual machine, say Y or M. + This is the virtual HBA driver for virtio. If the kernel will + be used in a virtual machine, say Y or M. source "drivers/scsi/csiostor/Kconfig" diff --git a/drivers/scsi/aic7xxx/Kconfig.aic7xxx b/drivers/scsi/aic7xxx/Kconfig.aic7xxx index 3546b8cc401f..4ed44ba4a55b 100644 --- a/drivers/scsi/aic7xxx/Kconfig.aic7xxx +++ b/drivers/scsi/aic7xxx/Kconfig.aic7xxx @@ -71,20 +71,20 @@ config AIC7XXX_DEBUG_ENABLE driver errors. config AIC7XXX_DEBUG_MASK - int "Debug code enable mask (2047 for all debugging)" - depends on SCSI_AIC7XXX - default "0" - help + int "Debug code enable mask (2047 for all debugging)" + depends on SCSI_AIC7XXX + default "0" + help Bit mask of debug options that is only valid if the CONFIG_AIC7XXX_DEBUG_ENABLE option is enabled. The bits in this mask are defined in the drivers/scsi/aic7xxx/aic7xxx.h - search for the variable ahc_debug in that file to find them. config AIC7XXX_REG_PRETTY_PRINT - bool "Decode registers during diagnostics" - depends on SCSI_AIC7XXX + bool "Decode registers during diagnostics" + depends on SCSI_AIC7XXX default y - help + help Compile in register value tables for the output of expanded register contents in diagnostics. This make it much easier to understand debug output without having to refer to a data book and/or the aic7xxx.reg diff --git a/drivers/scsi/pcmcia/Kconfig b/drivers/scsi/pcmcia/Kconfig index 2368f34efba3..03aec3410ac7 100644 --- a/drivers/scsi/pcmcia/Kconfig +++ b/drivers/scsi/pcmcia/Kconfig @@ -56,7 +56,7 @@ config PCMCIA_NINJA_SCSI [I-O DATA (OEM) (version string: "IO DATA","CBSC16 ","1")] I-O DATA CBSC-II [Kyusyu Matsushita Kotobuki (OEM) - (version string: "KME ","SCSI-CARD-001","1")] + (version string: "KME ","SCSI-CARD-001","1")] KME KXL-820AN's card HP M820e CDRW's card etc. diff --git a/drivers/scsi/qedf/Kconfig b/drivers/scsi/qedf/Kconfig index 7cd993be4e57..80328dbd44c9 100644 --- a/drivers/scsi/qedf/Kconfig +++ b/drivers/scsi/qedf/Kconfig @@ -3,8 +3,8 @@ config QEDF tristate "QLogic QEDF 25/40/100Gb FCoE Initiator Driver Support" depends on PCI && SCSI depends on QED - depends on LIBFC - depends on LIBFCOE + depends on LIBFC + depends on LIBFCOE select QED_LL2 select QED_FCOE ---help--- diff --git a/drivers/scsi/smartpqi/Kconfig b/drivers/scsi/smartpqi/Kconfig index bc6506884e3b..456ec474fa17 100644 --- a/drivers/scsi/smartpqi/Kconfig +++ b/drivers/scsi/smartpqi/Kconfig @@ -50,7 +50,7 @@ config SCSI_SMARTPQI To compile this driver as a module, choose M here: the module will be called smartpqi. - Note: the aacraid driver will not manage a smartpqi - controller. You need to enable smartpqi for smartpqi - controllers. For more information, please see - Documentation/scsi/smartpqi.txt + Note: the aacraid driver will not manage a smartpqi + controller. You need to enable smartpqi for smartpqi + controllers. For more information, please see + Documentation/scsi/smartpqi.txt diff --git a/drivers/soc/fsl/Kconfig b/drivers/soc/fsl/Kconfig index f9ad8ad54a7d..192e28f2cc9a 100644 --- a/drivers/soc/fsl/Kconfig +++ b/drivers/soc/fsl/Kconfig @@ -21,10 +21,10 @@ config FSL_GUTS into this driver as well. config FSL_MC_DPIO - tristate "QorIQ DPAA2 DPIO driver" - depends on FSL_MC_BUS - select SOC_BUS - help + tristate "QorIQ DPAA2 DPIO driver" + depends on FSL_MC_BUS + select SOC_BUS + help Driver for the DPAA2 DPIO object. A DPIO provides queue and buffer management facilities for software to interact with other DPAA2 objects. This driver does not expose the DPIO diff --git a/drivers/soc/qcom/Kconfig b/drivers/soc/qcom/Kconfig index 661e47acc354..fd3abdf82fc0 100644 --- a/drivers/soc/qcom/Kconfig +++ b/drivers/soc/qcom/Kconfig @@ -45,13 +45,13 @@ config QCOM_GLINK_SSR neighboring subsystems going up or down. config QCOM_GSBI - tristate "QCOM General Serial Bus Interface" - depends on ARCH_QCOM || COMPILE_TEST - select MFD_SYSCON - help - Say y here to enable GSBI support. The GSBI provides control - functions for connecting the underlying serial UART, SPI, and I2C - devices to the output pins. + tristate "QCOM General Serial Bus Interface" + depends on ARCH_QCOM || COMPILE_TEST + select MFD_SYSCON + help + Say y here to enable GSBI support. The GSBI provides control + functions for connecting the underlying serial UART, SPI, and I2C + devices to the output pins. config QCOM_LLCC tristate "Qualcomm Technologies, Inc. LLCC driver" @@ -196,8 +196,8 @@ config QCOM_APR depends on ARCH_QCOM || COMPILE_TEST depends on RPMSG help - Enable APR IPC protocol support between - application processor and QDSP6. APR is - used by audio driver to configure QDSP6 - ASM, ADM and AFE modules. + Enable APR IPC protocol support between + application processor and QDSP6. APR is + used by audio driver to configure QDSP6 + ASM, ADM and AFE modules. endmenu diff --git a/drivers/soc/rockchip/Kconfig b/drivers/soc/rockchip/Kconfig index b71b73bf5fc5..3e2057f22bbc 100644 --- a/drivers/soc/rockchip/Kconfig +++ b/drivers/soc/rockchip/Kconfig @@ -15,15 +15,15 @@ config ROCKCHIP_GRF to make some of them conform to expectations of the kernel. config ROCKCHIP_PM_DOMAINS - bool "Rockchip generic power domain" - depends on PM - select PM_GENERIC_DOMAINS - help - Say y here to enable power domain support. - In order to meet high performance and low power requirements, a power - management unit is designed or saving power when RK3288 in low power - mode. The RK3288 PMU is dedicated for managing the power of the whole chip. + bool "Rockchip generic power domain" + depends on PM + select PM_GENERIC_DOMAINS + help + Say y here to enable power domain support. + In order to meet high performance and low power requirements, a power + management unit is designed or saving power when RK3288 in low power + mode. The RK3288 PMU is dedicated for managing the power of the whole chip. - If unsure, say N. + If unsure, say N. endif diff --git a/drivers/spi/Kconfig b/drivers/spi/Kconfig index 6f7fdcbb9151..5e9d209e6d82 100644 --- a/drivers/spi/Kconfig +++ b/drivers/spi/Kconfig @@ -143,7 +143,7 @@ config SPI_BCM63XX tristate "Broadcom BCM63xx SPI controller" depends on BCM63XX || COMPILE_TEST help - Enable support for the SPI controller on the Broadcom BCM63xx SoCs. + Enable support for the SPI controller on the Broadcom BCM63xx SoCs. config SPI_BCM63XX_HSSPI tristate "Broadcom BCM63XX HS SPI controller driver" @@ -234,11 +234,11 @@ config SPI_DLN2 tristate "Diolan DLN-2 USB SPI adapter" depends on MFD_DLN2 help - If you say yes to this option, support will be included for Diolan - DLN2, a USB to SPI interface. + If you say yes to this option, support will be included for Diolan + DLN2, a USB to SPI interface. - This driver can also be built as a module. If so, the module - will be called spi-dln2. + This driver can also be built as a module. If so, the module + will be called spi-dln2. config SPI_EFM32 tristate "EFM32 SPI controller" @@ -747,10 +747,10 @@ config SPI_SYNQUACER It also supports the new dual-bit and quad-bit SPI protocol. config SPI_MXIC - tristate "Macronix MX25F0A SPI controller" - depends on SPI_MASTER - help - This selects the Macronix MX25F0A SPI controller driver. + tristate "Macronix MX25F0A SPI controller" + depends on SPI_MASTER + help + This selects the Macronix MX25F0A SPI controller driver. config SPI_MXS tristate "Freescale MXS SPI controller" diff --git a/drivers/staging/fbtft/Kconfig b/drivers/staging/fbtft/Kconfig index cb61c2a772bd..665548a0b234 100644 --- a/drivers/staging/fbtft/Kconfig +++ b/drivers/staging/fbtft/Kconfig @@ -95,8 +95,8 @@ config FB_TFT_PCD8544 Generic Framebuffer support for PCD8544 config FB_TFT_RA8875 - tristate "FB driver for the RA8875 LCD Controller" - depends on FB_TFT + tristate "FB driver for the RA8875 LCD Controller" + depends on FB_TFT help Generic Framebuffer support for RA8875 @@ -125,10 +125,10 @@ config FB_TFT_SSD1289 Framebuffer support for SSD1289 config FB_TFT_SSD1305 - tristate "FB driver for the SSD1305 OLED Controller" - depends on FB_TFT - help - Framebuffer support for SSD1305 + tristate "FB driver for the SSD1305 OLED Controller" + depends on FB_TFT + help + Framebuffer support for SSD1305 config FB_TFT_SSD1306 tristate "FB driver for the SSD1306 OLED Controller" diff --git a/drivers/staging/fwserial/Kconfig b/drivers/staging/fwserial/Kconfig index 9543f8454af9..d21124a1a127 100644 --- a/drivers/staging/fwserial/Kconfig +++ b/drivers/staging/fwserial/Kconfig @@ -3,7 +3,7 @@ config FIREWIRE_SERIAL tristate "TTY over Firewire" depends on FIREWIRE && TTY help - This enables TTY over IEEE 1394, providing high-speed serial + This enables TTY over IEEE 1394, providing high-speed serial connectivity to cabled peers. This driver implements a ad-hoc transport protocol and is currently limited to Linux-to-Linux communication. @@ -17,7 +17,7 @@ config FWTTY_MAX_TOTAL_PORTS int "Maximum number of serial ports supported" default "64" help - Set this to the maximum number of serial ports you want the + Set this to the maximum number of serial ports you want the firewire-serial driver to support. config FWTTY_MAX_CARD_PORTS @@ -25,7 +25,7 @@ config FWTTY_MAX_CARD_PORTS range 0 FWTTY_MAX_TOTAL_PORTS default "32" help - Set this to the maximum number of serial ports each firewire + Set this to the maximum number of serial ports each firewire adapter supports. The actual number of serial ports registered is set with the module parameter "ttys". diff --git a/drivers/staging/most/Kconfig b/drivers/staging/most/Kconfig index 8948d5246409..6262eb25c80b 100644 --- a/drivers/staging/most/Kconfig +++ b/drivers/staging/most/Kconfig @@ -1,9 +1,9 @@ # SPDX-License-Identifier: GPL-2.0 menuconfig MOST - tristate "MOST support" + tristate "MOST support" depends on HAS_DMA && CONFIGFS_FS - default n - help + default n + help Say Y here if you want to enable MOST support. This driver needs at least one additional component to enable the desired access from userspace (e.g. character devices) and one that @@ -12,7 +12,7 @@ menuconfig MOST To compile this driver as a module, choose M here: the module will be called most_core. - If in doubt, say N here. + If in doubt, say N here. diff --git a/drivers/staging/nvec/Kconfig b/drivers/staging/nvec/Kconfig index 5c12cacf75e1..9fa98c16f1d9 100644 --- a/drivers/staging/nvec/Kconfig +++ b/drivers/staging/nvec/Kconfig @@ -8,7 +8,7 @@ config MFD_NVEC controller. To compile this driver as a module, say M here: the module will be - called mfd-nvec + called mfd-nvec config KEYBOARD_NVEC tristate "Keyboard on nVidia compliant EC" @@ -18,7 +18,7 @@ config KEYBOARD_NVEC a nVidia compliant embedded controller. To compile this driver as a module, say M here: the module will be - called keyboard-nvec + called keyboard-nvec config SERIO_NVEC_PS2 tristate "PS2 on nVidia EC" @@ -28,7 +28,7 @@ config SERIO_NVEC_PS2 to a nVidia compliant embedded controller. To compile this driver as a module, say M here: the module will be - called serio-nvec-ps2 + called serio-nvec-ps2 config NVEC_POWER @@ -39,7 +39,7 @@ config NVEC_POWER nVidia compliant embedded controllers. To compile this driver as a module, say M here: the module will be - called nvec-power + called nvec-power config NVEC_PAZ00 @@ -50,5 +50,5 @@ config NVEC_PAZ00 devices, e.g. Toshbia AC100 and Dynabooks AZ netbooks. To compile this driver as a module, say M here: the module will be - called nvec-paz00 + called nvec-paz00 diff --git a/drivers/staging/pi433/Kconfig b/drivers/staging/pi433/Kconfig index 8acde0814206..dd9e4709d1a8 100644 --- a/drivers/staging/pi433/Kconfig +++ b/drivers/staging/pi433/Kconfig @@ -1,17 +1,17 @@ # SPDX-License-Identifier: GPL-2.0 config PI433 - tristate "Pi433 - a 433MHz radio module for Raspberry Pi" - depends on SPI - help - This option allows you to enable support for the radio module Pi433. + tristate "Pi433 - a 433MHz radio module for Raspberry Pi" + depends on SPI + help + This option allows you to enable support for the radio module Pi433. - Pi433 is a shield that fits onto the GPIO header of a Raspberry Pi - or compatible. It extends the Raspberry Pi with the option, to - send and receive data in the 433MHz ISM band - for example to - communicate between two systems without using ethernet or bluetooth - or for control or read sockets, actors, sensors, widely available - for low price. + Pi433 is a shield that fits onto the GPIO header of a Raspberry Pi + or compatible. It extends the Raspberry Pi with the option, to + send and receive data in the 433MHz ISM band - for example to + communicate between two systems without using ethernet or bluetooth + or for control or read sockets, actors, sensors, widely available + for low price. - For details or the option to buy, please visit https://pi433.de/en.html + For details or the option to buy, please visit https://pi433.de/en.html - If in doubt, say N here, but saying yes most probably won't hurt + If in doubt, say N here, but saying yes most probably won't hurt diff --git a/drivers/staging/uwb/Kconfig b/drivers/staging/uwb/Kconfig index 259e053e1e09..c03dcc76b57c 100644 --- a/drivers/staging/uwb/Kconfig +++ b/drivers/staging/uwb/Kconfig @@ -42,31 +42,31 @@ config UWB_HWA is safe to select any even if you do not have the hardware. config UWB_WHCI - tristate "UWB Radio Control driver for WHCI-compliant cards" - depends on PCI - help - This driver enables the radio controller for WHCI cards. + tristate "UWB Radio Control driver for WHCI-compliant cards" + depends on PCI + help + This driver enables the radio controller for WHCI cards. - WHCI is a specification developed by Intel - (http://www.intel.com/technology/comms/wusb/whci.htm) much - in the spirit of USB's EHCI, but for UWB and Wireless USB - radio/host controllers connected via memory mapping (eg: - PCI). Most of these cards come also with a Wireless USB host - controller. + WHCI is a specification developed by Intel + (http://www.intel.com/technology/comms/wusb/whci.htm) much + in the spirit of USB's EHCI, but for UWB and Wireless USB + radio/host controllers connected via memory mapping (eg: + PCI). Most of these cards come also with a Wireless USB host + controller. - To compile this driver select Y (built in) or M (module). It - is safe to select any even if you do not have the hardware. + To compile this driver select Y (built in) or M (module). It + is safe to select any even if you do not have the hardware. config UWB_I1480U - tristate "Support for Intel Wireless UWB Link 1480 HWA" - depends on UWB_HWA - select FW_LOADER - help - This driver enables support for the i1480 when connected via - USB. It consists of a firmware uploader that will enable it - to behave as an HWA device. + tristate "Support for Intel Wireless UWB Link 1480 HWA" + depends on UWB_HWA + select FW_LOADER + help + This driver enables support for the i1480 when connected via + USB. It consists of a firmware uploader that will enable it + to behave as an HWA device. - To compile this driver select Y (built in) or M (module). It - is safe to select any even if you do not have the hardware. + To compile this driver select Y (built in) or M (module). It + is safe to select any even if you do not have the hardware. endif # UWB diff --git a/drivers/staging/vc04_services/bcm2835-audio/Kconfig b/drivers/staging/vc04_services/bcm2835-audio/Kconfig index f66319512faf..d32ea348e846 100644 --- a/drivers/staging/vc04_services/bcm2835-audio/Kconfig +++ b/drivers/staging/vc04_services/bcm2835-audio/Kconfig @@ -1,9 +1,9 @@ # SPDX-License-Identifier: GPL-2.0 config SND_BCM2835 - tristate "BCM2835 Audio" - depends on (ARCH_BCM2835 || COMPILE_TEST) && SND - select SND_PCM - select BCM2835_VCHIQ - help - Say Y or M if you want to support BCM2835 built in audio + tristate "BCM2835 Audio" + depends on (ARCH_BCM2835 || COMPILE_TEST) && SND + select SND_PCM + select BCM2835_VCHIQ + help + Say Y or M if you want to support BCM2835 built in audio diff --git a/drivers/staging/wusbcore/Kconfig b/drivers/staging/wusbcore/Kconfig index a559d023b508..64be97ca734a 100644 --- a/drivers/staging/wusbcore/Kconfig +++ b/drivers/staging/wusbcore/Kconfig @@ -11,7 +11,7 @@ config USB_WUSB help Enable the host-side support for Wireless USB. - To compile this support select Y (built in). It is safe to + To compile this support select Y (built in). It is safe to select even if you don't have the hardware. config USB_WUSB_CBAF diff --git a/drivers/tty/Kconfig b/drivers/tty/Kconfig index c7623f99ac0f..ec53b1d4aef3 100644 --- a/drivers/tty/Kconfig +++ b/drivers/tty/Kconfig @@ -85,13 +85,13 @@ config VT_HW_CONSOLE_BINDING bool "Support for binding and unbinding console drivers" depends on HW_CONSOLE ---help--- - The virtual terminal is the device that interacts with the physical - terminal through console drivers. On these systems, at least one - console driver is loaded. In other configurations, additional console - drivers may be enabled, such as the framebuffer console. If more than - 1 console driver is enabled, setting this to 'y' will allow you to - select the console driver that will serve as the backend for the - virtual terminals. + The virtual terminal is the device that interacts with the physical + terminal through console drivers. On these systems, at least one + console driver is loaded. In other configurations, additional console + drivers may be enabled, such as the framebuffer console. If more than + 1 console driver is enabled, setting this to 'y' will allow you to + select the console driver that will serve as the backend for the + virtual terminals. See <file:Documentation/driver-api/console.rst> for more information. For framebuffer console users, please refer to @@ -173,15 +173,15 @@ config ROCKETPORT depends on SERIAL_NONSTANDARD && (ISA || EISA || PCI) help This driver supports Comtrol RocketPort and RocketModem PCI boards. - These boards provide 2, 4, 8, 16, or 32 high-speed serial ports or - modems. For information about the RocketPort/RocketModem boards - and this driver read <file:Documentation/driver-api/serial/rocket.rst>. + These boards provide 2, 4, 8, 16, or 32 high-speed serial ports or + modems. For information about the RocketPort/RocketModem boards + and this driver read <file:Documentation/driver-api/serial/rocket.rst>. To compile this driver as a module, choose M here: the module will be called rocket. If you want to compile this driver into the kernel, say Y here. If - you don't have a Comtrol RocketPort/RocketModem card installed, say N. + you don't have a Comtrol RocketPort/RocketModem card installed, say N. config CYCLADES tristate "Cyclades async mux support" @@ -437,8 +437,8 @@ config MIPS_EJTAG_FDC_KGDB depends on MIPS_EJTAG_FDC_TTY && KGDB default y help - This enables the use of KGDB over an FDC channel, allowing KGDB to be - used remotely or when a serial port isn't available. + This enables the use of KGDB over an FDC channel, allowing KGDB to be + used remotely or when a serial port isn't available. config MIPS_EJTAG_FDC_KGDB_CHAN int "KGDB FDC channel" diff --git a/drivers/tty/hvc/Kconfig b/drivers/tty/hvc/Kconfig index 4d22b911111f..bb5953dd1a2c 100644 --- a/drivers/tty/hvc/Kconfig +++ b/drivers/tty/hvc/Kconfig @@ -74,7 +74,7 @@ config HVC_UDBG depends on PPC select HVC_DRIVER help - This is meant to be used during HW bring up or debugging when + This is meant to be used during HW bring up or debugging when no other console mechanism exist but udbg, to get you a quick console for userspace. Do NOT enable in production kernels. @@ -83,7 +83,7 @@ config HVC_DCC depends on ARM || ARM64 select HVC_DRIVER help - This console uses the JTAG DCC on ARM to create a console under the HVC + This console uses the JTAG DCC on ARM to create a console under the HVC driver. This console is used through a JTAG only on ARM. If you don't have a JTAG then you probably don't want this option. diff --git a/drivers/tty/serial/8250/Kconfig b/drivers/tty/serial/8250/Kconfig index 7ef60f8b6e2c..7e132657f160 100644 --- a/drivers/tty/serial/8250/Kconfig +++ b/drivers/tty/serial/8250/Kconfig @@ -334,7 +334,7 @@ config SERIAL_8250_BCM2835AUX Features and limitations of the UART are Registers are similar to 16650 registers, - set bits in the control registers that are unsupported + set bits in the control registers that are unsupported are ignored and read back as 0 7/8 bit operation with 1 start and 1 stop bit 8 symbols deep fifo for rx and tx diff --git a/drivers/tty/serial/Kconfig b/drivers/tty/serial/Kconfig index 4789b5d62f63..b11b4d725ae6 100644 --- a/drivers/tty/serial/Kconfig +++ b/drivers/tty/serial/Kconfig @@ -287,26 +287,26 @@ config SERIAL_SAMSUNG_CONSOLE boot time.) config SERIAL_SIRFSOC - tristate "SiRF SoC Platform Serial port support" - depends on ARCH_SIRF - select SERIAL_CORE - help - Support for the on-chip UART on the CSR SiRFprimaII series, - providing /dev/ttySiRF0, 1 and 2 (note, some machines may not - provide all of these ports, depending on how the serial port - pins are configured). + tristate "SiRF SoC Platform Serial port support" + depends on ARCH_SIRF + select SERIAL_CORE + help + Support for the on-chip UART on the CSR SiRFprimaII series, + providing /dev/ttySiRF0, 1 and 2 (note, some machines may not + provide all of these ports, depending on how the serial port + pins are configured). config SERIAL_SIRFSOC_CONSOLE - bool "Support for console on SiRF SoC serial port" - depends on SERIAL_SIRFSOC=y - select SERIAL_CORE_CONSOLE - help - Even if you say Y here, the currently visible virtual console - (/dev/tty0) will still be used as the system console by default, but - you can alter that using a kernel command line option such as - "console=ttySiRFx". (Try "man bootparam" or see the documentation of - your boot loader about how to pass options to the kernel at - boot time.) + bool "Support for console on SiRF SoC serial port" + depends on SERIAL_SIRFSOC=y + select SERIAL_CORE_CONSOLE + help + Even if you say Y here, the currently visible virtual console + (/dev/tty0) will still be used as the system console by default, but + you can alter that using a kernel command line option such as + "console=ttySiRFx". (Try "man bootparam" or see the documentation of + your boot loader about how to pass options to the kernel at + boot time.) config SERIAL_TEGRA tristate "NVIDIA Tegra20/30 SoC serial controller" @@ -1077,41 +1077,41 @@ config SERIAL_SCCNXP_CONSOLE Support for console on SCCNXP serial ports. config SERIAL_SC16IS7XX_CORE - tristate + tristate config SERIAL_SC16IS7XX - tristate "SC16IS7xx serial support" - select SERIAL_CORE - depends on (SPI_MASTER && !I2C) || I2C - help - This selects support for SC16IS7xx serial ports. - Supported ICs are SC16IS740, SC16IS741, SC16IS750, SC16IS752, - SC16IS760 and SC16IS762. Select supported buses using options below. + tristate "SC16IS7xx serial support" + select SERIAL_CORE + depends on (SPI_MASTER && !I2C) || I2C + help + This selects support for SC16IS7xx serial ports. + Supported ICs are SC16IS740, SC16IS741, SC16IS750, SC16IS752, + SC16IS760 and SC16IS762. Select supported buses using options below. config SERIAL_SC16IS7XX_I2C - bool "SC16IS7xx for I2C interface" - depends on SERIAL_SC16IS7XX - depends on I2C - select SERIAL_SC16IS7XX_CORE if SERIAL_SC16IS7XX - select REGMAP_I2C if I2C - default y - help - Enable SC16IS7xx driver on I2C bus, - If required say y, and say n to i2c if not required, - Enabled by default to support oldconfig. - You must select at least one bus for the driver to be built. + bool "SC16IS7xx for I2C interface" + depends on SERIAL_SC16IS7XX + depends on I2C + select SERIAL_SC16IS7XX_CORE if SERIAL_SC16IS7XX + select REGMAP_I2C if I2C + default y + help + Enable SC16IS7xx driver on I2C bus, + If required say y, and say n to i2c if not required, + Enabled by default to support oldconfig. + You must select at least one bus for the driver to be built. config SERIAL_SC16IS7XX_SPI - bool "SC16IS7xx for spi interface" - depends on SERIAL_SC16IS7XX - depends on SPI_MASTER - select SERIAL_SC16IS7XX_CORE if SERIAL_SC16IS7XX - select REGMAP_SPI if SPI_MASTER - help - Enable SC16IS7xx driver on SPI bus, - If required say y, and say n to spi if not required, - This is additional support to exsisting driver. - You must select at least one bus for the driver to be built. + bool "SC16IS7xx for spi interface" + depends on SERIAL_SC16IS7XX + depends on SPI_MASTER + select SERIAL_SC16IS7XX_CORE if SERIAL_SC16IS7XX + select REGMAP_SPI if SPI_MASTER + help + Enable SC16IS7xx driver on SPI bus, + If required say y, and say n to spi if not required, + This is additional support to exsisting driver. + You must select at least one bus for the driver to be built. config SERIAL_TIMBERDALE tristate "Support for timberdale UART" @@ -1211,7 +1211,7 @@ config SERIAL_ALTERA_UART_CONSOLE Enable a Altera UART port to be the system console. config SERIAL_IFX6X60 - tristate "SPI protocol driver for Infineon 6x60 modem (EXPERIMENTAL)" + tristate "SPI protocol driver for Infineon 6x60 modem (EXPERIMENTAL)" depends on GPIOLIB || COMPILE_TEST depends on SPI && HAS_DMA help diff --git a/drivers/video/backlight/Kconfig b/drivers/video/backlight/Kconfig index 40676be2e46a..3b591e294707 100644 --- a/drivers/video/backlight/Kconfig +++ b/drivers/video/backlight/Kconfig @@ -9,7 +9,7 @@ menu "Backlight & LCD device support" # LCD # config LCD_CLASS_DEVICE - tristate "Lowlevel LCD controls" + tristate "Lowlevel LCD controls" help This framework adds support for low-level control of LCD. Some framebuffer devices connect to platform-specific LCD modules @@ -141,10 +141,10 @@ endif # LCD_CLASS_DEVICE # Backlight # config BACKLIGHT_CLASS_DEVICE - tristate "Lowlevel Backlight controls" + tristate "Lowlevel Backlight controls" help This framework adds support for low-level control of the LCD - backlight. This includes support for brightness and power. + backlight. This includes support for brightness and power. To have support for your specific LCD panel you will have to select the proper drivers which depend on this option. @@ -272,7 +272,7 @@ config BACKLIGHT_APPLE tristate "Apple Backlight Driver" depends on X86 && ACPI help - If you have an Intel-based Apple say Y to enable a driver for its + If you have an Intel-based Apple say Y to enable a driver for its backlight. config BACKLIGHT_TOSA diff --git a/drivers/video/console/Kconfig b/drivers/video/console/Kconfig index c10e17fb9a9a..ac3a28c08f78 100644 --- a/drivers/video/console/Kconfig +++ b/drivers/video/console/Kconfig @@ -27,7 +27,7 @@ config VGACON_SOFT_SCROLLBACK depends on VGA_CONSOLE default n help - The scrollback buffer of the standard VGA console is located in + The scrollback buffer of the standard VGA console is located in the VGA RAM. The size of this RAM is fixed and is quite small. If you require a larger scrollback buffer, this can be placed in System RAM which is dynamically allocated during initialization. @@ -84,12 +84,12 @@ config MDA_CONSOLE If unsure, say N. config SGI_NEWPORT_CONSOLE - tristate "SGI Newport Console support" + tristate "SGI Newport Console support" depends on SGI_IP22 && HAS_IOMEM - select FONT_SUPPORT - help - Say Y here if you want the console on the Newport aka XL graphics - card of your Indy. Most people say Y here. + select FONT_SUPPORT + help + Say Y here if you want the console on the Newport aka XL graphics + card of your Indy. Most people say Y here. config DUMMY_CONSOLE bool @@ -97,24 +97,24 @@ config DUMMY_CONSOLE default y config DUMMY_CONSOLE_COLUMNS - int "Initial number of console screen columns" - depends on DUMMY_CONSOLE && !ARM - default 160 if PARISC - default 80 - help - On PA-RISC, the default value is 160, which should fit a 1280x1024 - monitor. - Select 80 if you use a 640x480 resolution by default. + int "Initial number of console screen columns" + depends on DUMMY_CONSOLE && !ARM + default 160 if PARISC + default 80 + help + On PA-RISC, the default value is 160, which should fit a 1280x1024 + monitor. + Select 80 if you use a 640x480 resolution by default. config DUMMY_CONSOLE_ROWS - int "Initial number of console screen rows" - depends on DUMMY_CONSOLE && !ARM - default 64 if PARISC - default 25 - help - On PA-RISC, the default value is 64, which should fit a 1280x1024 - monitor. - Select 25 if you use a 640x480 resolution by default. + int "Initial number of console screen rows" + depends on DUMMY_CONSOLE && !ARM + default 64 if PARISC + default 25 + help + On PA-RISC, the default value is 64, which should fit a 1280x1024 + monitor. + Select 25 if you use a 640x480 resolution by default. config FRAMEBUFFER_CONSOLE bool "Framebuffer Console support" @@ -130,11 +130,11 @@ config FRAMEBUFFER_CONSOLE_DETECT_PRIMARY depends on FRAMEBUFFER_CONSOLE default n ---help--- - If this option is selected, the framebuffer console will - automatically select the primary display device (if the architecture + If this option is selected, the framebuffer console will + automatically select the primary display device (if the architecture supports this feature). Otherwise, the framebuffer console will - always select the first framebuffer driver that is loaded. The latter - is the default behavior. + always select the first framebuffer driver that is loaded. The latter + is the default behavior. You can always override the automatic selection of the primary device by using the fbcon=map: boot option. @@ -145,11 +145,11 @@ config FRAMEBUFFER_CONSOLE_ROTATION bool "Framebuffer Console Rotation" depends on FRAMEBUFFER_CONSOLE help - Enable display rotation for the framebuffer console. This is done - in software and may be significantly slower than a normally oriented - display. Note that the rotation is done at the console level only - such that other users of the framebuffer will remain normally - oriented. + Enable display rotation for the framebuffer console. This is done + in software and may be significantly slower than a normally oriented + display. Note that the rotation is done at the console level only + such that other users of the framebuffer will remain normally + oriented. config FRAMEBUFFER_CONSOLE_DEFERRED_TAKEOVER bool "Framebuffer Console Deferred Takeover" @@ -163,14 +163,14 @@ config FRAMEBUFFER_CONSOLE_DEFERRED_TAKEOVER black screen as soon as fbcon loads. config STI_CONSOLE - bool "STI text console" + bool "STI text console" depends on PARISC && HAS_IOMEM - select FONT_SUPPORT - default y - help - The STI console is the builtin display/keyboard on HP-PARISC - machines. Say Y here to build support for it into your kernel. - The alternative is to use your primary serial port as a console. + select FONT_SUPPORT + default y + help + The STI console is the builtin display/keyboard on HP-PARISC + machines. Say Y here to build support for it into your kernel. + The alternative is to use your primary serial port as a console. endmenu diff --git a/drivers/virt/Kconfig b/drivers/virt/Kconfig index 363af2eaf2ba..cb5d2d89592f 100644 --- a/drivers/virt/Kconfig +++ b/drivers/virt/Kconfig @@ -18,17 +18,17 @@ config FSL_HV_MANAGER depends on FSL_SOC select EPAPR_PARAVIRT help - The Freescale hypervisor management driver provides several services + The Freescale hypervisor management driver provides several services to drivers and applications related to the Freescale hypervisor: - 1) An ioctl interface for querying and managing partitions. + 1) An ioctl interface for querying and managing partitions. - 2) A file interface to reading incoming doorbells. + 2) A file interface to reading incoming doorbells. - 3) An interrupt handler for shutting down the partition upon + 3) An interrupt handler for shutting down the partition upon receiving the shutdown doorbell from a manager partition. - 4) A kernel interface for receiving callbacks when a managed + 4) A kernel interface for receiving callbacks when a managed partition shuts down. source "drivers/virt/vboxguest/Kconfig" diff --git a/drivers/virtio/Kconfig b/drivers/virtio/Kconfig index 078615cf2afc..29896374bf1b 100644 --- a/drivers/virtio/Kconfig +++ b/drivers/virtio/Kconfig @@ -29,17 +29,17 @@ config VIRTIO_PCI_LEGACY default y depends on VIRTIO_PCI ---help--- - Virtio PCI Card 0.9.X Draft (circa 2014) and older device support. + Virtio PCI Card 0.9.X Draft (circa 2014) and older device support. This option enables building a transitional driver, supporting both devices conforming to Virtio 1 specification, and legacy devices. If disabled, you get a slightly smaller, non-transitional driver, with no legacy compatibility. - So look out into your driveway. Do you have a flying car? If - so, you can happily disable this option and virtio will not - break. Otherwise, leave it set. Unless you're testing what - life will be like in The Future. + So look out into your driveway. Do you have a flying car? If + so, you can happily disable this option and virtio will not + break. Otherwise, leave it set. Unless you're testing what + life will be like in The Future. If unsure, say Y. diff --git a/drivers/w1/slaves/Kconfig b/drivers/w1/slaves/Kconfig index ebed495b9e69..035de04710d1 100644 --- a/drivers/w1/slaves/Kconfig +++ b/drivers/w1/slaves/Kconfig @@ -71,8 +71,8 @@ config W1_SLAVE_DS2805 help Say Y here if you want to use a 1-wire is a 112-byte user-programmable EEPROM is - organized as 7 pages of 16 bytes each with 64bit - unique number. Requires OverDrive Speed to talk to. + organized as 7 pages of 16 bytes each with 64bit + unique number. Requires OverDrive Speed to talk to. config W1_SLAVE_DS2431 tristate "1kb EEPROM family support (DS2431)" diff --git a/drivers/xen/Kconfig b/drivers/xen/Kconfig index 79cc75096f42..d8c9bba57cae 100644 --- a/drivers/xen/Kconfig +++ b/drivers/xen/Kconfig @@ -110,12 +110,12 @@ config XEN_COMPAT_XENFS depends on XENFS default y help - The old xenstore userspace tools expect to find "xenbus" - under /proc/xen, but "xenbus" is now found at the root of the - xenfs filesystem. Selecting this causes the kernel to create - the compatibility mount point /proc/xen if it is running on - a xen platform. - If in doubt, say yes. + The old xenstore userspace tools expect to find "xenbus" + under /proc/xen, but "xenbus" is now found at the root of the + xenfs filesystem. Selecting this causes the kernel to create + the compatibility mount point /proc/xen if it is running on + a xen platform. + If in doubt, say yes. config XEN_SYS_HYPERVISOR bool "Create xen entries under /sys/hypervisor" @@ -123,7 +123,7 @@ config XEN_SYS_HYPERVISOR select SYS_HYPERVISOR default y help - Create entries under /sys/hypervisor describing the Xen + Create entries under /sys/hypervisor describing the Xen hypervisor environment. When running native or in another virtual environment, /sys/hypervisor will still be present, but will have no xen contents. @@ -270,7 +270,7 @@ config XEN_ACPI_PROCESSOR depends on XEN && XEN_DOM0 && X86 && ACPI_PROCESSOR && CPU_FREQ default m help - This ACPI processor uploads Power Management information to the Xen + This ACPI processor uploads Power Management information to the Xen hypervisor. To do that the driver parses the Power Management data and uploads @@ -279,7 +279,7 @@ config XEN_ACPI_PROCESSOR SMM so that other drivers (such as ACPI cpufreq scaling driver) will not load. - To compile this driver as a module, choose M here: the module will be + To compile this driver as a module, choose M here: the module will be called xen_acpi_processor If you do not know what to choose, select M here. If the CPUFREQ drivers are built in, select Y here. @@ -312,8 +312,8 @@ config XEN_SYMS depends on X86 && XEN_DOM0 && XENFS default y if KALLSYMS help - Exports hypervisor symbols (along with their types and addresses) via - /proc/xen/xensyms file, similar to /proc/kallsyms + Exports hypervisor symbols (along with their types and addresses) via + /proc/xen/xensyms file, similar to /proc/kallsyms config XEN_HAVE_VPMU bool -- 2.17.1 [View Less]

2 3

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel October 2019