There is no need to explicitly initiate a register transfer and
turn off the DCU after initializing the plane registers. In fact,
this is harmful and leads to unnecessary flickers if the DCU has
been left on by the bootloader.
Signed-off-by: Stefan Agner
---
drivers/gpu/drm/fsl-dcu
The pixel clock should not be on if the CRTC is not in use, hence
move clock enable/disable calls into CRTC callbacks.
Signed-off-by: Stefan Agner
---
drivers/gpu/drm/fsl-dcu/fsl_dcu_drm_crtc.c | 2 ++
drivers/gpu/drm/fsl-dcu/fsl_dcu_drm_drv.c | 21 +
2 files changed, 3
There is no need to explicitly initiate a register transfer and
turn off the DCU after initializing the plane registers. In fact,
this is harmful and leads to unnecessary flickers if the DCU has
been left on by the bootloader.
Signed-off-by: Stefan Agner
---
drivers/gpu/drm/fsl-dcu
Do not schedule a transfer of mode settings early. Modes should
get applied on on CRTC enable where we also enable the pixel clock.
Signed-off-by: Stefan Agner
---
drivers/gpu/drm/fsl-dcu/fsl_dcu_drm_crtc.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/drivers/gpu/drm/fsl-dcu
mode_set_nofb
- add patch which only init fbdev if required
- remove disable unprepare pixel clock on module remove (already disabled
in CRTC disable callback).
- remove unused label
Stefan Agner (5):
drm/fsl-dcu: enable TCON bypass mode by default
drm/fsl-dcu: do not transfer registers on plane init
There is no need to request a CMA backed framebuffer if fbdev
emulation is not enabled.
Signed-off-by: Stefan Agner
---
drivers/gpu/drm/fsl-dcu/fsl_dcu_drm_drv.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/fsl-dcu/fsl_dcu_drm_drv.c
b/drivers/gpu/drm
Do not schedule a transfer of mode settings early. Modes should
get applied on on CRTC enable where we also enable the pixel clock.
Signed-off-by: Stefan Agner
---
drivers/gpu/drm/fsl-dcu/fsl_dcu_drm_crtc.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/drivers/gpu/drm/fsl-dcu
Hi Lukasz,
On 2016-10-04 00:48, Lukasz Majewski wrote:
> Dear Bhuvanchandra,
>
> Thank you for your effort to send those patches to ML.
>
>> Changes since v2:
>>
>> - Picked the stalled patchset[1] from Lothar Wassmann which adds the
>> basic support for polarity control on imx-pwm driver and ad
There is no need to explicitly initiate a register transfer and
turn off the DCU after initializing the plane registers. In fact,
this is harmful and leads to unnecessary flickers if the DCU has
been left on by the bootloader.
Signed-off-by: Stefan Agner
---
If you could give this and 3/3 a try
Do not use encoder disable/enable callbacks to control bypass
mode as this seems to mess with the signals not liked by
displays. This also makes more sense since the encoder is
already defined to be parallel RGB/LVDS at creation time.
Signed-off-by: Stefan Agner
---
I tested that on Vybrid. Meng
The pixel clock should not be on if the CRTC is not in use, hence
move clock enable/disable calls into CRTC callbacks.
Signed-off-by: Stefan Agner
---
drivers/gpu/drm/fsl-dcu/fsl_dcu_drm_crtc.c | 7 +++
drivers/gpu/drm/fsl-dcu/fsl_dcu_drm_drv.c | 16 +---
2 files changed, 8
On 2016-10-03 05:50, Sanchayan Maity wrote:
> Enable DMA for DSPI on Vybrid.
Hm, we have that in 4.4 already, is that meant for 4.1?
>
> Signed-off-by: Sanchayan Maity
> ---
> arch/arm/boot/dts/vf-colibri.dtsi | 4
> arch/arm/boot/dts/vfxxx.dtsi | 6 ++
> 2 files changed, 10 inse
On 2016-09-27 21:14, Viresh Kumar wrote:
> On 27-09-16, 20:38, Stefan Agner wrote:
>> The i.MX I2C driver touches the pinctrl in its prepare/unprepare
>> callbacks.
>>
>> So, on a i.MX or Vybrid, the call chain looks like this:
>>
>> i2c_generic_gpio_recove
When using bridge without bridge netfilter enabled the message
displayed is rather confusing and leads to belive that a deprecated
feature is in use. Use IS_MODULE to be explicit that the message only
affects users which use bridge netfilter as module and reword the
message.
Signed-off-by: Stefan
On 2016-09-27 19:00, Viresh Kumar wrote:
> On 27-09-16, 12:34, Stefan Agner wrote:
>> Added Viresh Kumar to the discussion, he implemented the I2C recovery
>> functions.
>>
>> Yes, reordering the pinctrl/gpio_free calls would fix the problem too.
>>
>> Howeve
On 2016-09-27 11:17, Vladimir Zapolskiy wrote:
> Hi Stefan,
>
> On 09/27/2016 07:37 PM, Stefan Agner wrote:
>> On 2016-09-27 05:12, Vladimir Zapolskiy wrote:
>>> Hi Stefan,
>>>
>>> On 09/27/2016 03:26 AM, Stefan Agner wrote:
>>>> If a GPIO
On 2016-09-27 05:12, Vladimir Zapolskiy wrote:
> Hi Stefan,
>
> On 09/27/2016 03:26 AM, Stefan Agner wrote:
>> If a GPIO gets freed after selecting a new pinctrl configuration
>> the driver should not change pinctrl anymore. Otherwise this will
>> likely lead to a unu
If a GPIO gets freed after selecting a new pinctrl configuration
the driver should not change pinctrl anymore. Otherwise this will
likely lead to a unusable pin configuration for the newly selected
pinctrl.
Signed-off-by: Stefan Agner
---
This turned out to be problematic when using the I2C GPIO
Some SoC might load the GPIO driver after the I2C driver and
using the I2C bus recovery mechanism via GPIOs. In this case
it is crucial to defer probing if the GPIO request functions
do so, otherwise the I2C driver gets loaded without recovery
mechanisms enabled.
Signed-off-by: Stefan Agner
ps://cloud.agner.ch/index.php/s/Yfqa2u7UBEWUT8N
It would be interesting whether you see that on LS1021a too.
--
Stefan
>>
>> Any ideas?
>>
>> Stefan Agner (4):
>> drm/fsl-dcu: support overlay and cursor planes
>> drm/fsl-dcu: respect pos/siz
On 2016-09-13 23:35, Sanchayan Maity wrote:
> Remove use of pwm-leds and use the standard /sys/class/pwm
> interface from PWM subsystem.
Don't we have actual leds on the Ixora?
--
Stefan
>
> Signed-off-by: Sanchayan Maity
> ---
> arch/arm/boot/dts/imx6q-apalis-ixora.dts | 22 -
On 2016-09-09 12:37, Leo Li wrote:
> On Fri, Sep 9, 2016 at 11:51 AM, Stefan Agner wrote:
>> On 2016-09-08 16:57, Leo Li wrote:
>>> On Thu, Sep 8, 2016 at 5:39 PM, Stefan Agner wrote:
>>>> On 2016-09-06 15:40, Leo Li wrote:
>>>>> On Tue, Sep 6, 20
On 2016-09-08 16:57, Leo Li wrote:
> On Thu, Sep 8, 2016 at 5:39 PM, Stefan Agner wrote:
>> On 2016-09-06 15:40, Leo Li wrote:
>>> On Tue, Sep 6, 2016 at 4:51 PM, Stefan Agner wrote:
>>>> On 2016-09-06 13:06, Leo Li wrote:
>>>>> On Tue, Sep 6, 2
On 2016-09-06 15:40, Leo Li wrote:
> On Tue, Sep 6, 2016 at 4:51 PM, Stefan Agner wrote:
>> On 2016-09-06 13:06, Leo Li wrote:
>>> On Tue, Sep 6, 2016 at 1:58 PM, Uwe Kleine-König
>>> wrote:
>>>> On Fri, Aug 19, 2016 at 05:05:22PM -0500, Li Yang wrote:
On 2016-09-05 11:00, Stefan Agner wrote:
> The cachepolicy variable gets initialized using a masked pmd
> value. So far, the pmd has been masked with flags valid for the
> 2-page table format, but the 3-page table format requires a
> different mask. On LPAE, this lead to a wrong assump
On 2016-09-07 11:53, Mark Brown wrote:
> On Tue, Sep 06, 2016 at 11:01:15AM -0700, Stefan Agner wrote:
>> On 2016-09-06 01:22, Mark Brown wrote:
>
>> > This is nonsense unless the device can work without this supply. Given
>> > that the supply is called VCC tha
On 2016-09-06 13:06, Leo Li wrote:
> On Tue, Sep 6, 2016 at 1:58 PM, Uwe Kleine-König
> wrote:
>> On Fri, Aug 19, 2016 at 05:05:22PM -0500, Li Yang wrote:
>>> Since commit 1c4b6c3bcf30 ("i2c: imx: implement bus recovery") the
>>> driver starts to use gpio/pinctrl to do i2c bus recovery. But pinct
The fsl,panel property is deprecated and we should use the new
of_graph dt bindings to describe the relationship between the DCU
controller and the panel.
Signed-off-by: Stefan Agner
---
arch/arm/boot/dts/vf-colibri-eval-v3.dtsi | 13 -
1 file changed, 12 insertions(+), 1 deletion
es the same
conversion for the remaining boards.
Acked-by: Stefan Agner
--
Stefan
> ---
> arch/arm/boot/dts/ls1021a-twr.dts | 13 -
> 1 file changed, 12 insertions(+), 1 deletion(-)
>
> diff --git a/arch/arm/boot/dts/ls1021a-twr.dts
> b/arch/arm/boot/dts/ls1021a
On 2016-09-06 01:21, Tomi Valkeinen wrote:
> Hi,
>
> On 04/09/16 07:26, Stefan Agner wrote:
>> The lcd-supply is meant to be optional, there are several device-
>> trees not specifying it and the code handles error values silently.
>> Therefor, avoid creating a dummy re
On 2016-09-06 01:22, Mark Brown wrote:
> On Tue, Sep 06, 2016 at 10:45:19AM +0300, Felipe Balbi wrote:
>> Stefan Agner writes:
>
>> > According to the device tree bindings the vcc-supply is optional.
>
> This is nonsense unless the device can work without this suppl
Use the UPDATE_MODE READREG bit to initiate a register transfer
on flush. This makes sure that we flush all registers only once
for all planes.
Signed-off-by: Stefan Agner
---
drivers/gpu/drm/fsl-dcu/fsl_dcu_drm_crtc.c | 3 +++
drivers/gpu/drm/fsl-dcu/fsl_dcu_drm_plane.c | 5 -
2 files
Add support for overlay plane and a cursor plane. The driver uses
the topmost plane as cursor plane. The DCU IP would have dedicated
cursor support, but that lacks proper color support and hence is
not practical to use for Linux systems.
Signed-off-by: Stefan Agner
---
drivers/gpu/drm/fsl-dcu
READREG, which according to
documentation:
The READREG bit causes a single transfer to begin at the next frame
blanking period. This bit is cleared when the transfer is complete.
I made a video how that looks:
https://cloud.agner.ch/index.php/s/Yfqa2u7UBEWUT8N
Any ideas?
Stefan Agner (4):
drm/fsl
The IRQ status and mask registers are not "double buffered" according
to the reference manual. Hence, there is no extra transfer/update
write needed when modifying these registers.
Signed-off-by: Stefan Agner
---
drivers/gpu/drm/fsl-dcu/fsl_dcu_drm_drv.c | 4
1 file changed, 4
Mask the size and position values to avoid mutual overwriting.
Especially, a negative X position caused the Y position to be
overwritten with 0xfff too. This has been observed when using
a layer as cursor layer.
Signed-off-by: Stefan Agner
---
drivers/gpu/drm/fsl-dcu/fsl_dcu_drm_drv.h | 8
On 2016-07-25 00:08, Wei Yongjun wrote:
> Use PTR_ERR_OR_ZERO rather than if(IS_ERR(...)) + PTR_ERR.
>
> Generated by: scripts/coccinelle/api/ptr_ret.cocci
>
> Signed-off-by: Wei Yongjun
Applied!
--
Stefan
rent endianness. Check
>> endianness using the device-tree property "big-endian" to determine the
>> location of DIV_RATIO.
>>
>> Cc: sta...@vger.kernel.org
>> Fixes: 2d701449bce1 ("drm/fsl-dcu: use common clock framework for pixel
>> clock divide
check forces the
cache policy to writealloc and prints the following warning:
Forcing write-allocate cache policy for SMP
This patch introduces a new definition PMD_SECT_CACHE_MASK for
both page table formats which masks in all cache flags in both
cases.
Signed-off-by: Stefan Agner
---
Changes since
On 2016-09-04 15:09, Russell King - ARM Linux wrote:
> On Sat, Sep 03, 2016 at 10:33:31PM -0700, Stefan Agner wrote:
>> The cachepolicy variable gets initialized using a masked pmd
>> So far, the pmd has been masked with flags valid for the 2-page
>> table format. In the LPAE
the following
warning:
Forcing write-allocate cache policy for SMP
This patch uses PMD_SECT_WBWA to mask all cache setting flags.
The define represents the complete mask of the cache relevant
flags for both page table formats.
Signed-off-by: Stefan Agner
---
arch/arm/mm/mmu.c | 2 +-
1 file
-tree bindings.
Signed-off-by: Stefan Agner
---
Documentation/devicetree/bindings/display/mxsfb.txt | 3 +++
drivers/video/fbdev/mxsfb.c | 2 +-
2 files changed, 4 insertions(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/display/mxsfb.txt
b/Documentation
false. This is the
correct behavior, since even if the regulator is optional, it might
get initialized later...
Signed-off-by: Stefan Agner
---
This gets rid of warnings such as this (seen on i.MX 7):
3080.aips-bus:usbphynop1 supply vcc not found, using dummy regulator
--
Stefan
drivers/usb
bce1 ("drm/fsl-dcu: use common clock framework for pixel clock
divider")
Reported-by: Meng Yi
Signed-off-by: Stefan Agner
---
drivers/gpu/drm/fsl-dcu/fsl_dcu_drm_drv.c | 7 ++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/fsl-dcu/fsl_dcu_drm_drv.c
b
On 2016-08-29 06:28, Vladimir Zapolskiy wrote:
> Hi Marcel,
>
> On 02/05/2016 06:12 PM, Marcel Ziswiler wrote:
>> From: Petr Štetiar
>>
>> Signed-off-by: Marcel Ziswiler
>> Signed-off-by: Petr Štetiar
>> Reviewed-by: Stefan Agner
>> ---
>>
a vin-supply property of
those new module level system regulators. This also synchronize
the name of the +3.3V regulator with the one used in the Colibri
VF50/VF61 device tree.
Signed-off-by: Stefan Agner
---
arch/arm/boot/dts/imx7-colibri.dtsi | 12 +---
1 file changed, 9 insertions
Add audio support via on module I2S SGTL5000 codec.
Signed-off-by: Stefan Agner
---
arch/arm/boot/dts/imx7-colibri.dtsi | 41 -
1 file changed, 40 insertions(+), 1 deletion(-)
diff --git a/arch/arm/boot/dts/imx7-colibri.dtsi
b/arch/arm/boot/dts/imx7
Move SD-card definition to module level. While at it, also disable
write-protect since the Colibri standard does not define a pin for
SD-Card write-protection.
Signed-off-by: Stefan Agner
---
arch/arm/boot/dts/imx7-colibri-eval-v3.dtsi | 4
arch/arm/boot/dts/imx7-colibri.dtsi | 8
driver does not get loaded on i.MX 7Solo devices
(since the fsl,imx7s compatible string is not in the list of devices
making use of the cpufreq-dt driver...).
Signed-off-by: Stefan Agner
---
Hi Shawn,
This is based on my earlier patchset:
ARM: dts: imx7d: move ARM platform peripherals inside soc
Add clock-frequency property to CPU nodes. Avoids warnings like
"/cpus/cpu@0 missing clock-frequency property".
Signed-off-by: Stefan Agner
---
arch/arm/boot/dts/imx7d.dtsi | 2 ++
arch/arm/boot/dts/imx7s.dtsi | 1 +
2 files changed, 3 insertions(+)
diff --git a/arch/arm/boot/dts/im
On 2016-04-28 05:13, patrice.chot...@st.com wrote:
> From: Patrice Chotard
>
> Reset was only implemented for STMPE1801 variant despite
> all variant have a SOFT_RESET bit.
>
> For STMPE2401/2403/801/1601/1801 SOFT_RESET bit is bit 7
> of SYS_CTRL register.
> For STMPE610/811 (which have the sam
Since we have a SoC level node we should make use of it and have
all nodes which are within the SoC, inside that node. This also
saves an extra interrupt-parent properties. While at it, also
order the Coresight nodes according to register addresses.
Signed-off-by: Stefan Agner
---
Hi Shawn,
Not
The i.MX 7 as a GICv2, hence its CPU interface register map (the
second register region) is 8kB long. Add the VGIC maintenance
interrupt which allows to use the new VGIC driver.
Signed-off-by: Stefan Agner
Suggested-by: Marc Zyngier
---
arch/arm/boot/dts/imx7s.dtsi | 3 ++-
1 file changed, 2
On 2016-07-04 00:40, Peter Chen wrote:
> of_node_put needs to be called when the device node which is got
> from of_parse_phandle has finished using, but current code only
> calls it at error path, fix it by adding it at correct code path.
>
> Signed-off-by: Peter Chen
> ---
> drivers/gpu/drm/fs
On 2016-07-08 10:23, Srinivas Kandagatla wrote:
> On 08/07/16 17:42, Stefan Agner wrote:
>> On 2016-07-08 08:41, Srinivas Kandagatla wrote:
>>> On 07/07/16 14:48, maitysancha...@gmail.com wrote:
>>>> Hello Srinivas,
>>>>
>>>> On 16-07-07 1
>
;>>> Hello Srinivas,
>>>>
>>>> On 16-07-07 10:18:49, Srinivas Kandagatla wrote:
>>>>>
>>>>>
>>>>> On 07/07/16 07:39, Sanchayan Maity wrote:
>>>>>> From: Stefan Agner
>>>>>>
>>>&g
On 2016-07-03 11:23, Fabio Estevam wrote:
> Hi Stefan,
>
> On Sun, Jul 3, 2016 at 2:48 PM, Stefan Agner wrote:
>
>> Fabio, thanks for testing v1.
>>
>> With v2, the warnings should definitly be gone. However, that might
>> break some boards...
>
>
lock which somehow rely
on the ENET PLL, need to reenable the ENET PLL which leads to a sleep.
Removing those subsequent reparenting calls works around this issue.
Also remove comments. The code is really verbose enough.
Signed-off-by: Stefan Agner
---
Changes since v1:
- Also remove PHY REF clo
On 2016-07-01 18:12, Stephen Boyd wrote:
> On 06/29, Dong Aisheng wrote:
>> Recently several people met the kernel complaining
>> "bad: scheduling from the idle thread!" issue which caused by
>> sleeping during kernel early booting phase by calling clk
>> APIs like clk_prepare_enable.
>>
>> See:
>>
eparenting calls works around this issue.
Signed-off-by: Stefan Agner
---
Hi Dong,
What do you think about this change? I really think there is no need
to set the ethernet time roots here, and it would solve the problem
for now.
Also, we could move the other two parent assignments of ethernet
clo
On 2016-06-29 01:12, Lee Jones wrote:
> On Tue, 28 Jun 2016, Stefan Agner wrote:
>
>> This patchset adds RN5T567 PMIC support which is used on the
>> Toradex Colibri iMX7S/iMX7D modules. The existing RN5T618 is from
>> the same family, hence this patchset uses the same dr
Only register power off if the PMIC is defined as system power
controller (see Documentation/devicetree/bindings/power/
power-controller.txt).
Signed-off-by: Stefan Agner
Reviewed-by: Marcel Ziswiler
Acked-by: Lee Jones
---
drivers/mfd/rn5t618.c | 10 +++---
1 file changed, 7 insertions
it is required
- Fix DCDC count and a typos in device tree bindings
Changes since v1:
- Removed obsolete include
Stefan Agner (5):
ARM: dts: meson: minix-neo-x8: define PMIC as power controller
mfd: add Ricoh RN5T567 PMIC support
regulator: rn5t618: add RN5T567 PMIC support
mfd: rn5t618: reg
Use the PMIC's repower capability for reboots. Register a restart
handler and use a slightly elevated priority of 192 since the PMIC
has suprior reset capability (causing a system wide reset).
Signed-off-by: Stefan Agner
Reviewed-by: Marcel Ziswiler
Acked-by: Lee Jones
---
drivers/mfd/rn
The Ricoh RN5T567 is from the same family as the Ricoh RN5T618 is,
the differences are:
+ DCDC4
+ Slightly different output voltage/currents
+ 32kHz Output
- ADC/Charger capabilities
Signed-off-by: Stefan Agner
Reviewed-by: Marcel Ziswiler
Acked-by: Rob Herring
Acked-by: Lee Jones
Extend the driver to support Ricoh RN5T567. Support the additional
DCDC and slightly different voltage range of LDORTC1.
Signed-off-by: Stefan Agner
Reviewed-by: Marcel Ziswiler
Acked-by: Mark Brown
Acked-by: Lee Jones
---
drivers/regulator/Kconfig | 5 +++--
drivers/regulator
The PMIC driver used to register itself as poweroff controller by
default, hence assuming that this device is using the PMIC as
system power controller.
Signed-off-by: Stefan Agner
Reviewed-by: Marcel Ziswiler
Acked-by: Carlo Caione
---
arch/arm/boot/dts/meson8-minix-neo-x8.dts | 1 +
1 file
dings
Changes since v1:
- Removed obsolete include
Stefan Agner (5):
ARM: dts: meson: minix-neo-x8: define PMIC as power controller
mfd: add Ricoh RN5T567 PMIC support
regulator: rn5t618: add RN5T567 PMIC support
mfd: rn5t618: register power off callback optionally
mfd: rn5t618: reg
Only register power off if the PMIC is defined as system power
controller (see Documentation/devicetree/bindings/power/
power-controller.txt).
Signed-off-by: Stefan Agner
Reviewed-by: Marcel Ziswiler
---
drivers/mfd/rn5t618.c | 10 +++---
1 file changed, 7 insertions(+), 3 deletions
Use the PMIC's repower capability for reboots. Register a restart
handler and use a slightly elevated priority of 192 since the PMIC
has suprior reset capability (causing a system wide reset).
Signed-off-by: Stefan Agner
Reviewed-by: Marcel Ziswiler
---
drivers/mfd/rn5t618.c
The Ricoh RN5T567 is from the same family as the Ricoh RN5T618 is,
the differences are:
+ DCDC4
+ Slightly different output voltage/currents
+ 32kHz Output
- ADC/Charger capabilities
Signed-off-by: Stefan Agner
Reviewed-by: Marcel Ziswiler
Acked-by: Rob Herring
---
Documentation/devicetree
Extend the driver to support Ricoh RN5T567. Support the additional
DCDC and slightly different voltage range of LDORTC1.
Signed-off-by: Stefan Agner
Reviewed-by: Marcel Ziswiler
Acked-by: Mark Brown
Acked-by: Lee Jones
---
drivers/regulator/Kconfig | 5 +++--
drivers/regulator
The PMIC driver used to register itself as poweroff controller by
default, hence assuming that this device is using the PMIC as
system power controller.
Signed-off-by: Stefan Agner
Reviewed-by: Marcel Ziswiler
Acked-by: Carlo Caione
---
arch/arm/boot/dts/meson8-minix-neo-x8.dts | 1 +
1 file
-by: Stefan Agner
---
arch/arm/boot/dts/imx28-m28.dtsi| 2 +-
arch/arm/boot/dts/imx51-ts4800.dts | 2 +-
arch/arm/boot/dts/imx53-m53.dtsi| 2 +-
arch/arm/boot/dts/imx6q-dmo-edmqmx6.dts | 2 +-
arch/arm/boot/dts/socfpga_cyclone5_socrates.dts | 2
.
Signed-off-by: Stefan Agner
---
arch/powerpc/boot/dts/ac14xx.dts | 2 +-
arch/powerpc/boot/dts/akebono.dts | 2 +-
arch/powerpc/boot/dts/bluestone.dts| 2 +-
arch/powerpc/boot/dts/canyonlands.dts | 2 +-
arch/powerpc/boot/dts/currituck.dts| 2 +-
arch
have any impact on device detection.
Signed-off-by: Stefan Agner
---
Hi,
Mark mentioned that issue already once in the past, see:
http://lkml.iu.edu/hypermail/linux/kernel/1309.0/01686.html
Not sure through which trees this patches should flow, I guess
the first through Wolfram's tree, th
to be GPIO_ACTIVE_LOW
- Use compatible toradex,colibri-imx7(s|d)-eval-v3 (with dashes and v3)
- Various device tree properties fixed/altered as suggested by Shawn
- Specify 1P0D regulator supply
Stefan Agner (5):
ARM: imx: add support for i.MX 7Solo
ARM: dts: imx7d: use imx7s.dtsi as base device tree
Add support for the Computer on Module Colibri iMX7S/iMX7D along
with the development/evaluation carrier board device trees. Follow
the usual hierarchic include model, maintaining shared configuration
in imx7-colibri.dtsi and imx7-colibri-eval-v3.dtsi respectively.
Signed-off-by: Stefan Agner
The base device tree uses KEY_POWER in the snvs-powerkey node,
hence include the input.h header file in the base device tree.
Signed-off-by: Stefan Agner
Acked-by: Igor Grinberg
---
arch/arm/boot/dts/imx7d-cl-som-imx7.dts | 1 -
arch/arm/boot/dts/imx7d-nitrogen7.dts | 1 -
arch/arm/boot/dts
Add device tree compatible string "imx7s" for i.MX 7Solo.
Signed-off-by: Stefan Agner
---
arch/arm/mach-imx/mach-imx7d.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/mach-imx/mach-imx7d.c b/arch/arm/mach-imx/mach-imx7d.c
index b450f52..36254a6 100644
--- a/arch/arm/mac
-by: Stefan Agner
---
arch/arm/boot/dts/imx7d-cl-som-imx7.dts | 2 +-
arch/arm/boot/dts/imx7d-nitrogen7.dts| 2 +-
arch/arm/boot/dts/imx7d-sdb.dts | 2 +-
arch/arm/boot/dts/{imx7d.dtsi => imx7s.dtsi} | 0
4 files changed, 3 insertions(+), 3 deletions(-)
rename arch/
t yet part of the device tree)
- PCIe (not yet part of the device tree)
- Additional USB2.0 OTG controller
Signed-off-by: Stefan Agner
---
arch/arm/boot/dts/imx7d-cl-som-imx7.dts | 2 +-
arch/arm/boot/dts/imx7d-nitrogen7.dts | 2 +-
arch/arm/boot/dts/imx7d-sdb.dts | 2 +-
arch/arm
Use the PMIC's repower capability for reboots. Register a restart
handler and use a slightly elevated priority of 192 since the PMIC
has suprior reset capability (causing a system wide reset).
Signed-off-by: Stefan Agner
Reviewed-by: Marcel Ziswiler
---
drivers/mfd/rn5t618.c
The PMIC driver used to register itself as poweroff controller by
default, hence assuming that this device is using the PMIC as
system power controller.
Signed-off-by: Stefan Agner
Reviewed-by: Marcel Ziswiler
---
arch/arm/boot/dts/meson8-minix-neo-x8.dts | 1 +
1 file changed, 1 insertion
Only register power off if the PMIC is defined as system power
controller (see Documentation/devicetree/bindings/power/
power-controller.txt).
Signed-off-by: Stefan Agner
Reviewed-by: Marcel Ziswiler
---
drivers/mfd/rn5t618.c | 10 +++---
1 file changed, 7 insertions(+), 3 deletions
(e.g. watchdog)
- Print a warning if poweroff callback is already assigned
- Reorder of_id and variant assignment
- Lower delay to 1ms and justify why it is required
- Fix DCDC count and a typos in device tree bindings
Changes since v1:
- Removed obsolete include
Stefan Agner (5):
ARM: dts: meson:
Extend the driver to support Ricoh RN5T567. Support the additional
DCDC and slightly different voltage range of LDORTC1.
Signed-off-by: Stefan Agner
Reviewed-by: Marcel Ziswiler
Acked-by: Mark Brown
Acked-by: Lee Jones
---
drivers/regulator/Kconfig | 5 +++--
drivers/regulator
The Ricoh RN5T567 is from the same family as the Ricoh RN5T618 is,
the differences are:
+ DCDC4
+ Slightly different output voltage/currents
+ 32kHz Output
- ADC/Charger capabilities
Signed-off-by: Stefan Agner
Reviewed-by: Marcel Ziswiler
Acked-by: Rob Herring
---
Documentation/devicetree
The display panel is powered by the Carrier board's 3.3V rail.
Signed-off-by: Stefan Agner
---
arch/arm/boot/dts/vf-colibri-eval-v3.dtsi | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/boot/dts/vf-colibri-eval-v3.dtsi
b/arch/arm/boot/dts/vf-colibri-eval-v3.dtsi
index a8
ock polarity changes which will be part of 4.7 work for
Tower? I could never actually test that since I don't have the display
here...
https://patchwork.kernel.org/patch/8874971/
This patch looks good to me:
Acked-by: Stefan Agner
--
Stefan
>
> Signed-off-by: Anthony Felice
> ---
On 2016-06-24 12:44, Anthony Felice wrote:
> Add driver for the Vybrid Tower CRTouch-based touchscreen. This is
> required for the touchscreen on the TWR-LCD-RGB to work on the Vybrid
> Tower platform.
>
> There is a known issue with this driver: rarely, SW1 on the TWR-LCD-RGB
> module needs to be
On 2016-06-11 18:35, Shawn Guo wrote:
> On Tue, Jun 07, 2016 at 07:37:07PM -0700, Stefan Agner wrote:
>> The i.MX 7 series currently consists of two SoCs: i.MX 7Solo and
>> 7Dual. The i.MX 7Solo implements a subset of features available on
>> i.MX 7Dual, hence create imx7s.dt
Commit 7566e247672d ("drm/fsl-dcu: handle initialization errors properly")
introduced error handling during initialization, but with a wrong cleanup
order.
Replace the error handling with the generic cleanup function
drm_mode_config_cleanup.
Signed-off-by: Stefan Agner
---
drivers/g
On 2016-06-16 07:59, Lee Jones wrote:
> On Tue, 07 Jun 2016, Stefan Agner wrote:
>
>> Only register power off if the PMIC is defined as system power
>> controller (see Documentation/devicetree/bindings/power/
>> power-controller.txt).
>>
>> Reviewed-by: Marce
On 2016-06-16 07:55, Lee Jones wrote:
> On Tue, 07 Jun 2016, Stefan Agner wrote:
>
>> The Ricoh RN5T567 is from the same family as the Ricoh RN5T618 is,
>> the differences are:
>>
>> + DCDC4
>> + Slightly different output voltage/currents
>> +
On 2016-06-11 19:31, Shawn Guo wrote:
> On Tue, Jun 07, 2016 at 07:37:09PM -0700, Stefan Agner wrote:
>> +&lcdif {
>> +status = "okay";
>> +display = <&display0>;
>
> Please put 'status' at the bottom of property list.
>
>
On June 13, 2016 5:18:19 PM PDT, Bhhuvanchandra DV
wrote:
>Hi Shawn,
>
>On 06/11/2016 02:03 PM, Shawn Guo wrote:
>
>> On Thu, Jun 09, 2016 at 08:40:33PM +0530, Bhuvanchandra DV wrote:
>>> From: Stefan Agner
>>>
>>> In order to allow wake support i
On 2016-06-09 13:08, Thomas Gleixner wrote:
> On Tue, 7 Jun 2016, Dong Aisheng wrote:
>> Then it may need introduce a lot changes and increase many new core APIs.
>> Is that a problem?
>
> No. That's all better than each driver having broken workarounds. It's a
> common problem so it wants to be a
On 2016-06-08 13:22, Rob Herring wrote:
> On Tue, Jun 07, 2016 at 06:04:26PM -0700, Stefan Agner wrote:
>> The Ricoh RN5T567 is from the same family as the Ricoh RN5T618 is,
>> the differences are:
>>
>> + DCDC4
>> + Slightly different output voltage/currents
&
gabit Ethernet controller
- EPD (Electronc Paper Display, not yet part of the device tree)
- PCIe (not yet part of the device tree)
- Additional USB2.0 OTG controller
Signed-off-by: Stefan Agner
---
arch/arm/boot/dts/imx7d.dtsi | 923 +++
arch/arm/boot/dts/imx7s
801 - 900 of 1811 matches
Mail list logo
