linux-arm-msm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Archit Taneja <architt@codeaurora.org>
To: John Stultz <john.stultz@linaro.org>
Cc: Stephen Boyd <sboyd@codeaurora.org>,
	"linux-arm-msm@vger.kernel.org" <linux-arm-msm@vger.kernel.org>,
	Vinay Simha <vinaysimha@inforcecomputing.com>
Subject: Re: [PATCH] clk: qcom: Fix pre-divider usage for pixel RCG
Date: Sun, 28 Feb 2016 15:36:12 +0530	[thread overview]
Message-ID: <56D2C694.5060808@codeaurora.org> (raw)
In-Reply-To: <CALAqxLUr2edygC6W3HJC2tzbvoR60Bzc=ojxXKuUcgUgDS8Ypg@mail.gmail.com>



On 2/27/2016 2:10 AM, John Stultz wrote:
> On Thu, Feb 25, 2016 at 9:30 PM, Archit Taneja <architt@codeaurora.org> wrote:
>> The clk_rcg_pixel_set_rate clk_op sets up the pre-divider by reading
>> its current value from the NS register.
>>
>> Using the pre-divider wasn't really intended when creating these ops.
>> The pixel RCG was only intended to achieve fractional multiplication
>> provided in the pixel_table array. Leaving the pre-divider to the
>> existing register value results in a wrong pixel clock when the
>> bootloader sets up the display. This was left unidentified because
>> the IFC6410 Plus board on which this was verified didn't have a
>> bootloader that configured the display.
>>
>> Don't set the RCG pre-divider in freq_tbl to the existing NS register
>> value. Instead, set it based on the fractional multiplication we want.
>> Prevent using M/N counter when we can just manage with using the
>> pre-divider.
>>
>> Cc: John Stultz <john.stultz@linaro.org>
>> Cc: Vinay Simha <vinaysimha@inforcecomputing.com>
>> Signed-off-by: Archit Taneja <architt@codeaurora.org>
>> ---
>> John, Vinay, could you please test this on N7 and confirm if it works?
>
> Hey Archit,
>
> So this did not work for me. I removed the earlier patch forcing
> pre_div to 1, and added this, but that ended up with a mostly black
> screen with a bit of blue slowly scrolling down the side.
>
> With the f.pre_div=1 line re-added, I don't see anything. The screen
> just goes black and doesn't come back.
>
> Let me know if I can test anything else for you, or add any debug messages.

Thanks for trying the patch. There was a small optimization which seems
to make things worse for us. I'm going to post out a v2 which does the
same thing as the earlier patch.

Archit

>
> thanks
> -john
> --
> To unsubscribe from this list: send the line "unsubscribe linux-arm-msm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>

-- 
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project

  reply	other threads:[~2016-02-28 10:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-26  5:30 [PATCH] clk: qcom: Fix pre-divider usage for pixel RCG Archit Taneja
2016-02-26 17:44 ` Stephen Boyd
2016-02-28  9:42   ` Archit Taneja
2016-02-26 20:40 ` John Stultz
2016-02-28 10:06   ` Archit Taneja [this message]
2016-02-28 10:07 ` [PATCH v2] " Archit Taneja
2016-02-29 19:31   ` John Stultz
2016-02-29 20:57   ` Stephen Boyd

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=56D2C694.5060808@codeaurora.org \
    --to=architt@codeaurora.org \
    --cc=john.stultz@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=sboyd@codeaurora.org \
    --cc=vinaysimha@inforcecomputing.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 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).