The irq for PWM v1-v3 used to be exclusively associated with oneshot
mode, but capture mode also needs interrupt, which does not depend on
CONFIG_PWM_ROCKCHIP_ONESHOT.
Change-Id: Iaf0e01ec7c5d02d2d379776cba41841d59c46d20
Signed-off-by: Damon Ding <damon.ding@rock-chips.com>
Although the previous patch helps to avoid display flashing during
the uboot/kernel logo switching, it forgot to set the
&rockchip_tve.tv_format in &drm_encoder_helper_funcs.mode_set()
which is needed in later &drm_encoder_helper_funcs.enable() process.
Fixes: e3b31a037d ("drm/rockchip: tve: add .loader_protect() support for tve")
Change-Id: Ib4e81f0c9ab64c1c2db9bd19209a6f108cae70e9
Signed-off-by: Damon Ding <damon.ding@rock-chips.com>
The f_uvc code includes an interrupt endpoint against the VideoControl
interface. According to section 2.4.2 of the UVC specification however
this endpoint is optional in at least some cases:
"This endpoint is optional, but may be mandatory under certain
conditions"
The conditions enumerated are whether...
1. The device supports hardware triggers
2. The device implements any AutoUpdate controls
3. The device implements any Asynchronous controls
As all of those things are implementation dependent, this endpoint
might be unnecessary for some users. Further to that it is unusable
in the current implementation as there is no mechanism within the
UVC gadget driver that allows data to be sent over that endpoint.
Disable the interrupt endpoint by default, but check whether the
user has asked for it to be enabled in configfs and continue to
generate it if so.
Change-Id: If7389f94d406d0c6f79229afbe9b63bee80ca74e
Signed-off-by: Daniel Scally <dan.scally@ideasonboard.com>
Link: https://lore.kernel.org/r/20230130105045.120886-4-dan.scally@ideasonboard.com
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Signed-off-by: William Wu <william.wu@rock-chips.com>
(cherry picked from commit 130c4dcbe8)
The f_uvc code defines an endpoint named "uvc_control_ep" but it
is configured with a non-zero endpoint address and has its
bmAttributes flagged as USB_ENDPOINT_XFER_INT - this cannot be the
VideoControl interface's control endpoint, as the default endpoint
0 is used for that purpose. This is instead the optional interrupt
endpoint that can be contained by a VideoControl interface. There
is also a Class-specific VC Interrupt Endpoint Descriptor and a
SuperSpeed companion descriptor that are also for the VC interface's
interrupt endpoint but are named as though they are for the control
endpoint.
Rename the variables to make that clear.
Change-Id: Iee00e91954dcd67fbec867e067c7e528bfb2c217
Signed-off-by: Daniel Scally <dan.scally@ideasonboard.com>
Link: https://lore.kernel.org/r/20230130105045.120886-2-dan.scally@ideasonboard.com
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Signed-off-by: William Wu <william.wu@rock-chips.com>
(cherry picked from commit 3078212caf)
drivers/input/touchscreen/gsl_point_id.c:2187:6: warning: no previous prototype for 'gsl_ReportPressure' [-Wmissing-prototypes]
drivers/input/touchscreen/gsl_point_id.c:2209:6: warning: no previous prototype for 'gsl_TouchNear' [-Wmissing-prototypes]
drivers/input/touchscreen/gsl_point_id.c:2317:6: warning: no previous prototype for 'gsl_DataInit' [-Wmissing-prototypes]
drivers/input/touchscreen/gsl_point_id.c:2595:14: warning: no previous prototype for 'gsl_version_id' [-Wmissing-prototypes]
drivers/input/touchscreen/gsl_point_id.c:2601:14: warning: no previous prototype for 'gsl_mask_tiaoping' [-Wmissing-prototypes]
drivers/input/touchscreen/gsl_point_id.c:2647:6: warning: no previous prototype for 'gsl_alg_id_main' [-Wmissing-prototypes]
drivers/input/touchscreen/gsl_point_id.c:2697:5: warning: no previous prototype for 'gsl_obtain_gesture' [-Wmissing-prototypes]
drivers/input/touchscreen/gsl_point_id.c:3001:6: warning: no previous prototype for 'gsl_GestureExtern' [-Wmissing-prototypes]
drivers/input/touchscreen/gsl_point_id.c:3076:14: warning: no previous prototype for 'gsl_GestureBuffer' [-Wmissing-prototypes]
drivers/input/touchscreen/gsl_point_id.c:549:5: warning: no previous prototype for 'abs' [-Wmissing-prototypes]
Signed-off-by: Tao Huang <huangtao@rock-chips.com>
Change-Id: I85aba64c02e93734df77e806b96f264bf91e244b
drivers/input/touchscreen/gt1x/gt1x_tools.c:104:6: warning: no previous prototype for gt1x_deinit_tool_nodeâ [-Wmissing-prototypes]
drivers/input/touchscreen/gt1x/gt1x_tools.c:79:5: warning: no previous prototype for gt1x_init_tool_nodeâ [-Wmissing-prototypes]
drivers/input/touchscreen/gt1x/gt1x_update.c:199:5: warning: no previous prototype for gt1x_i2c_write_with_readbackâ [-Wmissing-prototypes]
drivers/input/touchscreen/gt1x/gt1x_update.c:218:5: warning: no previous prototype for getUintâ [-Wmissing-prototypes]
drivers/input/touchscreen/gt1x/gt1x_update.c:750:5: warning: no previous prototype for __gt1x_hold_ss51_dsp_20â [-Wmissing-prototypes]
Signed-off-by: Tao Huang <huangtao@rock-chips.com>
Change-Id: Ic689a12dd469e7a4a6f306cbbad065903cf90891
drivers/mtd/spi-nor/core.c:736:5: warning: no previous prototype for ‘spi_nor_wait_till_ready_with_msleep’ [-Wmissing-prototypes]
Fixes a7b3870670 ("mtd: spi-nor: core: Change to use msleep for erase ops")
Change-Id: If2add4f5614f5337b5bd872db8a1b5149b7c4221
Signed-off-by: Jon Lin <jon.lin@rock-chips.com>
HDMI avmute is sent via GCP. If HDMI want to use
the avmute function, GCP must be sent.
Change-Id: Id844ea93c5296e1a5cf200f9ccf7bd2effd13e82
Signed-off-by: Algea Cao <algea.cao@rock-chips.com>
Set to the minimum value of the vcom voltage to make the regulator
happy.
Change-Id: I32d7c52eda3ee7c40047d2dd7630f3d9303323e7
Signed-off-by: Chaoyi Chen <chaoyi.chen@rock-chips.com>
error state may lead to reduce fps with offline camera when used dual camera
Signed-off-by: Zefa Chen <zefa.chen@rock-chips.com>
Change-Id: Ie45039ac7ff7ab65d02acde7aad0b6789f793738
If the value of covert_mode and csc_coef not initialize, the
compile will assign a default value which may be different by
different compiles. It should initialize their default value
explicitly before use.
Fixes: c08d820f80 ("drm/rockchip: vop2: Support post csc color range convert")
Change-Id: I39be672d6f8fda8fdf8298eafe140f449da32e46
Signed-off-by: Zhang Yubing <yubing.zhang@rock-chips.com>
1. Ensure that the PKA and ECC modules can be switched over.
2. Improve the security of verify to prevent all zeros from
being treated as the correct result in some exceptions.
Signed-off-by: Lin Jinhan <troy.lin@rock-chips.com>
Change-Id: If7cdc418cb3285fa7fb905381bfea51587750ee5
The regs overlay_mode/dclk_ddr/rgb_dclk_pol are unsupported, so
it is better to remove them.
Change-Id: I2f48b15c0bfc58eca6e21b7ec1a64724ecc0e359
Signed-off-by: Damon Ding <damon.ding@rock-chips.com>
Use SNDRV_PCM_RATE_CONTINUOUS to support continuous range
sample rate, which can support any rate in range.
e.g.
48048, 31000, 768000
SNDRV_PCM_RATE_CONTINUOUS
means the hardware supports all rates in a specific interval.
Sample rates are only restricted by the capabilities of the
clock driver, so use SNDRV_PCM_RATE_CONTINUOUS instead of
SNDRV_PCM_RATE_8000_384000.
Signed-off-by: Sugar Zhang <sugar.zhang@rock-chips.com>
Change-Id: I4811ca8ea63ed72da8cd06e9e8bbd5f450683165
Use SNDRV_PCM_RATE_CONTINUOUS to support continuous range
sample rate, which can support any rate in range.
e.g.
48048, 31000, 768000
SNDRV_PCM_RATE_CONTINUOUS
means the hardware supports all rates in a specific interval.
Sample rates are only restricted by the capabilities of the
clock driver, so use SNDRV_PCM_RATE_CONTINUOUS instead of
SNDRV_PCM_RATE_8000_384000.
Signed-off-by: Sugar Zhang <sugar.zhang@rock-chips.com>
Change-Id: Ieeea4f9ae414f2fa6475fa5f6559162e15c688c9
Use SNDRV_PCM_RATE_CONTINUOUS to support continuous range
sample rate, which can support any rate in range.
e.g.
48048, 31000, 768000
SNDRV_PCM_RATE_CONTINUOUS
means the hardware supports all rates in a specific interval.
Sample rates are only restricted by the capabilities of the
clock driver, so use SNDRV_PCM_RATE_CONTINUOUS instead of
SNDRV_PCM_RATE_8000_384000.
Signed-off-by: Sugar Zhang <sugar.zhang@rock-chips.com>
Change-Id: Iac49752b7919bc74ddcc89b53d34a6a5a96ea134
Use SNDRV_PCM_RATE_CONTINUOUS to support continuous range
sample rate, which can support any rate in range.
e.g.
48048, 31000, 768000
SNDRV_PCM_RATE_CONTINUOUS
means the hardware supports all rates in a specific interval.
Sample rates are only restricted by the capabilities of the
clock driver, so use SNDRV_PCM_RATE_CONTINUOUS instead of
SNDRV_PCM_RATE_8000_384000.
Signed-off-by: Sugar Zhang <sugar.zhang@rock-chips.com>
Change-Id: Ibff0ad918599a18ef29782ff379095996627d7be
