All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rob Clark <robdclark@gmail.com>
To: Valentin Rothberg <valentinrothberg@gmail.com>
Cc: Hai Li <hali@codeaurora.org>,
	"dri-devel@lists.freedesktop.org"
	<dri-devel@lists.freedesktop.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	David Airlie <airlied@linux.ie>, Paul Bolle <pebolle@tiscali.nl>,
	rupran@einserver.de, stefan.hengelein@fau.de
Subject: Re: drm/msm/mdp5: undefined CONFIG_MSM_BUS_SCALING
Date: Thu, 9 Apr 2015 09:49:58 -0400	[thread overview]
Message-ID: <CAF6AEGtLeQgwnPmMUN=ZECnW_uQ4NQx5XFeNXLjjfEuPe5o-3A@mail.gmail.com> (raw)
In-Reply-To: <20150409112240.GA4748@station.rsr.lip6.fr>

On Thu, Apr 9, 2015 at 7:22 AM, Valentin Rothberg
<valentinrothberg@gmail.com> wrote:
> Hi Hai,
>
> your commit d5af49c92a8a ("drm/msm/mdp5: Enable DSI connector in msm drm
> driver") in today's Linux next tree adds an #ifdef with CONFIG_MSM_BUS_SCALING
> as condition.  MSM_BUS_SCALING is not defined in Kconfig, so the code in this
> #ifdef block won't be compiled at its current state.
>
> I saw some references on this Kconfig option in other files; is there a
> reason for the absence of MSM_BUS_SCALING?

right now, it is something that only exists in downstream kernels (for
example, android device kernels).. but in those kernels it is
mandatory to use, as by default the memory/bus is downclocked and the
display would underflow if we did not request sufficient bandwidth.

It only exists right now in the upstream kernel to simplify
backporting to various device kernels

BR,
-R

> I found this issue with ./scripts/checkkconfigsymbols.py by diffing yesterday's
> and today's next tree.
>
> Kind regards,
>  Valentin

WARNING: multiple messages have this Message-ID (diff)
From: Rob Clark <robdclark@gmail.com>
To: Valentin Rothberg <valentinrothberg@gmail.com>
Cc: Paul Bolle <pebolle@tiscali.nl>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	"dri-devel@lists.freedesktop.org"
	<dri-devel@lists.freedesktop.org>,
	rupran@einserver.de, stefan.hengelein@fau.de
Subject: Re: drm/msm/mdp5: undefined CONFIG_MSM_BUS_SCALING
Date: Thu, 9 Apr 2015 09:49:58 -0400	[thread overview]
Message-ID: <CAF6AEGtLeQgwnPmMUN=ZECnW_uQ4NQx5XFeNXLjjfEuPe5o-3A@mail.gmail.com> (raw)
In-Reply-To: <20150409112240.GA4748@station.rsr.lip6.fr>

On Thu, Apr 9, 2015 at 7:22 AM, Valentin Rothberg
<valentinrothberg@gmail.com> wrote:
> Hi Hai,
>
> your commit d5af49c92a8a ("drm/msm/mdp5: Enable DSI connector in msm drm
> driver") in today's Linux next tree adds an #ifdef with CONFIG_MSM_BUS_SCALING
> as condition.  MSM_BUS_SCALING is not defined in Kconfig, so the code in this
> #ifdef block won't be compiled at its current state.
>
> I saw some references on this Kconfig option in other files; is there a
> reason for the absence of MSM_BUS_SCALING?

right now, it is something that only exists in downstream kernels (for
example, android device kernels).. but in those kernels it is
mandatory to use, as by default the memory/bus is downclocked and the
display would underflow if we did not request sufficient bandwidth.

It only exists right now in the upstream kernel to simplify
backporting to various device kernels

BR,
-R

> I found this issue with ./scripts/checkkconfigsymbols.py by diffing yesterday's
> and today's next tree.
>
> Kind regards,
>  Valentin
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2015-04-09 13:50 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-09 11:22 drm/msm/mdp5: undefined CONFIG_MSM_BUS_SCALING Valentin Rothberg
2015-04-09 13:49 ` Rob Clark [this message]
2015-04-09 13:49   ` Rob Clark
2015-04-09 14:20   ` Greg KH
2015-04-09 14:50     ` Rob Clark
2015-04-09 14:50       ` Rob Clark
2015-04-09 17:07       ` Greg KH
2015-04-09 18:02         ` Rob Clark
2015-04-09 18:02           ` Rob Clark
2015-04-09 18:12         ` Paul Bolle
2015-04-09 18:54           ` Rob Clark
2015-04-09 18:54             ` Rob Clark
2015-04-09 19:38             ` Paul Bolle
2015-04-09 19:38               ` Paul Bolle
2015-04-09 19:44             ` Valentin Rothberg
2015-04-09 20:20               ` Rob Clark
2015-04-09 20:20                 ` Rob Clark
2015-04-10  6:04                 ` Valentin Rothberg

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='CAF6AEGtLeQgwnPmMUN=ZECnW_uQ4NQx5XFeNXLjjfEuPe5o-3A@mail.gmail.com' \
    --to=robdclark@gmail.com \
    --cc=airlied@linux.ie \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=hali@codeaurora.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pebolle@tiscali.nl \
    --cc=rupran@einserver.de \
    --cc=stefan.hengelein@fau.de \
    --cc=valentinrothberg@gmail.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.