Re: [PATCH 1/3] media: rkvdec: Fix H264 scaling list order

2020-07-17 Thread Mauro Carvalho Chehab
Em Sat, 18 Jul 2020 07:05:54 +0200 Mauro Carvalho Chehab escreveu: > From: Jonas Karlman > > The Rockchip Video Decoder driver is expecting that the values in a > scaling list are in zig-zag order and applies the inverse scanning process > to get the values in matrix order. > > Commit

[PATCH 1/3] media: rkvdec: Fix H264 scaling list order

2020-07-17 Thread Mauro Carvalho Chehab
From: Jonas Karlman The Rockchip Video Decoder driver is expecting that the values in a scaling list are in zig-zag order and applies the inverse scanning process to get the values in matrix order. Commit 0b0393d59eb4 ("media: uapi: h264: clarify expected scaling_list_4x4/8x8 order") clarified

[PATCH 2/3] media: atomisp: fix the handling of clock number

2020-07-17 Thread Mauro Carvalho Chehab
Right now, the driver is not doing the right thing to detect the clock like used by the sensor, at least on devices without the gmin's EFI vars. Add some notes at the code to explain why and skip the wrong value provided by the _DSM table. Signed-off-by: Mauro Carvalho Chehab ---

[PATCH 3/3] media: atomisp: reorganize the code under gmin_subdev_add()

2020-07-17 Thread Mauro Carvalho Chehab
The gmin_subdev_add() currently doesn't use ACPI device power management. In order to prepare for adding support for it, let's shift some things, placing the PM-related stuff at the end of the probing logic. Let's also store the current gs on a temporary var, in order to simplify the source code.

Hello 18/07/2020.

2020-07-17 Thread hi
My name is Reem Hashimy, the Emirates Minister of State and Managing Director of the United Arab Emirates (Dubai) World Expo 2020 Committee which has been postponed to run from 1 October 2021 to 31 March 2022 because of the Covid-19 pandemic.   I am writing to you to manage the funds I

Mail delivery failed: returning message to sender

2020-07-17 Thread Mail Delivery System
This message was created automatically by mail delivery software. A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed: a...@afaq-uae.com: SMTP error from remote server for RCPT TO command, host:

Re: [PATCH v4 5/9] media: staging: rkisp1: remove unecessary clocks

2020-07-17 Thread Rob Herring
On Fri, Jul 17, 2020 at 12:14 PM Helen Koike wrote: > > Hi Rob, > > Thanks for your review. > > On 7/17/20 2:49 PM, Rob Herring wrote: > > On Thu, Jul 2, 2020 at 1:13 PM Helen Koike > > wrote: > >> > >> aclk_isp_wrap is a child of aclk_isp, and hclk_isp_wrap is a child of > >> hclk_isp, thus we

Re: [PATCH v4 5/9] media: staging: rkisp1: remove unecessary clocks

2020-07-17 Thread Helen Koike
Hi Rob, Thanks for your review. On 7/17/20 2:49 PM, Rob Herring wrote: > On Thu, Jul 2, 2020 at 1:13 PM Helen Koike wrote: >> >> aclk_isp_wrap is a child of aclk_isp, and hclk_isp_wrap is a child of >> hclk_isp, thus we can remove parents from the list. > > But it looks like it is the wrap

Re: [PATCH v4 5/9] media: staging: rkisp1: remove unecessary clocks

2020-07-17 Thread Rob Herring
On Thu, Jul 2, 2020 at 1:13 PM Helen Koike wrote: > > aclk_isp_wrap is a child of aclk_isp, and hclk_isp_wrap is a child of > hclk_isp, thus we can remove parents from the list. But it looks like it is the wrap clocks you are removing. > > Also, for the isp0, we only need the ISP clock, ACLK

Re: [PATCH v4 4/9] media: staging: dt-bindings: rkisp1: fix "no reg" error in parent node

2020-07-17 Thread Rob Herring
On Thu, Jul 2, 2020 at 1:13 PM Helen Koike wrote: > > Fix the following error found with make ARCH=arm64 dt_binding_check: > > Documentation/devicetree/bindings/media/rockchip-isp1.example.dts:24.27-101.11: > Warning (unit_address_vs_reg): /example-0/parent@0: node has a unit name, but > no reg

Re: [PATCH v4 3/9] media: staging: dt-bindings: rkisp1: re-order properties

2020-07-17 Thread Rob Herring
On Thu, Jul 2, 2020 at 1:13 PM Helen Koike wrote: > > Organize properties order in dt-binbings to move it out of staging. typo > > On top: compatible, reg and interrupts. > Then alphabetical order, then properties starting with '#'. > > Signed-off-by: Helen Koike > > --- > > V2: > - this is a

Re: [PATCH v4 1/9] media: staging: dt-bindings: rkisp1: add missing required nodes

2020-07-17 Thread Rob Herring
On Thu, Jul 2, 2020 at 1:13 PM Helen Koike wrote: > > Add missing required nodes in json-schema yaml file for > Rockchip ISP1 dt-bindings. > > Signed-off-by: Helen Koike > --- > > Changes in v2: > - New patch in the series > --- > .../devicetree/bindings/media/rockchip-isp1.yaml | 8

Re: [PATCH v4 2/9] media: staging: dt-bindings: rkisp1: add required items in i2c example

2020-07-17 Thread Rob Herring
On Thu, Jul 2, 2020 at 1:13 PM Helen Koike wrote: > > Add missing required items in Rockchip ISP1 dt-bindings example for > a complete i2c node. > > Signed-off-by: Helen Koike > --- > > Changes in v2: > - new patch in the series > --- > .../devicetree/bindings/media/rockchip-isp1.yaml

