[PATCH] ARM: dts: rockchip: Remove bogus 'i2s_clk_out' from rk3288-veyron-mickey

t's remove it. NOTE: for other rk3288-veyron devices this clock is consumed by 'maxim,max98090'. Presumably if this clock is needed for mickey it'll need to be consumed by something similar. Signed-off-by: Douglas Anderson --- arch/arm/boot/dts/rk3288-veyron-mickey.dts | 2 -- 1 file changed, 2 dele

[PATCH] ARM: dts: rockchip: Make rk3288-veyron-mickey's emmc work again

t not mine? In any case, hs200 seems good now. Let's turn it on. Signed-off-by: Douglas Anderson --- arch/arm/boot/dts/rk3288-veyron-mickey.dts | 4 1 file changed, 4 deletions(-) diff --git a/arch/arm/boot/dts/rk3288-veyron-mickey.dts b/arch/arm/boot/dts/rk3288-veyron-mickey.dts index e8

[PATCH] ARM: dts: rockchip: Make rk3288-veyron-minnie run at hs200

o ff0f.dwmmc > bind while true; do if [ -e /dev/mmcblk2 ]; then break; fi sleep .1 done done It worked fine. [1] https://lkml.kernel.org/r/20190503233526.226272-1-diand...@chromium.org Signed-off-by: Douglas Anderson --- arch/arm/boot/dts/rk3288-veyron-m

[PATCH] mmc: block: Fix memory leak in blk-mq when cleaning up

[<5102b986>] mmc_blk_alloc_req+0xf8/0x2d4 [] mmc_blk_probe+0x4a8/0x6c0 [<0dfdd9d5>] mmc_bus_probe+0x24/0x28 It's pretty clear that we're missing a call to blk_mq_free_tag_set(). Let's add it. Fixes: 81196976ed94 ("mmc: block: Add blk-mq support") Signed-off-by: Doug

[PATCH] clk: rockchip: Don't yell about bad mmc phases when getting

then we'll see the yells in rockchip_mmc_set_phase(). Fixes: 4bf59902b500 ("clk: rockchip: Prevent calculating mmc phase if clock rate is zero") Signed-off-by: Douglas Anderson --- drivers/clk/rockchip/clk-mmc-phase.c | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git

Re: [PATCH pstore-next v2 2/4] pstore: Allocate compression during late_initcall()

Hi, On Thu, Oct 18, 2018 at 11:56 AM Kees Cook wrote: > > From: "Joel Fernandes (Google)" > > ramoops's call of pstore_register() was recently moved to run during > late_initcall() because the crypto backend may not have been ready during > postcore_initcall(). This meant early-boot crash dumps

[PATCH] pstore/ram: Improve backward compatibility with older Chromebooks

e top level, left everything but the record size as 0, and somehow doesn't want this behavior, we can try to add more conditions here. Signed-off-by: Douglas Anderson --- fs/pstore/ram.c | 18 ++ 1 file changed, 18 insertions(+) diff --git a/fs/pstore/ram.c b/fs/pstore/ram.c

[PATCH 4/5] ARM: dts: rockchip: Add unwedge pinctrl entries for dw_hdmi on rk3288

lt;_ddc_unwedge>; Note that this isn't added by default because some boards may choose to mux i2c5 for their DDC bus (if that is more tested for them). Signed-off-by: Douglas Anderson --- arch/arm/boot/dts/rk3288.dtsi | 9 + 1 file changed, 9 insertions(+) diff --git a/arch/arm/boot/

[PATCH 5/5] ARM: dts: rockchip: Add HDMI i2c unwedging for rk3288-veyron

Veyron uses the builtin i2c controller that's part of dw-hdmi. Hook up the unwedging feature. Signed-off-by: Douglas Anderson --- arch/arm/boot/dts/rk3288-veyron.dtsi | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/arch/arm/boot/dts/rk3288-veyron.dtsi b/arch/arm/boot

[PATCH 3/5] ARM: dts: rockchip: Switch to builtin HDMI DDC bus on rk3288-veyron

working. Signed-off-by: Douglas Anderson --- arch/arm/boot/dts/rk3288-veyron.dtsi | 11 ++- 1 file changed, 2 insertions(+), 9 deletions(-) diff --git a/arch/arm/boot/dts/rk3288-veyron.dtsi b/arch/arm/boot/dts/rk3288-veyron.dtsi index 1252522392c7..e1bee663d2c5 100644 --- a/arch/arm/boot

[PATCH v2] mmc: dw_mmc: Disable SDIO interrupts while suspended to fix suspend/resume

190404040106.40519-1-diand...@chromium.org [2] https://crrev.com/c/230765 Cc: # 4.14.x Signed-off-by: Douglas Anderson --- I didn't put any "Fixes" tag here, but presumably this could be backported to whichever kernels folks found it useful for. I have at least confirmed that kernels v4

