Ah, I figured out why the dma stopped working. In s5pv210-aries.dtsi the dma's
for i2s0
are overriden to use pdma0 instead of pdma1. That also needs changing for this
to
work properly.
Thanks,
Jonathan
On 2020-09-07 5:17 p.m., Jonathan Bakker wrote:
> Initial testing on both an i900
Initial testing on both an i9000 and an SGH-T959P are showing that the audio has
stopped working with this. I'm not 100% convinced as I've had DMA issues in the
past. However trying to play something just results in a hang after 1.5s while
it works just fine without this patch.
Thanks,
Jonathan
Hi Krzysztof,
On 2020-09-07 9:11 a.m., Krzysztof Kozlowski wrote:
> The S3C RTC requires 32768 Hz clock as input which is provided by PMIC.
> However there is no such clock provider but rather a regulator driver
> which registers the clock as a regulator. This is an old driver which
> will not be
Sadly, this is causing issues for me. The machine driver is no longer probing
correctly
on the Galaxy S.
The failing call in sound/soc/samsung/aries_wm8994.c is
/* Set CPU of_node for BT DAI */
aries_dai[2].cpus->of_node = of_parse_phandle(cpu,
"sound-dai
Works for me on the Galaxy S.
Tested-by: Jonathan Bakker
Thanks,
Jonathan
On 2020-09-07 9:11 a.m., Krzysztof Kozlowski wrote:
> The device tree schema expects SPI controller to be named "spi",
> otherwise dtbs_check complain with a warning like:
>
> spi-gpio-0: $n
Audio still works for me on the Galaxy S.
Tested-by: Jonathan Bakker
Thanks,
Jonathan
On 2020-09-07 9:11 a.m., Krzysztof Kozlowski wrote:
> The 'audio-subsystem' node is an artificial creation, not representing
> real hardware. The hardware is described by its nodes - AUDSS cl
Works for me on the Galaxy S.
Tested-by: Jonathan Bakker
Thanks,
Jonathan
On 2020-09-07 9:11 a.m., Krzysztof Kozlowski wrote:
> The Power Management Unit (PMU) is a separate device which has little
> common with clock controller. Moving it to one level up (from clock
> controller chi
Works for me on the Galaxy S.
Tested-by: Jonathan Bakker
Thanks,
Jonathan
On 2020-09-07 9:11 a.m., Krzysztof Kozlowski wrote:
> The fixed clocks are kept under dedicated 'external-clocks' node, thus a
> fake 'reg' was added. This is not correct with dtschema as fixe
DMA still works for me on the Galaxy S.
Tested-by: Jonathan Bakker
Thanks,
Jonathan
On 2020-09-07 9:11 a.m., Krzysztof Kozlowski wrote:
> There is no need to keep DMA controller nodes under AMBA bus node.
> Remove the "amba" node to fix dtschema warnings like:
>
> am
Looking at this again, it appears that there is actually control for
it at offset 0x6818 of pmu_syscon (0xe0108000) [1]. However, it defaults to
enabled so it's not required for proper use of the block. Whether it should
be present in the schema/DTS is up to you.
Thanks,
Jonathan
[1]
https://a
On 2020-09-02 9:46 a.m., Colin Ian King wrote:
> On 02/09/2020 17:43, Gustavo A. R. Silva wrote:
>> On Wed, Sep 02, 2020 at 09:29:31AM -0700, Randy Dunlap wrote:
>>> On 9/2/20 9:23 AM, Gustavo A. R. Silva wrote:
A few months ago, commit e132fc6bb89b ("power: supply: charger-manager:
M
Both the galaxys and the fascinate4g have a wm8994 codec,
but they differ slightly in their jack detection and micbias
configuration.
Signed-off-by: Jonathan Bakker
---
arch/arm/boot/dts/s5pv210-aries.dtsi | 10 +++
arch/arm/boot/dts/s5pv210-fascinate4g.dts | 98
Commit ee7160e57c98 ("[media] s5p-fimc: Add support for JPEG capture")
added support for JPEG capture, but missed setting a register when the
parallel port was used rather than the CSIS device.
Signed-off-by: Jonathan Bakker
Reviewed-by: Sylwester Nawrocki
---
Changes from v1:
-
This is a no-op as it is never set and is a remnant from non-DT days
that can be safely removed.
Signed-off-by: Jonathan Bakker
Reviewed-by: Tomasz Figa
Reviewed-by: Sylwester Nawrocki
---
Changes from v1:
- Added R-b tags
---
drivers/media/platform/exynos4-is/fimc-capture.c | 13
tiple sensors
being connected to the same port.
Signed-off-by: Jonathan Bakker
---
Changes from v1:
- New patch
---
drivers/media/platform/exynos4-is/media-dev.c | 11 ---
1 file changed, 4 insertions(+), 7 deletions(-)
diff --git a/drivers/media/platform/exynos4-is/media-dev.c
b/drivers/
dded a WARN for unbalanced calls to media_pipeline_stop.
Signed-off-by: Jonathan Bakker
---
Changes from v1:
- re-worded commit message for a better description of the problem
---
drivers/media/platform/exynos4-is/fimc-capture.c | 7 +--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git
This is no longer used since the conversion to DT
Signed-off-by: Jonathan Bakker
Reviewed-by: Tomasz Figa
Reviewed-by: Sylwester Nawrocki
---
Changes from v1:
- Added R-b tags
---
drivers/media/platform/exynos4-is/fimc-core.h | 2 --
1 file changed, 2 deletions(-)
diff --git a/drivers/media
On some devices, there may be multiple camera sensors attached
to the same port. Make sure we probe all of them, not just the
first one.
Signed-off-by: Jonathan Bakker
---
Changes from v1:
- Separated parsing each endpoint into separate func
---
drivers/media/platform/exynos4-is/media-dev.c
The parallel port nodes should be numbered 1 and 2, not 0 and 1
for A and B respectively. The driver has always implemented 1
and 2 and the in-tree Goni DTS uses 1 as port A as well. Update
the documentation to match this behaviour.
Signed-off-by: Jonathan Bakker
---
Changes from v1:
- New
From: Tomasz Figa
On FIMC variants which don't have writeback channel, there is no need to
access system registers. This patch makes the driver request sysreg
regmap conditionally depending on whether writeback is supported.
Signed-off-by: Tomasz Figa
Signed-off-by: Jonathan Bakker
Rev
ly to check if we are using the subdev API
Signed-off-by: Jonathan Bakker
Reviewed-by: Sylwester Nawrocki
---
Changes from v1:
- Added R-b tag
---
drivers/media/platform/exynos4-is/media-dev.c | 17 -
1 file changed, 16 insertions(+), 1 deletion(-)
diff --git a/drivers/media/pla
gs on boot.
Signed-off-by: Jonathan Bakker
---
Changes from v1:
- Don't remove the function from the vfd entity as it is distinct
from the sd entity
- Re-word commit message for above change
---
drivers/media/platform/exynos4-is/fimc-capture.c | 1 +
1 file changed, 1 insertion(+)
diff --git
modifying driver
Jonathan Bakker (10):
media: exynos4-is: Remove static driver data for S5PV210 FIMC variants
media: exynos4-is: Fix nullptr when no CSIS device present
media: exynos4-is: Correct missing entity function initialization
media: exynos4-is: Properly set JPEG options for parallel
The S5PV210 platform only supports device tree based booting
where the FIMC variant data is parsed directly from
the device tree, hence the now unused static data can be removed.
Signed-off-by: Jonathan Bakker
Reviewed-by: Tomasz Figa
Reviewed-by: Sylwester Nawrocki
---
Changes from v1
Hi Tomasz,
On 2020-07-20 6:10 a.m., Tomasz Figa wrote:
> On Sat, Jul 11, 2020 at 8:17 PM Jonathan Bakker wrote:
>>
>> Hi Tomasz,
>>
>> On 2020-07-07 11:44 a.m., Tomasz Figa wrote:
>>> Hi Jonathan,
>>>
>>> On Sat, Apr 25, 2020 at 07:26:49PM
Hi Tomasz,
On 2020-07-07 11:13 a.m., Tomasz Figa wrote:
> Hi Jonathan,
>
> On Sat, Apr 25, 2020 at 07:26:44PM -0700, Jonathan Bakker wrote:
>> Commit 1c9f5bd7cb8a ("[media] s5p-fimc: Add support for sensors with
>> multiple pads") caught the case where
Hi Sylwester,
On 2020-07-08 9:15 a.m., Sylwester Nawrocki wrote:
> Hi,
>
> On 26.04.2020 04:26, Jonathan Bakker wrote:
>> According to the binding doc[1], port A should be reg = 0
>> and port B reg = 1. Unfortunately, the driver was treating 0
>> as invalid and 1 a
Hi Tomasz,
On 2020-07-07 11:44 a.m., Tomasz Figa wrote:
> Hi Jonathan,
>
> On Sat, Apr 25, 2020 at 07:26:49PM -0700, Jonathan Bakker wrote:
>> media_pipeline_stop can be called from both release and streamoff,
>> so make sure they're both protected under the streaming f
Hi Tomasz,
On 2020-07-07 11:36 a.m., Tomasz Figa wrote:
> On Sat, Apr 25, 2020 at 07:26:46PM -0700, Jonathan Bakker wrote:
>> On some devices, there may be multiple camera sensors attached
>> to the same port. Make sure we probe all of them, not just the
>> first one
Hi Sylwester and Tomasz,
On 2020-07-08 8:45 a.m., Sylwester Nawrocki wrote:
> Hi,
>
> On 07.07.2020 20:23, Tomasz Figa wrote:
>> On Sat, Apr 25, 2020 at 07:26:45PM -0700, Jonathan Bakker wrote:
>>> Commit ee7160e57c98 ("[media] s5p-fimc: Add support for JPEG capture
Hi Sylwester and Tomasz,
On 2020-07-08 8:34 a.m., Sylwester Nawrocki wrote:
> Hi,
>
> On 07.07.2020 20:09, Tomasz Figa wrote:
>> On Sat, Apr 25, 2020 at 07:26:43PM -0700, Jonathan Bakker wrote:
>>> Commit bae4500399c4 ("[media] exynos4-is: Add missing entity functi
Hi Sylwester and Tomasz,
On 2020-07-08 8:11 a.m., Sylwester Nawrocki wrote:
> Hi,
>
> On 07.07.2020 19:55, Tomasz Figa wrote:
>> On Sat, Apr 25, 2020 at 07:26:42PM -0700, Jonathan Bakker wrote:
>>> Not all devices use the CSIS device, some may use the FIMC directly in
Hi Tomasz,
On 2020-06-24 4:58 a.m., Tomasz Figa wrote:
> On Wed, Jun 24, 2020 at 1:54 PM Krzysztof Kozlowski wrote:
>>
>> On Wed, Jun 24, 2020 at 01:39:50PM +0200, Hans Verkuil wrote:
>>> Can someone from Samsung or someone who knows this SoC take a look at this
>>> series?
>>>
>>> This series l
FM and the modem is
the master.
Signed-off-by: Jonathan Bakker
---
.../bindings/sound/samsung,aries-wm8994.yaml | 147 ++
1 file changed, 147 insertions(+)
create mode 100644
Documentation/devicetree/bindings/sound/samsung,aries-wm8994.yaml
diff --git a/Documentation
The wm8994 exposes several inputs and outputs that can be used by
machine drivers in their routing. Add them to the documention so
they don't have been duplicated in any machine drivers bindings.
Signed-off-by: Jonathan Bakker
---
.../devicetree/bindings/sound/wm8994.txt
the headphone jack.
There are two main variants, one with an FM radio and where the modem
is the master and one without a radio and the modem is the slave.
Signed-off-by: Jonathan Bakker
---
sound/soc/samsung/Kconfig| 13 +
sound/soc/samsung/Makefile | 2 +
sound/soc/samsung
e AIF should
be forced into mono mode.
UCM2 config files are available at
https://github.com/xc-racer99/aries-hw-files/tree/ucm2/usr/share/alsa/ucm2
Jonathan Bakker (3):
dt-bindings: sound: Document wm8994 endpoints
dt-bindings: sound: Add bindings for Samsung Aries audio complex
ASoC: sams
Aries boards have a GP2A light/proximity sensor attached over i2c-gpio.
As the chip outputs a current and the board has no current ADC, a
current shunt resistor and a voltage ADC are used.
Signed-off-by: Jonathan Bakker
---
arch/arm/boot/dts/s5pv210-aries.dtsi | 50
some rates didn't work,
and the some pinctrl settings weren't explicitly set. Fix all
of the above issues.
While we're at it, update from the deprecated host-wakeup-gpios
property to the host-wake interrupt.
Signed-off-by: Jonathan Bakker
---
arch/arm/boot/dts/s5p
definition also had some issues
with it.
There is one change to the common s5pv210 dtsi and that is that the gph3
bank was missing the interrupt-controller property.
Jonathan Bakker (5):
ARM: dts: s5pv210: Add interrupt-controller property to gph3
ARM: dts: s5pv210: Correct fuelgauge definition
Correct the fuelgauge definition because only the fuelgauge on
fascinate4g has interrupt support (and even then it was wrong).
Also, assign the GPIO pinctrl so the interrupt is properly configured
Signed-off-by: Jonathan Bakker
---
arch/arm/boot/dts/s5pv210-aries.dtsi | 4 +---
arch/arm
The GPH3 pins on s5pv210 have interrupt support and had the
interrupt-cells property but was missing the interrupt-controller
property.
Signed-off-by: Jonathan Bakker
---
arch/arm/boot/dts/s5pv210-pinctrl.dtsi | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arm/boot/dts/s5pv210
Aries boards have a BMA023 accelerometer attached over i2c-gpio.
Signed-off-by: Jonathan Bakker
---
arch/arm/boot/dts/s5pv210-aries.dtsi | 8 ++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/arch/arm/boot/dts/s5pv210-aries.dtsi
b/arch/arm/boot/dts/s5pv210-aries.dtsi
index
x17040
but does for the later max17043/max77836 where its only 8 bits)?
Thanks and sorry for the issues,
Jonathan
On 2020-05-28 10:02 a.m., Sebastian Reichel wrote:
> Hi,
>
> This patch does not even compile, how did you test it?
>
> -- Sebastian
>
> On Mon, May 04, 2020 at 03
Hi Rob,
On 2020-05-28 1:13 p.m., Rob Herring wrote:
> On Fri, May 15, 2020 at 07:26:18PM -0700, Jonathan Bakker wrote:
>> Some devices may require a current adc, but only have a voltage
>> ADC onboard. In order to read the current, they have a resistor
>> connected to the A
lore.kernel.org/lkml/20110709030853.ga23...@opensource.wolfsonmicro.com/
On 2020-05-16 12:47 p.m., Jonathan Bakker wrote:
> The max8998 has a current regulator for charging control. The
> charger driver in drivers/power/supply/max8998_charger.c has a
> comment in it stating that 'charger control is done b
.
Signed-off-by: Jonathan Bakker
---
drivers/power/supply/max8998_charger.c | 25 ++---
1 file changed, 22 insertions(+), 3 deletions(-)
diff --git a/drivers/power/supply/max8998_charger.c
b/drivers/power/supply/max8998_charger.c
index 9a926c7c0f22..c26023b19f26 100644
--- a
have been extracted from a downstream driver
for the SGH-T959V.
Signed-off-by: Jonathan Bakker
---
drivers/regulator/max8998.c | 105
include/linux/mfd/max8998.h | 1 +
2 files changed, 106 insertions(+)
diff --git a/drivers/regulator/max8998.c b/drivers
max8998 has a current regulator for control of its charging
current. Document it.
Signed-off-by: Jonathan Bakker
---
Documentation/devicetree/bindings/mfd/max8998.txt | 8
1 file changed, 8 insertions(+)
diff --git a/Documentation/devicetree/bindings/mfd/max8998.txt
b/Documentation
Oops, sorry about that, you're absolutely right. The current-sense-shunt part
of iio-rescale is exactly what I was looking for.
Thanks,
Jonathan
On 2020-05-15 11:28 p.m., Lars-Peter Clausen wrote:
> On 5/16/20 4:26 AM, Jonathan Bakker wrote:
>> In the discussion around adding the
Some devices may require a current adc, but only have a voltage
ADC onboard. In order to read the current, they have a resistor
connected to the ADC. Add bindings for this possibility.
Signed-off-by: Jonathan Bakker
---
.../iio/adc/linux,current-from-voltage.yaml | 47 +++
1
Some devices may require a current adc, but only have a voltage
ADC onboard. In order to read the current, they have a resistor
connected to the ADC.
Suggested-by: Jonathan Cameron
Signed-off-by: Jonathan Bakker
---
MAINTAINERS| 8 ++
drivers/iio/adc/Kconfig
://lore.kernel.org/linux-iio/20200202150843.762c6897@archlinux/
Jonathan Bakker (2):
dt-bindings: iio: adc: Add binding for current-from-voltage
iio: adc: Add current-from-voltage driver
.../iio/adc/linux,current-from-voltage.yaml | 47 +++
MAINTAINERS | 8
, cm_monitor() moves battery state diagram and does the
optimal operation for current state. As a result, it reduces whole
monitoring time almost in half.
Signed-off-by: Jonghwa Lee
Signed-off-by: Krzysztof Kozlowski
Signed-off-by: Jonathan Bakker
---
drivers/power/supply/charger-manager.c | 181
og/drivers/power/charger-manager.c?h=tizen_5.0
Jonathan Bakker (4):
power: supply: charger-manager: Always use POWER_SUPPLY_PROP_TEMP
power: supply: charger-manager: Update extcon functions
power: supply: charger-manager: Count cm-chargers property directly
dt-bindings: power: supply: Clean
The bindings for charger-manager were very unclear and didn't
specify allowable values in many cases. Clean these up to show
what each value does and make sure all properties are documented
here rather than using wildcards.
Signed-off-by: Jonathan Bakker
---
.../bindings/power/supply/ch
From: Jonghwa Lee
The POWER_SUPPLY_CHARGE_NOW/FULL property reflects battery's charges
in uAh unit, but charger-manager has been used it wrongly as a
status field.
Signed-off-by: Jonghwa Lee
Signed-off-by: Krzysztof Kozlowski
Signed-off-by: Jonathan Bakker
---
drivers/power/supply/ch
-off-by: Jonghwa Lee
Signed-off-by: Krzysztof Kozlowski
Signed-off-by: Jonathan Bakker
---
drivers/power/supply/charger-manager.c | 183 ++---
include/linux/power/charger-manager.h | 33 +
2 files changed, 16 insertions(+), 200 deletions(-)
diff --git a/drivers/power
: Jonathan Bakker
---
drivers/power/supply/charger-manager.c | 91 --
1 file changed, 11 insertions(+), 80 deletions(-)
diff --git a/drivers/power/supply/charger-manager.c
b/drivers/power/supply/charger-manager.c
index a21e1a2673f8..330185b960a5 100644
--- a/drivers/power/supply
Signed-off-by: Krzysztof Kozlowski
Signed-off-by: Jonathan Bakker
---
drivers/power/supply/charger-manager.c | 18 ++
1 file changed, 6 insertions(+), 12 deletions(-)
diff --git a/drivers/power/supply/charger-manager.c
b/drivers/power/supply/charger-manager.c
index 80d1699c938a
more important
that charging is enabled always in safe context.
Signed-off-by: Jonghwa Lee
Signed-off-by: Krzysztof Kozlowski
Signed-off-by: Jonathan Bakker
---
drivers/power/supply/charger-manager.c | 12 ++--
1 file changed, 2 insertions(+), 10 deletions(-)
diff --git a/drivers/power/s
Rather than having a cm-chargers and a separate cm-num-chargers
property, simply count the entries in cm-chargers.
Signed-off-by: Jonathan Bakker
---
drivers/power/supply/charger-manager.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/power/supply/charger
oth to use POWER_SUPPLY_PROP_TEMP.
Signed-off-by: Jonathan Bakker
---
drivers/power/supply/charger-manager.c | 6 ++
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git a/drivers/power/supply/charger-manager.c
b/drivers/power/supply/charger-manager.c
index 413f291fda5f..6a5ae1d0e
the extcon cable names and their IDs is needed. In order to retain DT
compatibility, TA and CHARGE-DOWNSTREAM are added as they were present up
until commit 11eecf910bd8 ("extcon: Modify the id and name of external
connector")
Signed-off-by: Jonathan Bakker
---
drivers/power/supply/ch
The bma180 and related chips should have two registers attached to
them. The IIO driver currently uses them, document them here as
well.
Acked-by: Rob Herring
Reviewed-by: Linus Walleij
Signed-off-by: Jonathan Bakker
---
Changes from v1
- Added A-b and R-b tags
---
Documentation/devicetree
Some variants of the bma180 (eg bma023) have different reset
values. In preparation for adding support for them, factor
out the reset value into the chip specific data.
Reviewed-by: Linus Walleij
Signed-off-by: Jonathan Bakker
---
Changes from v1
- Added R-b tag
---
drivers/iio/accel/bma180.c
were working.
Changes from v1:
-Added patches for bma150 and smb380 variants
-Add R-b and A-b tags
-Change so BMA180 and INPUT_BMA150 conflict rather than removing
the i2c ids from the input driver when the iio driver is enabled
Jonathan Bakker (7):
iio: accel: bma180: Prepare for different
The bma150/smb380 are very similar to the bma023 but have a temperature
channel as well.
Signed-off-by: Jonathan Bakker
---
drivers/iio/accel/Kconfig | 6 ++--
drivers/iio/accel/bma180.c | 71 +++---
2 files changed, 70 insertions(+), 7 deletions(-)
diff --git
The bma180 IIO driver is being extended for support for the chips
support by input's bma150 driver (bma023, bma150, smb380). Don't
allow both drivers to be enabled simultaneously as they're for the
same hardware.
Signed-off-by: Jonathan Bakker
---
drivers/iio/accel/Kconfig
support is not added for it.
Reviewed-by: Linus Walleij
Signed-off-by: Jonathan Bakker
---
Changes from v1
- Added R-b tag
---
drivers/iio/accel/Kconfig | 6 +-
drivers/iio/accel/bma180.c | 123 +++--
2 files changed, 122 insertions(+), 7 deletions(-)
diff
The bma023, bma150, and smb380 are in the same family as the bma180
and support is being added to the bma180 IIO driver for them.
Reviewed-by: Linus Walleij
Signed-off-by: Jonathan Bakker
---
Changes from v1
- Added bma150 and smb380 compatibles
- Added R-b tag
---
Documentation/devicetree
The bma180 driver is being extended to support the bma150.
Its temperature channel is unsigned so the center_temp naming
no longer makes.
Signed-off-by: Jonathan Bakker
---
drivers/iio/accel/bma180.c | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/drivers/iio
Hi Krzysztof,
On 2020-05-11 3:08 a.m., Krzysztof Kozlowski wrote:
> On Fri, May 08, 2020 at 06:34:33PM -0700, Jonathan Bakker wrote:
>> Some variants of the samsung tty driver can pick which clock
>> to use for their baud rate generation. In the DT conversion,
>> a default
Hi Sebastian,
On 2020-05-10 1:08 p.m., Sebastian Reichel wrote:
> Hi,
>
> On Mon, May 04, 2020 at 03:13:00PM -0700, Jonathan Bakker wrote:
>> According to the datasheet (1), the rcomp parameter can
>> vary based on the typical operating temperature and the
>> batt
: 97d642e23037 ("iio: light: Add a driver for Sharp GP2AP002x00F")
Signed-off-by: Jonathan Bakker
---
Changes from v1:
- Add Fixes tag
---
drivers/iio/light/gp2ap002.c | 19 ---
1 file changed, 16 insertions(+), 3 deletions(-)
diff --git a/drivers/iio/light/gp2ap002.c b/d
x27;t even need to change the device id check.
It has been tested with a modified libdrm's test from
https://github.com/tobiasjakobi/libdrm/tree/ippv2
Signed-off-by: Jonathan Bakker
---
drivers/gpu/drm/exynos/exynos_drm_fimc.c | 13 -
1 file changed, 12 insertions(+), 1 delet
Hi Kishon,
Is there anything else you (or someone else) needs from me? I'd really
appreciate getting USB working again on s5pv210 as without this patch it is
entirely broken.
Thanks,
Jonathan
On 2020-04-28 2:50 p.m., Jonathan Bakker wrote:
> Hi Kishon,
>
> On 2020-04-27 5:4
-off-by: Jonathan Bakker
---
drivers/iio/light/gp2ap002.c | 19 ---
1 file changed, 16 insertions(+), 3 deletions(-)
diff --git a/drivers/iio/light/gp2ap002.c b/drivers/iio/light/gp2ap002.c
index b7ef16b28280..7a2679bdc987 100644
--- a/drivers/iio/light/gp2ap002.c
+++ b/drivers/iio
n was implemented in such
a way that only the default clock was ever actually compared.
Fix this by iterating through all possible clocks, except when a
specific clock has already been picked via clk_sel (which is
only possible via board files).
Signed-off-by: Jonathan Bakker
---
drivers/tty/s
for all mainline dts
and cross referenced with the public Exynos4412 and S5PV210
datasheets.
Signed-off-by: Jonathan Bakker
---
drivers/iio/adc/exynos_adc.c | 14 +-
1 file changed, 13 insertions(+), 1 deletion(-)
diff --git a/drivers/iio/adc/exynos_adc.c b/drivers/iio/adc
H Dmitry,
On 2020-05-06 9:23 p.m., Dmitry Torokhov wrote:
> On Wed, May 06, 2020 at 08:46:12PM -0700, Jonathan Bakker wrote:
>> Hi Linus,
>>
>> On 2020-05-06 5:46 a.m., Linus Walleij wrote:
>>> On Sun, May 3, 2020 at 7:22 PM Jonathan Bakker wrote:
>>>
>&
Hi Linus,
On 2020-05-06 5:47 a.m., Linus Walleij wrote:
> On Sun, May 3, 2020 at 7:22 PM Jonathan Bakker wrote:
>
>> This patchset adds support for the bma023 three axis accelerometer
>> to the bma180 IIO driver. The bma023 is found on several ~2010
>> phones, includin
Hi Linus,
On 2020-05-06 5:46 a.m., Linus Walleij wrote:
> On Sun, May 3, 2020 at 7:22 PM Jonathan Bakker wrote:
>
>> The bma180 IIO driver has been extended for support for bma023.
>> However, this could cause conflicts with this driver. Since some
>> setups may dep
The rcomp value is a device-specific value for configuration based
on specific chemistries. There is no public documentation on how
to tune it.
Signed-off-by: Jonathan Bakker
---
.../devicetree/bindings/power/supply/max17040_battery.txt | 3 +++
1 file changed, 3 insertions(+)
diff --git
-MAX17041.pdf
Signed-off-by: Jonathan Bakker
---
drivers/power/supply/max17040_battery.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/power/supply/max17040_battery.c
b/drivers/power/supply/max17040_battery.c
index 8a1f0ee493aa..48aa44665e2f 100644
--- a/drivers/power
According to the datasheet (1), the rcomp parameter can
vary based on the typical operating temperature and the
battery chemistry. If provided, make sure we set it after
we reset the chip on boot.
1) https://datasheets.maximintegrated.com/en/ds/MAX17040-MAX17041.pdf
Signed-off-by: Jonathan
This patchset does two things:
1) Corrects the voltage reading from the max17040, which was missing
the shift and scaling.
2) Adds the ability to the set the rcomp, which is used to optimize
performance for specific battery chemistries and/or workloads.
Jonathan Bakker (3):
power: supply
support is not added for it.
Signed-off-by: Jonathan Bakker
---
drivers/iio/accel/Kconfig | 6 +-
drivers/iio/accel/bma180.c | 123 +++--
2 files changed, 122 insertions(+), 7 deletions(-)
diff --git a/drivers/iio/accel/Kconfig b/drivers/iio/accel/Kconfig
index
The bma023 is in the same family as the bma180 and support is
being added to the bma180 IIO driver for it.
Signed-off-by: Jonathan Bakker
---
Documentation/devicetree/bindings/iio/accel/bma180.txt | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/Documentation/devicetree
Some variants of the bma180 (eg bma023) have different reset
values. In preparation for adding support for them, factor
out the reset value into the chip specific data.
Signed-off-by: Jonathan Bakker
---
drivers/iio/accel/bma180.c | 8 ++--
1 file changed, 6 insertions(+), 2 deletions
The bma180 IIO driver has been extended for support for bma023.
However, this could cause conflicts with this driver. Since some
setups may depend upon the evdev setup, disable support in this
driver for the bma023 only when the IIO driver is being built.
Signed-off-by: Jonathan Bakker
the dt binding doc was missing
the regulators, so I've added those in.
The patches have been tested on a GT-i9000. The interrupt pin
is not connected on this board so the trigger was not tested.
Jonathan Bakker (5):
iio: accel: bma180: Prepare for different reset values
input: misc: b
The bma180 and related chips should have two registers attached to
them. The IIO driver currently uses them, document them here as
well.
Signed-off-by: Jonathan Bakker
---
Documentation/devicetree/bindings/iio/accel/bma180.txt | 2 ++
1 file changed, 2 insertions(+)
diff --git a/Documentation
In order to minimize leakage current during sleep, set a config
for sleep GPIOs.
Signed-off-by: Jonathan Bakker
---
Changes from v1
- Note where sleep GPIOs came from
---
arch/arm/boot/dts/s5pv210-galaxys.dts | 241 ++
1 file changed, 241 insertions(+)
diff --git a
From: Paweł Chmiel
Add support for the Silicon Labs si4709 fmradio, which can be found
on Galaxy S GT-i9000 (but not most other aries variants).
Signed-off-by: Paweł Chmiel
Signed-off-by: Jonathan Bakker
---
arch/arm/boot/dts/s5pv210-aries.dtsi | 2 +-
arch/arm/boot/dts/s5pv210-galaxys.dts
Aries boards have a Wolfson WM8994 sound card attached over gpio-i2c.
There is currently no ASoC Machine Driver.
Signed-off-by: Jonathan Bakker
---
arch/arm/boot/dts/s5pv210-aries.dtsi | 65 ++-
arch/arm/boot/dts/s5pv210-fascinate4g.dts | 6 +++
2 files changed, 69
On aries boards, the ADC is used for things such as jack detection
and battery temperature monitoring. It is connected to ldo4 of max8998,
so only enable that regulator when we are actually using the ADC.
Signed-off-by: Jonathan Bakker
---
Changes from v1
- Replace removed regulator-off-in
The bitbanged GPIO i2c adapters have external pull-ups attached
so the internal pulls should be disabled for lower power usage.
Signed-off-by: Jonathan Bakker
---
arch/arm/boot/dts/s5pv210-aries.dtsi | 18 ++
1 file changed, 18 insertions(+)
diff --git a/arch/arm/boot/dts
The exynos-adc driver now supports the S5PV210, so add the DT
node so that devices can use it.
Signed-off-by: Jonathan Bakker
---
Changes from v1
- Adjust node name to match reg address
---
arch/arm/boot/dts/s5pv210.dtsi | 12
1 file changed, 12 insertions(+)
diff --git a/arch
The enable GPIO for the fixed vibrator regulator shouldn't be
pulled in one direction or the other.
Signed-off-by: Jonathan Bakker
---
arch/arm/boot/dts/s5pv210-aries.dtsi | 9 +
1 file changed, 9 insertions(+)
diff --git a/arch/arm/boot/dts/s5pv210-aries.dtsi
b/arch/arm/boo
1 - 100 of 125 matches
Mail list logo
