search for: 804000

...uot;%s%s%s%s%s", "Curve ", "( ", n_name," )", ".png"),width=480,height=480) par('bg'= "#FFFFCC") par(xaxt="n") plot(internal_category, IPD, "b", ylab="PD", xlab="Rating", fg= "#804000", font.main=2,cex.main=1,col="Red",col.main= "black",col.axis="black" ,col.lab = "black") title("Exponential Curve", sub = paste("(", n_name,")"), cex.main = 1.2, font.main= 2, col.main= "black", cex.sub = 1,...

...", "( ", class," )",".png"), width=480,height=480) par('bg'= "#FFFFCC") par(xaxt="n") plot(as.numeric(factor(Data[[ratings]])), Data[[IPD]], "b", ylab="PD", xlab="Rating", fg="#804000", font.main=2,cex.main=1,col="Red", col.main="black",col.axis="black" ,col.lab = "black") title("Exponential Curve", sub = paste("(", class,")"), cex.main=1.2, font.main= 2, col.main= "black", c...

..._______________________ e <- c(1:N) f <- c((e-.5)/N) Fx <- cdfgum(x, para = parameters_of_GUMBEL) g <- sort(Fx) png(filename = "GUMBEL_P-P.png") a <- par('bg'= "#FFFFCC") plot (f,g,bg=a,fg= "#804000",main ="P-P Plot", ylab=" Cumulative Distribution Function", xlab="i", font.main=2, cex.main=1,col="#999966",bty = "o",col.main="black",col.axis="black",col.lab ="black") abline(rq(g ~ f, tau = .5),col=&qu...

Hi, I am beginning to learn R and have a data table that I would like to produce a microarray-like plot. The table looks like this: 3 0 0 3 -377.61 1.94 3 0 0 3 -444.80 2.36 2 1 0 3 -519.60 2.39 1 1 1 3 -54.88 2.49 2 1 1 4 -536.55 2.53 1 0 1 2 108.29 2.62 2 0 0 2 39.56 2.62 3 0 1 4 108.32 2.63 2 0 0 2 -455.23 2.84 1 0 0 1 -432.30 2.98 ... I would like to assign colors to the first three columns

..._ P - P Plot ________________________ e <- c(1:N) f <- c((e-.5)/N) Fx <- cdfgum(x, para = parameters_of_GUMBEL) g <- sort(Fx) png(filename = "GUMBEL_P-P.png") a <- par('bg'= "#FFFFCC") plot (f,g,bg=a,fg= "#804000",main ="P-P Plot", ylab=" Cumulative Distribution Function", xlab="i", font.main=2, cex.main=1,col="#999966",bty = "o",col.main="black",col.axis="black",col.lab ="black") abline(rq(g ~ f, tau = .5),col="red&...

...{ > .base = { > .domain[nv_clk_src_gpc] = 708000, > + .voltage = 11, > }, > }, > { > .base = { > .domain[nv_clk_src_gpc] = 756000, > + .voltage = 12, > }, > }, > { > .base = { > .domain[nv_clk_src_gpc] = 804000, > + .voltage = 13, > }, > }, > { > .base = { > .domain[nv_clk_src_gpc] = 852000, > + .voltage = 14, > }, > }, > }; Is there a particular reason why this table is hard-coded rather than stored in the device tree? It doesn't seem to...

...; { >>> .base = { >>> .domain[nv_clk_src_gpc] = 756000, >>> + .voltage = 12, >>> }, >>> }, >>> { >>> .base = { >>> .domain[nv_clk_src_gpc] = 804000, >>> + .voltage = 13, >>> }, >>> }, >>> { >>> .base = { >>> .domain[nv_clk_src_gpc] = 852000, >>> + .voltage = 14, >>> }, >>> }, >&...

....base = { >>>> .domain[nv_clk_src_gpc] = 756000, >>>> + .voltage = 12, >>>> }, >>>> }, >>>> { >>>> .base = { >>>> .domain[nv_clk_src_gpc] = 804000, >>>> + .voltage = 13, >>>> }, >>>> }, >>>> { >>>> .base = { >>>> .domain[nv_clk_src_gpc] = 852000, >>>> + .voltage = 14, >>>>...

...{ .base = { .domain[nv_clk_src_gpc] = 684000, + .voltage = 10, }, }, { .base = { .domain[nv_clk_src_gpc] = 708000, + .voltage = 11, }, }, { .base = { .domain[nv_clk_src_gpc] = 756000, + .voltage = 12, }, }, { .base = { .domain[nv_clk_src_gpc] = 804000, + .voltage = 13, }, }, { .base = { .domain[nv_clk_src_gpc] = 852000, + .voltage = 14, }, }, }; diff --git a/nvkm/subdev/volt/gk20a.c b/nvkm/subdev/volt/gk20a.c new file mode 100644 index 000000000000..87385966e67f --- /dev/null +++ b/nvkm/subdev/volt/gk20a.c @@ -0,0 +1,202...

...{ .base = { .domain[nv_clk_src_gpc] = 684000, + .voltage = 10, }, }, { .base = { .domain[nv_clk_src_gpc] = 708000, + .voltage = 11, }, }, { .base = { .domain[nv_clk_src_gpc] = 756000, + .voltage = 12, }, }, { .base = { .domain[nv_clk_src_gpc] = 804000, + .voltage = 13, }, }, { .base = { .domain[nv_clk_src_gpc] = 852000, + .voltage = 14, }, }, }; diff --git a/nvkm/subdev/volt/gk20a.c b/nvkm/subdev/volt/gk20a.c new file mode 100644 index 000000000000..87385966e67f --- /dev/null +++ b/nvkm/subdev/volt/gk20a.c @@ -0,0 +1,202...

