/linux/drivers/gpu/drm/omapdrm/dss/ |
H A D | hdmi4_core.c | 549 r = FLD_MOD(r, cfg->i2s_cfg.justification, 2, 2); in hdmi_core_audio_config() 656 acore.i2s_cfg.justification = HDMI_AUDIO_JUSTIFY_LEFT; in hdmi4_audio_config() 658 acore.i2s_cfg.justification = HDMI_AUDIO_JUSTIFY_RIGHT; in hdmi4_audio_config() 790 audio_format.justification = HDMI_AUDIO_JUSTIFY_LEFT; in hdmi4_audio_config() 794 audio_format.justification = HDMI_AUDIO_JUSTIFY_RIGHT; in hdmi4_audio_config()
|
H A D | hdmi.h | 186 enum hdmi_audio_justify justification; member 202 u8 justification; member
|
H A D | hdmi_wp.c | 239 r = FLD_MOD(r, aud_fmt->justification, 3, 3); in hdmi_wp_audio_config_format()
|
H A D | hdmi5_core.c | 848 audio_format.justification = HDMI_AUDIO_JUSTIFY_LEFT; in hdmi5_audio_config()
|
/linux/drivers/video/fbdev/omap2/omapfb/dss/ |
H A D | hdmi4_core.c | 593 r = FLD_MOD(r, cfg->i2s_cfg.justification, 2, 2); in hdmi_core_audio_config() 700 acore.i2s_cfg.justification = HDMI_AUDIO_JUSTIFY_LEFT; in hdmi4_audio_config() 702 acore.i2s_cfg.justification = HDMI_AUDIO_JUSTIFY_RIGHT; in hdmi4_audio_config() 834 audio_format.justification = HDMI_AUDIO_JUSTIFY_LEFT; in hdmi4_audio_config() 838 audio_format.justification = HDMI_AUDIO_JUSTIFY_RIGHT; in hdmi4_audio_config()
|
H A D | hdmi.h | 182 enum hdmi_audio_justify justification; member 198 u8 justification; member
|
H A D | hdmi_wp.c | 219 r = FLD_MOD(r, aud_fmt->justification, 3, 3); in hdmi_wp_audio_config_format()
|
/linux/Documentation/filesystems/nfs/ |
H A D | pnfs.rst | 40 justification, but seems reasonable given that we can have multiple
|
/linux/arch/arm/boot/dts/xilinx/ |
H A D | zynq-zc706.dts | 95 adi,input-justification = "evenly";
|
H A D | zynq-zc702.dts | 147 adi,input-justification = "right";
|
/linux/Documentation/maintainer/ |
H A D | maintainer-entry-profile.rst | 65 the NEXT+1 merge window, or should come with sufficient justification
|
/linux/include/linux/ |
H A D | string.h | 395 #define unsafe_memcpy(dst, src, bytes, justification) \ argument
|
H A D | fortify-string.h | 142 #define unsafe_memcpy(dst, src, bytes, justification) \ argument
|
/linux/Documentation/process/ |
H A D | volatile-considered-harmful.rst | 105 they come with a justification which shows that the concurrency issues have
|
H A D | 4.Coding.rst | 415 justification is solid. Note that the Coccinelle tool can help with
|
H A D | howto.rst | 439 - requests for justification
|
H A D | coding-style.rst | 1228 good justification.
|
/linux/Documentation/spi/ |
H A D | spidev.rst | 136 which will return (RD) or assign (WR) the bit justification used to
|
/linux/Documentation/bpf/ |
H A D | kfuncs.rst | 421 kfunc without having a reasonable justification. Whether or not they'll choose 460 justification, but it is a possibility that must be accepted if one is to
|
/linux/Documentation/doc-guide/ |
H A D | sphinx.rst | 332 and should be avoided in the absence of a strong justification for their
|
/linux/Documentation/virt/kvm/x86/ |
H A D | timekeeping.rst | 498 cause similar problems to virtualization makes it a good justification for
|
/linux/Documentation/RCU/Design/Requirements/ |
H A D | Requirements.rst | 640 comes up with a good justification for a particular conditional RCU 646 guarantee. Therefore, the justification for adding a conditional
|
/linux/Documentation/RCU/ |
H A D | RTFP.txt | 40 theoretical justification for use of stale data.
|