linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jose Abreu <Jose.Abreu@synopsys.com>
To: Alexey Brodkin <Alexey.Brodkin@synopsys.com>,
	"daniel@ffwll.ch" <daniel@ffwll.ch>
Cc: "dri-devel@lists.freedesktop.org"
	<dri-devel@lists.freedesktop.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Jose.Abreu@synopsys.com" <Jose.Abreu@synopsys.com>,
	"daniel.vetter@ffwll.ch" <daniel.vetter@ffwll.ch>,
	"linux-snps-arc@lists.infradead.org" 
	<linux-snps-arc@lists.infradead.org>,
	"airlied@linux.ie" <airlied@linux.ie>
Subject: Re: [PATCH] drm/arcpgu: use .mode_fixup instead of .atomic_check
Date: Fri, 3 Mar 2017 18:05:15 +0000	[thread overview]
Message-ID: <873786fc-406e-850d-f9fb-a6c9ba8cf95c@synopsys.com> (raw)
In-Reply-To: <1488547649.2940.5.camel@synopsys.com>

Hi Alexey,


On 03-03-2017 13:27, Alexey Brodkin wrote:
>
> So if I understood you correct here what I really need is just to get rid of existing check,
> right? I.e. the following is to be in v2 respin:
> ------------------------------->8-------------------------------
> diff --git a/drivers/gpu/drm/arc/arcpgu_crtc.c b/drivers/gpu/drm/arc/arcpgu_crtc.c
> index ad9a95916f1f..86f1555914e8 100644
> --- a/drivers/gpu/drm/arc/arcpgu_crtc.c
> +++ b/drivers/gpu/drm/arc/arcpgu_crtc.c
> @@ -129,20 +129,6 @@ static void arc_pgu_crtc_disable(struct drm_crtc *crtc)
>                               ~ARCPGU_CTRL_ENABLE_MASK);
>  }
>  
> -static int arc_pgu_crtc_atomic_check(struct drm_crtc *crtc,
> -                                    struct drm_crtc_state *state)
> -{
> -       struct arcpgu_drm_private *arcpgu = crtc_to_arcpgu_priv(crtc);
> -       struct drm_display_mode *mode = &state->adjusted_mode;
> -       long rate, clk_rate = mode->clock * 1000;
> -
> -       rate = clk_round_rate(arcpgu->clk, clk_rate);
> -       if (rate != clk_rate)
> -               return -EINVAL;
> -
> -       return 0;
> -}
> -
>  static void arc_pgu_crtc_atomic_begin(struct drm_crtc *crtc,
>                                       struct drm_crtc_state *state)
>  {
> @@ -165,7 +151,6 @@ static const struct drm_crtc_helper_funcs arc_pgu_crtc_helper_funcs = {
>         .disable        = arc_pgu_crtc_disable,
>         .prepare        = arc_pgu_crtc_disable,
>         .commit         = arc_pgu_crtc_enable,
> -       .atomic_check   = arc_pgu_crtc_atomic_check,
>         .atomic_begin   = arc_pgu_crtc_atomic_begin,
>  };
> ------------------------------->8-------------------------------

I don't think you can remove the check entirely as this will make
any mode be accepted, right?

Best regards,
Jose Miguel Abreu

  reply	other threads:[~2017-03-03 18:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-02 17:27 [PATCH] drm/arcpgu: use .mode_fixup instead of .atomic_check Alexey Brodkin
2017-03-02 19:54 ` Daniel Vetter
2017-03-03 13:27   ` Alexey Brodkin
2017-03-03 18:05     ` Jose Abreu [this message]
2017-03-03 19:24       ` Alexey Brodkin
2017-03-06 10:48         ` Jose Abreu
2017-03-06 10:17       ` Daniel Vetter

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=873786fc-406e-850d-f9fb-a6c9ba8cf95c@synopsys.com \
    --to=jose.abreu@synopsys.com \
    --cc=Alexey.Brodkin@synopsys.com \
    --cc=airlied@linux.ie \
    --cc=daniel.vetter@ffwll.ch \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-snps-arc@lists.infradead.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).