[PATCH v2] ARM: errata: Workaround errata A12 857271 / A17 857272

]. Apparently the two errata got lumped together at some point in time. Let's actually get the workaround landed. [1] https://crrev.com/c/342753 [2] https://crbug.com/711784 Signed-off-by: Douglas Anderson Signed-off-by: Sonny Rao --- Changes in v2: - Squashed bits 10 and 11 into one errata

[PATCH 2/2] ARM: errata: add support for A12/A17 errata CR711784

are in http://crbug.com/711784 This erratum has no known number and thus I have tagged it CR711784 (after the Chrome OS bug number). I have created separate A12 / A17 configs to match how the rest of the A12 / A17 errata is handled. Signed-off-by: Douglas Anderson --- arch/arm/Kconfig

[PATCH 1/2] ARM: errata: Workaround errata A12 857271 / A17 857272

Signed-off-by: Douglas Anderson --- arch/arm/Kconfig | 19 +++ arch/arm/mm/proc-v7.S | 10 ++ 2 files changed, 29 insertions(+) diff --git a/arch/arm/Kconfig b/arch/arm/Kconfig index b509cd338219..4376fe74f95e 100644 --- a/arch/arm/Kconfig +++ b/arch/arm/Kconfig

[PATCH v2] clk: rockchip: undo several noc and special clocks as critical on rk3288

1], pclk_publ0[0-1]: On veyron Chromebooks we turn these 4 clocks on only when doing DDR transitions and they are off otherwise. I see no reason why they'd need to be on in the upstream kernel which doesn't support DDRFreq. Signed-off-by: Douglas Anderson --- Changes in v2: - Now keep pmu_hclk_

[PATCH 5/5] ARM: dts: rockchip: vdd_gpu off in suspend for rk3288-veyron

. It's unclear why the GPU is left enabled during suspend on the mainline kernel. Everything seems fine if I turn this off, so let's do it. Signed-off-by: Douglas Anderson --- arch/arm/boot/dts/rk3288-veyron.dtsi | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/arch/arm/boot/dts

[PATCH 3/5] ARM: dts: rockchip: Add DDR retention/poweroff to rk3288-veyron hogs

Even though upstream Linux doesn't yet go into deep enough suspend to get DDR into self refresh, there is no harm in setting these pins up. They'll only actually do something if we go into a deeper suspend but leaving them configed always is fine. Signed-off-by: Douglas Anderson --- arch/arm

[PATCH 2/5] ARM: rockchip: pm: Mark init functions __init

The functions rk3288_config_bootdata() and rk3288_suspend_init() are only called in the context of rockchip_suspend_init() which is already marked __init. We can mark them __init too. Signed-off-by: Douglas Anderson --- arch/arm/mach-rockchip/pm.c | 4 ++-- 1 file changed, 2 insertions(+), 2

[PATCH 4/5] ARM: dts: rockchip: vcc33_ccd off in suspend for rk3288-veyron-chromebook

g it on for now seems fine until we get suspend/resume > more solid. It's probably about time to do it right. [1] https://lore.kernel.org/linux-arm-kernel/CAD=FV=u37yx8mqk75_x05zxonvdc3qrmhqp8tytdpwghqsu...@mail.gmail.com/ Signed-off-by: Douglas Anderson --- arch/arm/boot/dts/rk3288-veyr

[PATCH 1/5] clk: rockchip: Turn on "aclk_dmac1" for suspend

o anything more than ungate it. In this case I have chosen D) because it seemed like the least work, but any of the other options would presumably also work fine. Signed-off-by: Douglas Anderson --- drivers/clk/rockchip/clk-rk3288.c | 11 +++ 1 file changed, 11 insertions(+) diff --git a/

[PATCH v2] clk: rockchip: Fix video codec clocks on rk3288

oo. [1] https://lkml.kernel.org/r/1d17b015-9e17-34b9-baf8-c285dc195...@rock-chips.com Fixes: 4d3e84f99628 ("clk: rockchip: describe aclk_vcodec using the new muxgrf type on rk3288") Suggested-by: Jonas Karlman Suggested-by: Randy Li Signed-off-by: Douglas Anderson --- Changes in v2:

[PATCH] soc: rockchip: Set the proper PWM for rk3288

r to set this bit. ...but occasionally folks have pointed back to my old patch series [1] in downstream kernels. [1] https://www.mail-archive.com/linux-kernel@vger.kernel.org/msg1391597.html Signed-off-by: Douglas Anderson --- drivers/soc/rockchip/grf.c | 2 ++ 1 file changed, 2 insertions(+)

[PATCH 2/3] clk: rockchip: Make rkpwm a critical clock on rk3288

pointed to the clock for the old IP block and they've all worked due to the fact that rkpwm was IGNORE_UNUSED and that the clock rates for both clocks were the same. Signed-off-by: Douglas Anderson --- drivers/clk/rockchip/clk-rk3288.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff

[PATCH 1/3] Revert "clk: rockchip: mark noc and some special clk as critical on rk3288"

been gated in shipping veyron Chromebooks so presumably this chip defect doesn't affect all boards. Signed-off-by: Douglas Anderson --- drivers/clk/rockchip/clk-rk3288.c | 14 -- 1 file changed, 4 insertions(+), 10 deletions(-) diff --git a/drivers/clk/rockchip/clk-rk3288.c b/drivers/clk/ro

