Re: [PATCH v3 00/27] kill devm_ioremap_nocache

Hi Christophe ， On 2018/1/4 16:05, Christophe LEROY wrote: > > > Le 25/12/2017 à 02:34, Yisheng Xie a écrit : >> >> >> On 2017/12/24 17:05, christophe leroy wrote: >>> >>> >>> Le 23/12/2017 à 14:48, Greg KH a écrit : >>>> On Sat,

Re: [PATCH v3 00/27] kill devm_ioremap_nocache

+ cris/ia64/mn10300/openrisc maintainers On 2017/12/25 9:09, Yisheng Xie wrote: > hi Christophe and Greg, > > On 2017/12/24 16:55, christophe leroy wrote: >> >> >> Le 23/12/2017 à 16:57, Guenter Roeck a écrit : >>> On 12/23/2017 05:48 AM, Greg KH wrote: >

Re: [PATCH v3 27/27] devres: kill devm_ioremap_nocache

On 2017/12/23 21:45, Greg KH wrote: > On Sat, Dec 23, 2017 at 07:02:59PM +0800, Yisheng Xie wrote: >> --- a/lib/devres.c >> +++ b/lib/devres.c >> @@ -44,35 +44,6 @@ void __iomem *devm_ioremap(struct device *dev, >> resource_size_t offset, >

Re: [PATCH v3 00/27] kill devm_ioremap_nocache

On 2017/12/24 17:05, christophe leroy wrote: > > > Le 23/12/2017 à 14:48, Greg KH a écrit : >> On Sat, Dec 23, 2017 at 06:55:25PM +0800, Yisheng Xie wrote: >>> Hi all, >>> >>> When I tried to use devm_ioremap function and review related code, I found

Re: [PATCH v3 00/27] kill devm_ioremap_nocache

hi Christophe and Greg, On 2017/12/24 16:55, christophe leroy wrote: > > > Le 23/12/2017 à 16:57, Guenter Roeck a écrit : >> On 12/23/2017 05:48 AM, Greg KH wrote: >>> On Sat, Dec 23, 2017 at 06:55:25PM +0800, Yisheng Xie wrote: >>>> Hi all, >>>>

[PATCH v3 27/27] devres: kill devm_ioremap_nocache

Now, nobody use devm_ioremap_nocache anymore, can it can just be removed. After this patch the size of devres.o will be reduced from 20304 bytes to 18992 bytes. Suggested-by: Greg KH Signed-off-by: Yisheng Xie --- Documentation/driver-model/devres.txt | 1 - include/linux/io.h

[PATCH v3 05/27] media: replace devm_ioremap_nocache with devm_ioremap

devm_ioremap_nocache. Cc: Mauro Carvalho Chehab Cc: linux-media@vger.kernel.org Signed-off-by: Yisheng Xie --- drivers/media/platform/tegra-cec/tegra_cec.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/media/platform/tegra-cec/tegra_cec.c b/drivers/media/platform

[PATCH v3 00/27] kill devm_ioremap_nocache

kill devm_ioremap_nocache for no need to keep a macro around for the duplicate thing. So here comes v3 and please help to review. Thanks so much! Yisheng Xie [1] https://lkml.org/lkml/2017/11/20/135 [2] https://lkml.org/lkml/2017/11/25/21 Yisheng Xie (27): ASOC: replace devm_ioremap_nocache

[PATCH v1] [media] uvcvideo: mark buffer error where overflow

Some cameras post inaccurate frame where next frame data overlap it. this results in screen flicker, and it need to be prevented. So this patch marks the buffer error to discard the frame where buffer overflow. Signed-off-by: Baoyou Xie --- drivers/media/usb/uvc/uvc_video.c | 1 + 1 file

[PATCH v1] [media] uvcvideo: mark buffer error where overflow

Some cameras post inaccurate frame where next frame data overlap it. this results in screen flicker, and it need to be prevented. So this patch marks the buffer error to discard the frame where buffer overflow. Signed-off-by: Baoyou Xie --- drivers/media/usb/uvc/uvc_video.c | 1 + 1 file

[PATCH] [media] coda: add missing header dependencies

pendencies. Signed-off-by: Baoyou Xie --- drivers/media/platform/coda/coda-h264.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/media/platform/coda/coda-h264.c b/drivers/media/platform/coda/coda-h264.c index 456773a..6d6f555 100644 --- a/drivers/media/platform/coda/coda-h264.c +++

[PATCH] dma-buf/sw_sync: mark sync_timeline_create() static

static. So this patch marks it 'static'. Signed-off-by: Baoyou Xie --- drivers/dma-buf/sw_sync.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/dma-buf/sw_sync.c b/drivers/dma-buf/sw_sync.c index 62e8e6d..6f16c85 100644 --- a/drivers/dma-buf/sw_sync.c +++ b/

[PATCH] dma-buf/sw_sync: mark sync_timeline_create() static

static. So this patch marks it 'static'. Signed-off-by: Baoyou Xie --- drivers/dma-buf/sw_sync.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/dma-buf/sw_sync.c b/drivers/dma-buf/sw_sync.c index 62e8e6d..6f16c85 100644 --- a/drivers/dma-buf/sw_sync.c +++ b/

[PATCH] [media] coda: add missing header dependencies

We get 1 warning when building kernel with W=1: drivers/media/platform/coda/coda-h264.c:22:5: warning: no previous prototype for 'coda_h264_padding' [-Wmissing-prototypes] In fact, this function is declared in coda.h, so this patch add missing header dependencies. Signed-off-by:

[PATCH] staging: media: omap4iss: mark omap4iss_flush() static

made static. so this patch marks this function with 'static'. Signed-off-by: Baoyou Xie --- drivers/staging/media/omap4iss/iss.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/staging/media/omap4iss/iss.c b/drivers/staging/media/omap4iss/iss.c index 6ceb

I wish you good luck everyday

Just look for Matthew Porter's presentation. > > Or maintainer who is responsible for v4l2 output can help you I > guess.(but not me) > Cheers, > > Nate > > > On Thu, Jun 11, 2009 at 7:06 PM, xie wrote: > > Dear Dongsoo Nathaniel ~~ > > > > Does t

About v4l2 output interface

Dear Dongsoo Nathaniel ~~ Does the capture interface get the image and the output interface display the image ~ ? Best regards ~ -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.ker

About v4l2 output interface

Dear Dongsoo Nathaniel ~~ In the spec , I have readed this sentence : Video output devices encode stills or image sequences as analog video signal. Can you give me a function-example about output interface in real life ~~ ? Thanks ~ Best regards ~!~ -- To unsubscribe from this list: send the lin

About V4l2 overlay sequence

Dear all ~~ With your help I have implemented the preview with capture interface ~~ Now i want to implement the preview with ovelay , and my camera support s ovelay ~ Who can tell me where I can find the document about ovelay sequcence ~ ? Or does there have a standard example source code ~ ? Tha

Re: About the VIDIOC_DQBUF

t is the maximum resolution-ed image data coming from > external camera module. And whatever it is, you might have no problem > getting data through memcpy with buf.byteused size. > Cheers, > > Nate > > On Tue, Jun 9, 2009 at 11:22 AM, xie wrote: > > hi ~~ Dongsoo, Nath

Re: About the VIDIOC_DQBUF

way, I wish you luck. > Cheers, > > Nate > > > On Mon, Jun 8, 2009 at 5:02 PM, xie wrote: > > Hi Dongsoo, Nathaniel ~ > > You must be expert on V4l2 ~ Thanks very much for your help and advice > > ~!~ > > I used the MXC camera interface driver from

Re: About the VIDIOC_DQBUF

eed to implement a hal for getting the frame data and post it to top layer , so I used the memcpy simply . Am I right ~ ? Or what about your advice ? Thanks a lot ~~ 在 2009-06-08一的 15:56 +0900，Dongsoo, Nathaniel Kim写道： > Hello Xie, > > I'm not sure which camera interface driver y

About the VIDIOC_DQBUF

Dear all ~~ I have met a issue when I used the mmap method for previewing . I just used the standard code as spec to get the image data : status_t CameraHardwareProwave::V4l2Camera::v4l2CaptureMainloop() { LOG_FUNCTION_NAME int rt ; unsigned int i ; fd_set fds ;