* Some questions about DRM(Direct Rendering Manager) @ 2011-06-22 4:26 ` daeinki 0 siblings, 0 replies; 13+ messages in thread From: daeinki @ 2011-06-22 4:26 UTC (permalink / raw) To: linux-arm-kernel Hi all, I'm writing Samsung SoC based DRM framework and this one includes FIMD and HDMI driver as hardware dependent modules. and for now, encoder, connector, crtc and fb module has been materialized almost. but I'm contending with framebuffer setting issue(created fb_info should be registered to linux framebuffer through register_framebuffer() or not)as default framebuffer at booting time. at drm_fb_helper_single_fb_probe() of drm_fb_helper.c file, fb_helper's fb_probe callback is called and this one creates new framebuffer and returns a value more then 0 if true. internally, this process creates an fb_info object and drm_framebuffer and then drm_framebuffer would be added to mode_config.fb_list of the drm_device. a value returned, new_fb is used to decide that it calls register_framebuffer() or drm_fb_helper_set_par(). at this point, I am confused it's a good way to call register_framebuffer() otherwise drm_fb_helper_set_par(). if register_framebuffer() is called then I guess drm_fb_helper_set_par() or drm_crtc_helper_set_config() should be called somewhere subsequently to apply this one to real hardware because previous process is just for maintaining data logically.(not set up data to h/w) it's a right way to call register_framebuffer() and then drm_fb_helper_set_par() or drm_crtc_helper_set_config()? otherwise just only drm_fb_helper_set_par() or drm_crtc_helper_set_config() ignoring register_framebuffer()? and what is the purpose of using register_framebuffer()? In my case, first, register_framebuffer() is called and then if desired default crtc id is matched with drm_fb_helper->crtc_info[0 ~ n].crtc_id, it gets mode_set of drm_fb_helper->crtc_info[n] and then it calls drm_crtc_helper_set_config(mode_set). at this time, all the hardware configurations would be completed. thank you in advance. Best Regards Inki Dae. ^ permalink raw reply [flat|nested] 13+ messages in thread
* Some questions about DRM(Direct Rendering Manager) @ 2011-06-22 4:26 ` daeinki 0 siblings, 0 replies; 13+ messages in thread From: daeinki @ 2011-06-22 4:26 UTC (permalink / raw) To: linux-arm-kernel Hi all, I'm writing Samsung SoC based DRM framework and this one includes FIMD and HDMI driver as hardware dependent modules. and for now, encoder, connector, crtc and fb module has been materialized almost. but I'm contending with framebuffer setting issue(created fb_info should be registered to linux framebuffer through register_framebuffer() or not)as default framebuffer at booting time. at drm_fb_helper_single_fb_probe() of drm_fb_helper.c file, fb_helper's fb_probe callback is called and this one creates new framebuffer and returns a value more then 0 if true. internally, this process creates an fb_info object and drm_framebuffer and then drm_framebuffer would be added to mode_config.fb_list of the drm_device. a value returned, new_fb is used to decide that it calls register_framebuffer() or drm_fb_helper_set_par(). at this point, I am confused it's a good way to call register_framebuffer() otherwise drm_fb_helper_set_par(). if register_framebuffer() is called then I guess drm_fb_helper_set_par() or drm_crtc_helper_set_config() should be called somewhere subsequently to apply this one to real hardware because previous process is just for maintaining data logically.(not set up data to h/w) it's a right way to call register_framebuffer() and then drm_fb_helper_set_par() or drm_crtc_helper_set_config()? otherwise just only drm_fb_helper_set_par() or drm_crtc_helper_set_config() ignoring register_framebuffer()? and what is the purpose of using register_framebuffer()? In my case, first, register_framebuffer() is called and then if desired default crtc id is matched with drm_fb_helper->crtc_info[0 ~ n].crtc_id, it gets mode_set of drm_fb_helper->crtc_info[n] and then it calls drm_crtc_helper_set_config(mode_set). at this time, all the hardware configurations would be completed. thank you in advance. Best Regards Inki Dae. ^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Some questions about DRM(Direct Rendering Manager) 2011-06-22 4:26 ` daeinki @ 2011-06-22 6:04 ` daeinki -1 siblings, 0 replies; 13+ messages in thread From: daeinki @ 2011-06-22 6:04 UTC (permalink / raw) To: linux-arm-kernel below is additional comments. daeinki ¾´ ±Û: > Hi all, > > I'm writing Samsung SoC based DRM framework and this one includes FIMD > and HDMI driver as hardware dependent modules. and for now, encoder, > connector, crtc and fb module has been materialized almost. but I'm > contending with framebuffer setting issue(created fb_info should be > registered to linux framebuffer through register_framebuffer() or not)as > default framebuffer at booting time. > > at drm_fb_helper_single_fb_probe() of drm_fb_helper.c file, fb_helper's > fb_probe callback is called and this one creates new framebuffer and > returns a value more then 0 if true. internally, this process creates an > fb_info object and drm_framebuffer and then drm_framebuffer would be > added to mode_config.fb_list of the drm_device. > it's my mistake. return value is 0 if true, nonzero otherwise. > a value returned, new_fb is used to decide that it calls > register_framebuffer() or drm_fb_helper_set_par(). at this point, I am > confused it's a good way to call register_framebuffer() otherwise > drm_fb_helper_set_par(). if register_framebuffer() is called then I > guess drm_fb_helper_set_par() or drm_crtc_helper_set_config() should be > called somewhere subsequently to apply this one to real hardware because > previous process is just for maintaining data logically.(not set up data > to h/w) > > it's a right way to call register_framebuffer() and then > drm_fb_helper_set_par() or drm_crtc_helper_set_config()? otherwise just > only drm_fb_helper_set_par() or drm_crtc_helper_set_config() ignoring > register_framebuffer()? and what is the purpose of using > register_framebuffer()? > I understood that if fb_probe() callback is fail then fb_info object is registered to linux framebuffer through register_framebuffer() otherwise(if true) hardware configuration would be completed by drm_fb_helper_set_par() so the reason of using register_framebuffer() is that the case of failing fb_probe() callback, it is for drawing on only linux framebuffer. is it right? > In my case, first, register_framebuffer() is called and then if desired > default crtc id is matched with drm_fb_helper->crtc_info[0 ~ n].crtc_id, > it gets mode_set of drm_fb_helper->crtc_info[n] and then it calls > drm_crtc_helper_set_config(mode_set). at this time, all the hardware > configurations would be completed. > > thank you in advance. > > Best Regards > Inki Dae. > ^ permalink raw reply [flat|nested] 13+ messages in thread
* Some questions about DRM(Direct Rendering Manager) @ 2011-06-22 6:04 ` daeinki 0 siblings, 0 replies; 13+ messages in thread From: daeinki @ 2011-06-22 6:04 UTC (permalink / raw) To: linux-arm-kernel below is additional comments. daeinki ? ?: > Hi all, > > I'm writing Samsung SoC based DRM framework and this one includes FIMD > and HDMI driver as hardware dependent modules. and for now, encoder, > connector, crtc and fb module has been materialized almost. but I'm > contending with framebuffer setting issue(created fb_info should be > registered to linux framebuffer through register_framebuffer() or not)as > default framebuffer at booting time. > > at drm_fb_helper_single_fb_probe() of drm_fb_helper.c file, fb_helper's > fb_probe callback is called and this one creates new framebuffer and > returns a value more then 0 if true. internally, this process creates an > fb_info object and drm_framebuffer and then drm_framebuffer would be > added to mode_config.fb_list of the drm_device. > it's my mistake. return value is 0 if true, nonzero otherwise. > a value returned, new_fb is used to decide that it calls > register_framebuffer() or drm_fb_helper_set_par(). at this point, I am > confused it's a good way to call register_framebuffer() otherwise > drm_fb_helper_set_par(). if register_framebuffer() is called then I > guess drm_fb_helper_set_par() or drm_crtc_helper_set_config() should be > called somewhere subsequently to apply this one to real hardware because > previous process is just for maintaining data logically.(not set up data > to h/w) > > it's a right way to call register_framebuffer() and then > drm_fb_helper_set_par() or drm_crtc_helper_set_config()? otherwise just > only drm_fb_helper_set_par() or drm_crtc_helper_set_config() ignoring > register_framebuffer()? and what is the purpose of using > register_framebuffer()? > I understood that if fb_probe() callback is fail then fb_info object is registered to linux framebuffer through register_framebuffer() otherwise(if true) hardware configuration would be completed by drm_fb_helper_set_par() so the reason of using register_framebuffer() is that the case of failing fb_probe() callback, it is for drawing on only linux framebuffer. is it right? > In my case, first, register_framebuffer() is called and then if desired > default crtc id is matched with drm_fb_helper->crtc_info[0 ~ n].crtc_id, > it gets mode_set of drm_fb_helper->crtc_info[n] and then it calls > drm_crtc_helper_set_config(mode_set). at this time, all the hardware > configurations would be completed. > > thank you in advance. > > Best Regards > Inki Dae. > ^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Some questions about DRM(Direct Rendering Manager) 2011-06-22 6:04 ` daeinki (?) @ 2011-06-22 7:50 ` InKi Dae -1 siblings, 0 replies; 13+ messages in thread From: InKi Dae @ 2011-06-22 7:50 UTC (permalink / raw) To: daeinki, dri-devel Cc: linux-fbdev, Kukjin Kim, Kyungmin Park, airlied, Paul Mundt, jesse.barnes, linux-arm-kernel It adds dri-devel@lists.freedesktop.org to this mail thread. Thank you. 2011년 6월 22일 오후 3:04, daeinki <inki.dae@samsung.com>님의 말: > below is additional comments. > > daeinki 쓴 글: >> Hi all, >> >> I'm writing Samsung SoC based DRM framework and this one includes FIMD >> and HDMI driver as hardware dependent modules. and for now, encoder, >> connector, crtc and fb module has been materialized almost. but I'm >> contending with framebuffer setting issue(created fb_info should be >> registered to linux framebuffer through register_framebuffer() or not)as >> default framebuffer at booting time. >> >> at drm_fb_helper_single_fb_probe() of drm_fb_helper.c file, fb_helper's >> fb_probe callback is called and this one creates new framebuffer and >> returns a value more then 0 if true. internally, this process creates an >> fb_info object and drm_framebuffer and then drm_framebuffer would be >> added to mode_config.fb_list of the drm_device. >> > it's my mistake. return value is 0 if true, nonzero otherwise. > >> a value returned, new_fb is used to decide that it calls >> register_framebuffer() or drm_fb_helper_set_par(). at this point, I am >> confused it's a good way to call register_framebuffer() otherwise >> drm_fb_helper_set_par(). if register_framebuffer() is called then I >> guess drm_fb_helper_set_par() or drm_crtc_helper_set_config() should be >> called somewhere subsequently to apply this one to real hardware because >> previous process is just for maintaining data logically.(not set up data >> to h/w) >> >> it's a right way to call register_framebuffer() and then >> drm_fb_helper_set_par() or drm_crtc_helper_set_config()? otherwise just >> only drm_fb_helper_set_par() or drm_crtc_helper_set_config() ignoring >> register_framebuffer()? and what is the purpose of using >> register_framebuffer()? >> > I understood that if fb_probe() callback is fail then fb_info object is > registered to linux framebuffer through register_framebuffer() > otherwise(if true) hardware configuration would be completed by > drm_fb_helper_set_par() so the reason of using register_framebuffer() is > that the case of failing fb_probe() callback, it is for drawing on only > linux framebuffer. is it right? > >> In my case, first, register_framebuffer() is called and then if desired >> default crtc id is matched with drm_fb_helper->crtc_info[0 ~ n].crtc_id, >> it gets mode_set of drm_fb_helper->crtc_info[n] and then it calls >> drm_crtc_helper_set_config(mode_set). at this time, all the hardware >> configurations would be completed. >> >> thank you in advance. >> >> Best Regards >> Inki Dae. >> > > > _______________________________________________ > linux-arm-kernel mailing list > linux-arm-kernel@lists.infradead.org > http://lists.infradead.org/mailman/listinfo/linux-arm-kernel > -- To unsubscribe from this list: send the line "unsubscribe linux-fbdev" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html ^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Some questions about DRM(Direct Rendering Manager) @ 2011-06-22 7:50 ` InKi Dae 0 siblings, 0 replies; 13+ messages in thread From: InKi Dae @ 2011-06-22 7:50 UTC (permalink / raw) To: daeinki, dri-devel Cc: linux-fbdev, Kukjin Kim, Kyungmin Park, airlied, Paul Mundt, jesse.barnes, linux-arm-kernel It adds dri-devel@lists.freedesktop.org to this mail thread. Thank you. 2011년 6월 22일 오후 3:04, daeinki <inki.dae@samsung.com>님의 말: > below is additional comments. > > daeinki 쓴 글: >> Hi all, >> >> I'm writing Samsung SoC based DRM framework and this one includes FIMD >> and HDMI driver as hardware dependent modules. and for now, encoder, >> connector, crtc and fb module has been materialized almost. but I'm >> contending with framebuffer setting issue(created fb_info should be >> registered to linux framebuffer through register_framebuffer() or not)as >> default framebuffer at booting time. >> >> at drm_fb_helper_single_fb_probe() of drm_fb_helper.c file, fb_helper's >> fb_probe callback is called and this one creates new framebuffer and >> returns a value more then 0 if true. internally, this process creates an >> fb_info object and drm_framebuffer and then drm_framebuffer would be >> added to mode_config.fb_list of the drm_device. >> > it's my mistake. return value is 0 if true, nonzero otherwise. > >> a value returned, new_fb is used to decide that it calls >> register_framebuffer() or drm_fb_helper_set_par(). at this point, I am >> confused it's a good way to call register_framebuffer() otherwise >> drm_fb_helper_set_par(). if register_framebuffer() is called then I >> guess drm_fb_helper_set_par() or drm_crtc_helper_set_config() should be >> called somewhere subsequently to apply this one to real hardware because >> previous process is just for maintaining data logically.(not set up data >> to h/w) >> >> it's a right way to call register_framebuffer() and then >> drm_fb_helper_set_par() or drm_crtc_helper_set_config()? otherwise just >> only drm_fb_helper_set_par() or drm_crtc_helper_set_config() ignoring >> register_framebuffer()? and what is the purpose of using >> register_framebuffer()? >> > I understood that if fb_probe() callback is fail then fb_info object is > registered to linux framebuffer through register_framebuffer() > otherwise(if true) hardware configuration would be completed by > drm_fb_helper_set_par() so the reason of using register_framebuffer() is > that the case of failing fb_probe() callback, it is for drawing on only > linux framebuffer. is it right? > >> In my case, first, register_framebuffer() is called and then if desired >> default crtc id is matched with drm_fb_helper->crtc_info[0 ~ n].crtc_id, >> it gets mode_set of drm_fb_helper->crtc_info[n] and then it calls >> drm_crtc_helper_set_config(mode_set). at this time, all the hardware >> configurations would be completed. >> >> thank you in advance. >> >> Best Regards >> Inki Dae. >> > > > _______________________________________________ > linux-arm-kernel mailing list > linux-arm-kernel@lists.infradead.org > http://lists.infradead.org/mailman/listinfo/linux-arm-kernel > _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel ^ permalink raw reply [flat|nested] 13+ messages in thread
* Some questions about DRM(Direct Rendering Manager) @ 2011-06-22 7:50 ` InKi Dae 0 siblings, 0 replies; 13+ messages in thread From: InKi Dae @ 2011-06-22 7:50 UTC (permalink / raw) To: linux-arm-kernel It adds dri-devel at lists.freedesktop.org to this mail thread. Thank you. 2011? 6? 22? ?? 3:04, daeinki <inki.dae@samsung.com>?? ?: > below is additional comments. > > daeinki ? ?: >> Hi all, >> >> I'm writing Samsung SoC based DRM framework and this one includes FIMD >> and HDMI driver as hardware dependent modules. and for now, encoder, >> connector, crtc and fb module has been materialized almost. but I'm >> contending with framebuffer setting issue(created fb_info should be >> registered to linux framebuffer through register_framebuffer() or not)as >> default framebuffer at booting time. >> >> at drm_fb_helper_single_fb_probe() of drm_fb_helper.c file, fb_helper's >> fb_probe callback is called and this one creates new framebuffer and >> returns a value more then 0 if true. internally, this process creates an >> fb_info object and drm_framebuffer and then drm_framebuffer would be >> added to mode_config.fb_list of the drm_device. >> > it's my mistake. return value is 0 if true, nonzero otherwise. > >> a value returned, new_fb is used to decide that it calls >> register_framebuffer() or drm_fb_helper_set_par(). at this point, I am >> confused it's a good way to call register_framebuffer() otherwise >> drm_fb_helper_set_par(). if register_framebuffer() is called then I >> guess drm_fb_helper_set_par() or drm_crtc_helper_set_config() should be >> called somewhere subsequently to apply this one to real hardware because >> previous process is just for maintaining data logically.(not set up data >> to h/w) >> >> it's a right way to call register_framebuffer() and then >> drm_fb_helper_set_par() or drm_crtc_helper_set_config()? otherwise just >> only drm_fb_helper_set_par() or drm_crtc_helper_set_config() ignoring >> register_framebuffer()? and what is the purpose of using >> register_framebuffer()? >> > I understood that if fb_probe() callback is fail then fb_info object is > registered to linux framebuffer through register_framebuffer() > otherwise(if true) hardware configuration would be completed by > drm_fb_helper_set_par() so the reason of using register_framebuffer() is > that the case of failing fb_probe() callback, it is for drawing on only > linux framebuffer. is it right? > >> In my case, first, register_framebuffer() is called and then if desired >> default crtc id is matched with drm_fb_helper->crtc_info[0 ~ n].crtc_id, >> it gets mode_set of drm_fb_helper->crtc_info[n] and then it calls >> drm_crtc_helper_set_config(mode_set). at this time, all the hardware >> configurations would be completed. >> >> thank you in advance. >> >> Best Regards >> Inki Dae. >> > > > _______________________________________________ > linux-arm-kernel mailing list > linux-arm-kernel at lists.infradead.org > http://lists.infradead.org/mailman/listinfo/linux-arm-kernel > ^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Some questions about DRM(Direct Rendering Manager) 2011-06-22 7:50 ` InKi Dae (?) @ 2011-06-22 13:07 ` Rob Clark -1 siblings, 0 replies; 13+ messages in thread From: Rob Clark @ 2011-06-22 13:07 UTC (permalink / raw) To: InKi Dae Cc: linux-fbdev, Kukjin Kim, Kyungmin Park, dri-devel, daeinki, Paul Mundt, jesse.barnes, linux-arm-kernel fwiw, drm_fb_helper_single_fb_probe() calls register_framebuffer() (if that was the question?) BR, -R 2011/6/22 InKi Dae <daeinki@gmail.com>: > It adds dri-devel@lists.freedesktop.org to this mail thread. > Thank you. > > 2011년 6월 22일 오후 3:04, daeinki <inki.dae@samsung.com>님의 말: >> below is additional comments. >> >> daeinki 쓴 글: >>> Hi all, >>> >>> I'm writing Samsung SoC based DRM framework and this one includes FIMD >>> and HDMI driver as hardware dependent modules. and for now, encoder, >>> connector, crtc and fb module has been materialized almost. but I'm >>> contending with framebuffer setting issue(created fb_info should be >>> registered to linux framebuffer through register_framebuffer() or not)as >>> default framebuffer at booting time. >>> >>> at drm_fb_helper_single_fb_probe() of drm_fb_helper.c file, fb_helper's >>> fb_probe callback is called and this one creates new framebuffer and >>> returns a value more then 0 if true. internally, this process creates an >>> fb_info object and drm_framebuffer and then drm_framebuffer would be >>> added to mode_config.fb_list of the drm_device. >>> >> it's my mistake. return value is 0 if true, nonzero otherwise. >> >>> a value returned, new_fb is used to decide that it calls >>> register_framebuffer() or drm_fb_helper_set_par(). at this point, I am >>> confused it's a good way to call register_framebuffer() otherwise >>> drm_fb_helper_set_par(). if register_framebuffer() is called then I >>> guess drm_fb_helper_set_par() or drm_crtc_helper_set_config() should be >>> called somewhere subsequently to apply this one to real hardware because >>> previous process is just for maintaining data logically.(not set up data >>> to h/w) >>> >>> it's a right way to call register_framebuffer() and then >>> drm_fb_helper_set_par() or drm_crtc_helper_set_config()? otherwise just >>> only drm_fb_helper_set_par() or drm_crtc_helper_set_config() ignoring >>> register_framebuffer()? and what is the purpose of using >>> register_framebuffer()? >>> >> I understood that if fb_probe() callback is fail then fb_info object is >> registered to linux framebuffer through register_framebuffer() >> otherwise(if true) hardware configuration would be completed by >> drm_fb_helper_set_par() so the reason of using register_framebuffer() is >> that the case of failing fb_probe() callback, it is for drawing on only >> linux framebuffer. is it right? >> >>> In my case, first, register_framebuffer() is called and then if desired >>> default crtc id is matched with drm_fb_helper->crtc_info[0 ~ n].crtc_id, >>> it gets mode_set of drm_fb_helper->crtc_info[n] and then it calls >>> drm_crtc_helper_set_config(mode_set). at this time, all the hardware >>> configurations would be completed. >>> >>> thank you in advance. >>> >>> Best Regards >>> Inki Dae. >>> >> >> >> _______________________________________________ >> linux-arm-kernel mailing list >> linux-arm-kernel@lists.infradead.org >> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel >> > _______________________________________________ > dri-devel mailing list > dri-devel@lists.freedesktop.org > http://lists.freedesktop.org/mailman/listinfo/dri-devel > -- To unsubscribe from this list: send the line "unsubscribe linux-fbdev" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html ^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Some questions about DRM(Direct Rendering Manager) @ 2011-06-22 13:07 ` Rob Clark 0 siblings, 0 replies; 13+ messages in thread From: Rob Clark @ 2011-06-22 13:07 UTC (permalink / raw) To: InKi Dae Cc: linux-fbdev, Kukjin Kim, Kyungmin Park, dri-devel, daeinki, Paul Mundt, jesse.barnes, linux-arm-kernel fwiw, drm_fb_helper_single_fb_probe() calls register_framebuffer() (if that was the question?) BR, -R 2011/6/22 InKi Dae <daeinki@gmail.com>: > It adds dri-devel@lists.freedesktop.org to this mail thread. > Thank you. > > 2011년 6월 22일 오후 3:04, daeinki <inki.dae@samsung.com>님의 말: >> below is additional comments. >> >> daeinki 쓴 글: >>> Hi all, >>> >>> I'm writing Samsung SoC based DRM framework and this one includes FIMD >>> and HDMI driver as hardware dependent modules. and for now, encoder, >>> connector, crtc and fb module has been materialized almost. but I'm >>> contending with framebuffer setting issue(created fb_info should be >>> registered to linux framebuffer through register_framebuffer() or not)as >>> default framebuffer at booting time. >>> >>> at drm_fb_helper_single_fb_probe() of drm_fb_helper.c file, fb_helper's >>> fb_probe callback is called and this one creates new framebuffer and >>> returns a value more then 0 if true. internally, this process creates an >>> fb_info object and drm_framebuffer and then drm_framebuffer would be >>> added to mode_config.fb_list of the drm_device. >>> >> it's my mistake. return value is 0 if true, nonzero otherwise. >> >>> a value returned, new_fb is used to decide that it calls >>> register_framebuffer() or drm_fb_helper_set_par(). at this point, I am >>> confused it's a good way to call register_framebuffer() otherwise >>> drm_fb_helper_set_par(). if register_framebuffer() is called then I >>> guess drm_fb_helper_set_par() or drm_crtc_helper_set_config() should be >>> called somewhere subsequently to apply this one to real hardware because >>> previous process is just for maintaining data logically.(not set up data >>> to h/w) >>> >>> it's a right way to call register_framebuffer() and then >>> drm_fb_helper_set_par() or drm_crtc_helper_set_config()? otherwise just >>> only drm_fb_helper_set_par() or drm_crtc_helper_set_config() ignoring >>> register_framebuffer()? and what is the purpose of using >>> register_framebuffer()? >>> >> I understood that if fb_probe() callback is fail then fb_info object is >> registered to linux framebuffer through register_framebuffer() >> otherwise(if true) hardware configuration would be completed by >> drm_fb_helper_set_par() so the reason of using register_framebuffer() is >> that the case of failing fb_probe() callback, it is for drawing on only >> linux framebuffer. is it right? >> >>> In my case, first, register_framebuffer() is called and then if desired >>> default crtc id is matched with drm_fb_helper->crtc_info[0 ~ n].crtc_id, >>> it gets mode_set of drm_fb_helper->crtc_info[n] and then it calls >>> drm_crtc_helper_set_config(mode_set). at this time, all the hardware >>> configurations would be completed. >>> >>> thank you in advance. >>> >>> Best Regards >>> Inki Dae. >>> >> >> >> _______________________________________________ >> linux-arm-kernel mailing list >> linux-arm-kernel@lists.infradead.org >> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel >> > _______________________________________________ > dri-devel mailing list > dri-devel@lists.freedesktop.org > http://lists.freedesktop.org/mailman/listinfo/dri-devel > _______________________________________________ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel ^ permalink raw reply [flat|nested] 13+ messages in thread
* Some questions about DRM(Direct Rendering Manager) @ 2011-06-22 13:07 ` Rob Clark 0 siblings, 0 replies; 13+ messages in thread From: Rob Clark @ 2011-06-22 13:07 UTC (permalink / raw) To: linux-arm-kernel fwiw, drm_fb_helper_single_fb_probe() calls register_framebuffer() (if that was the question?) BR, -R 2011/6/22 InKi Dae <daeinki@gmail.com>: > It adds dri-devel at lists.freedesktop.org to this mail thread. > Thank you. > > 2011? 6? 22? ?? 3:04, daeinki <inki.dae@samsung.com>?? ?: >> below is additional comments. >> >> daeinki ? ?: >>> Hi all, >>> >>> I'm writing Samsung SoC based DRM framework and this one includes FIMD >>> and HDMI driver as hardware dependent modules. and for now, encoder, >>> connector, crtc and fb module has been materialized almost. but I'm >>> contending with framebuffer setting issue(created fb_info should be >>> registered to linux framebuffer through register_framebuffer() or not)as >>> default framebuffer at booting time. >>> >>> at drm_fb_helper_single_fb_probe() of drm_fb_helper.c file, fb_helper's >>> fb_probe callback is called and this one creates new framebuffer and >>> returns a value more then 0 if true. internally, this process creates an >>> fb_info object and drm_framebuffer and then drm_framebuffer would be >>> added to mode_config.fb_list of the drm_device. >>> >> it's my mistake. return value is 0 if true, nonzero otherwise. >> >>> a value returned, new_fb is used to decide that it calls >>> register_framebuffer() or drm_fb_helper_set_par(). at this point, I am >>> confused it's a good way to call register_framebuffer() otherwise >>> drm_fb_helper_set_par(). if register_framebuffer() is called then I >>> guess drm_fb_helper_set_par() or drm_crtc_helper_set_config() should be >>> called somewhere subsequently to apply this one to real hardware because >>> previous process is just for maintaining data logically.(not set up data >>> to h/w) >>> >>> it's a right way to call register_framebuffer() and then >>> drm_fb_helper_set_par() or drm_crtc_helper_set_config()? otherwise just >>> only drm_fb_helper_set_par() or drm_crtc_helper_set_config() ignoring >>> register_framebuffer()? and what is the purpose of using >>> register_framebuffer()? >>> >> I understood that if fb_probe() callback is fail then fb_info object is >> registered to linux framebuffer through register_framebuffer() >> otherwise(if true) hardware configuration would be completed by >> drm_fb_helper_set_par() so the reason of using register_framebuffer() is >> that the case of failing fb_probe() callback, it is for drawing on only >> linux framebuffer. is it right? >> >>> In my case, first, register_framebuffer() is called and then if desired >>> default crtc id is matched with drm_fb_helper->crtc_info[0 ~ n].crtc_id, >>> it gets mode_set of drm_fb_helper->crtc_info[n] and then it calls >>> drm_crtc_helper_set_config(mode_set). at this time, all the hardware >>> configurations would be completed. >>> >>> thank you in advance. >>> >>> Best Regards >>> Inki Dae. >>> >> >> >> _______________________________________________ >> linux-arm-kernel mailing list >> linux-arm-kernel at lists.infradead.org >> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel >> > _______________________________________________ > dri-devel mailing list > dri-devel at lists.freedesktop.org > http://lists.freedesktop.org/mailman/listinfo/dri-devel > ^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Some questions about DRM(Direct Rendering Manager) 2011-06-22 13:07 ` Rob Clark (?) @ 2011-06-23 1:55 ` daeinki -1 siblings, 0 replies; 13+ messages in thread From: daeinki @ 2011-06-23 1:55 UTC (permalink / raw) To: Rob Clark Cc: linux-fbdev, Kukjin Kim, Kyungmin Park, dri-devel, Paul Mundt, jesse.barnes, InKi Dae, linux-arm-kernel Hi Rob Clark, I'm sorry for that my mean didn't convey to you so I condensed that into brief again. I know drm_fb_helper_single_fb_probe() calls register_framebuffer(), My question is that it's right way to call only drm_fb_helper_set_par() if fb_helper->funcs->fb_probe() returns nonzero. In this case, if fb_helper->funcs->fb_probe() returns zero then register_framebuffer() isn't called and this means linux framebuffer isn't used anymore. one more question, otherwise if it uses drm based framebuffer, register_framebuffer() should be called necessarily at booting time? Thank you. Rob Clark 쓴 글: > fwiw, drm_fb_helper_single_fb_probe() calls register_framebuffer() (if > that was the question?) > > BR, > -R > > 2011/6/22 InKi Dae <daeinki@gmail.com>: >> It adds dri-devel@lists.freedesktop.org to this mail thread. >> Thank you. >> >> 2011년 6월 22일 오후 3:04, daeinki <inki.dae@samsung.com>님의 말: >>> below is additional comments. >>> >>> daeinki 쓴 글: >>>> Hi all, >>>> >>>> I'm writing Samsung SoC based DRM framework and this one includes FIMD >>>> and HDMI driver as hardware dependent modules. and for now, encoder, >>>> connector, crtc and fb module has been materialized almost. but I'm >>>> contending with framebuffer setting issue(created fb_info should be >>>> registered to linux framebuffer through register_framebuffer() or not)as >>>> default framebuffer at booting time. >>>> >>>> at drm_fb_helper_single_fb_probe() of drm_fb_helper.c file, fb_helper's >>>> fb_probe callback is called and this one creates new framebuffer and >>>> returns a value more then 0 if true. internally, this process creates an >>>> fb_info object and drm_framebuffer and then drm_framebuffer would be >>>> added to mode_config.fb_list of the drm_device. >>>> >>> it's my mistake. return value is 0 if true, nonzero otherwise. >>> >>>> a value returned, new_fb is used to decide that it calls >>>> register_framebuffer() or drm_fb_helper_set_par(). at this point, I am >>>> confused it's a good way to call register_framebuffer() otherwise >>>> drm_fb_helper_set_par(). if register_framebuffer() is called then I >>>> guess drm_fb_helper_set_par() or drm_crtc_helper_set_config() should be >>>> called somewhere subsequently to apply this one to real hardware because >>>> previous process is just for maintaining data logically.(not set up data >>>> to h/w) >>>> >>>> it's a right way to call register_framebuffer() and then >>>> drm_fb_helper_set_par() or drm_crtc_helper_set_config()? otherwise just >>>> only drm_fb_helper_set_par() or drm_crtc_helper_set_config() ignoring >>>> register_framebuffer()? and what is the purpose of using >>>> register_framebuffer()? >>>> >>> I understood that if fb_probe() callback is fail then fb_info object is >>> registered to linux framebuffer through register_framebuffer() >>> otherwise(if true) hardware configuration would be completed by >>> drm_fb_helper_set_par() so the reason of using register_framebuffer() is >>> that the case of failing fb_probe() callback, it is for drawing on only >>> linux framebuffer. is it right? >>> >>>> In my case, first, register_framebuffer() is called and then if desired >>>> default crtc id is matched with drm_fb_helper->crtc_info[0 ~ n].crtc_id, >>>> it gets mode_set of drm_fb_helper->crtc_info[n] and then it calls >>>> drm_crtc_helper_set_config(mode_set). at this time, all the hardware >>>> configurations would be completed. >>>> >>>> thank you in advance. >>>> >>>> Best Regards >>>> Inki Dae. >>>> >>> >>> _______________________________________________ >>> linux-arm-kernel mailing list >>> linux-arm-kernel@lists.infradead.org >>> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel >>> >> _______________________________________________ >> dri-devel mailing list >> dri-devel@lists.freedesktop.org >> http://lists.freedesktop.org/mailman/listinfo/dri-devel >> > -- To unsubscribe from this list: send the line "unsubscribe linux-fbdev" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html ^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Some questions about DRM(Direct Rendering Manager) @ 2011-06-23 1:55 ` daeinki 0 siblings, 0 replies; 13+ messages in thread From: daeinki @ 2011-06-23 1:55 UTC (permalink / raw) To: Rob Clark Cc: linux-fbdev, Kukjin Kim, Kyungmin Park, dri-devel, Paul Mundt, jesse.barnes, InKi Dae, linux-arm-kernel Hi Rob Clark, I'm sorry for that my mean didn't convey to you so I condensed that into brief again. I know drm_fb_helper_single_fb_probe() calls register_framebuffer(), My question is that it's right way to call only drm_fb_helper_set_par() if fb_helper->funcs->fb_probe() returns nonzero. In this case, if fb_helper->funcs->fb_probe() returns zero then register_framebuffer() isn't called and this means linux framebuffer isn't used anymore. one more question, otherwise if it uses drm based framebuffer, register_framebuffer() should be called necessarily at booting time? Thank you. Rob Clark 쓴 글: > fwiw, drm_fb_helper_single_fb_probe() calls register_framebuffer() (if > that was the question?) > > BR, > -R > > 2011/6/22 InKi Dae <daeinki@gmail.com>: >> It adds dri-devel@lists.freedesktop.org to this mail thread. >> Thank you. >> >> 2011년 6월 22일 오후 3:04, daeinki <inki.dae@samsung.com>님의 말: >>> below is additional comments. >>> >>> daeinki 쓴 글: >>>> Hi all, >>>> >>>> I'm writing Samsung SoC based DRM framework and this one includes FIMD >>>> and HDMI driver as hardware dependent modules. and for now, encoder, >>>> connector, crtc and fb module has been materialized almost. but I'm >>>> contending with framebuffer setting issue(created fb_info should be >>>> registered to linux framebuffer through register_framebuffer() or not)as >>>> default framebuffer at booting time. >>>> >>>> at drm_fb_helper_single_fb_probe() of drm_fb_helper.c file, fb_helper's >>>> fb_probe callback is called and this one creates new framebuffer and >>>> returns a value more then 0 if true. internally, this process creates an >>>> fb_info object and drm_framebuffer and then drm_framebuffer would be >>>> added to mode_config.fb_list of the drm_device. >>>> >>> it's my mistake. return value is 0 if true, nonzero otherwise. >>> >>>> a value returned, new_fb is used to decide that it calls >>>> register_framebuffer() or drm_fb_helper_set_par(). at this point, I am >>>> confused it's a good way to call register_framebuffer() otherwise >>>> drm_fb_helper_set_par(). if register_framebuffer() is called then I >>>> guess drm_fb_helper_set_par() or drm_crtc_helper_set_config() should be >>>> called somewhere subsequently to apply this one to real hardware because >>>> previous process is just for maintaining data logically.(not set up data >>>> to h/w) >>>> >>>> it's a right way to call register_framebuffer() and then >>>> drm_fb_helper_set_par() or drm_crtc_helper_set_config()? otherwise just >>>> only drm_fb_helper_set_par() or drm_crtc_helper_set_config() ignoring >>>> register_framebuffer()? and what is the purpose of using >>>> register_framebuffer()? >>>> >>> I understood that if fb_probe() callback is fail then fb_info object is >>> registered to linux framebuffer through register_framebuffer() >>> otherwise(if true) hardware configuration would be completed by >>> drm_fb_helper_set_par() so the reason of using register_framebuffer() is >>> that the case of failing fb_probe() callback, it is for drawing on only >>> linux framebuffer. is it right? >>> >>>> In my case, first, register_framebuffer() is called and then if desired >>>> default crtc id is matched with drm_fb_helper->crtc_info[0 ~ n].crtc_id, >>>> it gets mode_set of drm_fb_helper->crtc_info[n] and then it calls >>>> drm_crtc_helper_set_config(mode_set). at this time, all the hardware >>>> configurations would be completed. >>>> >>>> thank you in advance. >>>> >>>> Best Regards >>>> Inki Dae. >>>> >>> >>> _______________________________________________ >>> linux-arm-kernel mailing list >>> linux-arm-kernel@lists.infradead.org >>> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel >>> >> _______________________________________________ >> dri-devel mailing list >> dri-devel@lists.freedesktop.org >> http://lists.freedesktop.org/mailman/listinfo/dri-devel >> > _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel ^ permalink raw reply [flat|nested] 13+ messages in thread
* Some questions about DRM(Direct Rendering Manager) @ 2011-06-23 1:55 ` daeinki 0 siblings, 0 replies; 13+ messages in thread From: daeinki @ 2011-06-23 1:55 UTC (permalink / raw) To: linux-arm-kernel Hi Rob Clark, I'm sorry for that my mean didn't convey to you so I condensed that into brief again. I know drm_fb_helper_single_fb_probe() calls register_framebuffer(), My question is that it's right way to call only drm_fb_helper_set_par() if fb_helper->funcs->fb_probe() returns nonzero. In this case, if fb_helper->funcs->fb_probe() returns zero then register_framebuffer() isn't called and this means linux framebuffer isn't used anymore. one more question, otherwise if it uses drm based framebuffer, register_framebuffer() should be called necessarily at booting time? Thank you. Rob Clark ? ?: > fwiw, drm_fb_helper_single_fb_probe() calls register_framebuffer() (if > that was the question?) > > BR, > -R > > 2011/6/22 InKi Dae <daeinki@gmail.com>: >> It adds dri-devel at lists.freedesktop.org to this mail thread. >> Thank you. >> >> 2011? 6? 22? ?? 3:04, daeinki <inki.dae@samsung.com>?? ?: >>> below is additional comments. >>> >>> daeinki ? ?: >>>> Hi all, >>>> >>>> I'm writing Samsung SoC based DRM framework and this one includes FIMD >>>> and HDMI driver as hardware dependent modules. and for now, encoder, >>>> connector, crtc and fb module has been materialized almost. but I'm >>>> contending with framebuffer setting issue(created fb_info should be >>>> registered to linux framebuffer through register_framebuffer() or not)as >>>> default framebuffer at booting time. >>>> >>>> at drm_fb_helper_single_fb_probe() of drm_fb_helper.c file, fb_helper's >>>> fb_probe callback is called and this one creates new framebuffer and >>>> returns a value more then 0 if true. internally, this process creates an >>>> fb_info object and drm_framebuffer and then drm_framebuffer would be >>>> added to mode_config.fb_list of the drm_device. >>>> >>> it's my mistake. return value is 0 if true, nonzero otherwise. >>> >>>> a value returned, new_fb is used to decide that it calls >>>> register_framebuffer() or drm_fb_helper_set_par(). at this point, I am >>>> confused it's a good way to call register_framebuffer() otherwise >>>> drm_fb_helper_set_par(). if register_framebuffer() is called then I >>>> guess drm_fb_helper_set_par() or drm_crtc_helper_set_config() should be >>>> called somewhere subsequently to apply this one to real hardware because >>>> previous process is just for maintaining data logically.(not set up data >>>> to h/w) >>>> >>>> it's a right way to call register_framebuffer() and then >>>> drm_fb_helper_set_par() or drm_crtc_helper_set_config()? otherwise just >>>> only drm_fb_helper_set_par() or drm_crtc_helper_set_config() ignoring >>>> register_framebuffer()? and what is the purpose of using >>>> register_framebuffer()? >>>> >>> I understood that if fb_probe() callback is fail then fb_info object is >>> registered to linux framebuffer through register_framebuffer() >>> otherwise(if true) hardware configuration would be completed by >>> drm_fb_helper_set_par() so the reason of using register_framebuffer() is >>> that the case of failing fb_probe() callback, it is for drawing on only >>> linux framebuffer. is it right? >>> >>>> In my case, first, register_framebuffer() is called and then if desired >>>> default crtc id is matched with drm_fb_helper->crtc_info[0 ~ n].crtc_id, >>>> it gets mode_set of drm_fb_helper->crtc_info[n] and then it calls >>>> drm_crtc_helper_set_config(mode_set). at this time, all the hardware >>>> configurations would be completed. >>>> >>>> thank you in advance. >>>> >>>> Best Regards >>>> Inki Dae. >>>> >>> >>> _______________________________________________ >>> linux-arm-kernel mailing list >>> linux-arm-kernel at lists.infradead.org >>> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel >>> >> _______________________________________________ >> dri-devel mailing list >> dri-devel at lists.freedesktop.org >> http://lists.freedesktop.org/mailman/listinfo/dri-devel >> > ^ permalink raw reply [flat|nested] 13+ messages in thread
end of thread, other threads:[~2011-06-23 1:55 UTC | newest] Thread overview: 13+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2011-06-22 4:26 Some questions about DRM(Direct Rendering Manager) daeinki 2011-06-22 4:26 ` daeinki 2011-06-22 6:04 ` daeinki 2011-06-22 6:04 ` daeinki 2011-06-22 7:50 ` InKi Dae 2011-06-22 7:50 ` InKi Dae 2011-06-22 7:50 ` InKi Dae 2011-06-22 13:07 ` Rob Clark 2011-06-22 13:07 ` Rob Clark 2011-06-22 13:07 ` Rob Clark 2011-06-23 1:55 ` daeinki 2011-06-23 1:55 ` daeinki 2011-06-23 1:55 ` daeinki
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.