Re: ivtv: use arch_phys_wc_add() and require PAT disabled

> On Mar 11, 2018, at 12:51 PM, Nick French wrote: > > On Sat, Mar 10, 2018 at 10:20:23AM -0800, Andy Lutomirski wrote: Perhaps the easy answer is to change the fatal is-pat-enabled check to just a warning like "you have PAT enabled, so wc is disabled for the

Re: ivtv: use arch_phys_wc_add() and require PAT disabled

On Sat, Mar 10, 2018 at 10:20:23AM -0800, Andy Lutomirski wrote: >>> Perhaps the easy answer is to change the fatal is-pat-enabled check to just >>> a warning like "you have PAT enabled, so wc is disabled for the framebuffer. >>> if you want wc, use the nopat parameter"? >> >> I like this idea

Re: [PATCH 5/5] media: MAINTAINERS: Add entry for Aptina MT9T112

Hi Jacopo, On Fri, Mar 02, 2018 at 05:35:41PM +0100, Jacopo Mondi wrote: > Add entry for Aptina/Micron MT9T112 camera sensor. The driver is > currently orphaned. > > Signed-off-by: Jacopo Mondi > --- > MAINTAINERS | 7 +++ > 1 file changed, 7 insertions(+) > >

Re: [RFCv4,19/21] media: vim2m: add request support

Hello, On 07.03.2018 19:37, Paul Kocialkowski wrote: > Hi, > > First off, I'd like to take the occasion to say thank-you for your work. > This is a major piece of plumbing that is required for me to add support > for the Allwinner CedarX VPU hardware in upstream Linux. Other drivers, > such as

Re: ivtv: use arch_phys_wc_add() and require PAT disabled

On Sat, 10 Mar 2018 16:57:41 + "French, Nicholas A." wrote: > > > No what if the framebuffer driver is just requested as a > > > secondary step after firmware loading? > > > > Its a possibility. The decoder firmware gets loaded at the > > beginning of the decoder memory range

Re: ivtv: use arch_phys_wc_add() and require PAT disabled

On Sun, Mar 11, 2018 at 01:19:03PM -0700, Andy Lutomirski wrote: > From memory, I see two potentially reasonable real fixes. One is to find a > way to punch a hole in an ioremap. > So you’d find the framebuffer, remove it from theproblematic mapping, and > then make a new mapping. > The second

[PATCH v2] media: ivtv: add parameter to enable ivtvfb on x86 PAT systems

ivtvfb was previously disabled for x86 PAT-enabled systems by commit 1bf1735b4780 ("x86/mm/pat, drivers/media/ivtv: Use arch_phys_wc_add() and require PAT disabled") as a workaround to abstract MTRR code away from device drivers. The driver is not easily upgradable to the PAT-aware ioremap_wc()

RE: [PATCH v7] media: imx258: Add imx258 camera sensor driver

Dear all, Please kindly check this v7. I noticed many incorrect line breaks again in this mail which was not identical to the original patch. Not sure how it was resulted. Such as -- Add one more resolution for 1048x780, used for VGA streaming "\n" since v6: -- improved i2c read/write function

Re: cron job: media_tree daily build: ERRORS

Hi! Sorry, my fault! Will fix that soon. BR, Jasmin On 03/11/2018 05:36 AM, Hans Verkuil wrote: > This message is generated daily by a cron job that builds media_tree for > the kernels and architectures in the list below. > > Results of the daily build of media_tree: > > date:

[PATCH] media: ov5640: add missing output pixel format setting

The output pixel format changed by set_fmt() pad operation is not correctly applied. It is intended to be restored by calling ov5640_set_framefmt() when the video stream is started. However, when the device is powered on by s_power subdev operation before the video stream is started, the current

[PATCH v7] media: imx258: Add imx258 camera sensor driver

Add a V4L2 sub-device driver for the Sony IMX258 image sensor. This is a camera sensor using the I2C bus for control and the CSI-2 bus for data. Signed-off-by: Jason Chen Signed-off-by: Alan Chiang --- since v2: -- Update the streaming function

RE: [PATCH v6] media: imx258: Add imx258 camera sensor driver

Okay. All comments are addressed in v7. (https://patchwork.linuxtv.org/patch/47869/) Thanks for all the comments and suggestions. Regards, Andy -Original Message- From: Tomasz Figa [mailto:tf...@chromium.org] Sent: Friday, March 2, 2018 11:44 PM To: Yeh, Andy Cc:

Re: [PATCH] media: rc: meson-ir: add timeout on idle

Hi Matthias, On Sat, Mar 10, 2018 at 06:38:28PM +0100, Matthias Reichl wrote: > On Sat, Mar 10, 2018 at 11:27:45AM +, Sean Young wrote: > > So if the timeout is below N then you will never get a space of N or larger; > > the largest space I know of in an IR message is 40ms in the sanyo

Re: ivtv: use arch_phys_wc_add() and require PAT disabled

On Sun, Mar 11, 2018 at 11:24:38PM +, Ian Armstrong wrote: > On Sat, 10 Mar 2018 16:57:41 + > "French, Nicholas A." wrote: > > > > > No what if the framebuffer driver is just requested as a > > > > secondary step after firmware loading? > > > > > > Its a possibility. The

[PATCH v6-1,15/17] arm64: dts: rockchip: add isp0 node for rk3399

rk3399 have two ISP, but we havn't test isp1, so just add isp0 at present. Signed-off-by: Shunqian Zheng Signed-off-by: Jacob Chen --- arch/arm64/boot/dts/rockchip/rk3399.dtsi | 18 ++ 1 file changed, 18 insertions(+) diff

cron job: media_tree daily build: ERRORS

This message is generated daily by a cron job that builds media_tree for the kernels and architectures in the list below. Results of the daily build of media_tree: date: Mon Mar 12 05:00:11 CET 2018 media-tree git hash:e68854a2588a923b31eebce348f8020374843f8e media_build

[PATCH] [media] mceusb: add IR learning support features (IR carrier frequency measurement and wide-band/short range receiver)

Windows Media Center IR transceivers include two IR receivers; wide-band/short-range and narrow-band/long-range. The short-range (5cm distance) receiver is for IR learning and has IR carrier frequency measuring ability. Add mceusb driver support to select the short range IR receiver and enable