Hi Maxime,
Dne sreda, 28. februar 2018 ob 08:36:08 CET je Maxime Ripard napisal(a):
> On Tue, Feb 27, 2018 at 11:26:51PM +0100, Jernej Skrabec wrote:
> > TCON checks for LVDS properties even if it doesn't support it. Add a
> > check to skip that part of the code if TCON doesn't support channel 0.
operation for some resolutions,
> is also fixed.
>
> Code is based on linux-next, next-20180226 tag.
Today I tried on this series on next-20180228, but resolution switching
doesn't really work. The reason for this is use of clk_set_rate_exclusive() in
sun4i_tcon1_mode_set(). If I rev
Hi,
Dne sreda, 28. februar 2018 ob 08:34:40 CET je Maxime Ripard napisal(a):
> Hi,
>
> On Tue, Feb 27, 2018 at 11:26:46PM +0100, Jernej Skrabec wrote:
> > Some NM PLLs doesn't work well when their output clock rate is set below
> > certain rate.
> >
> > Add support for that constrain.
> >
> >
The Allwinner A83T is a SoC with two clusters of 4 A7 which have a
different clock and regulator.
Set the CPU regulator.
Signed-off-by: Quentin Schulz
---
arch/arm/boot/dts/sun8i-a83t-tbs-a711.dts | 9 +
1 file changed, 9 insertions(+)
diff --git
The Allwinner A83T is an octacore A7 divided in two clusters of 4 A7,
each cluster having its own regulator and clock.
The operating points were found in Allwinner BSP and fex files.
Note that there are a few OPPs that are missing:
160800Hz with 92mV
18Hz with 100mV
The Allwinner A83T is a SoC with two clusters of 4 A7, each cluster
having its own regulator and clock.
The regulators are board-specific, thus we need labels for cpu0 and
cpu100 so that we can use references to these nodes from the board
header file.
Signed-off-by: Quentin Schulz
Hi all,
The Allwinner A83T is an octacore A7 divided in two clusters of 4 A7,
each cluster having its own regulator and clock.
Let's add the OPPs for each cluster so that we can use cpufreq on this SoC.
The operating points were found in Allwinner BSP and fex files and have
been tested on a TBS
Hi,
On 26/02/18 15:54, Samuel Holland wrote:
> On 02/26/18 03:26, Maxime Ripard wrote:
>> On Fri, Feb 23, 2018 at 11:22:06PM +0800, Icenowy Zheng wrote:
> + psci {
> + compatible = "arm,psci-0.2";
> + method = "smc";
> + };
Is it needed? The bootloader
As axp20x-battery-power-supply now supports AXP813, add a cell for it.
Signed-off-by: Quentin Schulz
Acked-for-MFD-by: Lee Jones
Reviewed-by: Chen-Yu Tsai
---
drivers/mfd/axp20x.c | 3 +++
1 file changed, 3 insertions(+)
diff
We used to use IDs to select a function or a feature depending on the
variant. It's easier to maintain the code by adding data structure
storing the few differences between variants so that we don't add a pile
of if conditions.
Let's use this data structure and update the code to use it.
The AXP813 PMIC is relatively close to the already supported AXP20X and
AXP22X. It provides three different power outputs: battery, AC and USB, and
measures a few different things: temperature, power supply status, current
current and voltage supplied, maximum current limit, battery capacity, min
The X-Powers AXP813 PMIC has got some slight differences from
AXP20X/AXP22X PMICs:
- the maximum voltage supplied by the PMIC is 4.35 instead of 4.36/4.24
for AXP20X/AXP22X,
- the constant charge current formula is different,
It also has a bit to tell whether the battery percentage returned by
This makes AXP209 and AXP22x ADCs probe first via DT and then by
fallback via platform.
Signed-off-by: Quentin Schulz
Acked-for-MFD-by: Lee Jones
Acked-by: Chen-Yu Tsai
---
drivers/mfd/axp20x.c | 5 -
1 file changed, 4
The AXP813 can have a battery as power supply, so let's add it to the
list of compatibles.
Signed-off-by: Quentin Schulz
Reviewed-by: Rob Herring
Acked-by: Chen-Yu Tsai
---
This makes the axp20x_adc driver probe with platform device id
"axp813-adc".
Signed-off-by: Quentin Schulz
Acked-for-MFD-by: Lee Jones
Acked-by: Chen-Yu Tsai
---
drivers/mfd/axp20x.c | 5 -
1 file changed, 4 insertions(+), 1
15 matches
Mail list logo