From: Sudeep Holla <sudeep.holla@arm.com>
To: Kevin Brodsky <kevin.brodsky@arm.com>
Cc: devicetree@vger.kernel.org, Pawel Moll <pawel.moll@arm.com>,
Ruben Ayrapetyan <ruben.ayrapetyan@arm.com>,
Linus Walleij <linus.walleij@linaro.org>,
Liviu Dudau <liviu.dudau@arm.com>,
dri-devel@lists.freedesktop.org,
Sudeep Holla <sudeep.holla@arm.com>,
Robin Murphy <robin.murphy@arm.com>,
Brian Starkey <brian.starkey@arm.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2] arm64: dts: fast models: Remove clcd's max-memory-bandwidth
Date: Fri, 26 Jul 2019 10:50:25 +0100 [thread overview]
Message-ID: <20190726095025.GB11177@e107155-lin> (raw)
In-Reply-To: <20190725171215.71801-1-kevin.brodsky@arm.com>
On Thu, Jul 25, 2019 at 06:12:14PM +0100, Kevin Brodsky wrote:
> It is unclear why max-memory-bandwidth should be set for CLCD on the
> fast model. Removing that property allows allocating and using 32bpp
> buffers, which may be desirable on certain platforms such as
> Android.
>
> Reported-by: Ruben Ayrapetyan <ruben.ayrapetyan@arm.com>
> Signed-off-by: Kevin Brodsky <kevin.brodsky@arm.com>
> ---
>
> Changes in v2:
> - Remove the attribute completely instead of increasing its value. It is
> optional and there is no clear reason why it should be set at all.
>
> arch/arm64/boot/dts/arm/fvp-base-revc.dts | 8 --------
> arch/arm64/boot/dts/arm/rtsm_ve-motherboard.dtsi | 2 --
I was about to ask about the above file in v1, and then saw v2.
I will take this for v5.4. Thanks
--
Regards,
Sudeep
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-07-26 9:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-25 17:12 [PATCH v2] arm64: dts: fast models: Remove clcd's max-memory-bandwidth Kevin Brodsky
2019-07-26 9:50 ` Sudeep Holla [this message]
2019-08-05 10:31 ` Linus Walleij
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=20190726095025.GB11177@e107155-lin \
--to=sudeep.holla@arm.com \
--cc=brian.starkey@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=kevin.brodsky@arm.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=liviu.dudau@arm.com \
--cc=pawel.moll@arm.com \
--cc=robin.murphy@arm.com \
--cc=ruben.ayrapetyan@arm.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