- 27 Nov, 2020 27 commits
-
-
Alexander A. Klimov authored
Rationale: Reduces attack surface on kernel devs opening the links for MITM as HTTPS traffic is much harder to manipulate. Deterministic algorithm: For each file: If not .svg: For each line: If doesn't contain `\bxmlns\b`: If neither `\bgnu\.org/license`, nor `\bmozilla\.org/MPL\b`: If both the HTTP and HTTPS versions return 200 OK and serve the same content: Replace HTTP with HTTPS. Signed-off-by:Alexander A. Klimov <grandmaster@al2klimov.de> Signed-off-by:
Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
-
Randy Dunlap authored
Drop the doubled word "errors". Signed-off-by:
Randy Dunlap <rdunlap@infradead.org> Cc: Jonathan Corbet <corbet@lwn.net> Cc: linux-doc@vger.kernel.org Signed-off-by:
-
Randy Dunlap authored
Drop the doubled word "device". Signed-off-by:
-
Randy Dunlap authored
Drop the doubled words "type" and "the". Signed-off-by:
-
Randy Dunlap authored
Drop the doubled word "the". Signed-off-by:
-
Randy Dunlap authored
Drop the doubled word "and". Signed-off-by:
-
Randy Dunlap authored
Drop the doubled word "and". Signed-off-by:
-
Randy Dunlap authored
Drop the doubled word "Any". Signed-off-by:
-
Randy Dunlap authored
Drop the doubled word "in". Signed-off-by:
-
Randy Dunlap authored
Drop the doubled word "controls". Signed-off-by:
-
Randy Dunlap authored
Drop the doubled word "standard.". Signed-off-by:
-
Randy Dunlap authored
Drop the doubled word "the". Signed-off-by:
-
Randy Dunlap authored
Drop the doubled word "and". Signed-off-by:
-
Randy Dunlap authored
Drop the doubled word "the". Signed-off-by:
-
Randy Dunlap authored
Drop the doubled word "and". Signed-off-by:
-
Randy Dunlap authored
Drop the doubled word "and". Signed-off-by:
-
Geert Uytterhoeven authored
The MEDIA_SUPPORT_FILTER configuration option is located inside a block protected by "#if MEDIA_SUPPORT", so there is no need to have an explicit dependency on MEDIA_SUPPORT. Drop it. Fixes: c6774ee0 ("media: Kconfig: make filtering devices optional") Signed-off-by:
Geert Uytterhoeven <geert@linux-m68k.org> Signed-off-by:
-
Sameer Puri authored
These writes to 0x162, 0x163 already appear earlier in the struct for the 1920x1080 mode and do not need to be repeated. Signed-off-by:
Sameer Puri <purisame@spuri.io> Reviewed-by:
Dave Stevenson <dave.stevenson@raspberrypi.com> Signed-off-by:
-
Colin Ian King authored
The variable err is being initialized with a value that is never read and it is being updated later with a new value. The initialization is redundant and can be removed. Addresses-Coverity: ("Unused value") Signed-off-by:Colin Ian King <colin.king@canonical.com> Signed-off-by:
-
Dan Carpenter authored
This is supposed to return negative error codes but the type is bool so it returns true instead. Fixes: b47b79d8 ("[media] media: i2c: max2175: Add MAX2175 support") Signed-off-by:
Dan Carpenter <dan.carpenter@oracle.com> Signed-off-by:
-
Dan Carpenter authored
The "seg_num," line wasn't indented. All the arguments can fit nicely on two lines. Signed-off-by:
Patrice Chotard <patrice.chotard@st.com> Signed-off-by:
-
zhong jiang authored
The kernel.h macro DIV_ROUND_CLOSEST performs the computation (x + d/2)/d but is perhaps more readable. Signed-off-by:
zhong jiang <zhongjiang@huawei.com> Signed-off-by:
-
Daniel Gomez authored
Stop video streaming when requested. When s_stream is called to stop the video streaming, if/else condition calls start_streaming function instead of the one for stopping it. Fixes: 43619059 ("media: imx214: Add imx214 camera sensor driver") Signed-off-by:
Daniel Gomez <daniel@qtec.com> Signed-off-by:
Ricardo Ribalda <ribalda@kernel.org> Signed-off-by:
-
Antti Palosaari authored
SPI bus number must be assigned dynamically for each device, otherwise it will crash when multiple devices are plugged to system. Reported-and-tested-by: syzbot+c60ddb60b685777d9d59@syzkaller.appspotmail.com Cc: stable@vger.kernel.org Signed-off-by:
Antti Palosaari <crope@iki.fi> Signed-off-by:
-
Jia-Ju Bai authored
In msi2500_stop_streaming(), there is an if statement on line 870 to check whether dev->udev is NULL: if (dev->udev) When dev->udev is NULL, it is used on line 877: msi2500_ctrl_msg(dev, CMD_STOP_STREAMING, 0) usb_control_msg(dev->udev, usb_sndctrlpipe(dev->udev, 0), ...) Thus, a possible null-pointer dereference may occur. To fix this bug, dev->udev is checked before calling msi2500_ctrl_msg(). This bug is found by a static analysis tool STCheck written by us. Signed-off-by:Jia-Ju Bai <baijiaju1990@gmail.com> Signed-off-by:
-
Nishka Dasgupta authored
Each iteration of for_each_child_of_node puts the previous node, but in the case of a goto from the middle of the loop, there is no put, thus causing a memory leak. Hence add a new label that puts the last used node, and edit the goto statements in the middle of the loop to first go to the new label. Issue found with Coccinelle. Signed-off-by:
Nishka Dasgupta <nishkadg.linux@gmail.com> Acked-by:
-
Mauro Carvalho Chehab authored
As reported on: https://lore.kernel.org/linux-media/20190627222020.45909-1-willemdebruijn.kernel@gmail.com/ if gp8psk_usb_in_op() returns an error, the status var is not initialized. Yet, this var is used later on, in order to identify: - if the device was already started; - if firmware has loaded; - if the LNBf was powered on. Using status = 0 seems to ensure that everything will be properly powered up. So, instead of the proposed solution, let's just set status = 0. Reported-by:
syzbot <syzkaller@googlegroups.com> Reported-by:
Willem de Bruijn <willemb@google.com> Signed-off-by:
-
- 26 Nov, 2020 6 commits
-
-
Sean Young authored
The rc_proto enum values should be ignored for now, otherwise we get warnings like: Documentation/output/lirc.h.rst:6: WARNING: undefined label: rc-proto-max (if the link has no caption the label must precede a section header) Reported-by:
Stephen Rothwell <sfr@canb.auug.org.au> Fixes: 72e637fe ("media: rc: validate that "rc_proto" is reasonable") Fixes: cea357bc ("media: lirc: ensure RC_PROTO_MAX has documentation") Signed-off-by:
Sean Young <sean@mess.org> Signed-off-by:
-
Christian Hewitt authored
This remote ships with the Amlogic SML-5442TW IPTV/VOD Set-Top Box used by O2.cz. This keymap adds support for the default IR controls. Signed-off-by:
Christian Hewitt <christianshewitt@gmail.com> Signed-off-by:
-
Kai Muenz authored
Hauppauge MAX S2 or WinTV NOVA HD USB2.0. Signed-off-by:
Kai Muenz <squ@tent.at> Signed-off-by:
-
Keita Suzuki authored
When dvb_create_media_graph fails, the debugfs kept inside client should be released. However, the current implementation does not release them. Fix this by adding a new goto label to call smsdvb_debugfs_release. Fixes: 0d3ab841 ("[media] dvb core: must check dvb_create_media_graph()") Signed-off-by:
Keita Suzuki <keitasuzuki.park@sslab.ics.keio.ac.jp> Signed-off-by:
-
Mauro Carvalho Chehab authored
Add documentation for enum rc_proto and struct lirc_scancode at the generated docs. Signed-off-by:
-
Mauro Carvalho Chehab authored
Make the license for those documents also compatible with GPLv2. Signed-off-by:
-
- 25 Nov, 2020 7 commits
-
-
AngeloGioacchino Del Regno authored
The SDM630/660 SoCs (and variants) have another clock source for the PHY, which must be set to a rate that's equal or greater than the CSI PHY timer clock: failing to do this will produce PHY overflows when trying to get a stream from a very high bandwidth camera sensor and outputting no frame or a partial one. Since I haven't found any usecase in which the csiX_phy clock needs to be higher than the csiXphy_timer, let's just set the same rate on both, which seems to work just perfect. Signed-off-by:
AngeloGioacchino Del Regno <kholk11@gmail.com> Reviewed-by:
Robert Foss <robert.foss@linaro.org> Signed-off-by:
Hans Verkuil <hverkuil-cisco@xs4all.nl> Signed-off-by:
-
AngeloGioacchino Del Regno authored
The CSIPHY on SDM630/660 needs a slightly longer T_HS_CLK_MISS configuration on lanes CFG4. Signed-off-by:
-
AngeloGioacchino Del Regno authored
Add support for the Qualcomm SDM630/636/660 and SDA variants' camera subsystem. These SoCs are equipped with: - 3x CSI PHY 3-Phase v1.0 (downstream csiphy-v3.5) - 4x CSID v5.0 - 2x ISPIF v3.0 - 2x VFE 4.8 As a note, this camera subsystem is very similar to the one that is found in the MSM8998/APQ8098 SoCs. Signed-off-by:
-
AngeloGioacchino Del Regno authored
Add bindings for qcom,sdm660-camss in order to support the camera subsystem on SDM630/660 and SDA variants. Signed-off-by:
Rob Herring <robh@kernel.org> Signed-off-by:
-
AngeloGioacchino Del Regno authored
Add the support for VFE 4.8 in the camss-vfe-4-7 driver, as this one really is a minor revision, requiring the very same management and basically having the same register layout as VFE 4.7, but needing a different QoS and DS configuration, using a different register to enable the wm and habing the same UB size for both instances (instead of a different size between instance 0 and 1). Signed-off-by:
-
AngeloGioacchino Del Regno authored
In preparation to add support for VFE 4.8, rename these functions by adding the vfe version that they are referred to (for example, vfe_get_ub_size -> vfe47_get_ub_size), as these are the only ones that will be different for the VFE version 4.8. Signed-off-by:
-
AngeloGioacchino Del Regno authored
Resetting the ISPIF VFE0 context is wrong if we are using the VFE1 for dual-camera or simply because a secondary camera is connected to it: in this case the reset will always happen on the VFE0 ctx of the ISPIF, which is .. useless. Fix this usecase by adding the ISPIF_RST_CMD_1 address and choose where to do the (or what to) reset based on the VFE line id. Signed-off-by:
-