[PATCH 3/3] ARM: dts: rockchip: fix PWM clock found on RK3288 Socs

From: Caesar Wang We use the new PWM IP on RK3288, but the PWM's clock indeed incorrect. Signed-off-by: Caesar Wang Signed-off-by: Douglas Anderson --- arch/arm/boot/dts/rk3288.dtsi | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/arch/arm/boot/dts/rk3288.dtsi b

[PATCH 0/3] rockchip: A few clock cleanups for rk3288

the PWM marked as a critical clock _definitely_ needs to land before switching the clock in the device tree. Caesar Wang (1): ARM: dts: rockchip: fix PWM clock found on RK3288 Socs Douglas Anderson (2): Revert "clk: rockchip: mark noc and some special clk as critical on rk3288&q

[PATCH v3] platform/chrome: cros_ec_spi: Transfer messages at high priority

s this patch will still not make things worse. [1] https://crbug.com/678675 Signed-off-by: Douglas Anderson --- Changes in v3: - Use flush_work(), not a completion (Brian) Changes in v2: - Use system_highpri_wq + completion (Matthias) - Avoid duplication by using a function pointer (Matthias)

[PATCH v2] platform/chrome: cros_ec_spi: Transfer messages at high priority

s this patch will still not make things worse. [1] https://crbug.com/678675 Signed-off-by: Douglas Anderson --- Changes in v2: - Use system_highpri_wq + completion (Matthias) - Avoid duplication by using a function pointer (Matthias) drivers/platform/chrome/cros_ec_spi.c | 83 +++

[PATCH] platform/chrome: cros_ec_spi: Transfer messages at high priority

tion. Even if it isn't true sometimes this patch will still not make things worse. [1] https://crbug.com/678675 Signed-off-by: Douglas Anderson --- drivers/platform/chrome/cros_ec_spi.c | 107 -- 1 file changed, 101 insertions(+), 6 deletions(-) diff --git a/drivers/platfor

[PATCH v5 6/7] ARM: dts: rockchip: Specify rk3288-veyron-chromebook's display timings

://crrev.com/c/324558. NOTE: minnie uses a different panel will be fixed up in a future patch, so for now we'll just delete the panel timings there. Signed-off-by: Douglas Anderson --- Changes in v5: - It's not just jerry, it's most rk3288 Chromebooks (Heiko) Changes in v4: - rk3288-veyron

[PATCH] clk: rockchip: Fix video codec clocks on rk3288

signed-clocks and the video codec still probes OK. Fixes: 4d3e84f99628 ("clk: rockchip: describe aclk_vcodec using the new muxgrf type on rk3288") Signed-off-by: Douglas Anderson --- I currently have no way to test the JPEG mem2mem driver, so hopefully others can test this and make s

[PATCH v2 2/2] ARM: dts: rockchip: Add device tree for rk3288-veyron-mighty

a "dtsi" and Mighty just adds the SD write protect (needed for a full-sized SD slot). We'll do this upstream by just including the Jaq dts and make the changes. Signed-off-by: Douglas Anderson --- Changes in v2: - Directly include the jaq dts and just specify diffs. arch/arm/boot/dt

[PATCH v2 1/2] dt-bindings: ARM: dts: rockchip: Add bindings for rk3288-veyron-mighty

Mighty is basically the same Chromebook as Jaq but it has a full-sized SD slot and some different (slightly more rugged) plastics around it. Like Jaq, Mighty may show up with various different brandings but all of them have the same board inside. Signed-off-by: Douglas Anderson Reviewed-by: Rob

[PATCH 2/2] ARM: dts: rockchip: Add rk3288-veyron-jerry rev 10-15

safety if we match them here just in case something actually shipped with one of these revisions and that device will break if we don't claim support. Signed-off-by: Douglas Anderson --- arch/arm/boot/dts/rk3288-veyron-jerry.dts | 5 - 1 file changed, 4 insertions(+), 1 deletion(-) diff --git

[PATCH 1/2] dt-bindings: ARM: dts: rockchip: Add rk3288-veyron-jerry rev 10-15

safety if we match them here just in case something actually shipped with one of these revisions and that device will break if we don't claim support. Signed-off-by: Douglas Anderson --- Documentation/devicetree/bindings/arm/rockchip.yaml | 6 ++ 1 file changed, 6 insertions(+) diff --git

[PATCH 2/2] ARM: dts: rockchip: Add device tree for rk3288-veyron-mighty

a "dtsi" and Mighty just adds the SD write protect (needed for a full-sized SD slot). It seems cleaner for upstream just to add a separate dts file, though. Signed-off-by: Douglas Anderson --- arch/arm/boot/dts/Makefile | 1 + arch/arm/boot/dts/rk3288-veyron-mighty

[PATCH 1/2] dt-bindings: ARM: dts: rockchip: Add bindings for rk3288-veyron-mighty

