From: pavel@ucw.cz (Pavel Machek)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V3 8/8] drivers: boot_constraint: Add Qualcomm display controller constraints
Date: Mon, 4 Sep 2017 18:25:44 +0200 [thread overview]
Message-ID: <20170904162544.GA21849@amd> (raw)
In-Reply-To: <f1d035bb3202dd6135e6cde9e4a142ea32a6a79c.1501578037.git.viresh.kumar@linaro.org>
Hi!
> From: Rajendra Nayak <rnayak@codeaurora.org>
>
> NOT TO BE MERGED
>
> This sets boot constraints for the display controller used on Qualcomm
> dragonboard 410c.
>
> Not-signed-off-by: Rajendra Nayak <rnayak@codeaurora.org>
> Not-signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
> +#include <linux/boot_constraint.h>
> +#include <linux/init.h>
> +#include <linux/kernel.h>
> +
> +struct dev_boot_constraint_clk_info iface_clk_info = {
> + .name = "iface_clk",
> +};
> +
> +struct dev_boot_constraint_clk_info bus_clk_info = {
> + .name = "bus_clk",
> +};
> +
> +struct dev_boot_constraint_clk_info core_clk_info = {
> + .name = "core_clk",
> +};
> +
> +struct dev_boot_constraint_clk_info vsync_clk_info = {
> + .name = "vsync_clk",
> +};
> +
> +struct dev_boot_constraint_clk_info esc0_clk_info = {
> + .name = "core_clk",
> +};
> +
> +struct dev_boot_constraint_clk_info byte_clk_info = {
> + .name = "byte_clk",
> +};
> +
> +struct dev_boot_constraint_clk_info pixel_clk_info = {
> + .name = "pixel_clk",
> +};
> +
> +struct dev_boot_constraint_supply_info vdda_info = {
> + .name = "vdda"
> +};
> +
> +struct dev_boot_constraint_supply_info vddio_info = {
> + .name = "vddio"
> +};
> +
> +struct dev_boot_constraint constraints_mdss[] = {
> + {
> + .type = DEV_BOOT_CONSTRAINT_PM,
> + .data = NULL,
> + },
> +};
> +
> +struct dev_boot_constraint constraints_mdp[] = {
> + {
> + .type = DEV_BOOT_CONSTRAINT_CLK,
> + .data = &iface_clk_info,
> + }, {
> + .type = DEV_BOOT_CONSTRAINT_CLK,
> + .data = &bus_clk_info,
> + }, {
> + .type = DEV_BOOT_CONSTRAINT_CLK,
> + .data = &core_clk_info,
> + }, {
> + .type = DEV_BOOT_CONSTRAINT_CLK,
> + .data = &vsync_clk_info,
> + },
> +};
Hmm. I know this is not for merge, but should this go to device tree somewhere?
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20170904/61d21e65/attachment.sig>
next prev parent reply other threads:[~2017-09-04 16:25 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-01 9:23 [PATCH V3 0/8] drivers: Boot Constraints core Viresh Kumar
2017-08-01 9:23 ` [PATCH V3 1/8] drivers: Add boot constraints core Viresh Kumar
2017-08-29 6:39 ` Greg Kroah-Hartman
2017-08-29 9:52 ` Viresh Kumar
2017-08-29 12:03 ` Greg Kroah-Hartman
2017-09-04 9:15 ` Viresh Kumar
2017-09-04 9:38 ` Greg Kroah-Hartman
2017-09-19 22:46 ` Viresh Kumar
2017-08-01 9:23 ` [PATCH V3 2/8] drivers: boot_constraint: Add boot_constraints_disable kernel parameter Viresh Kumar
2017-08-29 6:37 ` Greg Kroah-Hartman
2017-08-29 6:48 ` Jani Nikula
2017-08-29 10:02 ` Viresh Kumar
2017-08-29 11:56 ` Greg Kroah-Hartman
2017-08-01 9:23 ` [PATCH V3 3/8] drivers: boot_constraint: Add support for supply constraints Viresh Kumar
2017-08-01 9:23 ` [PATCH V3 4/8] drivers: boot_constraint: Add support for clk constraints Viresh Kumar
2017-08-01 9:23 ` [PATCH V3 5/8] drivers: boot_constraint: Add support for PM constraints Viresh Kumar
2017-08-01 9:23 ` [PATCH V3 6/8] drivers: boot_constraint: Add debugfs support Viresh Kumar
2017-08-29 6:36 ` Greg Kroah-Hartman
2017-08-29 10:04 ` Viresh Kumar
2017-08-01 9:23 ` [PATCH V3 7/8] drivers: boot_constraint: Manage deferrable constraints Viresh Kumar
2017-08-01 9:23 ` [PATCH V3 8/8] drivers: boot_constraint: Add Qualcomm display controller constraints Viresh Kumar
2017-09-04 16:25 ` Pavel Machek [this message]
2017-09-19 22:40 ` Viresh Kumar
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=20170904162544.GA21849@amd \
--to=pavel@ucw.cz \
--cc=linux-arm-kernel@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).