On 10/14/2017 08:27 PM, Stefan Bruens wrote:
On Montag, 9. Oktober 2017 11:29:43 CEST Maciej Purski wrote:
On 10/01/2017 09:48 PM, Stefan Brüns wrote:
According to the ABI documentation, the shunt resistor value should be
specificied in Ohm. As this is also used/documented for the MAX9611
On 10/24/2017 08:58 PM, Rob Herring wrote:
On Wed, Oct 18, 2017 at 02:47:00PM +0200, Maciej Purski wrote:
Some regulators require keeping their voltage spread below defined
max_spread.
Add properties to provide information on regulators' coupling.
Signed-off-by: Maciej P
On 10/25/2017 02:59 PM, Rob Herring wrote:
On Wed, Oct 25, 2017 at 2:31 AM, Maciej Purski wrote:
On 10/24/2017 08:58 PM, Rob Herring wrote:
On Wed, Oct 18, 2017 at 02:47:00PM +0200, Maciej Purski wrote:
Some regulators require keeping their voltage spread below defined
max_spread.
Add
m and remove double
entries
3. Always lock all coupled regulators and their parents - to avoid deadlock
on common parent, introduce so called reentrant locks (lock which might
be taken multiple times by the same process).
Best regards,
Maciej Purski
--
Changes in RFC v2:
- allow
Some regulators require keeping their voltage spread below defined
max_spread.
Add properties to provide information on regulators' coupling.
Signed-off-by: Maciej Purski
---
Documentation/devicetree/bindings/regulator/regulator.txt | 4
1 file changed, 4 insertions(+)
diff --
which can succeed only if all the coupled regulators are already
initialized, so it should be done only once per coupled regulators group
by the last regulator initialized.
Check if coupled regulators phandles arrays match for all coupled
regulators and if their max_spread values are the same.
d_get_optimal_voltage()
should find the best possible change for the regulator, which doesn't break
max_spread constraint. In function regulator_balance_coupled_voltage()
optimize number of steps by finding highest voltage difference on each
iteration.
MHL1, MHL2 and MHL3 using various vendors' dongles both in
DVI and HDMI mode.
Signed-off-by: Maciej Purski
---
Changes in v2:
- handle MHL1 and MHL2 initialization sequence
- rename hpd_plugged() function to identify_sink(), as it is now used
in different contexts
- fix commit me
Current implementation of mode_valid() and mode_fixup() callbacks
handle packed pixel modes improperly.
Fix it by using proper maximum clock values from the documentation.
Signed-off-by: Maciej Purski
---
drivers/gpu/drm/bridge/sil-sii8620.c | 90
1 file
Signed-off-by: Maciej Purski
---
drivers/gpu/drm/bridge/sil-sii8620.c | 17 +
1 file changed, 1 insertion(+), 16 deletions(-)
diff --git a/drivers/gpu/drm/bridge/sil-sii8620.c
b/drivers/gpu/drm/bridge/sil-sii8620.c
index 1718c2e..e13708d 100644
--- a/drivers/gpu/drm/bridge/sil
The current assumption is that an uncoupled regulator is a special case
of a coupled one, so they should share a common voltage setting path.
Best regards,
Maciej Purski
---
Changes in v4:
- make paths for coupled and uncoupled regulators common
- coupling descriptors are now always pres
Some regulators require keeping their voltage spread below defined
max_spread.
Add properties to provide information on regulators' coupling.
Reviewed-by: Rob Herring
Signed-off-by: Maciej Purski
---
Documentation/devicetree/bindings/regulator/regulator.txt | 5 +
1 file chang
has not been registered.
Add function for locking coupled regulators. Extract a new function
regulator_set_voltage_rdev() from regulator_set_voltage_unlocked(),
which is called when setting voltage of a single regulator.
Signed-off-by: Maciej Purski
---
which is about to change its voltage, is not coupled,
method regulator_get_optimal_voltage() should simply return the lowest
voltage fulfilling consumers' demands.
Coupling should be checked only if the system is in PM_SUSPEND_ON state.
Signed-off-by: Maciej Purski
---
drivers/regulator/core.c | 192 +++
regulators.
Signed-off-by: Maciej Purski
---
drivers/regulator/core.c | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/drivers/regulator/core.c b/drivers/regulator/core.c
index ab6652e..1118527 100644
--- a/drivers/regulator/core.c
+++ b/drivers/regulator/core.c
@@ -2448,10
data
inconsistency occurs. If some coupled regulators are not yet registered,
don't fail to register, but try to resolve them in late init call.
Signed-off-by: Maciej Purski
---
drivers/regulator/core.c | 92
1 file changed, 92 insertions(+)
of the structure,
number of coupled regulators and counter of currently resolved
regulators.
Add of_functions to parse all data needed in regulator coupling.
Provide method to check DTS data consistency. Check if each coupled
regulator's max_spread is equal and if their lists of regulat
parsing coupled regulators properties.
Declare of_find_regulator_by_node() function in internal.h as well as
regulator_class and dev_to_rdev(), as they are needed by
of_find_regulator_by_node().
Signed-off-by: Maciej Purski
---
drivers/regulator/core.c | 23
On 03/09/2018 01:56 PM, Mark Brown wrote:
On Fri, Mar 09, 2018 at 01:50:20PM +0100, Maciej Purski wrote:
On 03/09/2018 01:42 PM, Mark Brown wrote:
Is it possible to respin this in terms of the test/coupled branch in my
git tree? There were a bunch of build fixes that got sent and I don&#
On 03/09/2018 04:58 PM, Tony Lindgren wrote:
* Mark Brown [180309 12:43]:
On Fri, Mar 09, 2018 at 01:22:02PM +0100, Maciej Purski wrote:
I would like to kindly ask Fabio Estevam and Tony Lindgren to test the patch
series on their boards.
I gave it a quick try and this set still causes at
Hi Fabio,
thank you for your response.
Could you tell me on which board precisely (on which DTS) has this issue
occurred?
Also, I don't understand, did you boot successfully and you got only a lockdep
warning or you encountered an actual deadlock?
Best regards,
Maciej Purski
On 03/05
pply(struct regulator_dev
*rdev)
{
int i;
- for (i = 0; rdev; rdev = rdev_get_supply(rdev), i++)
+ for (i = 1000; rdev; rdev = rdev_get_supply(rdev), i++)
mutex_lock_nested(&rdev->mutex, i);
}
Best regards,
Maciej Purski
On 03/07/2018 03:10 PM, Mark Brown wrote:
On Wed, Mar 07, 2018 at 01:57:12PM +0100, Maciej Purski wrote:
I'm trying to figure out what is so special about these boards. The only
strange thing, that I haven't noticed at first, is that all regulators share
a common supply - dummy reg
forbidden is simultaneous coupling and supplying between a pair of
regulators.
The idea is based on clk core.
Signed-off-by: Maciej Purski
---
drivers/regulator/core.c | 132 +++
include/linux/regulator/driver.h | 2 +
2 files changed, 93 insertions(+), 41
Some regulators require keeping their voltage spread below defined
max_spread.
Add properties to provide information on regulators' coupling.
Signed-off-by: Maciej Purski
---
Documentation/devicetree/bindings/regulator/regulator.txt | 5 +
1 file changed, 5 insertions(+)
diff --
forbidden is simultaneous coupling and supplying between a pair of
regulators.
The idea is based on clk core.
Signed-off-by: Maciej Purski
---
drivers/regulator/core.c | 132 +++
include/linux/regulator/driver.h | 2 +
2 files changed, 93 insertions(+), 41
has not been registered.
Add function for locking coupled regulators and supplies. Extract
a new function regulator_set_voltage_rdev() from
regulator_set_voltage_unlocked(), which is called when setting
voltage of a single regulator.
Signed-off-by: Maciej Purski
---
which is about to change its voltage, is not coupled,
method regulator_get_optimal_voltage() should simply return the lowest
voltage fulfilling consumers' demands.
Coupling should be checked only if the system is in PM_SUSPEND_ON state.
Signed-off-by: Maciej Purski
---
drivers/regulator/core.c | 192 +++
y.
I would like to kindly ask Fabio Estevam and Tony Lindgren to test the patch
series on their boards.
Best regards,
Maciej Purski
---
Changes in v6:
- change locking model
- fix build errors on non-of architectures
- update bindings
Changes in v5:
- rebase against current Mark Brown&#x
data
inconsistency occurs. If some coupled regulators are not yet registered,
don't fail to register, but try to resolve them in late init call.
Signed-off-by: Maciej Purski
---
drivers/regulator/core.c | 100 +++
1 file changed, 100 insertions(+)
of the structure,
number of coupled regulators and counter of currently resolved
regulators.
Add of_functions to parse all data needed in regulator coupling.
Provide method to check DTS data consistency. Check if each coupled
regulator's max_spread is equal and if their lists of regulat
On 03/09/2018 01:42 PM, Mark Brown wrote:
On Fri, Mar 09, 2018 at 01:22:02PM +0100, Maciej Purski wrote:
I would like to kindly ask Fabio Estevam and Tony Lindgren to test the patch
series on their boards.
That'd be great, yeah - I can run some tests with kernelci as well,
thoug
On 06/04/2018 04:20 PM, Lucas Stach wrote:
> Hi Maciej,
>
> Am Montag, den 04.06.2018, 15:59 +0200 schrieb Maciej Purski:
>> Implementing coupled regulators adds a new dependency between
>> regulators. Therefore, the current locking model should be changed.
>> C
On 06/15/2018 01:29 PM, Tony Lindgren wrote:
> Hi,
>
> * Maciej Purski [180613 10:39]:
>> Call regulator_balance_voltage() instead of set_voltage_rdev()
>> in set_voltage_unlocked() and in enabling and disabling functions,
>> but only if the regulator is coupled.
If the regulator is not coupled, balance_voltage() should preserve
its desired max uV, instead of setting the exact value like in
coupled regulators case.
Remove debugs, which are not necessary for now.
Signed-off-by: Maciej Purski
---
drivers/regulator/core.c | 26
In order to allow bridge drivers to use DSI transfers in their
pre_enable callbacks, pm_runtime_get_sync() should be performed before
exynos_dsi_enable(). DSIM_STATE_ENABLED flag now should not guard
from calling dsi_host_transfer() before enabling.
Signed-off-by: Maciej Purski
---
drivers/gpu
can revert it and
in the next version I'll fix the build error and split the last patch even
more, so we could perform a more precise bisection. I'd be grateful if you
could push it on your test coupled branch and Tony could test it again before
merging it with next again.
Best regards,
Maciej Purski
Call regulator_balance_voltage() instead of set_voltage_rdev()
in set_voltage_unlocked() and in enabling and disabling functions,
but only if the regulator is coupled.
Signed-off-by: Maciej Purski
---
Changes in v2:
- fix compile errors
- make debug messages more informative
---
drivers
-arndale.dtsi.
Best regards,
Maciej Purski
Maciej Purski (12):
drm/exynos: rename "bridge_node" to "mic_bridge_node"
drm/exynos: move pm_runtime_get_sync() to exynos_dsi_init()
drm/exynos: move connector creation to attach callback
drm/exynos: add non-panel path to exynos_
In order to allow bridge drivers to use DSI transfers in their
pre_enable callbacks, pm_runtime_get_sync() should be performed before
exynos_dsi_enable(). DSIM_STATE_ENABLED flag now should not guard
from calling dsi_host_transfer() before enabling.
Signed-off-by: Maciej Purski
---
drivers/gpu
The patch adds phy node, required by MIPI devices.
Signed-off-by: Andrzej Hajda
Signed-off-by: Maciej Purski
---
arch/arm/boot/dts/exynos5250.dtsi | 6 ++
1 file changed, 6 insertions(+)
diff --git a/arch/arm/boot/dts/exynos5250.dtsi
b/arch/arm/boot/dts/exynos5250.dtsi
index 2daf505
The patch adds bindings to Toshiba DSI/LVDS bridge TC358764.
Bindings describe power supplies, reset gpio and video interfaces.
Signed-off-by: Andrzej Hajda
Signed-off-by: Maciej Purski
---
.../bindings/display/bridge/toshiba,tc358764.txt | 42 ++
1 file changed, 42
Add a drm_bridge driver for the Toshiba TC358764 DSI to LVDS bridge.
Signed-off-by: Andrzej Hajda
Signed-off-by: Maciej Purski
---
drivers/gpu/drm/bridge/Kconfig| 7 +
drivers/gpu/drm/bridge/Makefile | 1 +
drivers/gpu/drm/bridge/tc358764.c | 547
The current implementation assumes that the only possible peripheral
device for DSIM is a panel. Using an output bridge should also be
possible.
If an output bridge in available, don't create a new connector.
Instead add bridge to DSIM encdoer in dsi_host_attach().
Signed-off-by: Maciej P
When adding support for peripheral out bridges, the "bridge" name
becomes imprecise as it refers to a different device than the
"out_bridge".
Signed-off-by: Maciej Purski
---
drivers/gpu/drm/exynos/exynos_drm_dsi.c | 16
1 file changed, 8 insertions(+),
As DSIM can now have a bridge connected as a peripheral, it should be
possible to successfully enable exynos_dsi, when there is no panel
provided.
Signed-off-by: Maciej Purski
---
drivers/gpu/drm/exynos/exynos_drm_dsi.c | 27 +--
1 file changed, 13 insertions(+), 14
The patch adds support for BOE HV070WSA-100 WSVGA 7.01 inch panel
in panel-simple driver. The panel is used in Exynos5250-arndale boards.
Signed-off-by: Andrzej Hajda
Signed-off-by: Maciej Purski
---
drivers/gpu/drm/panel/panel-simple.c | 25 +
1 file changed, 25
The patch adds bindings to BOE HV070-WSA WSVGA panel.
Bindings are compatible with simple panel bindings.
Signed-off-by: Andrzej Hajda
Signed-off-by: Maciej Purski
---
.../devicetree/bindings/display/panel/boe,hv070wsa-100.txt | 7 +++
1 file changed, 7 insertions(+)
create mode
The patch adds common part of DSI node for Exynos5250 platforms.
Signed-off-by: Andrzej Hajda
Signed-off-by: Maciej Purski
---
arch/arm/boot/dts/exynos5250.dtsi | 14 ++
1 file changed, 14 insertions(+)
diff --git a/arch/arm/boot/dts/exynos5250.dtsi
b/arch/arm/boot/dts/exynos5250
The patch adds fixed regulators used by DSI/LVDS bridge
and panel. Regulators are named according to schematics.
Signed-off-by: Andrzej Hajda
Signed-off-by: Maciej Purski
---
arch/arm/boot/dts/exynos5250-arndale.dts | 24
1 file changed, 24 insertions(+)
diff --git a
The patch adds bridge and panel nodes.
It adds also DSI properties specific for arndale board.
Signed-off-by: Andrzej Hajda
Signed-off-by: Maciej Purski
---
arch/arm/boot/dts/exynos5250-arndale.dts | 39
1 file changed, 39 insertions(+)
diff --git a/arch/arm
Add debug messages on voltage setting and enabling path in order
to debug the coupled regulators problem.
Signed-off-by: Maciej Purski
---
drivers/regulator/core.c | 9 +
1 file changed, 9 insertions(+)
diff --git a/drivers/regulator/core.c b/drivers/regulator/core.c
index 6ed568b
Refactor regulator_set_voltage_unlocked() by taking code related to
regulator_dev and creating a new function regulator_set_voltage_rdev(),
which operates only on struct regulator_dev.
Signed-off-by: Maciej Purski
---
drivers/regulator/core.c | 40
1
Re-entrant locks were implemented in previous patches. They should
substitute all mutex_lock() and mutex_unlock() calls on regulators'
mutexes.
Signed-off-by: Maciej Purski
---
drivers/regulator/core.c | 16
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git a/dr
Call regulator_balance_voltage() instead of set_voltage_rdev()
in set_voltage_unlocked() and in enabling and disabling functions,
but only if the regulator is coupled.
Signed-off-by: Maciej Purski
---
drivers/regulator/core.c | 24 +++-
1 file changed, 23 insertions(+), 1
at if you could try to find out, which patch causes failure. They should
be appliable on the current next.
Thanks,
Maciej Purski
Maciej Purski (7):
regulator: core: Add debug messages
regulator: core: Add regulator_set_voltage_rdev()
regulator: core: Use re-entrant locks
regulator:
Since regulator_enable() might now call regulator_balance_voltage(),
it should also lock its coupled regulators and suppliers.
Signed-off-by: Maciej Purski
---
drivers/regulator/core.c | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/drivers/regulator/core.c b
which is about to change its voltage, is not coupled,
method regulator_get_optimal_voltage() should simply return the lowest
voltage fulfilling consumers' demands.
Signed-off-by: Maciej Purski
---
drivers/regulator/core.c | 183 +++
1 file changed, 183 inserti
with the one, that is being changed.
Signed-off-by: Maciej Purski
---
drivers/regulator/core.c | 75 +---
1 file changed, 52 insertions(+), 23 deletions(-)
diff --git a/drivers/regulator/core.c b/drivers/regulator/core.c
index 0b366c5..7c57268 100644
Hi all,
unfortunately, I don't work at kernel anymore. That would be great, if you
could take over those patches and finish the
work.
Best regards,
Maciej
On 09/29/2018 02:44 AM, Dmitry Osipenko wrote:
> On 9/29/18 3:27 AM, Tony Lindgren wrote:
>> * Dmitry Osipenko [180928 23:55]:
>>> On 9/29/1
Some regulators require keeping their voltage spread below defined
max_spread.
Add properties to provide information on regulators' coupling.
Reviewed-by: Rob Herring
Signed-off-by: Maciej Purski
---
Documentation/devicetree/bindings/regulator/regulator.txt | 5 +
1 file chang
of the structure,
number of coupled regulators and counter of currently resolved
regulators.
Add of_functions to parse all data needed in regulator coupling.
Provide method to check DTS data consistency. Check if each coupled
regulator's max_spread is equal and if their lists of regulat
The current assumption is that an uncoupled regulator is a special case
of a coupled one, so they should share a common voltage setting path.
Best regards,
Maciej Purski
---
Changes in v5:
- rebase against current Mark Brown's regulators next
Changes in v4:
- make paths for coup
data
inconsistency occurs. If some coupled regulators are not yet registered,
don't fail to register, but try to resolve them in late init call.
Signed-off-by: Maciej Purski
---
drivers/regulator/core.c | 92
1 file changed, 92 insertions(+)
which is about to change its voltage, is not coupled,
method regulator_get_optimal_voltage() should simply return the lowest
voltage fulfilling consumers' demands.
Coupling should be checked only if the system is in PM_SUSPEND_ON state.
Signed-off-by: Maciej Purski
---
drivers/regulator/core.c | 192 +++
has not been registered.
Add function for locking coupled regulators. Extract a new function
regulator_set_voltage_rdev() from regulator_set_voltage_unlocked(),
which is called when setting voltage of a single regulator.
Signed-off-by: Maciej Purski
---
Build errors detected by kbuild test robot occur on non-of
architectures.
This patch fixes this behavior as well as using plain integer instead
of NULL in of_count_phandle_with_args().
Fixes: 0c55103 ("regulator: core: Parse coupled regulators properties")
Signed-off-by: Mac
ue, now
set to 10)
- change algorithm to be more readable
- introduce better locking
- add more comments
- split first patch into two
- update commit messages
- change sequence of the patches
Maciej Purski (6):
regulator: core: Make locks re-entrant
regulator: bindings: Add properties for c
which is about to change its voltage, is not coupled,
method regulator_get_optimal_voltage() should simply return the lowest
voltage fulfilling consumers' demands.
Coupling should be checked only if the system is in PM_SUSPEND_ON state.
Signed-off-by: Maciej Purski
---
drivers/regulator/core.c | 192 +++
Some regulators require keeping their voltage spread below defined
max_spread.
Add properties to provide information on regulators' coupling.
Signed-off-by: Maciej Purski
Reviewed-by: Rob Herring
---
Documentation/devicetree/bindings/regulator/regulator.txt | 5 +
1 file chang
of the structure,
number of coupled regulators and counter of currently resolved
regulators.
Add of_functions to parse all data needed in regulator coupling.
Provide method to check DTS data consistency. Check if each coupled
regulator's max_spread is equal and if their lists of regulat
has not been registered.
Add function for locking coupled regulators and supplies. Extract
a new function regulator_set_voltage_rdev() from
regulator_set_voltage_unlocked(), which is called when setting
voltage of a single regulator.
Signed-off-by: Maciej Purski
---
forbidden is simultaneous coupling and supplying between a pair of
regulators.
The idea is based on clk core.
Signed-off-by: Maciej Purski
---
drivers/regulator/core.c | 132 +++
include/linux/regulator/driver.h | 2 +
2 files changed, 93 insertions(+), 41
data
inconsistency occurs. If some coupled regulators are not yet registered,
don't fail to register, but try to resolve them in late init call.
Signed-off-by: Maciej Purski
---
drivers/regulator/core.c | 100 +++
1 file changed, 100 insertions(+)
Current implementation of mode_valid() and mode_fixup() callbacks
handle packed pixel modes improperly.
Fix it by using proper maximum clock values from the documentation.
Signed-off-by: Maciej Purski
---
Changes in v2:
- simplify is_packing_required() function
- fix uninitialized variable
by clk_bulk_alloc() function.
Add a managed version of clk_bulk_alloc().
Signed-off-by: Maciej Purski
---
drivers/clk/clk-bulk.c | 16
drivers/clk/clk-devres.c | 37 +---
include/linux/clk.h | 64
3 files
Using bulk clk functions simplifies the driver's code. Use devm_clk_bulk
functions instead of iterating over an array of clks.
Signed-off-by: Maciej Purski
---
drivers/media/platform/s5p-jpeg/jpeg-core.c | 45 -
drivers/media/platform/s5p-jpeg/jpeg-core.h | 2
Using bulk clk functions simplifies the driver's code. Use devm_clk_bulk
functions instead of iterating over an array of clks.
Signed-off-by: Maciej Purski
---
drivers/media/platform/s5p-mfc/s5p_mfc_common.h | 6 ++--
drivers/media/platform/s5p-mfc/s5p_mfc_pm.c
Hi all,
the main goal of this patchset is to simplify clk management code in
exynos5433 drivers by using clk bulk API. In order to achieve that,
patch #1 adds a new function to clk core, which dynamically allocates
clk_bulk_data array and fills its id fields.
Best regards,
Maciej Purski
Maciej
Using bulk clk functions simplifies the driver's code. Use devm_clk_bulk
functions instead of iterating over an array of clks.
Signed-off-by: Maciej Purski
---
drivers/gpu/drm/exynos/exynos_hdmi.c | 97 ++--
1 file changed, 27 insertions(+), 70 deletions(-)
Using bulk clk functions simplifies the driver's code. Use devm_clk_bulk
functions instead of iterating over an array of clks.
Signed-off-by: Maciej Purski
---
drivers/media/platform/exynos-gsc/gsc-core.c | 55 ++--
drivers/media/platform/exynos-gsc/gsc-core.h | 2
Using bulk clk functions simplifies the driver's code. Use devm_clk_bulk
functions instead of iterating over an array of clks.
In order to achieve consistency with other drivers, define clock names
in driver's variants structures.
Signed-off-by: Maciej Purski
---
drivers/gpu/
Using bulk clk functions simplifies the driver's code. Use devm_clk_bulk
functions instead of iterating over an array of clks.
Signed-off-by: Maciej Purski
---
drivers/gpu/drm/exynos/exynos_drm_mic.c | 41 +++--
1 file changed, 14 insertions(+), 27 deletions(-)
Using bulk clk functions simplifies the driver's code. Use devm_clk_bulk
functions instead of iterating over an array of clks.
Signed-off-by: Maciej Purski
---
drivers/gpu/drm/exynos/exynos5433_drm_decon.c | 50 ---
1 file changed, 15 insertions(+), 35 deletions(-)
Add 'component' directory to debugfs. Create a new file for each master,
when a master is added. Remove it on a master deletion.
Show a list of devices matched with master and indicate if
master's components were successfully added and if the whole master is
bound.
Signed-off-by
Add 'component' directory to debugfs. Create a new file for each master,
when a master is added. Remove it on a master deletion.
Show a list of devices matched with master and indicate if
master's components were successfully added and if the whole master is
bound.
Signed-off-by
On 11/15/2017 03:01 PM, Greg Kroah-Hartman wrote:
On Wed, Nov 15, 2017 at 01:05:26PM +0100, Maciej Purski wrote:
Add 'component' directory to debugfs. Create a new file for each master,
when a master is added. Remove it on a master deletion.
Show a list of devices matched with
On 12/12/2017 12:35 PM, Mark Brown wrote:
On Thu, Dec 07, 2017 at 10:46:14AM +0100, Maciej Purski wrote:
(...)
+ mutex_lock(®ulator_list_mutex);
+ regulator_resolve_coupling(rdev);
+ mutex_unlock(®ulator_list_mutex);
+
I'd really expect us to be failing to probe if w
On 12/15/2017 04:19 PM, Mark Brown wrote:
On Wed, Dec 13, 2017 at 10:25:00AM +0100, Maciej Purski wrote:
shared. To that end I'd adjust the code so that we always have a
coupling descriptor and then handle the case where there's only one
regulator described in there.
Do yo
regards,
Maciej Purski
Maciej Purski (2):
iio: adc: ina2xx: Make calibration register value fixed
hwmon: (ina2xx) Make calibration register value fixed
drivers/hwmon/ina2xx.c | 87 +---
drivers/iio/adc/ina2xx-adc.c | 59
226)
power_lsb = 20 * current_lsb (ina 219)
Signed-off-by: Maciej Purski
---
drivers/hwmon/ina2xx.c | 87 +-
1 file changed, 50 insertions(+), 37 deletions(-)
diff --git a/drivers/hwmon/ina2xx.c b/drivers/hwmon/ina2xx.c
index 62e38fa..e362a93
226)
power_lsb = 20 * current_lsb (ina 219)
Signed-off-by: Maciej Purski
---
drivers/iio/adc/ina2xx-adc.c | 59
1 file changed, 32 insertions(+), 27 deletions(-)
diff --git a/drivers/iio/adc/ina2xx-adc.c b/drivers/iio/adc/ina2xx-adc.c
index 84a4387
226)
power_lsb = 20 * current_lsb (ina 219)
This is a part of the patchset: https://lkml.org/lkml/2017/11/22/394
Signed-off-by: Maciej Purski
---
Changes in v3:
- remove variable current_lsb and calculate it on each read of current
and power scale value
- update comments
Changes in v2
226)
power_lsb = 20 * current_lsb (ina 219)
This is a part of the patchset: https://lkml.org/lkml/2017/11/22/394
Signed-off-by: Maciej Purski
---
Changes in v4:
- fix comments
Changes in v3:
- remove variable current_lsb and calculate it on each read of current
and power scale value
- update
On 12/12/2017 12:54 PM, Mark Brown wrote:
On Thu, Dec 07, 2017 at 10:46:15AM +0100, Maciej Purski wrote:
@@ -2447,10 +2482,9 @@ static int _regulator_is_enabled(struct regulator_dev
*rdev)
return rdev->desc->ops->is_enabled(rdev);
}
-static int _regulator_list_volta
This patch adds muic of_compatible in order to use the muic device
driver in device tree.
v2:
- added muic to documentation
Signed-off-by: Maciej Purski
---
Documentation/devicetree/bindings/mfd/max77693.txt | 6 ++
drivers/mfd/max77693.c | 5 -
2 files
This patch adds muic of_compatible in order to use the muic device
driver in device tree.
v2:
- added muic to documentation
v3:
- removed duplication
Signed-off-by: Maciej Purski
---
Documentation/devicetree/bindings/mfd/max77693.txt | 6 ++
drivers/mfd/max77693.c
This patch adds muic of_compatible in order to use the muic device
driver in device tree.
Signed-off-by: Maciej Purski
---
v2:
- added muic to documentation
v3:
- removed duplication
v4:
- fixed commit message
Documentation/devicetree/bindings/mfd/max77693.txt | 6 ++
drivers/mfd/max77693
Some regulators require keeping their voltage spread below defined
max_spread.
Add properties to provide information on regulators' coupling.
Signed-off-by: Maciej Purski
---
Documentation/devicetree/bindings/regulator/regulator.txt | 3 +++
1 file changed, 3 insertions(+)
diff --
le support for generic CPUfreq
and devfreq drivers for the mentioned boards.
Best regards,
Maciej Purski
Maciej Purski (2):
regulator: core: Add coupled regulators mechanism
regulator: bindings: Add properties for coupled regulators
.../devicetree/bindings/regulator/regulator.txt
1 - 100 of 121 matches
Mail list logo