Mighty is basically the same Chromebook as Jaq but it has a full-sized SD slot and some different (slightly more rugged) plastics around it. Like Jaq, Mighty may show up with various different brandings but all of them have the same board inside. Signed-off-by: Douglas Anderson

[PATCH] ARM: dts: rockchip: Add dvs-gpios to rk3288-veyron-jerry

age transitions. [1] https://lore.kernel.org/linux-arm-kernel/CAD=FV=wwfgjzbk9xf5tu_ie6unhqmyrz176d4+jjtwwooak...@mail.gmail.com/ Fixes: f3ee390e4ef2 ("ARM: dts: rockchip: add veyron-jerry board") Signed-off-by: Douglas Anderson --- arch/arm/boot/dts/rk3288-veyron-jerry.dts | 4 +++-

[PATCH] ARM: dts: rockchip: Add vdd_logic to rk3288-veyron

d found that with the upstream kernel voltage difference between requested and actual was 9.2 mV at 950 mV and 13.4 mV at 1350 mV with in-between voltages consistently showing ~1% error. This error is likely expected as voltage can be seen to sag a bit when more load is put on the rail. Signed-off-by: D

[PATCH 4/4] ARM: dts: rockchip: Remove #address/#size-cells from rk3288-veyron gpio-keys

They are pointless. As dtc points out: Warning (avoid_unnecessary_addr_size): /gpio-keys: unnecessary #address-cells/#size-cells without "ranges" or child "reg" property Let's remove them. Signed-off-by: Douglas Anderson --- arch/arm/boot/dts/rk3288-veyron.dtsi |

[PATCH 1/4] ARM: dts: rockchip: Fix gic/efuse sort ordering for rk3288

It can be seen that 0xffb4 < 0xffc01000, thus efuse comes first. Signed-off-by: Douglas Anderson --- arch/arm/boot/dts/rk3288.dtsi | 26 +- 1 file changed, 13 insertions(+), 13 deletions(-) diff --git a/arch/arm/boot/dts/rk3288.dtsi b/arch/arm/boot/dts/rk3288.d

[PATCH 3/4] ARM: dts: rockchip: Remove #address/#size-cells from rk3288 mipi_dsi

They are pointless. As dtc points out: Warning (avoid_unnecessary_addr_size): /mipi@ff96: unnecessary #address-cells/#size-cells without "ranges" or child "reg" property Let's remove them. Signed-off-by: Douglas Anderson --- arch/arm/boot/dts/rk3288.dtsi | 2 -

[PATCH 2/4] ARM: dts: rockchip: Fix gpu opp node names for rk3288

The device tree compiler yells like this: Warning (unit_address_vs_reg): /gpu-opp-table/opp@1: node has a unit name, but no reg property Let's match the cpu opp node names and use a dash. Signed-off-by: Douglas Anderson --- arch/arm/boot/dts/rk3288.dtsi | 12 ++-- 1 file

[PATCH v6 2/3] tracing: Add trace_total_entries() / trace_total_entries_cpu()

These two new exported functions will be used in a future patch by kdb_ftdump() to quickly skip all but the last few trace entries. Suggested-by: Steven Rostedt Signed-off-by: Douglas Anderson Acked-by: Daniel Thompson --- Changes in v6: - Add Daniel Thompson Ack. Changes in v5: None Changes

[PATCH] Revert "modsign: Abort modules_install when signing fails"

://lkml.kernel.org/r/CAK7LNASde0Q9S5GKeQiWhArfER4S4wL1=R_FW8q0++_X3T5=h...@mail.gmail.com Signed-off-by: Douglas Anderson --- scripts/Makefile.modinst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/scripts/Makefile.modinst b/scripts/Makefile.modinst index ff5ca9817a85..0dae402661f3

[PATCH] kbuild: Make NOSTDINC_FLAGS a simply expanded variable

sive expansion the patch would have just removed the ":". Signed-off-by: Douglas Anderson --- Makefile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Makefile b/Makefile index 9ef547fc7ffe..3034ba66ad51 100644 --- a/Makefile +++ b/Makefile @@ -402,7 +402,7 @@ CH

[PATCH] kbuild: If the module stripping command fails the build should abort

If the call to strip returns an error code then it makes sense for the build to fail. Currently we'll just chug along and ship unstripped modules. Fixes: e2a666d52b48 ("kbuild: sign the modules at install time") Signed-off-by: Douglas Anderson --- scripts/Makefile.modinst | 2

[PATCH] kbuild: Speed up install, modules_install and kernelrelease

l kernel build/install. With my current setup, this brings it from ~40 seconds to ~28 seconds. Re-introducing the Makefile cache would likely save us an extra ~3 seconds since we'd avoid the parsing in the compile stage. Signed-off-by: Douglas Anderson --- Makefile | 14 ++ 1 file chan

[PATCH v2 1/2] tracing: kdb: Fix ftdump to not sleep