linux/drivers/staging/pi433/

2020-07-17 Thread christopher tyerman
hello Im looking for information on the pi433 driver. Who is currently maintaining the driver? as the original author appears not to have made any alterations since the original commit, and links are no longer valid. Im looking to determine what would be necessary to confirm/implement 

[PATCH] staging: rtl8192e: Fixed the space and indentation coding styles

2020-07-17 Thread Darshan D V
rtllib_crypt_ccmp.c: Fixed the error - space required before the open parenthesis '(' on line #281. rtllib_crypt_ccmp.c: Fixed the warning - suspect code indent for conditional statements on line #338 Signed-off-by: Darshan D V --- drivers/staging/rtl8192e/rtllib_crypt_ccmp.c | 4 ++-- 1 file

[PATCH 1/4] staging: comedi: ni_6527: fix INSN_CONFIG_DIGITAL_TRIG support

2020-07-17 Thread Ian Abbott
`ni6527_intr_insn_config()` processes `INSN_CONFIG` comedi instructions for the "interrupt" subdevice. When `data[0]` is `INSN_CONFIG_DIGITAL_TRIG` it is configuring the digital trigger. When `data[2]` is `COMEDI_DIGITAL_TRIG_ENABLE_EDGES` it is configuring rising and falling edge detection for

[PATCH 3/4] staging: comedi: addi_apci_1564: check INSN_CONFIG_DIGITAL_TRIG shift

2020-07-17 Thread Ian Abbott
The `INSN_CONFIG` comedi instruction with sub-instruction code `INSN_CONFIG_DIGITAL_TRIG` includes a base channel in `data[3]`. This is used as a right shift amount for other bitmask values without being checked. Shift amounts greater than or equal to 32 will result in undefined behavior. Add

[PATCH 2/4] staging: comedi: addi_apci_1032: check INSN_CONFIG_DIGITAL_TRIG shift

2020-07-17 Thread Ian Abbott
The `INSN_CONFIG` comedi instruction with sub-instruction code `INSN_CONFIG_DIGITAL_TRIG` includes a base channel in `data[3]`. This is used as a right shift amount for other bitmask values without being checked. Shift amounts greater than or equal to 32 will result in undefined behavior. Add

[PATCH 4/4] staging: comedi: addi_apci_1500: check INSN_CONFIG_DIGITAL_TRIG shift

2020-07-17 Thread Ian Abbott
The `INSN_CONFIG` comedi instruction with sub-instruction code `INSN_CONFIG_DIGITAL_TRIG` includes a base channel in `data[3]`. This is used as a right shift amount for other bitmask values without being checked. Shift amounts greater than or equal to 32 will result in undefined behavior. Add

[PATCH 0/4] staging: comedi: INSN_CONFIG_DIGITAL_TRIG fixes

2020-07-17 Thread Ian Abbott
These patches correct problems with INSN_CONFIG_DIGITAL_TRIG comedi configuration instructions in various comedi drivers, in particular the use of unconstrained bit shift amounts from userspace leading to undefined behaviour (although hopefully not the kernel crashy sort). The patches have been

Re: linux/drivers/staging/pi433/

2020-07-17 Thread Dan Carpenter
On Fri, Jul 17, 2020 at 12:11:50PM +0100, christopher tyerman wrote: > hello > > Im looking for information on the pi433 driver. Who is currently > maintaining the driver? as the original author appears not to have made > any alterations since the original commit, and links are no longer valid.

Re: linux/drivers/staging/pi433/

2020-07-17 Thread Greg KH
On Fri, Jul 17, 2020 at 12:11:50PM +0100, christopher tyerman wrote: > hello > > Im looking for information on the pi433 driver. Who is currently > maintaining the driver? as the original author appears not to have made > any alterations since the original commit, and links are no longer valid.

Greetings

2020-07-17 Thread Mr Qi zhu
Hello, Acknowledge please if you still use this e-mail. There is a heritage that has your surname. get in touch at:zhuq...@gmail.com Thanks, Qi ___ devel mailing list de...@linuxdriverproject.org

[PATCH v5] staging: comedi: comedi_fops.c: added casts to get rid of sparse warnings

2020-07-17 Thread B K Karthik
fixed sparse warnings by adding a cast in assignment from void [noderef] __user * to unsigned int __force * and a reverse cast in argument from unsigned int * to unsigned int __user * . Signed-off-by: B K Karthik Reviewed-by: Ian Abbott --- v1 -> v2: - Added a reverse cast in argument v2 ->

Re: [PATCH v4] staging: comedi: comedi_fops.c: added casts to get rid of sparse warnings

2020-07-17 Thread Greg Kroah-Hartman
On Thu, Jul 16, 2020 at 11:25:48AM -0400, B K Karthik wrote: > fixed sparse warnings by adding a cast in assignment from > void [noderef] __user * to unsigned int __force * > and a reverse cast in argument from > unsigned int * to unsigned int __user * . > > v1 -> v2: > - Add a reverse cast in

Re: [PATCH v4] staging: comedi: comedi_fops.c: added casts to get rid of sparse warnings

2020-07-17 Thread Ian Abbott
On 16/07/2020 16:25, B K Karthik wrote: fixed sparse warnings by adding a cast in assignment from void [noderef] __user * to unsigned int __force * and a reverse cast in argument from unsigned int * to unsigned int __user * . v1 -> v2: - Add a reverse cast in argument v2 -> v3: - Change commit