All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Tomi Valkeinen <tomi.valkeinen@ti.com>
Cc: linux-fbdev@vger.kernel.org,
	Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
	linux-kernel@vger.kernel.org, stable@vger.kernel.org,
	dri-devel@lists.freedesktop.org, linux-omap@vger.kernel.org,
	Adam Ford <aford173@gmail.com>
Subject: Re: [PATCH] omapfb: dss: Fix max fclk divider for omap36xx
Date: Fri, 03 Jul 2020 19:36:48 +0000	[thread overview]
Message-ID: <20200703193648.GA373653@ravnborg.org> (raw)
In-Reply-To: <b9052a12-af5a-c1b9-5b86-907eac470cf8@ti.com>

Hi Tomi.

On Fri, Jul 03, 2020 at 10:17:29AM +0300, Tomi Valkeinen wrote:
> On 30/06/2020 21:26, Adam Ford wrote:
> > The drm/omap driver was fixed to correct an issue where using a
> > divider of 32 breaks the DSS despite the TRM stating 32 is a valid
> > number.  Through experimentation, it appears that 31 works, and
> > it is consistent with the value used by the drm/omap driver.
> > 
> > This patch fixes the divider for fbdev driver instead of the drm.
> > 
> > Fixes: f76ee892a99e ("omapfb: copy omapdss & displays for omapfb")
> > 
> > Cc: <stable@vger.kernel.org> #4.9+
> > Signed-off-by: Adam Ford <aford173@gmail.com>
> > ---
> > Linux 4.4 will need a similar patch, but it doesn't apply cleanly.
> > 
> > The DRM version of this same fix is:
> > e2c4ed148cf3 ("drm/omap: fix max fclk divider for omap36xx")
> > 
> > 
> > diff --git a/drivers/video/fbdev/omap2/omapfb/dss/dss.c b/drivers/video/fbdev/omap2/omapfb/dss/dss.c
> > index 7252d22dd117..bfc5c4c5a26a 100644
> > --- a/drivers/video/fbdev/omap2/omapfb/dss/dss.c
> > +++ b/drivers/video/fbdev/omap2/omapfb/dss/dss.c
> > @@ -833,7 +833,7 @@ static const struct dss_features omap34xx_dss_feats = {
> >   };
> >   static const struct dss_features omap3630_dss_feats = {
> > -	.fck_div_max		=	32,
> > +	.fck_div_max		=	31,
> >   	.dss_fck_multiplier	=	1,
> >   	.parent_clk_name	=	"dpll4_ck",
> >   	.dpi_select_source	=	&dss_dpi_select_source_omap2_omap3,
> > 
> 
> Reviewed-by: Tomi Valkeinen <tomi.valkeinen@ti.com>
Will you apply to drm-misc?

Note  following output from "dim fixes":
$ dim fixes f76ee892a99e
Fixes: f76ee892a99e ("omapfb: copy omapdss & displays for omapfb")
Cc: Tomi Valkeinen <tomi.valkeinen@ti.com>
Cc: Dave Airlie <airlied@gmail.com>
Cc: Rob Clark <robdclark@gmail.com>
Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: Sam Ravnborg <sam@ravnborg.org>
Cc: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
Cc: Jason Yan <yanaijie@huawei.com>
Cc: "Andrew F. Davis" <afd@ti.com>
Cc: YueHaibing <yuehaibing@huawei.com>
Cc: <stable@vger.kernel.org> # v4.5+

Here it says the fix is valid from v4.5 onwards.

	Sam
> 
>  Tomi
> 
> -- 
> Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki.
> Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/dri-devel

WARNING: multiple messages have this Message-ID (diff)
From: Sam Ravnborg <sam@ravnborg.org>
To: Tomi Valkeinen <tomi.valkeinen@ti.com>
Cc: Adam Ford <aford173@gmail.com>,
	linux-fbdev@vger.kernel.org,
	Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
	linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
	stable@vger.kernel.org, linux-omap@vger.kernel.org
Subject: Re: [PATCH] omapfb: dss: Fix max fclk divider for omap36xx
Date: Fri, 3 Jul 2020 21:36:48 +0200	[thread overview]
Message-ID: <20200703193648.GA373653@ravnborg.org> (raw)
In-Reply-To: <b9052a12-af5a-c1b9-5b86-907eac470cf8@ti.com>

Hi Tomi.

On Fri, Jul 03, 2020 at 10:17:29AM +0300, Tomi Valkeinen wrote:
> On 30/06/2020 21:26, Adam Ford wrote:
> > The drm/omap driver was fixed to correct an issue where using a
> > divider of 32 breaks the DSS despite the TRM stating 32 is a valid
> > number.  Through experimentation, it appears that 31 works, and
> > it is consistent with the value used by the drm/omap driver.
> > 
> > This patch fixes the divider for fbdev driver instead of the drm.
> > 
> > Fixes: f76ee892a99e ("omapfb: copy omapdss & displays for omapfb")
> > 
> > Cc: <stable@vger.kernel.org> #4.9+
> > Signed-off-by: Adam Ford <aford173@gmail.com>
> > ---
> > Linux 4.4 will need a similar patch, but it doesn't apply cleanly.
> > 
> > The DRM version of this same fix is:
> > e2c4ed148cf3 ("drm/omap: fix max fclk divider for omap36xx")
> > 
> > 
> > diff --git a/drivers/video/fbdev/omap2/omapfb/dss/dss.c b/drivers/video/fbdev/omap2/omapfb/dss/dss.c
> > index 7252d22dd117..bfc5c4c5a26a 100644
> > --- a/drivers/video/fbdev/omap2/omapfb/dss/dss.c
> > +++ b/drivers/video/fbdev/omap2/omapfb/dss/dss.c
> > @@ -833,7 +833,7 @@ static const struct dss_features omap34xx_dss_feats = {
> >   };
> >   static const struct dss_features omap3630_dss_feats = {
> > -	.fck_div_max		=	32,
> > +	.fck_div_max		=	31,
> >   	.dss_fck_multiplier	=	1,
> >   	.parent_clk_name	=	"dpll4_ck",
> >   	.dpi_select_source	=	&dss_dpi_select_source_omap2_omap3,
> > 
> 
> Reviewed-by: Tomi Valkeinen <tomi.valkeinen@ti.com>
Will you apply to drm-misc?

Note  following output from "dim fixes":
$ dim fixes f76ee892a99e
Fixes: f76ee892a99e ("omapfb: copy omapdss & displays for omapfb")
Cc: Tomi Valkeinen <tomi.valkeinen@ti.com>
Cc: Dave Airlie <airlied@gmail.com>
Cc: Rob Clark <robdclark@gmail.com>
Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: Sam Ravnborg <sam@ravnborg.org>
Cc: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
Cc: Jason Yan <yanaijie@huawei.com>
Cc: "Andrew F. Davis" <afd@ti.com>
Cc: YueHaibing <yuehaibing@huawei.com>
Cc: <stable@vger.kernel.org> # v4.5+

Here it says the fix is valid from v4.5 onwards.

	Sam
> 
>  Tomi
> 
> -- 
> Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki.
> Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/dri-devel

WARNING: multiple messages have this Message-ID (diff)
From: Sam Ravnborg <sam@ravnborg.org>
To: Tomi Valkeinen <tomi.valkeinen@ti.com>
Cc: linux-fbdev@vger.kernel.org,
	Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
	linux-kernel@vger.kernel.org, stable@vger.kernel.org,
	dri-devel@lists.freedesktop.org, linux-omap@vger.kernel.org,
	Adam Ford <aford173@gmail.com>
Subject: Re: [PATCH] omapfb: dss: Fix max fclk divider for omap36xx
Date: Fri, 3 Jul 2020 21:36:48 +0200	[thread overview]
Message-ID: <20200703193648.GA373653@ravnborg.org> (raw)
In-Reply-To: <b9052a12-af5a-c1b9-5b86-907eac470cf8@ti.com>

Hi Tomi.

On Fri, Jul 03, 2020 at 10:17:29AM +0300, Tomi Valkeinen wrote:
> On 30/06/2020 21:26, Adam Ford wrote:
> > The drm/omap driver was fixed to correct an issue where using a
> > divider of 32 breaks the DSS despite the TRM stating 32 is a valid
> > number.  Through experimentation, it appears that 31 works, and
> > it is consistent with the value used by the drm/omap driver.
> > 
> > This patch fixes the divider for fbdev driver instead of the drm.
> > 
> > Fixes: f76ee892a99e ("omapfb: copy omapdss & displays for omapfb")
> > 
> > Cc: <stable@vger.kernel.org> #4.9+
> > Signed-off-by: Adam Ford <aford173@gmail.com>
> > ---
> > Linux 4.4 will need a similar patch, but it doesn't apply cleanly.
> > 
> > The DRM version of this same fix is:
> > e2c4ed148cf3 ("drm/omap: fix max fclk divider for omap36xx")
> > 
> > 
> > diff --git a/drivers/video/fbdev/omap2/omapfb/dss/dss.c b/drivers/video/fbdev/omap2/omapfb/dss/dss.c
> > index 7252d22dd117..bfc5c4c5a26a 100644
> > --- a/drivers/video/fbdev/omap2/omapfb/dss/dss.c
> > +++ b/drivers/video/fbdev/omap2/omapfb/dss/dss.c
> > @@ -833,7 +833,7 @@ static const struct dss_features omap34xx_dss_feats = {
> >   };
> >   static const struct dss_features omap3630_dss_feats = {
> > -	.fck_div_max		=	32,
> > +	.fck_div_max		=	31,
> >   	.dss_fck_multiplier	=	1,
> >   	.parent_clk_name	=	"dpll4_ck",
> >   	.dpi_select_source	=	&dss_dpi_select_source_omap2_omap3,
> > 
> 
> Reviewed-by: Tomi Valkeinen <tomi.valkeinen@ti.com>
Will you apply to drm-misc?

Note  following output from "dim fixes":
$ dim fixes f76ee892a99e
Fixes: f76ee892a99e ("omapfb: copy omapdss & displays for omapfb")
Cc: Tomi Valkeinen <tomi.valkeinen@ti.com>
Cc: Dave Airlie <airlied@gmail.com>
Cc: Rob Clark <robdclark@gmail.com>
Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: Sam Ravnborg <sam@ravnborg.org>
Cc: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
Cc: Jason Yan <yanaijie@huawei.com>
Cc: "Andrew F. Davis" <afd@ti.com>
Cc: YueHaibing <yuehaibing@huawei.com>
Cc: <stable@vger.kernel.org> # v4.5+

Here it says the fix is valid from v4.5 onwards.

	Sam
> 
>  Tomi
> 
> -- 
> Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki.
> Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/dri-devel
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2020-07-03 19:36 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20200630182652eucas1p1ce5e07b065127e32ab734f4447c2f735@eucas1p1.samsung.com>
2020-06-30 18:26 ` [PATCH] omapfb: dss: Fix max fclk divider for omap36xx Adam Ford
2020-06-30 18:26   ` Adam Ford
2020-06-30 18:26   ` Adam Ford
2020-07-03  7:17   ` Tomi Valkeinen
2020-07-03  7:17     ` Tomi Valkeinen
2020-07-03  7:17     ` Tomi Valkeinen
2020-07-03 19:36     ` Sam Ravnborg [this message]
2020-07-03 19:36       ` Sam Ravnborg
2020-07-03 19:36       ` Sam Ravnborg
2020-07-06  6:02       ` Tomi Valkeinen
2020-07-06  6:02         ` Tomi Valkeinen
2020-07-06  6:02         ` Tomi Valkeinen
2020-07-06 11:18         ` Adam Ford
2020-07-06 11:18           ` Adam Ford
2020-07-06 11:18           ` Adam Ford
2020-07-08 23:37           ` Adam Ford
2020-07-08 23:37             ` Adam Ford
2020-07-08 23:37             ` Adam Ford
2020-07-09  6:10             ` Greg KH
2020-07-09  6:10               ` Greg KH
2020-07-09  6:10               ` Greg KH
2020-07-10 14:23   ` Bartlomiej Zolnierkiewicz
2020-07-10 14:23     ` Bartlomiej Zolnierkiewicz
2020-07-10 14:23     ` Bartlomiej Zolnierkiewicz
2020-07-09 12:12 Adam Ford
     [not found] ` <CAHCN7x+crwfE4pfufad_WEUhiJQXccSZHot+YNDZzZKvqhrmWA@mail.gmail.com>
2020-08-04 13:19   ` Tomi Valkeinen
2020-08-05 14:33     ` Greg KH
2020-08-06  9:46       ` Tomi Valkeinen
2020-08-13 16:41         ` Adam Ford
2020-08-24  8:16           ` Greg KH

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200703193648.GA373653@ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=aford173@gmail.com \
    --cc=b.zolnierkie@samsung.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=tomi.valkeinen@ti.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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.