last few lines of the buffer will also be hard to implement. [1] https://lkml.kernel.org/r/20161117191605.ga21...@google.com Reported-by: Brian Norris Signed-off-by: Douglas Anderson --- Changes in v2: - Don't introduce _ring_buffer_read_prepare(), just change args include/linux/ring_buffer.h

[PATCH v2 2/2] tracing: kdb: Allow ftdump to skip all but the last few lines

lines you should skip. Let's do similar to python and allow you to use a negative number to indicate that you want to skip all lines except the last few. This allows you to quickly see what you want. Signed-off-by: Douglas Anderson --- Changes in v2: None kernel/trace/trace_kdb.c | 51

[PATCH 2/2] tracing: kdb: Allow ftdump to skip all but the last few lines

lines you should skip. Let's do similar to python and allow you to use a negative number to indicate that you want to skip all lines except the last few. This allows you to quickly see what you want. Signed-off-by: Douglas Anderson --- kernel/trace/trace_kdb.c | 51

[PATCH 1/2] tracing: kdb: Fix ftdump to not sleep

A future patch to dump only the last few lines of the buffer will also be hard to implement. [1] https://lkml.kernel.org/r/20161117191605.ga21...@google.com Reported-by: Brian Norris Signed-off-by: Douglas Anderson --- include/linux/ring_buffer.h | 2 ++ kernel/trace/ring_buffer.c | 42 +++

[PATCH v2] iommu/arm-smmu: Break insecure users by disabling bypass by default

. Suggested-by: Robin Murphy Signed-off-by: Douglas Anderson --- Changes in v2: - Flipped default to 'yes' and changed comments a lot. drivers/iommu/Kconfig| 25 + drivers/iommu/arm-smmu.c | 3 ++- 2 files changed, 27 insertions(+), 1 deletion(-) diff --git a/drivers

[PATCH] iommu/arm-smmu: Allow disabling bypass via kernel config

the existing ability to adjust the configuration via kernel command line. Signed-off-by: Douglas Anderson --- drivers/iommu/Kconfig| 22 ++ drivers/iommu/arm-smmu.c | 3 ++- 2 files changed, 24 insertions(+), 1 deletion(-) diff --git a/drivers/iommu/Kconfig b/drivers/iommu

[PATCH 1/2] PM / Domains: Mark "name" const in genpd_dev_pm_attach_by_name()

red "const" in a driver. Fixes: 5d6be70add65 ("PM / Domains: Introduce option to attach a device by name to genpd") Signed-off-by: Douglas Anderson --- drivers/base/power/domain.c | 2 +- include/linux/pm_domain.h | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) d

[PATCH 2/2] PM / Domains: Mark "name" const in dev_pm_domain_attach_by_name()

f445 ("PM / Domains: Introduce dev_pm_domain_attach_by_name()") Signed-off-by: Douglas Anderson --- drivers/base/power/common.c | 2 +- include/linux/pm_domain.h | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/drivers/base/power/common.c b/drivers/base/power/c

[PATCH] soc: qcom: rpmhpd: Set 'active_only' for active only power domains

river") Signed-off-by: Douglas Anderson --- drivers/soc/qcom/rpmhpd.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/drivers/soc/qcom/rpmhpd.c b/drivers/soc/qcom/rpmhpd.c index 5741ec3fa814..51850cc68b70 100644 --- a/drivers/soc/qcom/rpmhpd.c +++ b/drivers/soc/qcom/rpmhpd.c @@ -

[PATCH] dts: arm64/sdm845: Add clocks to WCN3990 WLAN module device node

the clock should be there, so let's add it. Fixes: be7019103469 ("dts: arm64/sdm845: Add WCN3990 WLAN module device node") Signed-off-by: Douglas Anderson --- arch/arm64/boot/dts/qcom/sdm845.dtsi | 2 ++ 1 file changed, 2 insertions(+) diff --git a/arch/arm64/boot/dts/qcom/sdm845.dtsi b

[PATCH v2 2/2] drm/msm: Cleanup A6XX opp-level reading

The patch ("OPP: Add support for parsing the 'opp-level' property") adds an API enabling a cleaner way to read the opp-level. Let's use the new API. Signed-off-by: Douglas Anderson Reviewed-by: Jordan Crouse --- Obviously this can't land until we have a tree that contains the pa

[PATCH v2 1/2] drm/msm: Fix A6XX support for opp-level

vice support") Signed-off-by: Douglas Anderson --- Changes in v2: - Split into two patches to facilitate landing. drivers/gpu/drm/msm/adreno/a6xx_gmu.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/gpu/drm/msm/adreno/a6xx_gmu.c b/drivers/gpu/drm/msm/adreno

[PATCH] drm/msm: Fix A6XX support for opp-level

e nodes") since if a tree contains the device tree patch but not this one you'll get a crash at bootup. Signed-off-by: Douglas Anderson --- drivers/gpu/drm/msm/adreno/a6xx_gmu.c | 17 ++--- 1 file changed, 6 insertions(+), 11 deletions(-) diff --git a/drivers/gpu/drm/msm/

[PATCH v2] regulator: core: Clean enabling always-on regulators + their supplies