Some Tegra drivers might be complied as kernel modules, and they need the fuse information for initialization. One example is the GK20A Nouveau driver. It needs the GPU speedo value to calculate frequency-voltage table. So export the tegra_sku_info. Signed-off-by: Vince Hsu <vinceh at nvidia.com> --- v2: add more description why we need this patch drivers/soc/tegra/fuse/fuse-tegra.c | 1

...}, >> }, >> { >> .base = { >> .domain[nv_clk_src_gpc] = 756000, >> + .voltage = 12, >> }, >> }, >> { >> .base = { >> .domain[nv_clk_src_gpc] = 804000, >> + .voltage = 13, >> }, >> }, >> { >> .base = { >> .domain[nv_clk_src_gpc] = 852000, >> + .voltage = 14, >> }, >> }, >> }; > > Is there a partic...

Signed-off-by: Vince Hsu <vinceh at nvidia.com> --- nvkm/subdev/volt/base.c | 67 ++++++++++++++++++++++++++++--------------------- 1 file changed, 38 insertions(+), 29 deletions(-) diff --git a/nvkm/subdev/volt/base.c b/nvkm/subdev/volt/base.c index 32794a999106..26ccd8df193f 100644 --- a/nvkm/subdev/volt/base.c +++ b/nvkm/subdev/volt/base.c @@ -101,6 +101,41 @@ nouveau_volt_set_id(struct

Some Tegra drivers might be compiled as kernel modules, and they need the fuse information for initialization. One example is the GK20A Nouveau driver. It needs the GPU speedo value to calculate frequency-voltage table. So export the tegra_sku_info. Signed-off-by: Vince Hsu <vinceh at nvidia.com> Acked-by: Alexandre Courbot <acourbot at nvidia.com> Acked-by: Thierry Reding <treding

Some Tegra drivers might be compiled as kernel modules, and they need the fuse information for initialization. One example is the GK20A Nouveau driver. It needs the GPU speedo value to calculate frequency-voltage table. So export the tegra_sku_info. Signed-off-by: Vince Hsu <vinceh at nvidia.com> Acked-by: Alexandre Courbot <acourbot at nvidia.com> Acked-by: Thierry Reding <treding

...e = { + .domain[nv_clk_src_gpc] = 648000, + }, + }, + { + .base = { + .domain[nv_clk_src_gpc] = 684000, + }, + }, + { + .base = { + .domain[nv_clk_src_gpc] = 708000, + }, + }, + { + .base = { + .domain[nv_clk_src_gpc] = 756000, + }, + }, + { + .base = { + .domain[nv_clk_src_gpc] = 804000, + }, + }, + { + .base = { + .domain[nv_clk_src_gpc] = 852000, + }, + }, +}; + +static int +gk20a_clock_read(struct nouveau_clock *clk, enum nv_clk_src src) +{ + struct gk20a_clock_priv *priv = (void *)clk; + + switch (src) { + case nv_clk_src_crystal: + return nv_device(clk)->crystal; + c...

....domain[nv_clk_src_gpc] = 684000, > + }, > + }, > + { > + .base = { > + .domain[nv_clk_src_gpc] = 708000, > + }, > + }, > + { > + .base = { > + .domain[nv_clk_src_gpc] = 756000, > + }, > + }, > + { > + .base = { > + .domain[nv_clk_src_gpc] = 804000, > + }, > + }, > + { > + .base = { > + .domain[nv_clk_src_gpc] = 852000, > + }, > + }, > +}; > + > +static int > +gk20a_clock_read(struct nouveau_clock *clk, enum nv_clk_src src) > +{ > + struct gk20a_clock_priv *priv = (void *)clk; > + > + switch (...

This series adds support for reclocking on GK20A. The first two patches touch the clock subsystem to allow GK20A to operate, by making the presence of the thermal and voltage devices optional, and allowing pstates to be provided directly instead of being probed using the BIOS (which Tegra does not have). The last patch adds the GK20A clock device. Arguably the clock can be seen as a stripped-down

Second version of the gk20a clock patches. I have tried to keep the therm and volt devices mandatory in the clock driver, but unfortunately they are too tied to bios to allow this, at least for the moment. Consequently this version is mostly a port of the first version to Ben's tree. Ben, please let me know what I have done wrong in terms of integration to your tree, as the main purpose of