[PATCH v5 0/2] simplefb: Add regulator handling support

From: Chen-Yu Tsai
Date: Mon Nov 16 2015 - 23:31:33 EST

Hi everyone,

This is v5 of the simplefb regulator support series. This series adds
regulator claiming and enabling support for simplefb.

Hans, I dropped your Reviewed-by tag from patch 2 since v4.

Changes since v5:
- Rebased onto v4.4-rc1
- Dropped dts patches (merged)

Changes since v4:
- Fixed inverted logic when testing the property name.
- Fixed regulator supply name string copy length off by 1.
- Added real world user, MSI Primo 81 dts patches.

Changes since v3:
- Dropped extra "if" which is always true, leftover from v1.
- Updated commit message of patch 1

Sometimes the simplefb display output path consits of external conversion
chips and/or LCD drivers and backlights. These devices normally have
GPIOs to turn them on and/or bring them out of reset, and regulators
supplying power to them.

While the kernel does not touch unclaimed GPIOs, the regulator core
happily disables unused regulators. Thus we need simplefb to claim
and enable the regulators used throughout the display pipeline.

The binding supports any named regulator supplies under its device
node. The driver will look through its properties, and claim any
regulators by matching "*-supply", as Mark suggested.

I've not done a generic helper in the regulator core yet, instead doing
the regulator property handling in the simplefb code for now.

Patch 1 adds the regulator properties to the DT binding.

Patch 2 adds code to the simplefb driver to claim and enable regulators.


Chen-Yu Tsai (2):
dt-bindings: simplefb: Support regulator supply properties
simplefb: Claim and enable regulators

.../bindings/display/simple-framebuffer.txt | 13 ++-
drivers/video/fbdev/simplefb.c | 120 ++++++++++++++++++++-
2 files changed, 128 insertions(+), 5 deletions(-)


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/