Fixes: 1fc12b05895e ("regulator: core: Avoid propagating to supplies when possible") Reported-by: Evan Green Signed-off-by: Douglas Anderson Tested-by: Brian Masney --- Changes in v2: - Rebased to 4.21 since the CL it fixes is there. drivers/regulator/core.c | 19 --- 1 fil

[PATCH] debug: Allow forcing entering debug mode on panic/exception

bug kernels. Hopefully having this extra config option is OK and useful to others who would also prefer to make sure that kgdb is always entered on a panic no matter what userspace might request. Signed-off-by: Douglas Anderson --- kernel/debug/debug_core.c | 5 +++-- lib/Kconfig.kgdb

[PATCH] regulator: core: Clean enabling always-on regulators + their supplies

Fixes: 1fc12b05895e ("regulator: core: Avoid propagating to supplies when possible") Reported-by: Evan Green Signed-off-by: Douglas Anderson --- drivers/regulator/core.c | 19 --- 1 file changed, 16 insertions(+), 3 deletions(-) diff --git a/drivers/regulator/core.c b/

[PATCH] regulator: core: Clean enabling always-on regulators + their supplies

Fixes: 1fc12b05895e ("regulator: core: Avoid propagating to supplies when possible") Reported-by: Evan Green Signed-off-by: Douglas Anderson --- drivers/regulator/core.c | 19 --- 1 file changed, 16 insertions(+), 3 deletions(-) diff --git a/drivers/regulator/core.c b/

[PATCH v2] arm64: dts: sdm845: Add videocc node

From: Taniya Das This adds the video clock controller node to sdm845 based on the examples in the bindings. Signed-off-by: Taniya Das Signed-off-by: Douglas Anderson --- Changes in v2: - Add #reset-cells = <1>. - Sort properly. arch/arm64/boot/dts/qcom/sdm845.dtsi | 9 +

[PATCH v2] arm64: dts: sdm845: Add videocc node

From: Taniya Das This adds the video clock controller node to sdm845 based on the examples in the bindings. Signed-off-by: Taniya Das Signed-off-by: Douglas Anderson --- Changes in v2: - Add #reset-cells = <1>. - Sort properly. arch/arm64/boot/dts/qcom/sdm845.dtsi | 9 +

[PATCH 2/2] arm64: dts: sdm845: Add gpu clock controller node

Add the GPU clock controller nodes as per the example. Signed-off-by: Douglas Anderson --- arch/arm64/boot/dts/qcom/sdm845.dtsi | 11 +++ 1 file changed, 11 insertions(+) diff --git a/arch/arm64/boot/dts/qcom/sdm845.dtsi b/arch/arm64/boot/dts/qcom/sdm845.dtsi index 1419b0098cb3

[PATCH 2/2] arm64: dts: sdm845: Add gpu clock controller node

Add the GPU clock controller nodes as per the example. Signed-off-by: Douglas Anderson --- arch/arm64/boot/dts/qcom/sdm845.dtsi | 11 +++ 1 file changed, 11 insertions(+) diff --git a/arch/arm64/boot/dts/qcom/sdm845.dtsi b/arch/arm64/boot/dts/qcom/sdm845.dtsi index 1419b0098cb3

[PATCH 1/2] dt-bindings: clock: qcom: Fix the xo parent in gpucc example

is actually provided by the RPMh Clock Controller. Presumably that's the one that was wanted. Let's update the example to make this clearer. Fixes: e431c92188a9 ("dt-bindings: clock: Introduce QCOM Graphics clock bindings") Signed-off-by: Douglas Anderson --- Documentation/device

[PATCH 1/2] dt-bindings: clock: qcom: Fix the xo parent in gpucc example

is actually provided by the RPMh Clock Controller. Presumably that's the one that was wanted. Let's update the example to make this clearer. Fixes: e431c92188a9 ("dt-bindings: clock: Introduce QCOM Graphics clock bindings") Signed-off-by: Douglas Anderson --- Documentation/device

[PATCH] clk: qcom: gpu_cc_gmu_clk_src has 5 parents, not 6

is goes boom at bootup. Fixes: 453361cdd757 ("clk: qcom: Add graphics clock controller driver for SDM845") Signed-off-by: Douglas Anderson --- drivers/clk/qcom/gpucc-sdm845.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/clk/qcom/gpucc-sdm845.c b/drivers/cl

[PATCH] clk: qcom: gpu_cc_gmu_clk_src has 5 parents, not 6

is goes boom at bootup. Fixes: 453361cdd757 ("clk: qcom: Add graphics clock controller driver for SDM845") Signed-off-by: Douglas Anderson --- drivers/clk/qcom/gpucc-sdm845.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/clk/qcom/gpucc-sdm845.c b/drivers/cl

[PATCH] dt-bindings: clock: Require #reset-cells in sdm845-videocc

1603 ("dt-bindings: clock: Introduce QCOM Video clock bindings") Suggested-by: Stephen Boyd Signed-off-by: Douglas Anderson --- Documentation/devicetree/bindings/clock/qcom,videocc.txt | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/Documentation/devicetree/bindings/clo

