* Suggestion:S3C64XX and next-S3C MFC need IOCTL_MFC_RESET ?
@ 2009-11-06 7:51 tommy
0 siblings, 0 replies; 3+ messages in thread
From: tommy @ 2009-11-06 7:51 UTC (permalink / raw)
To: linux-arm-kernel
hi,emailist!
I think S3C64XX and next-s3c MFC driver need IOCTL_MFC_RESET,because
if APP unlegal exit mfc operation or MFC met some uncorrect
h264/mpeg4/vc1/wmv9 media stream,can cause MFC inter unit become
uncorrect state,it need RESET to recover to work for next!When under
that uncorrect condition,APP must use ioctl_MFC_RESET to recover!
i have test it ,also OK even met uncorrect stream and unlegal app file
descriptor exit !
patch may be similiar as following:
/*For MFC RESET,when met uncorrect stram or unlegal file
descriptor exit ,for APP engineer*/
case IOCTL_MFC_RESET:
MFC_Mutex_Lock();
MFC_HW_Init(); /*RESET MFC,download
firmware ,reset mfc busy flag*/
MFC_Mutex_Release();
break;
Tommy at China
^ permalink raw reply [flat|nested] 3+ messages in thread* Suggestion:S3C64XX and next-S3C MFC need IOCTL_MFC_RESET ?
@ 2009-11-06 7:45 tommy.hong
0 siblings, 0 replies; 3+ messages in thread
From: tommy.hong @ 2009-11-06 7:45 UTC (permalink / raw)
To: linux-arm-kernel
hi,emailist!
I think S3C64XX and next-s3c MFC driver need IOCTL_MFC_RESET,because if APP unlegal exit mfc operation or MFC met some uncorrect h264/mpeg4/vc1/wmv9 media stream,can cause MFC inter unit become uncorrect state,it need RESET to recover to work for next!When under that uncorrect condition,APP must use ioctl_MFC_RESET to recover!
i have test it ,also OK even met uncorrect stream and unlegal app file descriptor exit !
patch may be similiar as following:
/*For MFC RESET,when met uncorrect stram or unlegal file descriptor exit ,for APP engineer*/
case IOCTL_MFC_RESET:
MFC_Mutex_Lock();
MFC_HW_Init(); /*RESET MFC,download firmware ,reset mfc busy flag*/
MFC_Mutex_Release();
break;
Tommy
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20091106/a25464f4/attachment-0001.htm>
^ permalink raw reply [flat|nested] 3+ messages in thread* Suggestion:S3C64XX and next-S3C MFC need IOCTL_MFC_RESET ?
@ 2009-11-06 3:26 tommy tommy
0 siblings, 0 replies; 3+ messages in thread
From: tommy tommy @ 2009-11-06 3:26 UTC (permalink / raw)
To: linux-arm-kernel
hi,emailist!
I think S3C64XX and next-s3c MFC driver need IOCTL_MFC_RESET,because if
APP unlegal exit mfc operation or MFC met some uncorrect h264/mpeg4/vc1/wmv9
media stream,can cause MFC inter unit become uncorrect state,it need RESET
to recover to work for next!When under that uncorrect condition,APP must use
ioctl_MFC_RESET to recover!
i have test it ,also OK even met uncorrect stream and unlegal app file
descriptor exit !
patch may be similiar as following:
/*For MFC RESET,when met uncorrect stram or unlegal file
descriptor exit ,for APP engineer*/
case IOCTL_MFC_RESET:
MFC_Mutex_Lock();
MFC_HW_Init(); /*RESET MFC,download firmware ,reset
mfc busy flag*/
MFC_Mutex_Release();
break;
Tommy at China
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20091106/0fe0973d/attachment-0001.htm>
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2009-11-06 7:51 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-11-06 7:51 Suggestion:S3C64XX and next-S3C MFC need IOCTL_MFC_RESET ? tommy
-- strict thread matches above, loose matches on Subject: below --
2009-11-06 7:45 tommy.hong
2009-11-06 3:26 tommy tommy
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox