Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1726167 > unrolled thread

Re: [PATCH V3 8/8] drivers: boot_constraint: Add Qualcomm display controller constraints

Started byPavel Machek <pavel@ucw.cz>
First post2017-09-04 18:30 +0200
Last post2017-09-04 18:30 +0200
Articles 1 — 1 participant

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: [PATCH V3 8/8] drivers: boot_constraint: Add Qualcomm display  controller constraints Pavel Machek <pavel@ucw.cz> - 2017-09-04 18:30 +0200

#1726167 — Re: [PATCH V3 8/8] drivers: boot_constraint: Add Qualcomm display controller constraints

FromPavel Machek <pavel@ucw.cz>
Date2017-09-04 18:30 +0200
SubjectRe: [PATCH V3 8/8] drivers: boot_constraint: Add Qualcomm display controller constraints
Message-ID<um2q5-7L6-5@gated-at.bofh.it>

[Multipart message — attachments visible in raw view] — view raw

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

[toc] | [standalone]


Back to top | Article view | linux.kernel


csiph-web