[PATCH] dt-bindings: clock: Require #reset-cells in sdm845-videocc

1603 ("dt-bindings: clock: Introduce QCOM Video clock bindings") Suggested-by: Stephen Boyd Signed-off-by: Douglas Anderson --- Documentation/devicetree/bindings/clock/qcom,videocc.txt | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/Documentation/devicetree/bindings/clo

[PATCH] regulator: core: Apply system load even if no consumer loads

) Reported-by: Brian Masney Signed-off-by: Douglas Anderson Tested-by: Brian Masney --- drivers/regulator/core.c | 6 ++ 1 file changed, 6 insertions(+) diff --git a/drivers/regulator/core.c b/drivers/regulator/core.c index dbe2f2e6e625..dffee5432ca1 100644 --- a/drivers/regulator/core.c +++

[PATCH] regulator: core: Apply system load even if no consumer loads

) Reported-by: Brian Masney Signed-off-by: Douglas Anderson Tested-by: Brian Masney --- drivers/regulator/core.c | 6 ++ 1 file changed, 6 insertions(+) diff --git a/drivers/regulator/core.c b/drivers/regulator/core.c index dbe2f2e6e625..dffee5432ca1 100644 --- a/drivers/regulator/core.c +++

[PATCH v2 2/2] regulator: core: Avoid propagating to supplies when possible

