* db820c: Input signal Out of range @ 2018-08-10 6:38 Ricardo Ribalda Delgado [not found] ` <CAPybu_0ooyLXuFK4x7kAk6-cpXeCO09yjfx9SwHFAKp5n2fsEQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> 0 siblings, 1 reply; 11+ messages in thread From: Ricardo Ribalda Delgado @ 2018-08-10 6:38 UTC (permalink / raw) To: Archit Taneja, Rob Clark, linux-arm-msm-u79uwXL29TY76Z2rM5mHXA, freedreno-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW Hello I have a screen that via edid expects the following modeline by default via detailed mode: Modeline "1680x1050"x60.0 146.30 1680 1784 1960 2240 1050 1053 1059 1089 +hsync -vsync When the card is configured to that modeline the screen cannot output the image and shows the following error message: Input signal out of range. I have tried with a different card and that exact modeline: xrandr --newmode fast 146.30 1680 1784 1960 2240 1050 1053 1059 1089 +hsync -vsync xrandr --addmode HDMI-1 slow xrandr --output HDMI-1 --mode fast and the screen works just fine. If I just tweak down a bit the clock: xrandr --newmode slow 146.25 1680 1784 1960 2240 1050 1053 1059 1089 +hsync -vsync the screen shows an image as expected. I believe that there might be a misscalculation on the pll code. And I am printing the debug info from: drivers/gpu/drm/msm/hdmi/hdmi_phy_8996.c The configuration that fails shows: [ 138.553168] VCO freq: 8778000000 [ 138.553172] fdata: 1463000000 [ 138.553187] pix_clk: 146300000 [ 138.555447] tmds clk: 146300000 [ 138.558336] HSCLK_SEL: 1 [ 138.561277] DEC_START: 114 [ 138.564316] DIV_FRAC_START: 311296 [ 138.567080] PLL_CPCTRL: 11 [ 138.569614] PLL_RCTRL: 22 [ 138.572996] PLL_CCTRL: 40 [ 138.575698] INTEGLOOP_GAIN: 256 [ 138.578366] TX_BAND: 0 [ 138.580986] PLL_CMP: 7802 [ 138.583936] com_svs_mode_clk_sel = 0x2 [ 138.586351] com_hsclk_sel = 0x21 [ 138.589067] com_lock_cmp_en = 0x0 [ 138.592704] com_pll_cctrl_mode0 = 0x28 [ 138.596089] com_pll_rctrl_mode0 = 0x16 [ 138.599286] com_cp_ctrl_mode0 = 0xb [ 138.602955] com_dec_start_mode0 = 0x72 [ 138.606678] com_div_frac_start1_mode0 = 0x0 [ 138.610064] com_div_frac_start2_mode0 = 0xc0 [ 138.613894] com_div_frac_start3_mode0 = 0x4 [ 138.617964] com_integloop_gain0_mode0 = 0x0 [ 138.622478] com_integloop_gain1_mode0 = 0x1 [ 138.626393] com_lock_cmp1_mode0 = 0x7a [ 138.630550] com_lock_cmp2_mode0 = 0x1e [ 138.634719] com_lock_cmp3_mode0 = 0x0 [ 138.638545] com_core_clk_en = 0x2c [ 138.642271] com_coreclk_div = 0x5 [ 138.646001] phy_mode = 0x0 [ 138.649308] tx_l0_lane_mode = 0x43 [ 138.652684] tx_l2_lane_mode = 0x43 [ 138.655275] tx_l0_tx_band = 0x4 [ 138.658679] tx_l0_tx_drv_lvl = 0x25 [ 138.662070] tx_l0_tx_emp_post1_lvl = 0x23 [ 138.665101] tx_l0_vmode_ctrl1 = 0x0 [ 138.668571] tx_l0_vmode_ctrl2 = 0xd [ 138.672747] tx_l1_tx_band = 0x4 [ 138.676037] tx_l1_tx_drv_lvl = 0x25 [ 138.679493] tx_l1_tx_emp_post1_lvl = 0x23 [ 138.682633] tx_l1_vmode_ctrl1 = 0x0 [ 138.686117] tx_l1_vmode_ctrl2 = 0xd [ 138.690272] tx_l2_tx_band = 0x4 [ 138.693571] tx_l2_tx_drv_lvl = 0x25 [ 138.697050] tx_l2_tx_emp_post1_lvl = 0x23 [ 138.700168] tx_l2_vmode_ctrl1 = 0x0 [ 138.703641] tx_l2_vmode_ctrl2 = 0xd [ 138.707816] tx_l3_tx_band = 0x4 [ 138.711092] tx_l3_tx_drv_lvl = 0x25 [ 138.714577] tx_l3_tx_emp_post1_lvl = 0x23 [ 138.717705] tx_l3_vmode_ctrl1 = 0x0 [ 138.721182] tx_l3_vmode_ctrl2 = 0x0 and the configuration that works: [ 62.936970] VCO freq: 8775000000 [ 62.936976] fdata: 1462500000 [ 62.936990] pix_clk: 146250000 [ 62.939250] tmds clk: 146250000 [ 62.942175] HSCLK_SEL: 1 [ 62.945095] DEC_START: 114 [ 62.948117] DIV_FRAC_START: 270336 [ 62.950881] PLL_CPCTRL: 11 [ 62.953421] PLL_RCTRL: 22 [ 62.956798] PLL_CCTRL: 40 [ 62.959475] INTEGLOOP_GAIN: 256 [ 62.962179] TX_BAND: 0 [ 62.964785] PLL_CMP: 7799 [ 62.967738] com_svs_mode_clk_sel = 0x2 [ 62.970153] com_hsclk_sel = 0x21 [ 62.972862] com_lock_cmp_en = 0x0 [ 62.976506] com_pll_cctrl_mode0 = 0x28 [ 62.979893] com_pll_rctrl_mode0 = 0x16 [ 62.983088] com_cp_ctrl_mode0 = 0xb [ 62.986749] com_dec_start_mode0 = 0x72 [ 62.990480] com_div_frac_start1_mode0 = 0x0 [ 62.993868] com_div_frac_start2_mode0 = 0x20 [ 62.997688] com_div_frac_start3_mode0 = 0x4 [ 63.001769] com_integloop_gain0_mode0 = 0x0 [ 63.006281] com_integloop_gain1_mode0 = 0x1 [ 63.010189] com_lock_cmp1_mode0 = 0x77 [ 63.014354] com_lock_cmp2_mode0 = 0x1e [ 63.018521] com_lock_cmp3_mode0 = 0x0 [ 63.022338] com_core_clk_en = 0x2c [ 63.026072] com_coreclk_div = 0x5 [ 63.029804] phy_mode = 0x0 [ 63.033103] tx_l0_lane_mode = 0x43 [ 63.036488] tx_l2_lane_mode = 0x43 [ 63.039078] tx_l0_tx_band = 0x4 [ 63.042479] tx_l0_tx_drv_lvl = 0x25 [ 63.045864] tx_l0_tx_emp_post1_lvl = 0x23 [ 63.048901] tx_l0_vmode_ctrl1 = 0x0 [ 63.052375] tx_l0_vmode_ctrl2 = 0xd [ 63.056541] tx_l1_tx_band = 0x4 [ 63.059840] tx_l1_tx_drv_lvl = 0x25 [ 63.063295] tx_l1_tx_emp_post1_lvl = 0x23 [ 63.066437] tx_l1_vmode_ctrl1 = 0x0 [ 63.069908] tx_l1_vmode_ctrl2 = 0xd [ 63.074075] tx_l2_tx_band = 0x4 [ 63.077373] tx_l2_tx_drv_lvl = 0x25 [ 63.080844] tx_l2_tx_emp_post1_lvl = 0x23 [ 63.083971] tx_l2_vmode_ctrl1 = 0x0 [ 63.087428] tx_l2_vmode_ctrl2 = 0xd [ 63.091609] tx_l3_tx_band = 0x4 [ 63.094906] tx_l3_tx_drv_lvl = 0x25 [ 63.098379] tx_l3_tx_emp_post1_lvl = 0x23 [ 63.101505] tx_l3_vmode_ctrl1 = 0x0 [ 63.104979] tx_l3_vmode_ctrl2 = 0x0 Unfortunately I do not have the documentation of the pll to validade any of the two setups. Where can I find that doc? Any ideas of how to proceed? Thanks! -- Ricardo Ribalda _______________________________________________ Freedreno mailing list Freedreno@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/freedreno ^ permalink raw reply [flat|nested] 11+ messages in thread
[parent not found: <CAPybu_0ooyLXuFK4x7kAk6-cpXeCO09yjfx9SwHFAKp5n2fsEQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>]
* Re: db820c: Input signal Out of range [not found] ` <CAPybu_0ooyLXuFK4x7kAk6-cpXeCO09yjfx9SwHFAKp5n2fsEQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> @ 2018-08-12 7:47 ` Archit Taneja [not found] ` <d4542b41-aa79-5c50-4971-9e1c1b937b02-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org> 0 siblings, 1 reply; 11+ messages in thread From: Archit Taneja @ 2018-08-12 7:47 UTC (permalink / raw) To: Ricardo Ribalda Delgado, Rob Clark, linux-arm-msm-u79uwXL29TY76Z2rM5mHXA, freedreno-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW Hi, On Friday 10 August 2018 12:08 PM, Ricardo Ribalda Delgado wrote: > Hello > > I have a screen that via edid expects the following modeline by > default via detailed mode: > > Modeline "1680x1050"x60.0 146.30 1680 1784 1960 2240 1050 1053 1059 > 1089 +hsync -vsync > > When the card is configured to that modeline the screen cannot output > the image and shows the following error message: Input signal out of > range. > > I have tried with a different card and that exact modeline: > > xrandr --newmode fast 146.30 1680 1784 1960 2240 1050 1053 1059 1089 > +hsync -vsync > xrandr --addmode HDMI-1 slow > xrandr --output HDMI-1 --mode fast > > and the screen works just fine. > > > If I just tweak down a bit the clock: > xrandr --newmode slow 146.25 1680 1784 1960 2240 1050 1053 1059 1089 > +hsync -vsync > the screen shows an image as expected. > > I believe that there might be a misscalculation on the pll code. And I > am printing the debug info from: > drivers/gpu/drm/msm/hdmi/hdmi_phy_8996.c > > The configuration that fails shows: > > [ 138.553168] VCO freq: 8778000000 > [ 138.553172] fdata: 1463000000 > [ 138.553187] pix_clk: 146300000 > [ 138.555447] tmds clk: 146300000 > [ 138.558336] HSCLK_SEL: 1 > [ 138.561277] DEC_START: 114 > [ 138.564316] DIV_FRAC_START: 311296 > [ 138.567080] PLL_CPCTRL: 11 > [ 138.569614] PLL_RCTRL: 22 > [ 138.572996] PLL_CCTRL: 40 > [ 138.575698] INTEGLOOP_GAIN: 256 > [ 138.578366] TX_BAND: 0 > [ 138.580986] PLL_CMP: 7802 > [ 138.583936] com_svs_mode_clk_sel = 0x2 > [ 138.586351] com_hsclk_sel = 0x21 > [ 138.589067] com_lock_cmp_en = 0x0 > [ 138.592704] com_pll_cctrl_mode0 = 0x28 > [ 138.596089] com_pll_rctrl_mode0 = 0x16 > [ 138.599286] com_cp_ctrl_mode0 = 0xb > [ 138.602955] com_dec_start_mode0 = 0x72 > [ 138.606678] com_div_frac_start1_mode0 = 0x0 > [ 138.610064] com_div_frac_start2_mode0 = 0xc0 > [ 138.613894] com_div_frac_start3_mode0 = 0x4 > [ 138.617964] com_integloop_gain0_mode0 = 0x0 > [ 138.622478] com_integloop_gain1_mode0 = 0x1 > [ 138.626393] com_lock_cmp1_mode0 = 0x7a > [ 138.630550] com_lock_cmp2_mode0 = 0x1e > [ 138.634719] com_lock_cmp3_mode0 = 0x0 > [ 138.638545] com_core_clk_en = 0x2c > [ 138.642271] com_coreclk_div = 0x5 > [ 138.646001] phy_mode = 0x0 > [ 138.649308] tx_l0_lane_mode = 0x43 > [ 138.652684] tx_l2_lane_mode = 0x43 > [ 138.655275] tx_l0_tx_band = 0x4 > [ 138.658679] tx_l0_tx_drv_lvl = 0x25 > [ 138.662070] tx_l0_tx_emp_post1_lvl = 0x23 > [ 138.665101] tx_l0_vmode_ctrl1 = 0x0 > [ 138.668571] tx_l0_vmode_ctrl2 = 0xd > [ 138.672747] tx_l1_tx_band = 0x4 > [ 138.676037] tx_l1_tx_drv_lvl = 0x25 > [ 138.679493] tx_l1_tx_emp_post1_lvl = 0x23 > [ 138.682633] tx_l1_vmode_ctrl1 = 0x0 > [ 138.686117] tx_l1_vmode_ctrl2 = 0xd > [ 138.690272] tx_l2_tx_band = 0x4 > [ 138.693571] tx_l2_tx_drv_lvl = 0x25 > [ 138.697050] tx_l2_tx_emp_post1_lvl = 0x23 > [ 138.700168] tx_l2_vmode_ctrl1 = 0x0 > [ 138.703641] tx_l2_vmode_ctrl2 = 0xd > [ 138.707816] tx_l3_tx_band = 0x4 > [ 138.711092] tx_l3_tx_drv_lvl = 0x25 > [ 138.714577] tx_l3_tx_emp_post1_lvl = 0x23 > [ 138.717705] tx_l3_vmode_ctrl1 = 0x0 > [ 138.721182] tx_l3_vmode_ctrl2 = 0x0 > > and the configuration that works: > > [ 62.936970] VCO freq: 8775000000 > [ 62.936976] fdata: 1462500000 > [ 62.936990] pix_clk: 146250000 > [ 62.939250] tmds clk: 146250000 > [ 62.942175] HSCLK_SEL: 1 > [ 62.945095] DEC_START: 114 > [ 62.948117] DIV_FRAC_START: 270336 > [ 62.950881] PLL_CPCTRL: 11 > [ 62.953421] PLL_RCTRL: 22 > [ 62.956798] PLL_CCTRL: 40 > [ 62.959475] INTEGLOOP_GAIN: 256 > [ 62.962179] TX_BAND: 0 > [ 62.964785] PLL_CMP: 7799 > [ 62.967738] com_svs_mode_clk_sel = 0x2 > [ 62.970153] com_hsclk_sel = 0x21 > [ 62.972862] com_lock_cmp_en = 0x0 > [ 62.976506] com_pll_cctrl_mode0 = 0x28 > [ 62.979893] com_pll_rctrl_mode0 = 0x16 > [ 62.983088] com_cp_ctrl_mode0 = 0xb > [ 62.986749] com_dec_start_mode0 = 0x72 > [ 62.990480] com_div_frac_start1_mode0 = 0x0 > [ 62.993868] com_div_frac_start2_mode0 = 0x20 > [ 62.997688] com_div_frac_start3_mode0 = 0x4 > [ 63.001769] com_integloop_gain0_mode0 = 0x0 > [ 63.006281] com_integloop_gain1_mode0 = 0x1 > [ 63.010189] com_lock_cmp1_mode0 = 0x77 > [ 63.014354] com_lock_cmp2_mode0 = 0x1e > [ 63.018521] com_lock_cmp3_mode0 = 0x0 > [ 63.022338] com_core_clk_en = 0x2c > [ 63.026072] com_coreclk_div = 0x5 > [ 63.029804] phy_mode = 0x0 > [ 63.033103] tx_l0_lane_mode = 0x43 > [ 63.036488] tx_l2_lane_mode = 0x43 > [ 63.039078] tx_l0_tx_band = 0x4 > [ 63.042479] tx_l0_tx_drv_lvl = 0x25 > [ 63.045864] tx_l0_tx_emp_post1_lvl = 0x23 > [ 63.048901] tx_l0_vmode_ctrl1 = 0x0 > [ 63.052375] tx_l0_vmode_ctrl2 = 0xd > [ 63.056541] tx_l1_tx_band = 0x4 > [ 63.059840] tx_l1_tx_drv_lvl = 0x25 > [ 63.063295] tx_l1_tx_emp_post1_lvl = 0x23 > [ 63.066437] tx_l1_vmode_ctrl1 = 0x0 > [ 63.069908] tx_l1_vmode_ctrl2 = 0xd > [ 63.074075] tx_l2_tx_band = 0x4 > [ 63.077373] tx_l2_tx_drv_lvl = 0x25 > [ 63.080844] tx_l2_tx_emp_post1_lvl = 0x23 > [ 63.083971] tx_l2_vmode_ctrl1 = 0x0 > [ 63.087428] tx_l2_vmode_ctrl2 = 0xd > [ 63.091609] tx_l3_tx_band = 0x4 > [ 63.094906] tx_l3_tx_drv_lvl = 0x25 > [ 63.098379] tx_l3_tx_emp_post1_lvl = 0x23 > [ 63.101505] tx_l3_vmode_ctrl1 = 0x0 > [ 63.104979] tx_l3_vmode_ctrl2 = 0x0 > > Unfortunately I do not have the documentation of the pll to validade > any of the two setups. I'm not sure if there is any public documentation of the hardware registers for 8x96. I'd myself mostly ported this code from the downstream hdmi PLL driver (the 8996_v3 code in particular): https://source.codeaurora.org/quic/la/kernel/msm-3.18/tree/drivers/clk/msm/mdss/mdss-hdmi-pll-8996.c?h=msm-3.18 The PLL seems to be getting locked for both cases. But for some reason, when trying to configure it for 146.30 Mhz, it's generating a wayward enough value for the monitor to reject it. I looked at the logs, and the configurations match what both the upstream and downstream drivers are trying to do. The main differences between the configurations seem to be the fractional component calculation and the computation of PLL_CMP. From my experience, minor changes in the fractional component don't calculation doesn't cause too much of a difference. As an experiment, you could try to forcibly set the PLL_CMP value to 7799 in the non-working case to check if that's causing the issue. We could then try to find out from someone within Qualcomm if there's a better way to compute this parameter. Thanks, Archit > > Where can I find that doc? > Any ideas of how to proceed? > > > Thanks! > _______________________________________________ Freedreno mailing list Freedreno@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/freedreno ^ permalink raw reply [flat|nested] 11+ messages in thread
[parent not found: <d4542b41-aa79-5c50-4971-9e1c1b937b02-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>]
* Re: db820c: Input signal Out of range [not found] ` <d4542b41-aa79-5c50-4971-9e1c1b937b02-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org> @ 2018-08-13 8:54 ` Ricardo Ribalda Delgado [not found] ` <CAPybu_0dMfaxBhybHapqfmjHVotA0BBsBs0cjYwdu4eaTT9rmQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> 0 siblings, 1 reply; 11+ messages in thread From: Ricardo Ribalda Delgado @ 2018-08-13 8:54 UTC (permalink / raw) To: Archit Taneja Cc: linux-arm-msm-u79uwXL29TY76Z2rM5mHXA, Rob Clark, freedreno-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW, alex-fkYMi7rYDl0 Hi Archit On Sun, Aug 12, 2018 at 9:47 AM Archit Taneja <architt@codeaurora.org> wrote: > > Hi, > > On Friday 10 August 2018 12:08 PM, Ricardo Ribalda Delgado wrote: > > Hello > > > > I have a screen that via edid expects the following modeline by > > default via detailed mode: > > > > Modeline "1680x1050"x60.0 146.30 1680 1784 1960 2240 1050 1053 1059 > > 1089 +hsync -vsync > > > > When the card is configured to that modeline the screen cannot output > > the image and shows the following error message: Input signal out of > > range. > > > > I have tried with a different card and that exact modeline: > > > > xrandr --newmode fast 146.30 1680 1784 1960 2240 1050 1053 1059 1089 > > +hsync -vsync > > xrandr --addmode HDMI-1 slow > > xrandr --output HDMI-1 --mode fast > > > > and the screen works just fine. > > > > > > If I just tweak down a bit the clock: > > xrandr --newmode slow 146.25 1680 1784 1960 2240 1050 1053 1059 1089 > > +hsync -vsync > > the screen shows an image as expected. > > > > I believe that there might be a misscalculation on the pll code. And I > > am printing the debug info from: > > drivers/gpu/drm/msm/hdmi/hdmi_phy_8996.c > > > > The configuration that fails shows: > > > > [ 138.553168] VCO freq: 8778000000 > > [ 138.553172] fdata: 1463000000 > > [ 138.553187] pix_clk: 146300000 > > [ 138.555447] tmds clk: 146300000 > > [ 138.558336] HSCLK_SEL: 1 > > [ 138.561277] DEC_START: 114 > > [ 138.564316] DIV_FRAC_START: 311296 > > [ 138.567080] PLL_CPCTRL: 11 > > [ 138.569614] PLL_RCTRL: 22 > > [ 138.572996] PLL_CCTRL: 40 > > [ 138.575698] INTEGLOOP_GAIN: 256 > > [ 138.578366] TX_BAND: 0 > > [ 138.580986] PLL_CMP: 7802 > > [ 138.583936] com_svs_mode_clk_sel = 0x2 > > [ 138.586351] com_hsclk_sel = 0x21 > > [ 138.589067] com_lock_cmp_en = 0x0 > > [ 138.592704] com_pll_cctrl_mode0 = 0x28 > > [ 138.596089] com_pll_rctrl_mode0 = 0x16 > > [ 138.599286] com_cp_ctrl_mode0 = 0xb > > [ 138.602955] com_dec_start_mode0 = 0x72 > > [ 138.606678] com_div_frac_start1_mode0 = 0x0 > > [ 138.610064] com_div_frac_start2_mode0 = 0xc0 > > [ 138.613894] com_div_frac_start3_mode0 = 0x4 > > [ 138.617964] com_integloop_gain0_mode0 = 0x0 > > [ 138.622478] com_integloop_gain1_mode0 = 0x1 > > [ 138.626393] com_lock_cmp1_mode0 = 0x7a > > [ 138.630550] com_lock_cmp2_mode0 = 0x1e > > [ 138.634719] com_lock_cmp3_mode0 = 0x0 > > [ 138.638545] com_core_clk_en = 0x2c > > [ 138.642271] com_coreclk_div = 0x5 > > [ 138.646001] phy_mode = 0x0 > > [ 138.649308] tx_l0_lane_mode = 0x43 > > [ 138.652684] tx_l2_lane_mode = 0x43 > > [ 138.655275] tx_l0_tx_band = 0x4 > > [ 138.658679] tx_l0_tx_drv_lvl = 0x25 > > [ 138.662070] tx_l0_tx_emp_post1_lvl = 0x23 > > [ 138.665101] tx_l0_vmode_ctrl1 = 0x0 > > [ 138.668571] tx_l0_vmode_ctrl2 = 0xd > > [ 138.672747] tx_l1_tx_band = 0x4 > > [ 138.676037] tx_l1_tx_drv_lvl = 0x25 > > [ 138.679493] tx_l1_tx_emp_post1_lvl = 0x23 > > [ 138.682633] tx_l1_vmode_ctrl1 = 0x0 > > [ 138.686117] tx_l1_vmode_ctrl2 = 0xd > > [ 138.690272] tx_l2_tx_band = 0x4 > > [ 138.693571] tx_l2_tx_drv_lvl = 0x25 > > [ 138.697050] tx_l2_tx_emp_post1_lvl = 0x23 > > [ 138.700168] tx_l2_vmode_ctrl1 = 0x0 > > [ 138.703641] tx_l2_vmode_ctrl2 = 0xd > > [ 138.707816] tx_l3_tx_band = 0x4 > > [ 138.711092] tx_l3_tx_drv_lvl = 0x25 > > [ 138.714577] tx_l3_tx_emp_post1_lvl = 0x23 > > [ 138.717705] tx_l3_vmode_ctrl1 = 0x0 > > [ 138.721182] tx_l3_vmode_ctrl2 = 0x0 > > > > and the configuration that works: > > > > [ 62.936970] VCO freq: 8775000000 > > [ 62.936976] fdata: 1462500000 > > [ 62.936990] pix_clk: 146250000 > > [ 62.939250] tmds clk: 146250000 > > [ 62.942175] HSCLK_SEL: 1 > > [ 62.945095] DEC_START: 114 > > [ 62.948117] DIV_FRAC_START: 270336 > > [ 62.950881] PLL_CPCTRL: 11 > > [ 62.953421] PLL_RCTRL: 22 > > [ 62.956798] PLL_CCTRL: 40 > > [ 62.959475] INTEGLOOP_GAIN: 256 > > [ 62.962179] TX_BAND: 0 > > [ 62.964785] PLL_CMP: 7799 > > [ 62.967738] com_svs_mode_clk_sel = 0x2 > > [ 62.970153] com_hsclk_sel = 0x21 > > [ 62.972862] com_lock_cmp_en = 0x0 > > [ 62.976506] com_pll_cctrl_mode0 = 0x28 > > [ 62.979893] com_pll_rctrl_mode0 = 0x16 > > [ 62.983088] com_cp_ctrl_mode0 = 0xb > > [ 62.986749] com_dec_start_mode0 = 0x72 > > [ 62.990480] com_div_frac_start1_mode0 = 0x0 > > [ 62.993868] com_div_frac_start2_mode0 = 0x20 > > [ 62.997688] com_div_frac_start3_mode0 = 0x4 > > [ 63.001769] com_integloop_gain0_mode0 = 0x0 > > [ 63.006281] com_integloop_gain1_mode0 = 0x1 > > [ 63.010189] com_lock_cmp1_mode0 = 0x77 > > [ 63.014354] com_lock_cmp2_mode0 = 0x1e > > [ 63.018521] com_lock_cmp3_mode0 = 0x0 > > [ 63.022338] com_core_clk_en = 0x2c > > [ 63.026072] com_coreclk_div = 0x5 > > [ 63.029804] phy_mode = 0x0 > > [ 63.033103] tx_l0_lane_mode = 0x43 > > [ 63.036488] tx_l2_lane_mode = 0x43 > > [ 63.039078] tx_l0_tx_band = 0x4 > > [ 63.042479] tx_l0_tx_drv_lvl = 0x25 > > [ 63.045864] tx_l0_tx_emp_post1_lvl = 0x23 > > [ 63.048901] tx_l0_vmode_ctrl1 = 0x0 > > [ 63.052375] tx_l0_vmode_ctrl2 = 0xd > > [ 63.056541] tx_l1_tx_band = 0x4 > > [ 63.059840] tx_l1_tx_drv_lvl = 0x25 > > [ 63.063295] tx_l1_tx_emp_post1_lvl = 0x23 > > [ 63.066437] tx_l1_vmode_ctrl1 = 0x0 > > [ 63.069908] tx_l1_vmode_ctrl2 = 0xd > > [ 63.074075] tx_l2_tx_band = 0x4 > > [ 63.077373] tx_l2_tx_drv_lvl = 0x25 > > [ 63.080844] tx_l2_tx_emp_post1_lvl = 0x23 > > [ 63.083971] tx_l2_vmode_ctrl1 = 0x0 > > [ 63.087428] tx_l2_vmode_ctrl2 = 0xd > > [ 63.091609] tx_l3_tx_band = 0x4 > > [ 63.094906] tx_l3_tx_drv_lvl = 0x25 > > [ 63.098379] tx_l3_tx_emp_post1_lvl = 0x23 > > [ 63.101505] tx_l3_vmode_ctrl1 = 0x0 > > [ 63.104979] tx_l3_vmode_ctrl2 = 0x0 > > > > Unfortunately I do not have the documentation of the pll to validade > > any of the two setups. > > I'm not sure if there is any public documentation of the hardware > registers for 8x96. I'd myself mostly ported this code from the > downstream hdmi PLL driver (the 8996_v3 code in particular): > > https://source.codeaurora.org/quic/la/kernel/msm-3.18/tree/drivers/clk/msm/mdss/mdss-hdmi-pll-8996.c?h=msm-3.18 > > The PLL seems to be getting locked for both cases. But for some reason, > when trying to configure it for 146.30 Mhz, it's generating a > wayward enough value for the monitor to reject it. > > I looked at the logs, and the configurations match what both the > upstream and downstream drivers are trying to do. > > The main differences between the configurations seem to be the > fractional component calculation and the computation of PLL_CMP. > > From my experience, minor changes in the fractional component don't > calculation doesn't cause too much of a difference. > > As an experiment, you could try to forcibly set the PLL_CMP value to > 7799 in the non-working case to check if that's causing the issue. > We could then try to find out from someone within Qualcomm if there's > a better way to compute this parameter. forcing PLL_CMP to 7799 worked :) Now trying with a different monitor. And it also fails :S This time with this modeline Modeline "1680x1050"x59.9 119.00 1680 1728 1760 1840 1050 1053 1059 1080 +hsync -vsync (64.7 kHz eP) [ 6.362578] VCO freq: 9520000000 [ 6.362582] fdata: 2380000000 [ 6.362584] pix_clk: 119000000 [ 6.362586] tmds clk: 119000000 [ 6.362588] HSCLK_SEL: 8 [ 6.362589] DEC_START: 123 [ 6.362591] DIV_FRAC_START: 1004885 [ 6.362592] PLL_CPCTRL: 11 [ 6.362594] PLL_RCTRL: 22 [ 6.362596] PLL_CCTRL: 40 [ 6.362597] INTEGLOOP_GAIN: 256 [ 6.362599] TX_BAND: 1 [ 6.362600] PLL_CMP: 12692 [ 6.362602] com_svs_mode_clk_sel = 0x2 [ 6.362604] com_hsclk_sel = 0x28 [ 6.362605] com_lock_cmp_en = 0x0 [ 6.362607] com_pll_cctrl_mode0 = 0x28 [ 6.362608] com_pll_rctrl_mode0 = 0x16 [ 6.362610] com_cp_ctrl_mode0 = 0xb [ 6.362611] com_dec_start_mode0 = 0x7b [ 6.362613] com_div_frac_start1_mode0 = 0x55 [ 6.362615] com_div_frac_start2_mode0 = 0x55 [ 6.362616] com_div_frac_start3_mode0 = 0xf [ 6.362617] com_integloop_gain0_mode0 = 0x0 [ 6.362619] com_integloop_gain1_mode0 = 0x1 [ 6.362621] com_lock_cmp1_mode0 = 0x94 [ 6.362622] com_lock_cmp2_mode0 = 0x31 [ 6.362624] com_lock_cmp3_mode0 = 0x0 [ 6.362625] com_core_clk_en = 0x2c [ 6.362627] com_coreclk_div = 0x5 [ 6.362628] phy_mode = 0x0 [ 6.362630] tx_l0_lane_mode = 0x43 [ 6.362631] tx_l2_lane_mode = 0x43 [ 6.362633] tx_l0_tx_band = 0x5 [ 6.362635] tx_l0_tx_drv_lvl = 0x25 [ 6.362636] tx_l0_tx_emp_post1_lvl = 0x23 [ 6.362638] tx_l0_vmode_ctrl1 = 0x0 [ 6.362640] tx_l0_vmode_ctrl2 = 0xd [ 6.362641] tx_l1_tx_band = 0x5 [ 6.362643] tx_l1_tx_drv_lvl = 0x25 [ 6.362644] tx_l1_tx_emp_post1_lvl = 0x23 [ 6.362646] tx_l1_vmode_ctrl1 = 0x0 [ 6.362647] tx_l1_vmode_ctrl2 = 0xd [ 6.362649] tx_l2_tx_band = 0x5 [ 6.362650] tx_l2_tx_drv_lvl = 0x25 [ 6.362652] tx_l2_tx_emp_post1_lvl = 0x23 [ 6.362653] tx_l2_vmode_ctrl1 = 0x0 [ 6.362655] tx_l2_vmode_ctrl2 = 0xd [ 6.362656] tx_l3_tx_band = 0x5 [ 6.362658] tx_l3_tx_drv_lvl = 0x25 [ 6.362659] tx_l3_tx_emp_post1_lvl = 0x23 [ 6.362661] tx_l3_vmode_ctrl1 = 0x0 [ 6.362662] tx_l3_vmode_ctrl2 = 0x0 [ 6.362663] Disabling PHY [ 6.363531] Waiting for PLL lock [ 6.364455] HDMI PLL is locked [ 6.364471] Waiting for PHY ready [ 6.364473] PHY is ready I have tried subtracting 3 to PLL_CMP, but that did not work also tried with 12687, which failed. On the other hand, the standard cvt for 1680x1050@60Hz worked just fine (like before) Thanks! > > Thanks, > Archit > > > > > > Where can I find that doc? > > Any ideas of how to proceed? > > > > > > Thanks! > > -- Ricardo Ribalda _______________________________________________ Freedreno mailing list Freedreno@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/freedreno ^ permalink raw reply [flat|nested] 11+ messages in thread
[parent not found: <CAPybu_0dMfaxBhybHapqfmjHVotA0BBsBs0cjYwdu4eaTT9rmQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>]
* Re: db820c: Input signal Out of range [not found] ` <CAPybu_0dMfaxBhybHapqfmjHVotA0BBsBs0cjYwdu4eaTT9rmQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> @ 2018-08-13 12:16 ` Archit Taneja [not found] ` <3007c578-59bf-9b16-25f3-2c97ae9486d0-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org> 0 siblings, 1 reply; 11+ messages in thread From: Archit Taneja @ 2018-08-13 12:16 UTC (permalink / raw) To: Ricardo Ribalda Delgado Cc: linux-arm-msm-u79uwXL29TY76Z2rM5mHXA, Rob Clark, Sibi S, vivek.gautam-sgV2jX0FEOL9JmXXK+q4OQ, alex-fkYMi7rYDl0, freedreno-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW Hi, On Monday 13 August 2018 02:24 PM, Ricardo Ribalda Delgado wrote: > Hi Archit > On Sun, Aug 12, 2018 at 9:47 AM Archit Taneja <architt@codeaurora.org> wrote: >> >> Hi, >> >> On Friday 10 August 2018 12:08 PM, Ricardo Ribalda Delgado wrote: >>> Hello >>> >>> I have a screen that via edid expects the following modeline by >>> default via detailed mode: >>> >>> Modeline "1680x1050"x60.0 146.30 1680 1784 1960 2240 1050 1053 1059 >>> 1089 +hsync -vsync >>> >>> When the card is configured to that modeline the screen cannot output >>> the image and shows the following error message: Input signal out of >>> range. >>> >>> I have tried with a different card and that exact modeline: >>> >>> xrandr --newmode fast 146.30 1680 1784 1960 2240 1050 1053 1059 1089 >>> +hsync -vsync >>> xrandr --addmode HDMI-1 slow >>> xrandr --output HDMI-1 --mode fast >>> >>> and the screen works just fine. >>> >>> >>> If I just tweak down a bit the clock: >>> xrandr --newmode slow 146.25 1680 1784 1960 2240 1050 1053 1059 1089 >>> +hsync -vsync >>> the screen shows an image as expected. >>> >>> I believe that there might be a misscalculation on the pll code. And I >>> am printing the debug info from: >>> drivers/gpu/drm/msm/hdmi/hdmi_phy_8996.c >>> >>> The configuration that fails shows: >>> >>> [ 138.553168] VCO freq: 8778000000 >>> [ 138.553172] fdata: 1463000000 >>> [ 138.553187] pix_clk: 146300000 >>> [ 138.555447] tmds clk: 146300000 >>> [ 138.558336] HSCLK_SEL: 1 >>> [ 138.561277] DEC_START: 114 >>> [ 138.564316] DIV_FRAC_START: 311296 >>> [ 138.567080] PLL_CPCTRL: 11 >>> [ 138.569614] PLL_RCTRL: 22 >>> [ 138.572996] PLL_CCTRL: 40 >>> [ 138.575698] INTEGLOOP_GAIN: 256 >>> [ 138.578366] TX_BAND: 0 >>> [ 138.580986] PLL_CMP: 7802 >>> [ 138.583936] com_svs_mode_clk_sel = 0x2 >>> [ 138.586351] com_hsclk_sel = 0x21 >>> [ 138.589067] com_lock_cmp_en = 0x0 >>> [ 138.592704] com_pll_cctrl_mode0 = 0x28 >>> [ 138.596089] com_pll_rctrl_mode0 = 0x16 >>> [ 138.599286] com_cp_ctrl_mode0 = 0xb >>> [ 138.602955] com_dec_start_mode0 = 0x72 >>> [ 138.606678] com_div_frac_start1_mode0 = 0x0 >>> [ 138.610064] com_div_frac_start2_mode0 = 0xc0 >>> [ 138.613894] com_div_frac_start3_mode0 = 0x4 >>> [ 138.617964] com_integloop_gain0_mode0 = 0x0 >>> [ 138.622478] com_integloop_gain1_mode0 = 0x1 >>> [ 138.626393] com_lock_cmp1_mode0 = 0x7a >>> [ 138.630550] com_lock_cmp2_mode0 = 0x1e >>> [ 138.634719] com_lock_cmp3_mode0 = 0x0 >>> [ 138.638545] com_core_clk_en = 0x2c >>> [ 138.642271] com_coreclk_div = 0x5 >>> [ 138.646001] phy_mode = 0x0 >>> [ 138.649308] tx_l0_lane_mode = 0x43 >>> [ 138.652684] tx_l2_lane_mode = 0x43 >>> [ 138.655275] tx_l0_tx_band = 0x4 >>> [ 138.658679] tx_l0_tx_drv_lvl = 0x25 >>> [ 138.662070] tx_l0_tx_emp_post1_lvl = 0x23 >>> [ 138.665101] tx_l0_vmode_ctrl1 = 0x0 >>> [ 138.668571] tx_l0_vmode_ctrl2 = 0xd >>> [ 138.672747] tx_l1_tx_band = 0x4 >>> [ 138.676037] tx_l1_tx_drv_lvl = 0x25 >>> [ 138.679493] tx_l1_tx_emp_post1_lvl = 0x23 >>> [ 138.682633] tx_l1_vmode_ctrl1 = 0x0 >>> [ 138.686117] tx_l1_vmode_ctrl2 = 0xd >>> [ 138.690272] tx_l2_tx_band = 0x4 >>> [ 138.693571] tx_l2_tx_drv_lvl = 0x25 >>> [ 138.697050] tx_l2_tx_emp_post1_lvl = 0x23 >>> [ 138.700168] tx_l2_vmode_ctrl1 = 0x0 >>> [ 138.703641] tx_l2_vmode_ctrl2 = 0xd >>> [ 138.707816] tx_l3_tx_band = 0x4 >>> [ 138.711092] tx_l3_tx_drv_lvl = 0x25 >>> [ 138.714577] tx_l3_tx_emp_post1_lvl = 0x23 >>> [ 138.717705] tx_l3_vmode_ctrl1 = 0x0 >>> [ 138.721182] tx_l3_vmode_ctrl2 = 0x0 >>> >>> and the configuration that works: >>> >>> [ 62.936970] VCO freq: 8775000000 >>> [ 62.936976] fdata: 1462500000 >>> [ 62.936990] pix_clk: 146250000 >>> [ 62.939250] tmds clk: 146250000 >>> [ 62.942175] HSCLK_SEL: 1 >>> [ 62.945095] DEC_START: 114 >>> [ 62.948117] DIV_FRAC_START: 270336 >>> [ 62.950881] PLL_CPCTRL: 11 >>> [ 62.953421] PLL_RCTRL: 22 >>> [ 62.956798] PLL_CCTRL: 40 >>> [ 62.959475] INTEGLOOP_GAIN: 256 >>> [ 62.962179] TX_BAND: 0 >>> [ 62.964785] PLL_CMP: 7799 >>> [ 62.967738] com_svs_mode_clk_sel = 0x2 >>> [ 62.970153] com_hsclk_sel = 0x21 >>> [ 62.972862] com_lock_cmp_en = 0x0 >>> [ 62.976506] com_pll_cctrl_mode0 = 0x28 >>> [ 62.979893] com_pll_rctrl_mode0 = 0x16 >>> [ 62.983088] com_cp_ctrl_mode0 = 0xb >>> [ 62.986749] com_dec_start_mode0 = 0x72 >>> [ 62.990480] com_div_frac_start1_mode0 = 0x0 >>> [ 62.993868] com_div_frac_start2_mode0 = 0x20 >>> [ 62.997688] com_div_frac_start3_mode0 = 0x4 >>> [ 63.001769] com_integloop_gain0_mode0 = 0x0 >>> [ 63.006281] com_integloop_gain1_mode0 = 0x1 >>> [ 63.010189] com_lock_cmp1_mode0 = 0x77 >>> [ 63.014354] com_lock_cmp2_mode0 = 0x1e >>> [ 63.018521] com_lock_cmp3_mode0 = 0x0 >>> [ 63.022338] com_core_clk_en = 0x2c >>> [ 63.026072] com_coreclk_div = 0x5 >>> [ 63.029804] phy_mode = 0x0 >>> [ 63.033103] tx_l0_lane_mode = 0x43 >>> [ 63.036488] tx_l2_lane_mode = 0x43 >>> [ 63.039078] tx_l0_tx_band = 0x4 >>> [ 63.042479] tx_l0_tx_drv_lvl = 0x25 >>> [ 63.045864] tx_l0_tx_emp_post1_lvl = 0x23 >>> [ 63.048901] tx_l0_vmode_ctrl1 = 0x0 >>> [ 63.052375] tx_l0_vmode_ctrl2 = 0xd >>> [ 63.056541] tx_l1_tx_band = 0x4 >>> [ 63.059840] tx_l1_tx_drv_lvl = 0x25 >>> [ 63.063295] tx_l1_tx_emp_post1_lvl = 0x23 >>> [ 63.066437] tx_l1_vmode_ctrl1 = 0x0 >>> [ 63.069908] tx_l1_vmode_ctrl2 = 0xd >>> [ 63.074075] tx_l2_tx_band = 0x4 >>> [ 63.077373] tx_l2_tx_drv_lvl = 0x25 >>> [ 63.080844] tx_l2_tx_emp_post1_lvl = 0x23 >>> [ 63.083971] tx_l2_vmode_ctrl1 = 0x0 >>> [ 63.087428] tx_l2_vmode_ctrl2 = 0xd >>> [ 63.091609] tx_l3_tx_band = 0x4 >>> [ 63.094906] tx_l3_tx_drv_lvl = 0x25 >>> [ 63.098379] tx_l3_tx_emp_post1_lvl = 0x23 >>> [ 63.101505] tx_l3_vmode_ctrl1 = 0x0 >>> [ 63.104979] tx_l3_vmode_ctrl2 = 0x0 >>> >>> Unfortunately I do not have the documentation of the pll to validade >>> any of the two setups. >> >> I'm not sure if there is any public documentation of the hardware >> registers for 8x96. I'd myself mostly ported this code from the >> downstream hdmi PLL driver (the 8996_v3 code in particular): >> >> https://source.codeaurora.org/quic/la/kernel/msm-3.18/tree/drivers/clk/msm/mdss/mdss-hdmi-pll-8996.c?h=msm-3.18 >> >> The PLL seems to be getting locked for both cases. But for some reason, >> when trying to configure it for 146.30 Mhz, it's generating a >> wayward enough value for the monitor to reject it. >> >> I looked at the logs, and the configurations match what both the >> upstream and downstream drivers are trying to do. >> >> The main differences between the configurations seem to be the >> fractional component calculation and the computation of PLL_CMP. >> >> From my experience, minor changes in the fractional component don't >> calculation doesn't cause too much of a difference. >> >> As an experiment, you could try to forcibly set the PLL_CMP value to >> 7799 in the non-working case to check if that's causing the issue. >> We could then try to find out from someone within Qualcomm if there's >> a better way to compute this parameter. > > forcing PLL_CMP to 7799 worked :) > > > Now trying with a different monitor. And it also fails :S This time > with this modeline > > Modeline "1680x1050"x59.9 119.00 1680 1728 1760 1840 1050 1053 1059 > 1080 +hsync -vsync (64.7 kHz eP) > > [ 6.362578] VCO freq: 9520000000 > [ 6.362582] fdata: 2380000000 > [ 6.362584] pix_clk: 119000000 > [ 6.362586] tmds clk: 119000000 > [ 6.362588] HSCLK_SEL: 8 > [ 6.362589] DEC_START: 123 > [ 6.362591] DIV_FRAC_START: 1004885 > [ 6.362592] PLL_CPCTRL: 11 > [ 6.362594] PLL_RCTRL: 22 > [ 6.362596] PLL_CCTRL: 40 > [ 6.362597] INTEGLOOP_GAIN: 256 > [ 6.362599] TX_BAND: 1 > [ 6.362600] PLL_CMP: 12692 > [ 6.362602] com_svs_mode_clk_sel = 0x2 > [ 6.362604] com_hsclk_sel = 0x28 > [ 6.362605] com_lock_cmp_en = 0x0 > [ 6.362607] com_pll_cctrl_mode0 = 0x28 > [ 6.362608] com_pll_rctrl_mode0 = 0x16 > [ 6.362610] com_cp_ctrl_mode0 = 0xb > [ 6.362611] com_dec_start_mode0 = 0x7b > [ 6.362613] com_div_frac_start1_mode0 = 0x55 > [ 6.362615] com_div_frac_start2_mode0 = 0x55 > [ 6.362616] com_div_frac_start3_mode0 = 0xf > [ 6.362617] com_integloop_gain0_mode0 = 0x0 > [ 6.362619] com_integloop_gain1_mode0 = 0x1 > [ 6.362621] com_lock_cmp1_mode0 = 0x94 > [ 6.362622] com_lock_cmp2_mode0 = 0x31 > [ 6.362624] com_lock_cmp3_mode0 = 0x0 > [ 6.362625] com_core_clk_en = 0x2c > [ 6.362627] com_coreclk_div = 0x5 > [ 6.362628] phy_mode = 0x0 > [ 6.362630] tx_l0_lane_mode = 0x43 > [ 6.362631] tx_l2_lane_mode = 0x43 > [ 6.362633] tx_l0_tx_band = 0x5 > [ 6.362635] tx_l0_tx_drv_lvl = 0x25 > [ 6.362636] tx_l0_tx_emp_post1_lvl = 0x23 > [ 6.362638] tx_l0_vmode_ctrl1 = 0x0 > [ 6.362640] tx_l0_vmode_ctrl2 = 0xd > [ 6.362641] tx_l1_tx_band = 0x5 > [ 6.362643] tx_l1_tx_drv_lvl = 0x25 > [ 6.362644] tx_l1_tx_emp_post1_lvl = 0x23 > [ 6.362646] tx_l1_vmode_ctrl1 = 0x0 > [ 6.362647] tx_l1_vmode_ctrl2 = 0xd > [ 6.362649] tx_l2_tx_band = 0x5 > [ 6.362650] tx_l2_tx_drv_lvl = 0x25 > [ 6.362652] tx_l2_tx_emp_post1_lvl = 0x23 > [ 6.362653] tx_l2_vmode_ctrl1 = 0x0 > [ 6.362655] tx_l2_vmode_ctrl2 = 0xd > [ 6.362656] tx_l3_tx_band = 0x5 > [ 6.362658] tx_l3_tx_drv_lvl = 0x25 > [ 6.362659] tx_l3_tx_emp_post1_lvl = 0x23 > [ 6.362661] tx_l3_vmode_ctrl1 = 0x0 > [ 6.362662] tx_l3_vmode_ctrl2 = 0x0 > [ 6.362663] Disabling PHY > [ 6.363531] Waiting for PLL lock > [ 6.364455] HDMI PLL is locked > [ 6.364471] Waiting for PHY ready > [ 6.364473] PHY is ready > > I have tried subtracting 3 to PLL_CMP, but that did not work > > also tried with 12687, which failed. > > On the other hand, the standard cvt for 1680x1050@60Hz worked just > fine (like before) +Sibi, Vivek Are you seeing issues only for this mode in particular(1680x1050)? I'm wondering if the issue is specific to a frequency range. One thing that the driver is missing is enabling spread spectrum clocking. I don't know if it will fix this issue, but it's generally nice to have enabled if EMI (which can happen with long HDMI cables) is a worry. It'll be nice if we could get some info on how to program it. Archit > > Thanks! > > >> >> Thanks, >> Archit >> >> >>> >>> Where can I find that doc? >>> Any ideas of how to proceed? >>> >>> >>> Thanks! >>> > > > > -- > Ricardo Ribalda > _______________________________________________ Freedreno mailing list Freedreno@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/freedreno ^ permalink raw reply [flat|nested] 11+ messages in thread
[parent not found: <3007c578-59bf-9b16-25f3-2c97ae9486d0-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>]
* Re: db820c: Input signal Out of range [not found] ` <3007c578-59bf-9b16-25f3-2c97ae9486d0-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org> @ 2018-08-13 12:18 ` Ricardo Ribalda Delgado [not found] ` <CAPybu_2cPoMG9zkM8oa3MOSpGg20L14JyWc_e+1cba3uaSz7iA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> 0 siblings, 1 reply; 11+ messages in thread From: Ricardo Ribalda Delgado @ 2018-08-13 12:18 UTC (permalink / raw) To: Archit Taneja Cc: linux-arm-msm-u79uwXL29TY76Z2rM5mHXA, Rob Clark, sibis-sgV2jX0FEOL9JmXXK+q4OQ, vivek.gautam-sgV2jX0FEOL9JmXXK+q4OQ, alex-fkYMi7rYDl0, freedreno-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW Hi Archit, On Mon, Aug 13, 2018 at 2:16 PM Archit Taneja <architt@codeaurora.org> wrote: > > Hi, > > > > On Monday 13 August 2018 02:24 PM, Ricardo Ribalda Delgado wrote: > > Hi Archit > > On Sun, Aug 12, 2018 at 9:47 AM Archit Taneja <architt@codeaurora.org> wrote: > >> > >> Hi, > >> > >> On Friday 10 August 2018 12:08 PM, Ricardo Ribalda Delgado wrote: > >>> Hello > >>> > >>> I have a screen that via edid expects the following modeline by > >>> default via detailed mode: > >>> > >>> Modeline "1680x1050"x60.0 146.30 1680 1784 1960 2240 1050 1053 1059 > >>> 1089 +hsync -vsync > >>> > >>> When the card is configured to that modeline the screen cannot output > >>> the image and shows the following error message: Input signal out of > >>> range. > >>> > >>> I have tried with a different card and that exact modeline: > >>> > >>> xrandr --newmode fast 146.30 1680 1784 1960 2240 1050 1053 1059 1089 > >>> +hsync -vsync > >>> xrandr --addmode HDMI-1 slow > >>> xrandr --output HDMI-1 --mode fast > >>> > >>> and the screen works just fine. > >>> > >>> > >>> If I just tweak down a bit the clock: > >>> xrandr --newmode slow 146.25 1680 1784 1960 2240 1050 1053 1059 1089 > >>> +hsync -vsync > >>> the screen shows an image as expected. > >>> > >>> I believe that there might be a misscalculation on the pll code. And I > >>> am printing the debug info from: > >>> drivers/gpu/drm/msm/hdmi/hdmi_phy_8996.c > >>> > >>> The configuration that fails shows: > >>> > >>> [ 138.553168] VCO freq: 8778000000 > >>> [ 138.553172] fdata: 1463000000 > >>> [ 138.553187] pix_clk: 146300000 > >>> [ 138.555447] tmds clk: 146300000 > >>> [ 138.558336] HSCLK_SEL: 1 > >>> [ 138.561277] DEC_START: 114 > >>> [ 138.564316] DIV_FRAC_START: 311296 > >>> [ 138.567080] PLL_CPCTRL: 11 > >>> [ 138.569614] PLL_RCTRL: 22 > >>> [ 138.572996] PLL_CCTRL: 40 > >>> [ 138.575698] INTEGLOOP_GAIN: 256 > >>> [ 138.578366] TX_BAND: 0 > >>> [ 138.580986] PLL_CMP: 7802 > >>> [ 138.583936] com_svs_mode_clk_sel = 0x2 > >>> [ 138.586351] com_hsclk_sel = 0x21 > >>> [ 138.589067] com_lock_cmp_en = 0x0 > >>> [ 138.592704] com_pll_cctrl_mode0 = 0x28 > >>> [ 138.596089] com_pll_rctrl_mode0 = 0x16 > >>> [ 138.599286] com_cp_ctrl_mode0 = 0xb > >>> [ 138.602955] com_dec_start_mode0 = 0x72 > >>> [ 138.606678] com_div_frac_start1_mode0 = 0x0 > >>> [ 138.610064] com_div_frac_start2_mode0 = 0xc0 > >>> [ 138.613894] com_div_frac_start3_mode0 = 0x4 > >>> [ 138.617964] com_integloop_gain0_mode0 = 0x0 > >>> [ 138.622478] com_integloop_gain1_mode0 = 0x1 > >>> [ 138.626393] com_lock_cmp1_mode0 = 0x7a > >>> [ 138.630550] com_lock_cmp2_mode0 = 0x1e > >>> [ 138.634719] com_lock_cmp3_mode0 = 0x0 > >>> [ 138.638545] com_core_clk_en = 0x2c > >>> [ 138.642271] com_coreclk_div = 0x5 > >>> [ 138.646001] phy_mode = 0x0 > >>> [ 138.649308] tx_l0_lane_mode = 0x43 > >>> [ 138.652684] tx_l2_lane_mode = 0x43 > >>> [ 138.655275] tx_l0_tx_band = 0x4 > >>> [ 138.658679] tx_l0_tx_drv_lvl = 0x25 > >>> [ 138.662070] tx_l0_tx_emp_post1_lvl = 0x23 > >>> [ 138.665101] tx_l0_vmode_ctrl1 = 0x0 > >>> [ 138.668571] tx_l0_vmode_ctrl2 = 0xd > >>> [ 138.672747] tx_l1_tx_band = 0x4 > >>> [ 138.676037] tx_l1_tx_drv_lvl = 0x25 > >>> [ 138.679493] tx_l1_tx_emp_post1_lvl = 0x23 > >>> [ 138.682633] tx_l1_vmode_ctrl1 = 0x0 > >>> [ 138.686117] tx_l1_vmode_ctrl2 = 0xd > >>> [ 138.690272] tx_l2_tx_band = 0x4 > >>> [ 138.693571] tx_l2_tx_drv_lvl = 0x25 > >>> [ 138.697050] tx_l2_tx_emp_post1_lvl = 0x23 > >>> [ 138.700168] tx_l2_vmode_ctrl1 = 0x0 > >>> [ 138.703641] tx_l2_vmode_ctrl2 = 0xd > >>> [ 138.707816] tx_l3_tx_band = 0x4 > >>> [ 138.711092] tx_l3_tx_drv_lvl = 0x25 > >>> [ 138.714577] tx_l3_tx_emp_post1_lvl = 0x23 > >>> [ 138.717705] tx_l3_vmode_ctrl1 = 0x0 > >>> [ 138.721182] tx_l3_vmode_ctrl2 = 0x0 > >>> > >>> and the configuration that works: > >>> > >>> [ 62.936970] VCO freq: 8775000000 > >>> [ 62.936976] fdata: 1462500000 > >>> [ 62.936990] pix_clk: 146250000 > >>> [ 62.939250] tmds clk: 146250000 > >>> [ 62.942175] HSCLK_SEL: 1 > >>> [ 62.945095] DEC_START: 114 > >>> [ 62.948117] DIV_FRAC_START: 270336 > >>> [ 62.950881] PLL_CPCTRL: 11 > >>> [ 62.953421] PLL_RCTRL: 22 > >>> [ 62.956798] PLL_CCTRL: 40 > >>> [ 62.959475] INTEGLOOP_GAIN: 256 > >>> [ 62.962179] TX_BAND: 0 > >>> [ 62.964785] PLL_CMP: 7799 > >>> [ 62.967738] com_svs_mode_clk_sel = 0x2 > >>> [ 62.970153] com_hsclk_sel = 0x21 > >>> [ 62.972862] com_lock_cmp_en = 0x0 > >>> [ 62.976506] com_pll_cctrl_mode0 = 0x28 > >>> [ 62.979893] com_pll_rctrl_mode0 = 0x16 > >>> [ 62.983088] com_cp_ctrl_mode0 = 0xb > >>> [ 62.986749] com_dec_start_mode0 = 0x72 > >>> [ 62.990480] com_div_frac_start1_mode0 = 0x0 > >>> [ 62.993868] com_div_frac_start2_mode0 = 0x20 > >>> [ 62.997688] com_div_frac_start3_mode0 = 0x4 > >>> [ 63.001769] com_integloop_gain0_mode0 = 0x0 > >>> [ 63.006281] com_integloop_gain1_mode0 = 0x1 > >>> [ 63.010189] com_lock_cmp1_mode0 = 0x77 > >>> [ 63.014354] com_lock_cmp2_mode0 = 0x1e > >>> [ 63.018521] com_lock_cmp3_mode0 = 0x0 > >>> [ 63.022338] com_core_clk_en = 0x2c > >>> [ 63.026072] com_coreclk_div = 0x5 > >>> [ 63.029804] phy_mode = 0x0 > >>> [ 63.033103] tx_l0_lane_mode = 0x43 > >>> [ 63.036488] tx_l2_lane_mode = 0x43 > >>> [ 63.039078] tx_l0_tx_band = 0x4 > >>> [ 63.042479] tx_l0_tx_drv_lvl = 0x25 > >>> [ 63.045864] tx_l0_tx_emp_post1_lvl = 0x23 > >>> [ 63.048901] tx_l0_vmode_ctrl1 = 0x0 > >>> [ 63.052375] tx_l0_vmode_ctrl2 = 0xd > >>> [ 63.056541] tx_l1_tx_band = 0x4 > >>> [ 63.059840] tx_l1_tx_drv_lvl = 0x25 > >>> [ 63.063295] tx_l1_tx_emp_post1_lvl = 0x23 > >>> [ 63.066437] tx_l1_vmode_ctrl1 = 0x0 > >>> [ 63.069908] tx_l1_vmode_ctrl2 = 0xd > >>> [ 63.074075] tx_l2_tx_band = 0x4 > >>> [ 63.077373] tx_l2_tx_drv_lvl = 0x25 > >>> [ 63.080844] tx_l2_tx_emp_post1_lvl = 0x23 > >>> [ 63.083971] tx_l2_vmode_ctrl1 = 0x0 > >>> [ 63.087428] tx_l2_vmode_ctrl2 = 0xd > >>> [ 63.091609] tx_l3_tx_band = 0x4 > >>> [ 63.094906] tx_l3_tx_drv_lvl = 0x25 > >>> [ 63.098379] tx_l3_tx_emp_post1_lvl = 0x23 > >>> [ 63.101505] tx_l3_vmode_ctrl1 = 0x0 > >>> [ 63.104979] tx_l3_vmode_ctrl2 = 0x0 > >>> > >>> Unfortunately I do not have the documentation of the pll to validade > >>> any of the two setups. > >> > >> I'm not sure if there is any public documentation of the hardware > >> registers for 8x96. I'd myself mostly ported this code from the > >> downstream hdmi PLL driver (the 8996_v3 code in particular): > >> > >> https://source.codeaurora.org/quic/la/kernel/msm-3.18/tree/drivers/clk/msm/mdss/mdss-hdmi-pll-8996.c?h=msm-3.18 > >> > >> The PLL seems to be getting locked for both cases. But for some reason, > >> when trying to configure it for 146.30 Mhz, it's generating a > >> wayward enough value for the monitor to reject it. > >> > >> I looked at the logs, and the configurations match what both the > >> upstream and downstream drivers are trying to do. > >> > >> The main differences between the configurations seem to be the > >> fractional component calculation and the computation of PLL_CMP. > >> > >> From my experience, minor changes in the fractional component don't > >> calculation doesn't cause too much of a difference. > >> > >> As an experiment, you could try to forcibly set the PLL_CMP value to > >> 7799 in the non-working case to check if that's causing the issue. > >> We could then try to find out from someone within Qualcomm if there's > >> a better way to compute this parameter. > > > > forcing PLL_CMP to 7799 worked :) > > > > > > Now trying with a different monitor. And it also fails :S This time > > with this modeline > > > > Modeline "1680x1050"x59.9 119.00 1680 1728 1760 1840 1050 1053 1059 > > 1080 +hsync -vsync (64.7 kHz eP) > > > > [ 6.362578] VCO freq: 9520000000 > > [ 6.362582] fdata: 2380000000 > > [ 6.362584] pix_clk: 119000000 > > [ 6.362586] tmds clk: 119000000 > > [ 6.362588] HSCLK_SEL: 8 > > [ 6.362589] DEC_START: 123 > > [ 6.362591] DIV_FRAC_START: 1004885 > > [ 6.362592] PLL_CPCTRL: 11 > > [ 6.362594] PLL_RCTRL: 22 > > [ 6.362596] PLL_CCTRL: 40 > > [ 6.362597] INTEGLOOP_GAIN: 256 > > [ 6.362599] TX_BAND: 1 > > [ 6.362600] PLL_CMP: 12692 > > [ 6.362602] com_svs_mode_clk_sel = 0x2 > > [ 6.362604] com_hsclk_sel = 0x28 > > [ 6.362605] com_lock_cmp_en = 0x0 > > [ 6.362607] com_pll_cctrl_mode0 = 0x28 > > [ 6.362608] com_pll_rctrl_mode0 = 0x16 > > [ 6.362610] com_cp_ctrl_mode0 = 0xb > > [ 6.362611] com_dec_start_mode0 = 0x7b > > [ 6.362613] com_div_frac_start1_mode0 = 0x55 > > [ 6.362615] com_div_frac_start2_mode0 = 0x55 > > [ 6.362616] com_div_frac_start3_mode0 = 0xf > > [ 6.362617] com_integloop_gain0_mode0 = 0x0 > > [ 6.362619] com_integloop_gain1_mode0 = 0x1 > > [ 6.362621] com_lock_cmp1_mode0 = 0x94 > > [ 6.362622] com_lock_cmp2_mode0 = 0x31 > > [ 6.362624] com_lock_cmp3_mode0 = 0x0 > > [ 6.362625] com_core_clk_en = 0x2c > > [ 6.362627] com_coreclk_div = 0x5 > > [ 6.362628] phy_mode = 0x0 > > [ 6.362630] tx_l0_lane_mode = 0x43 > > [ 6.362631] tx_l2_lane_mode = 0x43 > > [ 6.362633] tx_l0_tx_band = 0x5 > > [ 6.362635] tx_l0_tx_drv_lvl = 0x25 > > [ 6.362636] tx_l0_tx_emp_post1_lvl = 0x23 > > [ 6.362638] tx_l0_vmode_ctrl1 = 0x0 > > [ 6.362640] tx_l0_vmode_ctrl2 = 0xd > > [ 6.362641] tx_l1_tx_band = 0x5 > > [ 6.362643] tx_l1_tx_drv_lvl = 0x25 > > [ 6.362644] tx_l1_tx_emp_post1_lvl = 0x23 > > [ 6.362646] tx_l1_vmode_ctrl1 = 0x0 > > [ 6.362647] tx_l1_vmode_ctrl2 = 0xd > > [ 6.362649] tx_l2_tx_band = 0x5 > > [ 6.362650] tx_l2_tx_drv_lvl = 0x25 > > [ 6.362652] tx_l2_tx_emp_post1_lvl = 0x23 > > [ 6.362653] tx_l2_vmode_ctrl1 = 0x0 > > [ 6.362655] tx_l2_vmode_ctrl2 = 0xd > > [ 6.362656] tx_l3_tx_band = 0x5 > > [ 6.362658] tx_l3_tx_drv_lvl = 0x25 > > [ 6.362659] tx_l3_tx_emp_post1_lvl = 0x23 > > [ 6.362661] tx_l3_vmode_ctrl1 = 0x0 > > [ 6.362662] tx_l3_vmode_ctrl2 = 0x0 > > [ 6.362663] Disabling PHY > > [ 6.363531] Waiting for PLL lock > > [ 6.364455] HDMI PLL is locked > > [ 6.364471] Waiting for PHY ready > > [ 6.364473] PHY is ready > > > > I have tried subtracting 3 to PLL_CMP, but that did not work > > > > also tried with 12687, which failed. > > > > On the other hand, the standard cvt for 1680x1050@60Hz worked just > > fine (like before) > > +Sibi, Vivek > > Are you seeing issues only for this mode in particular(1680x1050)? I'm > wondering if the issue is specific to a frequency range. > I have only tried with the native resolution of the panel, which on both screens in 1680x1050 I will try different resolution and paste the results. > One thing that the driver is missing is enabling spread spectrum > clocking. I don't know if it will fix this issue, but it's generally > nice to have enabled if EMI (which can happen with long HDMI cables) > is a worry. It'll be nice if we could get some info on how to program Cabling should not be an issue here. I am using short and high quality cables on my setup, to rule out EMI as much as possible. Thanks! > it. > > Archit > > > > > Thanks! > > > > > >> > >> Thanks, > >> Archit > >> > >> > >>> > >>> Where can I find that doc? > >>> Any ideas of how to proceed? > >>> > >>> > >>> Thanks! > >>> > > > > > > > > -- > > Ricardo Ribalda > > -- Ricardo Ribalda _______________________________________________ Freedreno mailing list Freedreno@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/freedreno ^ permalink raw reply [flat|nested] 11+ messages in thread
[parent not found: <CAPybu_2cPoMG9zkM8oa3MOSpGg20L14JyWc_e+1cba3uaSz7iA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>]
* Re: db820c: Input signal Out of range [not found] ` <CAPybu_2cPoMG9zkM8oa3MOSpGg20L14JyWc_e+1cba3uaSz7iA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> @ 2018-08-13 12:41 ` Ricardo Ribalda Delgado [not found] ` <CAPybu_1PGuTNaxEzFG86JzysQFPyoV4BpQ79j_-wAGqEAM8BNQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> 0 siblings, 1 reply; 11+ messages in thread From: Ricardo Ribalda Delgado @ 2018-08-13 12:41 UTC (permalink / raw) To: Archit Taneja Cc: linux-arm-msm-u79uwXL29TY76Z2rM5mHXA, Rob Clark, sibis-sgV2jX0FEOL9JmXXK+q4OQ, vivek.gautam-sgV2jX0FEOL9JmXXK+q4OQ, alex-fkYMi7rYDl0, freedreno-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW Hello again > On Mon, Aug 13, 2018 at 2:16 PM Archit Taneja <architt@codeaurora.org> wrote: > > > > Are you seeing issues only for this mode in particular(1680x1050)? I'm > > wondering if the issue is specific to a frequency range. > > > > I have only tried with the native resolution of the panel, which on > both screens in 1680x1050 Result of the tests Screen 1 (Lenovo) FAILS: xrandr --output HDMI-1 --mode 1600x1000 --rate 60.01 OK: xrandr --output HDMI-1 --mode 1280x1024 --rate 75.02 FAILS: xrandr --output HDMI-1 --mode 1280x1024 --rate 72.05 FAILS: xrandr --output HDMI-1 --mode 1280x1024 --rate 60.02 OK: xrandr --output HDMI-1 --mode 1440x900 --rate 74.98 OK: xrandr --output HDMI-1 --mode 1440x900 --rate 59.90 FAILS: xrandr --output HDMI-1 --mode 1152x864 --rate 75.00 OK: xrandr --output HDMI-1 --mode 1024x768 --rate 75.03 OK: xrandr --output HDMI-1 --mode 1024x768 --rate 70.07 FAILS: xrandr --output HDMI-1 --mode 1024x768 --rate 60.00 FAILS: xrandr --output HDMI-1 --mode 800x600 --rate 72.19 FAILS: xrandr --output HDMI-1 --mode 800x600 --rate 75.00 OK: xrandr --output HDMI-1 --mode 800x600 --rate 60.32 OK: xrandr --output HDMI-1 --mode 640x480 --rate 75.00 OK: xrandr --output HDMI-1 --mode 640x480 --rate 72.81 FAILS: xrandr --output HDMI-1 --mode 640x480 --rate 66.67 FAILS: xrandr --output HDMI-1 --mode 640x480 --rate 59.94 FAILS:xrandr --output HDMI-1 --mode 720x400 --rate 70.08 [ 16.216] (II) modeset(0): EDID (in hex): [ 16.216] (II) modeset(0): 00ffffffffffff0030ae0c0a01010101 [ 16.216] (II) modeset(0): 1e140103802f1e78eedc55a359489e24 [ 16.216] (II) modeset(0): 115054bdcf00714f8180818c9500950f [ 16.216] (II) modeset(0): a900b300010126399030621a274068b0 [ 16.216] (II) modeset(0): 3600da281100001a000000fd00324b1e [ 16.216] (II) modeset(0): 5311000a202020202020000000fc004c [ 16.216] (II) modeset(0): 323235307020576964652020000000ff [ 16.217] (II) modeset(0): 0036563656373533330a2020202000a8 [ 16.217] (II) modeset(0): Printing probed modes for output HDMI-1 [ 16.217] (II) modeset(0): Modeline "1680x1050"x60.0 146.30 1680 1784 1960 2240 1050 1053 1059 1089 +hsync -vsync (65.3 kHz eP) [ 16.217] (II) modeset(0): Modeline "1600x1000"x60.0 133.16 1600 1704 1872 2144 1000 1001 1004 1035 -hsync +vsync (62.1 kHz) [ 16.217] (II) modeset(0): Modeline "1280x1024"x75.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e) [ 16.217] (II) modeset(0): Modeline "1280x1024"x72.0 132.84 1280 1368 1504 1728 1024 1025 1028 1067 -hsync +vsync (76.9 kHz) [ 16.217] (II) modeset(0): Modeline "1280x1024"x60.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e) [ 16.217] (II) modeset(0): Modeline "1440x900"x75.0 136.75 1440 1536 1688 1936 900 903 909 942 -hsync +vsync (70.6 kHz e) [ 16.217] (II) modeset(0): Modeline "1440x900"x59.9 88.75 1440 1488 1520 1600 900 903 909 926 +hsync -vsync (55.5 kHz e) [ 16.217] (II) modeset(0): Modeline "1152x864"x75.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e) [ 16.217] (II) modeset(0): Modeline "1024x768"x75.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz e) [ 16.217] (II) modeset(0): Modeline "1024x768"x70.1 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz e) [ 16.217] (II) modeset(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e) [ 16.217] (II) modeset(0): Modeline "800x600"x72.2 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync (48.1 kHz e) [ 16.217] (II) modeset(0): Modeline "800x600"x75.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e) [ 16.217] (II) modeset(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e) [ 16.217] (II) modeset(0): Modeline "640x480"x75.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e) [ 16.217] (II) modeset(0): Modeline "640x480"x72.8 31.50 640 664 704 832 480 489 492 520 -hsync -vsync (37.9 kHz e) [ 16.217] (II) modeset(0): Modeline "640x480"x66.7 30.24 640 704 768 864 480 483 486 525 -hsync -vsync (35.0 kHz e) [ 16.217] (II) modeset(0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e) [ 16.217] (II) modeset(0): Modeline "720x400"x70.1 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e) Screen 2 (Samsung) OK: xrandr --output HDMI-1 --mode 1280x1024 --rate 75.02 FAILS: xrandr --output HDMI-1 --mode 1280x1024 --rate 60.02 FAILS: xrandr --output HDMI-1 --mode 1280x960 --rate 60.00 FAILS: xrandr --output HDMI-1 --mode 1152x864 --rate 75.00 OK: xrandr --output HDMI-1 --mode 1024x768 --rate 75.03 OK: xrandr --output HDMI-1 --mode 1024x768 --rate 70.07 FAILS: xrandr --output HDMI-1 --mode 1024x768 --rate 60.00 OK: xrandr --output HDMI-1 --mode 832x624 --rate 74.55 FAILS: xrandr --output HDMI-1 --mode 800x600 --rate 72.19 FAILS: xrandr --output HDMI-1 --mode 800x600 --rate 75.00 OK: xrandr --output HDMI-1 --mode 800x600 --rate 60.32 FAILS: xrandr --output HDMI-1 --mode 800x600 --rate 56.25 OK: xrandr --output HDMI-1 --mode 640x480 --rate 75.00 OK: xrandr --output HDMI-1 --mode 640x480 --rate 72.81 FAILS: xrandr --output HDMI-1 --mode 640x480 --rate 66.67 FAILS: xrandr --output HDMI-1 --mode 640x480 --rate 59.94 FAILS: xrandr --output HDMI-1 --mode 720x400 --rate 70.08 [ 16.820] (II) modeset(0): EDID (in hex): [ 16.820] (II) modeset(0): 00ffffffffffff004c2d040332324550 [ 16.820] (II) modeset(0): 1d120103803120782a9345a3554a9827 [ 16.820] (II) modeset(0): 155054bfef80b30081808140714f0101 [ 16.820] (II) modeset(0): 0101010101017c2e90a0601a1e403020 [ 16.820] (II) modeset(0): 3600ee401100001a000000fd00384b1e [ 16.820] (II) modeset(0): 510e000a202020202020000000fc0053 [ 16.820] (II) modeset(0): 796e634d61737465720a2020000000ff [ 16.820] (II) modeset(0): 00483958513730313333330a2020009f [ 16.821] (II) modeset(0): Printing probed modes for output HDMI-1 [ 16.821] (II) modeset(0): Modeline "1680x1050"x59.9 119.00 1680 1728 1760 1840 1050 1053 1059 1080 +hsync -vsync (64.7 kHz eP) [ 16.821] (II) modeset(0): Modeline "1280x1024"x75.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e) [ 16.821] (II) modeset(0): Modeline "1280x1024"x60.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e) [ 16.821] (II) modeset(0): Modeline "1280x960"x60.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz e) [ 16.821] (II) modeset(0): Modeline "1152x864"x75.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e) [ 16.821] (II) modeset(0): Modeline "1024x768"x75.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz e) [ 16.821] (II) modeset(0): Modeline "1024x768"x70.1 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz e) [ 16.821] (II) modeset(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e) [ 16.821] (II) modeset(0): Modeline "832x624"x74.6 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz e) [ 16.821] (II) modeset(0): Modeline "800x600"x72.2 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync (48.1 kHz e) [ 16.821] (II) modeset(0): Modeline "800x600"x75.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e) [ 16.821] (II) modeset(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e) [ 16.821] (II) modeset(0): Modeline "800x600"x56.2 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz e) [ 16.821] (II) modeset(0): Modeline "640x480"x75.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e) [ 16.821] (II) modeset(0): Modeline "640x480"x72.8 31.50 640 664 704 832 480 489 492 520 -hsync -vsync (37.9 kHz e) [ 16.821] (II) modeset(0): Modeline "640x480"x66.7 30.24 640 704 768 864 480 483 486 525 -hsync -vsync (35.0 kHz e) [ 16.821] (II) modeset(0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e) [ 16.821] (II) modeset(0): Modeline "720x400"x70.1 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e) -- Ricardo Ribalda _______________________________________________ Freedreno mailing list Freedreno@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/freedreno ^ permalink raw reply [flat|nested] 11+ messages in thread
[parent not found: <CAPybu_1PGuTNaxEzFG86JzysQFPyoV4BpQ79j_-wAGqEAM8BNQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>]
* Re: db820c: Input signal Out of range [not found] ` <CAPybu_1PGuTNaxEzFG86JzysQFPyoV4BpQ79j_-wAGqEAM8BNQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> @ 2018-08-14 6:10 ` Archit Taneja [not found] ` <dee8b931-321e-a4a1-18e7-b5467c3348d0-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org> 0 siblings, 1 reply; 11+ messages in thread From: Archit Taneja @ 2018-08-14 6:10 UTC (permalink / raw) To: Ricardo Ribalda Delgado Cc: linux-arm-msm-u79uwXL29TY76Z2rM5mHXA, Rob Clark, sibis-sgV2jX0FEOL9JmXXK+q4OQ, vivek.gautam-sgV2jX0FEOL9JmXXK+q4OQ, alex-fkYMi7rYDl0, freedreno-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW On Monday 13 August 2018 06:11 PM, Ricardo Ribalda Delgado wrote: > Hello again > >> On Mon, Aug 13, 2018 at 2:16 PM Archit Taneja <architt@codeaurora.org> wrote: > >>> >>> Are you seeing issues only for this mode in particular(1680x1050)? I'm >>> wondering if the issue is specific to a frequency range. >>> >> >> I have only tried with the native resolution of the panel, which on >> both screens in 1680x1050 > > Result of the tests > > Screen 1 (Lenovo) > > FAILS: xrandr --output HDMI-1 --mode 1600x1000 --rate 60.01 > OK: xrandr --output HDMI-1 --mode 1280x1024 --rate 75.02 > FAILS: xrandr --output HDMI-1 --mode 1280x1024 --rate 72.05 > FAILS: xrandr --output HDMI-1 --mode 1280x1024 --rate 60.02 > OK: xrandr --output HDMI-1 --mode 1440x900 --rate 74.98 > OK: xrandr --output HDMI-1 --mode 1440x900 --rate 59.90 > FAILS: xrandr --output HDMI-1 --mode 1152x864 --rate 75.00 > OK: xrandr --output HDMI-1 --mode 1024x768 --rate 75.03 > OK: xrandr --output HDMI-1 --mode 1024x768 --rate 70.07 > FAILS: xrandr --output HDMI-1 --mode 1024x768 --rate 60.00 > FAILS: xrandr --output HDMI-1 --mode 800x600 --rate 72.19 > FAILS: xrandr --output HDMI-1 --mode 800x600 --rate 75.00 > OK: xrandr --output HDMI-1 --mode 800x600 --rate 60.32 > OK: xrandr --output HDMI-1 --mode 640x480 --rate 75.00 > OK: xrandr --output HDMI-1 --mode 640x480 --rate 72.81 > FAILS: xrandr --output HDMI-1 --mode 640x480 --rate 66.67 > FAILS: xrandr --output HDMI-1 --mode 640x480 --rate 59.94 > FAILS:xrandr --output HDMI-1 --mode 720x400 --rate 70.08 > Thanks for the info. The number of failed modes is quite bad, and across a wide range of modes. Another query: Does the mode fail to set every time you set it? i.e, if we call the following successively, do we get the "out of range" issue every time? xrandr --output HDMI-1 --mode 1600x1000 --rate 60.01 I'd looped in some friends who can help verify if the driver is configuring the regs correctly. Thanks, Archit > > [ 16.216] (II) modeset(0): EDID (in hex): > [ 16.216] (II) modeset(0): 00ffffffffffff0030ae0c0a01010101 > [ 16.216] (II) modeset(0): 1e140103802f1e78eedc55a359489e24 > [ 16.216] (II) modeset(0): 115054bdcf00714f8180818c9500950f > [ 16.216] (II) modeset(0): a900b300010126399030621a274068b0 > [ 16.216] (II) modeset(0): 3600da281100001a000000fd00324b1e > [ 16.216] (II) modeset(0): 5311000a202020202020000000fc004c > [ 16.216] (II) modeset(0): 323235307020576964652020000000ff > [ 16.217] (II) modeset(0): 0036563656373533330a2020202000a8 > [ 16.217] (II) modeset(0): Printing probed modes for output HDMI-1 > [ 16.217] (II) modeset(0): Modeline "1680x1050"x60.0 146.30 1680 > 1784 1960 2240 1050 1053 1059 1089 +hsync -vsync (65.3 kHz eP) > [ 16.217] (II) modeset(0): Modeline "1600x1000"x60.0 133.16 1600 > 1704 1872 2144 1000 1001 1004 1035 -hsync +vsync (62.1 kHz) > [ 16.217] (II) modeset(0): Modeline "1280x1024"x75.0 135.00 1280 > 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e) > [ 16.217] (II) modeset(0): Modeline "1280x1024"x72.0 132.84 1280 > 1368 1504 1728 1024 1025 1028 1067 -hsync +vsync (76.9 kHz) > [ 16.217] (II) modeset(0): Modeline "1280x1024"x60.0 108.00 1280 > 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e) > [ 16.217] (II) modeset(0): Modeline "1440x900"x75.0 136.75 1440 > 1536 1688 1936 900 903 909 942 -hsync +vsync (70.6 kHz e) > [ 16.217] (II) modeset(0): Modeline "1440x900"x59.9 88.75 1440 > 1488 1520 1600 900 903 909 926 +hsync -vsync (55.5 kHz e) > [ 16.217] (II) modeset(0): Modeline "1152x864"x75.0 108.00 1152 > 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e) > [ 16.217] (II) modeset(0): Modeline "1024x768"x75.0 78.75 1024 > 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz e) > [ 16.217] (II) modeset(0): Modeline "1024x768"x70.1 75.00 1024 > 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz e) > [ 16.217] (II) modeset(0): Modeline "1024x768"x60.0 65.00 1024 > 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e) > [ 16.217] (II) modeset(0): Modeline "800x600"x72.2 50.00 800 856 > 976 1040 600 637 643 666 +hsync +vsync (48.1 kHz e) > [ 16.217] (II) modeset(0): Modeline "800x600"x75.0 49.50 800 816 > 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e) > [ 16.217] (II) modeset(0): Modeline "800x600"x60.3 40.00 800 840 > 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e) > [ 16.217] (II) modeset(0): Modeline "640x480"x75.0 31.50 640 656 > 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e) > [ 16.217] (II) modeset(0): Modeline "640x480"x72.8 31.50 640 664 > 704 832 480 489 492 520 -hsync -vsync (37.9 kHz e) > [ 16.217] (II) modeset(0): Modeline "640x480"x66.7 30.24 640 704 > 768 864 480 483 486 525 -hsync -vsync (35.0 kHz e) > [ 16.217] (II) modeset(0): Modeline "640x480"x59.9 25.18 640 656 > 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e) > [ 16.217] (II) modeset(0): Modeline "720x400"x70.1 28.32 720 738 > 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e) > > Screen 2 (Samsung) > > OK: xrandr --output HDMI-1 --mode 1280x1024 --rate 75.02 > FAILS: xrandr --output HDMI-1 --mode 1280x1024 --rate 60.02 > FAILS: xrandr --output HDMI-1 --mode 1280x960 --rate 60.00 > FAILS: xrandr --output HDMI-1 --mode 1152x864 --rate 75.00 > OK: xrandr --output HDMI-1 --mode 1024x768 --rate 75.03 > OK: xrandr --output HDMI-1 --mode 1024x768 --rate 70.07 > FAILS: xrandr --output HDMI-1 --mode 1024x768 --rate 60.00 > OK: xrandr --output HDMI-1 --mode 832x624 --rate 74.55 > FAILS: xrandr --output HDMI-1 --mode 800x600 --rate 72.19 > FAILS: xrandr --output HDMI-1 --mode 800x600 --rate 75.00 > OK: xrandr --output HDMI-1 --mode 800x600 --rate 60.32 > FAILS: xrandr --output HDMI-1 --mode 800x600 --rate 56.25 > OK: xrandr --output HDMI-1 --mode 640x480 --rate 75.00 > OK: xrandr --output HDMI-1 --mode 640x480 --rate 72.81 > FAILS: xrandr --output HDMI-1 --mode 640x480 --rate 66.67 > FAILS: xrandr --output HDMI-1 --mode 640x480 --rate 59.94 > FAILS: xrandr --output HDMI-1 --mode 720x400 --rate 70.08 > > > [ 16.820] (II) modeset(0): EDID (in hex): > [ 16.820] (II) modeset(0): 00ffffffffffff004c2d040332324550 > [ 16.820] (II) modeset(0): 1d120103803120782a9345a3554a9827 > [ 16.820] (II) modeset(0): 155054bfef80b30081808140714f0101 > [ 16.820] (II) modeset(0): 0101010101017c2e90a0601a1e403020 > [ 16.820] (II) modeset(0): 3600ee401100001a000000fd00384b1e > [ 16.820] (II) modeset(0): 510e000a202020202020000000fc0053 > [ 16.820] (II) modeset(0): 796e634d61737465720a2020000000ff > [ 16.820] (II) modeset(0): 00483958513730313333330a2020009f > [ 16.821] (II) modeset(0): Printing probed modes for output HDMI-1 > [ 16.821] (II) modeset(0): Modeline "1680x1050"x59.9 119.00 1680 > 1728 1760 1840 1050 1053 1059 1080 +hsync -vsync (64.7 kHz eP) > [ 16.821] (II) modeset(0): Modeline "1280x1024"x75.0 135.00 1280 > 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e) > [ 16.821] (II) modeset(0): Modeline "1280x1024"x60.0 108.00 1280 > 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e) > [ 16.821] (II) modeset(0): Modeline "1280x960"x60.0 108.00 1280 > 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz e) > [ 16.821] (II) modeset(0): Modeline "1152x864"x75.0 108.00 1152 > 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e) > [ 16.821] (II) modeset(0): Modeline "1024x768"x75.0 78.75 1024 > 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz e) > [ 16.821] (II) modeset(0): Modeline "1024x768"x70.1 75.00 1024 > 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz e) > [ 16.821] (II) modeset(0): Modeline "1024x768"x60.0 65.00 1024 > 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e) > [ 16.821] (II) modeset(0): Modeline "832x624"x74.6 57.28 832 864 > 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz e) > [ 16.821] (II) modeset(0): Modeline "800x600"x72.2 50.00 800 856 > 976 1040 600 637 643 666 +hsync +vsync (48.1 kHz e) > [ 16.821] (II) modeset(0): Modeline "800x600"x75.0 49.50 800 816 > 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e) > [ 16.821] (II) modeset(0): Modeline "800x600"x60.3 40.00 800 840 > 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e) > [ 16.821] (II) modeset(0): Modeline "800x600"x56.2 36.00 800 824 > 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz e) > [ 16.821] (II) modeset(0): Modeline "640x480"x75.0 31.50 640 656 > 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e) > [ 16.821] (II) modeset(0): Modeline "640x480"x72.8 31.50 640 664 > 704 832 480 489 492 520 -hsync -vsync (37.9 kHz e) > [ 16.821] (II) modeset(0): Modeline "640x480"x66.7 30.24 640 704 > 768 864 480 483 486 525 -hsync -vsync (35.0 kHz e) > [ 16.821] (II) modeset(0): Modeline "640x480"x59.9 25.18 640 656 > 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e) > [ 16.821] (II) modeset(0): Modeline "720x400"x70.1 28.32 720 738 > 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e) > > _______________________________________________ Freedreno mailing list Freedreno@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/freedreno ^ permalink raw reply [flat|nested] 11+ messages in thread
[parent not found: <dee8b931-321e-a4a1-18e7-b5467c3348d0-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>]
* Re: db820c: Input signal Out of range [not found] ` <dee8b931-321e-a4a1-18e7-b5467c3348d0-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org> @ 2018-08-15 14:10 ` Ricardo Ribalda Delgado [not found] ` <CAPybu_0Lvcv8AUt16wfaPQhzMdVhWrAD4khdkP6P-_T8Ud0k6g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> 0 siblings, 1 reply; 11+ messages in thread From: Ricardo Ribalda Delgado @ 2018-08-15 14:10 UTC (permalink / raw) To: Archit Taneja Cc: linux-arm-msm-u79uwXL29TY76Z2rM5mHXA, Rob Clark, sibis-sgV2jX0FEOL9JmXXK+q4OQ, vivek.gautam-sgV2jX0FEOL9JmXXK+q4OQ, alex-fkYMi7rYDl0, freedreno-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW Hello On Tue, Aug 14, 2018 at 8:10 AM Archit Taneja <architt@codeaurora.org> wrote: > > Thanks for the info. The number of failed modes is quite bad, > and across a wide range of modes. > > Another query: Does the mode fail to set every time you set it? > i.e, if we call the following successively, do we get the > "out of range" issue every time? > > xrandr --output HDMI-1 --mode 1600x1000 --rate 60.01 > > I'd looped in some friends who can help verify if the > driver is configuring the regs correctly. > The pll does not seem to be reconfigured if I set the same resolution again and again. So I am trying to go between two faulty resolutions: while true; do xrandr --output HDMI-1 --mode 1600x1000 --rate 60.01 ; sleep 5; xrandr --output HDMI-1 --mode 1680x1050 --rate 59.97; sleep 5 ; done and after 10 minutes or so I havent seen anything on the screen besides some blinks. Thanks! -- Ricardo Ribalda _______________________________________________ Freedreno mailing list Freedreno@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/freedreno ^ permalink raw reply [flat|nested] 11+ messages in thread
[parent not found: <CAPybu_0Lvcv8AUt16wfaPQhzMdVhWrAD4khdkP6P-_T8Ud0k6g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>]
* Re: db820c: Input signal Out of range [not found] ` <CAPybu_0Lvcv8AUt16wfaPQhzMdVhWrAD4khdkP6P-_T8Ud0k6g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> @ 2018-09-04 19:50 ` Ricardo Ribalda Delgado [not found] ` <CAPybu_2A7t7vy6qRrj4VhJ8rapyO1aQm0v1-J9YGwPSQpsk12A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> 0 siblings, 1 reply; 11+ messages in thread From: Ricardo Ribalda Delgado @ 2018-09-04 19:50 UTC (permalink / raw) To: Archit Taneja Cc: linux-arm-msm-u79uwXL29TY76Z2rM5mHXA, Rob Clark, sibis-sgV2jX0FEOL9JmXXK+q4OQ, vivek.gautam-sgV2jX0FEOL9JmXXK+q4OQ, alex-fkYMi7rYDl0, freedreno-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW Hi all Any update on this? I have hacked the way the modelines are probed and now it works on my screens, but of course there is no warranty that it will work with other screens : Thanks! On Wed, Aug 15, 2018 at 4:10 PM Ricardo Ribalda Delgado <ricardo.ribalda@gmail.com> wrote: > > Hello > On Tue, Aug 14, 2018 at 8:10 AM Archit Taneja <architt@codeaurora.org> wrote: > > > > > Thanks for the info. The number of failed modes is quite bad, > > and across a wide range of modes. > > > > Another query: Does the mode fail to set every time you set it? > > i.e, if we call the following successively, do we get the > > "out of range" issue every time? > > > > xrandr --output HDMI-1 --mode 1600x1000 --rate 60.01 > > > > I'd looped in some friends who can help verify if the > > driver is configuring the regs correctly. > > > > The pll does not seem to be reconfigured if I set the same resolution > again and again. > > So I am trying to go between two faulty resolutions: > > while true; do xrandr --output HDMI-1 --mode 1600x1000 --rate 60.01 ; > sleep 5; xrandr --output HDMI-1 --mode 1680x1050 --rate 59.97; sleep 5 > ; done > > and after 10 minutes or so I havent seen anything on the screen > besides some blinks. > > Thanks! > > -- > Ricardo Ribalda -- Ricardo Ribalda _______________________________________________ Freedreno mailing list Freedreno@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/freedreno ^ permalink raw reply [flat|nested] 11+ messages in thread
[parent not found: <CAPybu_2A7t7vy6qRrj4VhJ8rapyO1aQm0v1-J9YGwPSQpsk12A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>]
* Re: db820c: Input signal Out of range [not found] ` <CAPybu_2A7t7vy6qRrj4VhJ8rapyO1aQm0v1-J9YGwPSQpsk12A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> @ 2018-09-11 6:20 ` Sibi Sankar [not found] ` <75f4fac43ee84ab498f1b4ffb4ab1509-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org> 0 siblings, 1 reply; 11+ messages in thread From: Sibi Sankar @ 2018-09-11 6:20 UTC (permalink / raw) To: Ricardo Ribalda Delgado Cc: Archit Taneja, linux-arm-msm-u79uwXL29TY76Z2rM5mHXA, Rob Clark, vivek.gautam-sgV2jX0FEOL9JmXXK+q4OQ, alex-fkYMi7rYDl0, freedreno-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW Hi Ricardo, On 2018-09-05 01:20, Ricardo Ribalda Delgado wrote: > Hi all > > Any update on this? I have hacked the way the modelines are probed and > now it works on my screens, but of course there is no warranty that it > will work with other screens : > I plan to complete this task in the next two weeks. Really sorry for the delay. > Thanks! > On Wed, Aug 15, 2018 at 4:10 PM Ricardo Ribalda Delgado > <ricardo.ribalda@gmail.com> wrote: >> >> Hello >> On Tue, Aug 14, 2018 at 8:10 AM Archit Taneja <architt@codeaurora.org> >> wrote: >> >> > >> > Thanks for the info. The number of failed modes is quite bad, >> > and across a wide range of modes. >> > >> > Another query: Does the mode fail to set every time you set it? >> > i.e, if we call the following successively, do we get the >> > "out of range" issue every time? >> > >> > xrandr --output HDMI-1 --mode 1600x1000 --rate 60.01 >> > >> > I'd looped in some friends who can help verify if the >> > driver is configuring the regs correctly. >> > >> >> The pll does not seem to be reconfigured if I set the same resolution >> again and again. >> >> So I am trying to go between two faulty resolutions: >> >> while true; do xrandr --output HDMI-1 --mode 1600x1000 --rate 60.01 ; >> sleep 5; xrandr --output HDMI-1 --mode 1680x1050 --rate 59.97; sleep 5 >> ; done >> >> and after 10 minutes or so I havent seen anything on the screen >> besides some blinks. >> >> Thanks! >> >> -- >> Ricardo Ribalda -- -- Sibi Sankar -- Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project. _______________________________________________ Freedreno mailing list Freedreno@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/freedreno ^ permalink raw reply [flat|nested] 11+ messages in thread
[parent not found: <75f4fac43ee84ab498f1b4ffb4ab1509-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>]
* Re: db820c: Input signal Out of range [not found] ` <75f4fac43ee84ab498f1b4ffb4ab1509-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org> @ 2018-09-11 6:29 ` Ricardo Ribalda Delgado 0 siblings, 0 replies; 11+ messages in thread From: Ricardo Ribalda Delgado @ 2018-09-11 6:29 UTC (permalink / raw) To: sibis-sgV2jX0FEOL9JmXXK+q4OQ Cc: Archit Taneja, linux-arm-msm-u79uwXL29TY76Z2rM5mHXA, Rob Clark, vivek.gautam-sgV2jX0FEOL9JmXXK+q4OQ, alex-fkYMi7rYDl0, freedreno-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW Hi Sibi On Tue, Sep 11, 2018 at 8:20 AM Sibi Sankar <sibis@codeaurora.org> wrote: > > Hi Ricardo, > > On 2018-09-05 01:20, Ricardo Ribalda Delgado wrote: > > Hi all > > > > Any update on this? I have hacked the way the modelines are probed and > > now it works on my screens, but of course there is no warranty that it > > will work with other screens : > > > > I plan to complete this task in the next two weeks. Really sorry for the > delay. No worries, thanks for your help > > > Thanks! > > On Wed, Aug 15, 2018 at 4:10 PM Ricardo Ribalda Delgado > > <ricardo.ribalda@gmail.com> wrote: > >> > >> Hello > >> On Tue, Aug 14, 2018 at 8:10 AM Archit Taneja <architt@codeaurora.org> > >> wrote: > >> > >> > > >> > Thanks for the info. The number of failed modes is quite bad, > >> > and across a wide range of modes. > >> > > >> > Another query: Does the mode fail to set every time you set it? > >> > i.e, if we call the following successively, do we get the > >> > "out of range" issue every time? > >> > > >> > xrandr --output HDMI-1 --mode 1600x1000 --rate 60.01 > >> > > >> > I'd looped in some friends who can help verify if the > >> > driver is configuring the regs correctly. > >> > > >> > >> The pll does not seem to be reconfigured if I set the same resolution > >> again and again. > >> > >> So I am trying to go between two faulty resolutions: > >> > >> while true; do xrandr --output HDMI-1 --mode 1600x1000 --rate 60.01 ; > >> sleep 5; xrandr --output HDMI-1 --mode 1680x1050 --rate 59.97; sleep 5 > >> ; done > >> > >> and after 10 minutes or so I havent seen anything on the screen > >> besides some blinks. > >> > >> Thanks! > >> > >> -- > >> Ricardo Ribalda > > -- > -- Sibi Sankar -- > Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, > a Linux Foundation Collaborative Project. -- Ricardo Ribalda _______________________________________________ Freedreno mailing list Freedreno@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/freedreno ^ permalink raw reply [flat|nested] 11+ messages in thread
end of thread, other threads:[~2018-09-11 6:29 UTC | newest] Thread overview: 11+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2018-08-10 6:38 db820c: Input signal Out of range Ricardo Ribalda Delgado [not found] ` <CAPybu_0ooyLXuFK4x7kAk6-cpXeCO09yjfx9SwHFAKp5n2fsEQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> 2018-08-12 7:47 ` Archit Taneja [not found] ` <d4542b41-aa79-5c50-4971-9e1c1b937b02-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org> 2018-08-13 8:54 ` Ricardo Ribalda Delgado [not found] ` <CAPybu_0dMfaxBhybHapqfmjHVotA0BBsBs0cjYwdu4eaTT9rmQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> 2018-08-13 12:16 ` Archit Taneja [not found] ` <3007c578-59bf-9b16-25f3-2c97ae9486d0-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org> 2018-08-13 12:18 ` Ricardo Ribalda Delgado [not found] ` <CAPybu_2cPoMG9zkM8oa3MOSpGg20L14JyWc_e+1cba3uaSz7iA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> 2018-08-13 12:41 ` Ricardo Ribalda Delgado [not found] ` <CAPybu_1PGuTNaxEzFG86JzysQFPyoV4BpQ79j_-wAGqEAM8BNQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> 2018-08-14 6:10 ` Archit Taneja [not found] ` <dee8b931-321e-a4a1-18e7-b5467c3348d0-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org> 2018-08-15 14:10 ` Ricardo Ribalda Delgado [not found] ` <CAPybu_0Lvcv8AUt16wfaPQhzMdVhWrAD4khdkP6P-_T8Ud0k6g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> 2018-09-04 19:50 ` Ricardo Ribalda Delgado [not found] ` <CAPybu_2A7t7vy6qRrj4VhJ8rapyO1aQm0v1-J9YGwPSQpsk12A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> 2018-09-11 6:20 ` Sibi Sankar [not found] ` <75f4fac43ee84ab498f1b4ffb4ab1509-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org> 2018-09-11 6:29 ` Ricardo Ribalda Delgado
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.