gether in one patch. Also: since this comes after commit f8702f9e4aa7 ("regulator: core: Use ww_mutex for regulators locking") we can now move to use _regulator_disable() for our supply and keep it in the lock. Signed-off-by: Douglas Anderson --- NOTE: this patch is based atop the patch (&q

[PATCH v2 2/2] regulator: core: Avoid propagating to supplies when possible

gether in one patch. Also: since this comes after commit f8702f9e4aa7 ("regulator: core: Use ww_mutex for regulators locking") we can now move to use _regulator_disable() for our supply and keep it in the lock. Signed-off-by: Douglas Anderson --- NOTE: this patch is based atop the patch (&q

[PATCH v2 1/2] regulator: core: Only count load for enabled consumers

optimization still for some cases, it's cleaner to just remove it. A later patch will attempt to get some efficiency back by not propogating enables up unnecessarily. Signed-off-by: Douglas Anderson --- Please give this patch lots of extra review. It seems to work for me, but I haven't d

[PATCH v2 1/2] regulator: core: Only count load for enabled consumers

optimization still for some cases, it's cleaner to just remove it. A later patch will attempt to get some efficiency back by not propogating enables up unnecessarily. Signed-off-by: Douglas Anderson --- Please give this patch lots of extra review. It seems to work for me, but I haven't d

[PATCH 3/7] regulator: core: Don't double-disable supplies in regulator_disable_deferred()

e: Use ww_mutex for regulators locking") Signed-off-by: Douglas Anderson --- drivers/regulator/core.c | 10 -- 1 file changed, 10 deletions(-) diff --git a/drivers/regulator/core.c b/drivers/regulator/core.c index 0052bbc8c531..63a8af1e2256 100644 --- a/drivers/regulator/core.c +++

[PATCH 3/7] regulator: core: Don't double-disable supplies in regulator_disable_deferred()

e: Use ww_mutex for regulators locking") Signed-off-by: Douglas Anderson --- drivers/regulator/core.c | 10 -- 1 file changed, 10 deletions(-) diff --git a/drivers/regulator/core.c b/drivers/regulator/core.c index 0052bbc8c531..63a8af1e2256 100644 --- a/drivers/regulator/core.c +++

[PATCH 6/7] regulator: core: Avoid propagating to supplies when possible

ulators. Signed-off-by: Douglas Anderson --- drivers/regulator/core.c | 7 --- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/drivers/regulator/core.c b/drivers/regulator/core.c index 23e852d38b88..2eda87520832 100644 --- a/drivers/regulator/core.c +++ b/drivers/regulator/core.c @@ -1822

[PATCH 5/7] regulator: core: add enable_count for consumers to debug fs

Now that consumers all keep track of their own enable count, let's add it into the regulator_summary. Signed-off-by: Douglas Anderson --- drivers/regulator/core.c | 5 - 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/drivers/regulator/core.c b/drivers/regulator/core.c index

[PATCH 4/7] regulator: core: Only count load for enabled consumers

optimization still for some cases, it's cleaner to just remove it. A later patch will attempt to get some efficiency back by not propogating enables up unnecessarily. Signed-off-by: Douglas Anderson --- Please give this patch lots of extra review. It seems to work for me, but I haven't d

[PATCH 7/7] regulator: core: Remove loop disabling supplies in regulator_force_disable()

_count, but even that might be a little strange. For now let's just remove the code and we can add something back in if someone can explain what's expected. Fixes: f8702f9e4aa7 ("regulator: core: Use ww_mutex for regulators locking") Signed-off-by: Douglas Anderson --- drivers/regulator/co

[PATCH 6/7] regulator: core: Avoid propagating to supplies when possible

ulators. Signed-off-by: Douglas Anderson --- drivers/regulator/core.c | 7 --- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/drivers/regulator/core.c b/drivers/regulator/core.c index 23e852d38b88..2eda87520832 100644 --- a/drivers/regulator/core.c +++ b/drivers/regulator/core.c @@ -1822

[PATCH 5/7] regulator: core: add enable_count for consumers to debug fs

Now that consumers all keep track of their own enable count, let's add it into the regulator_summary. Signed-off-by: Douglas Anderson --- drivers/regulator/core.c | 5 - 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/drivers/regulator/core.c b/drivers/regulator/core.c index

[PATCH 4/7] regulator: core: Only count load for enabled consumers

optimization still for some cases, it's cleaner to just remove it. A later patch will attempt to get some efficiency back by not propogating enables up unnecessarily. Signed-off-by: Douglas Anderson --- Please give this patch lots of extra review. It seems to work for me, but I haven't d

[PATCH 7/7] regulator: core: Remove loop disabling supplies in regulator_force_disable()

_count, but even that might be a little strange. For now let's just remove the code and we can add something back in if someone can explain what's expected. Fixes: f8702f9e4aa7 ("regulator: core: Use ww_mutex for regulators locking") Signed-off-by: Douglas Anderson --- drivers/regulator/co

[PATCH 2/7] regulator: core: Don't assume always_on when is_enabled returns err

n the code were not properly checking for errors. Let's resolve this. Signed-off-by: Douglas Anderson --- drivers/regulator/core.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/regulator/core.c b/drivers/regulator/core.c index ff5ca185bb8f..0052bbc8c531 100644 ---

[PATCH 1/7] regulator: core: Properly expose requested_microamps in sysfs

The "requested_microamps" sysfs attribute was only being exposed for "current" regulators. This didn't make sense. Allow it to be exposed always. Signed-off-by: Douglas Anderson --- drivers/regulator/core.c | 4 1 file changed, 4 deletions(-) diff --git a/driver

[PATCH 1/7] regulator: core: Properly expose requested_microamps in sysfs

The "requested_microamps" sysfs attribute was only being exposed for "current" regulators. This didn't make sense. Allow it to be exposed always. Signed-off-by: Douglas Anderson --- drivers/regulator/core.c | 4 1 file changed, 4 deletions(-) diff --git a/driver

[PATCH 2/7] regulator: core: Don't assume always_on when is_enabled returns err

n the code were not properly checking for errors. Let's resolve this. Signed-off-by: Douglas Anderson --- drivers/regulator/core.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/regulator/core.c b/drivers/regulator/core.c index ff5ca185bb8f..0052bbc8c531 100644 ---

[PATCH 2/2] arm64: dts: qcom: Add SoC-specific string for sdhci-msm-v4 nodes

As per upstream discussion [1], we should have an SoC-specific compatible string for Qualcomm's SDHCI nodes. Let's add it. [1] https://lkml.kernel.org/r/20181105203657.GA32282@bogus Signed-off-by: Douglas Anderson --- arch/arm64/boot/dts/qcom/msm8916.dtsi | 4 ++-- arch/arm64/boot/dts/qcom

[PATCH 1/2] ARM: dts: qcom: Add SoC-specific string for sdhci-msm-v4 nodes

As per upstream discussion [1], we should have an SoC-specific compatible string for Qualcomm's SDHCI nodes. Let's add it. [1] https://lkml.kernel.org/r/20181105203657.GA32282@bogus Signed-off-by: Douglas Anderson --- arch/arm/boot/dts/qcom-apq8084.dtsi | 4 ++-- arch/arm/boot/dts/qcom

[PATCH 2/2] arm64: dts: qcom: Add SoC-specific string for sdhci-msm-v4 nodes

As per upstream discussion [1], we should have an SoC-specific compatible string for Qualcomm's SDHCI nodes. Let's add it. [1] https://lkml.kernel.org/r/20181105203657.GA32282@bogus Signed-off-by: Douglas Anderson --- arch/arm64/boot/dts/qcom/msm8916.dtsi | 4 ++-- arch/arm64/boot/dts/qcom

[PATCH 1/2] ARM: dts: qcom: Add SoC-specific string for sdhci-msm-v4 nodes

As per upstream discussion [1], we should have an SoC-specific compatible string for Qualcomm's SDHCI nodes. Let's add it. [1] https://lkml.kernel.org/r/20181105203657.GA32282@bogus Signed-off-by: Douglas Anderson --- arch/arm/boot/dts/qcom-apq8084.dtsi | 4 ++-- arch/arm/boot/dts/qcom

[PATCH 1/6] dt-bindings: drm/panel: simple: Add no-hpd property

the HPD isn't hooked up you can look at the timing diagram on the panel datasheet and insert a delay for the maximum amount of time that the HPD might take to come up. Let's add a property in the device tree for this concept. Signed-off-by: Douglas Anderson --- .../devicetree/bindings/display/panel

<    1   2   3   4   5   6   7   8   9   10   >