Age | Commit message (Collapse) | Author |
|
Properly support probe deferral e.g. in case I2C is behind an I2C switch
as is the case for our new DSI to HDMI Adapter V1.1A.
Signed-off-by: Marcel Ziswiler <marcel.ziswiler@toradex.com>
|
|
Properly reserve I2C sub addresses as well.
Signed-off-by: Marcel Ziswiler <marcel.ziswiler@toradex.com>
|
|
This fixes a compilation error:
CC drivers/rtc/rtc-lib.o
In file included from drivers/phy/ti/phy-omap-usb2.c:30:0:
./include/linux/phy/omap_control_phy.h:46:2: error: redeclaration of enumerator ‘USB_MODE_HOST’
USB_MODE_HOST,
^~~~~~~~~~~~~
In file included from ./include/linux/usb/otg.h:14:0,
from ./include/linux/phy/omap_usb.h:23,
from drivers/phy/ti/phy-omap-usb2.c:24:
./include/linux/usb/phy.h:69:2: note: previous definition of ‘USB_MODE_HOST’ was here
USB_MODE_HOST,
^~~~~~~~~~~~~
In file included from drivers/phy/ti/phy-omap-usb2.c:30:0:
./include/linux/phy/omap_control_phy.h:47:2: error: redeclaration of enumerator ‘USB_MODE_DEVICE’
USB_MODE_DEVICE,
^~~~~~~~~~~~~~~
In file included from ./include/linux/usb/otg.h:14:0,
from ./include/linux/phy/omap_usb.h:23,
from drivers/phy/ti/phy-omap-usb2.c:24:
./include/linux/usb/phy.h:70:2: note: previous definition of ‘USB_MODE_DEVICE’ was here
USB_MODE_DEVICE,
^~~~~~~~~~~~~~~
make[3]: *** [scripts/Makefile.build:328: drivers/phy/ti/phy-omap-usb2.o] Error 1
AR drivers/pps/clients/built-in.o
make[2]: *** [scripts/Makefile.build:587: drivers/phy/ti] Error 2
make[1]: *** [scripts/Makefile.build:587: drivers/phy] Error 2
make[1]: *** Waiting for unfinished jobs....
CC drivers/rtc/hctosys.o
Related to: #50570
Signed-off-by: Oleksandr Suvorov <oleksandr.suvorov@toradex.com>
|
|
Any IIO ADC can be used with the driver, so do not depend
on VF610_ADC.
Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
|
|
Implement optional regular DDC/EDID I2C bus handling which may be
enabled via ddc-i2c-bus device tree property.
Signed-off-by: Marcel Ziswiler <marcel.ziswiler@toradex.com>
|
|
The regmap represents bytes, so when writting low and high bytes,
truncate the low byte to 0xff.
No adverse effects been seen though, regmap_write() seems to truncate
passed values.
Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
|
|
Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
|
|
(cherry picked from commit da9f0f3fe975924601f361d413bb71361cf11dd2)
Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
|
|
While it is legal it may be confusing to the reader.
Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
(cherry picked from commit fbc3228c0d26e82038b7658a4bde3ddc2f61cab5)
|
|
Signed-off-by: Philippe Schenker <philippe.schenker@toradex.com>
(cherry picked from commit 645bf88b06cdf707fdb5f1ad2cf435203940a959)
|
|
Make 1920x1080 really the default and only mark one resolution as the
preferred one.
(cherry picked from commit c61d21ae6156ff7c6ce981a586c52ca0abefa17c)
|
|
- Port the driver to use the gpiod framework
This allows to choose the polarity of the power_on and disable gpio in
the device tree.
- Actually use the gpios in the initialisation sequence
Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
(cherry picked from commit 91aedb97b4e65c4afc66f5a5b8d670061addd80d)
(cherry picked from commit 15a9d28286bba122f15e342cd40c6da7294b9bb6)
Fixed gpiod stuff after imx_4.14.98_2.3.0 resp. 4.14-2.3.x-imx merge.
Signed-off-by: Marcel Ziswiler <marcel.ziswiler@toradex.com>
|
|
Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
(cherry picked from commit 0c0420dcf29549bf045e0764a50c4c482cbb7232)
(cherry picked from commit 91bfc951ee0cff636db5dae01ed61f03132416e6)
|
|
The Lontium LT8912 MIPI-DSI to LVDS and HDMI/MHL bridge features a
single-channel MIPI D-PHY receiver front-end configuration with 4 data
lanes per channel operating at 1.5Gbps per data lane and a maximum
input bandwidth of 6Gbps.
Change-Id: I7733ea5f33094151bb62e62406561cc0025cf900
Signed-off-by: Wyon Bi <bivvy.bi@rock-chips.com>
Import and forward port to 4.9 (API change of_get_drm_display_mode() )
from https://github.com/rockchip-linux/kernel/commit/230f7f061036a99fc02d2cd7d20f66f7f0efae99
Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
drop drm_atomic_helper_connector_dpms, see 7d902c05b drm: Nuke drm_atomic_helper_connector_dpms
(cherry picked from commit 265fac62bf9defe0de5c1ce088013b61c9b46fb7)
(cherry picked from commit 7d2bdcf5aa35191aa0810884ea8eef944059269c)
|
|
Using regmap update bits the way it was used is wrong as only additional bits
gets set but no bits would be cleared.
The whole register or NRD and PDS are reserved for those two function.
There are no bits which needs to be preserved in the registers so just
writting the new value is all that is needed.
Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
(cherry picked from commit 02a78261315045011a5a987761d7a76e51b04480)
(cherry picked from commit b38bde54f80dbb67be727e04c8ee3e8d2969a3f9)
|
|
This allows to configure the NRD register from device tree or platform data.
Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
(cherry picked from commit 92ed1faf672e46e3e54b1f41f0b38f533b53b1aa)
(cherry picked from commit 6b5280f4e71770600d5b89638d849896158f2ec3)
|
|
While the usb3503 variant uses a HSIC connection to upstream,
the usb3803 uses a regular USB connection and provides a
bypass mode which connects the upstream port with downstream
port 3.
This adds an additional control gpio to the configuration which
allows moving away from the bypass mode to either standby or hub
mode once the driver is instantiated.
Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
(cherry picked from commit e7812f55781bd9453a231d104a2c6c520491e2e4)
(cherry picked from commit 8662817b83bee3c30336f104608752fcb652f5c4)
|
|
inital_io_dir: a 1 at a bit positions sets the corresponding pin as output.
inital_output: a 1 sets a gpio which is set to output with inital_io_dir to 1.
Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
(cherry picked from commit a7d303d7d63d444ed012200e98e6575814439101)
(cherry picked from commit 990f8c1dcb28cdc8eb6551b86621e1b29067136b)
|
|
Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
(cherry picked from commit f8df25d5785377f11fe8a757346ba8241847fb8d)
(cherry picked from commit 2d24d0eecddbc85c84f58e70b4d32778fbbcb9ec)
|
|
This commit needs to be split up and cleaned up. Also we should add
interrupt support before pushing upstream.
Signed-off-by: Eric Anholt <eric@anholt.net>
Imported from: https://patchwork.kernel.org/patch/9148419/
Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
(cherry picked from commit ca11f963f8c10dfd74392131cfde0fa653cdc80a)
(cherry picked from commit a09c79c004d49b44e010b246ee6036a89634a54f)
|
|
Add external reference clock via clock tree. This allows to model
the shared reference clock provided via PCIE_SATA_REFCLK100M_P/N
properly.
This is analogous to what we did for PCIe in commit db22e7590338
("PCI: imx6: add external clock support for i.MX8QM").
Signed-off-by: Marcel Ziswiler <marcel.ziswiler@toradex.com>
(cherry picked from commit 4b2d05c05c9e775abf7218ad7a4b52c2d220dd14)
Conflicts:
drivers/ata/ahci_imx.c
Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
(cherry picked from commit da0aa53df04d82eb15cecab90d98e6696d882923)
(cherry picked from commit 52683295a0ad72808f997be5548ec592828c61a1)
|
|
Remove the lpcg_xxx clocks codes, since they are HW gated.
These clocks controlled by HW, and would be turned on
automatically, if there are access operations.
Signed-off-by: Richard Zhu <hongxing.zhu@nxp.com>
(cherry picked from commit 9b8da32493057502a912b6d1426eadeb76780e69)
Conflicts:
arch/arm64/boot/dts/freescale/fsl-imx8qm.dtsi
drivers/pci/host/pci-imx6.c
Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
(cherry picked from commit 7615a560c48aeb53911c7a6f025420c0f9a5a51f)
(cherry picked from commit 0507816aa4b9a4f5764d308b23332fc297e6fe0f)
(cherry picked from commit 24258f088b89df68e5fa2c54eb3334ff50fcb8f0)
|
|
This commit adds code that forces setting the requested format in the
actual sensor driver.
Note that currently it is commented out as imx8 isi does not seem to
work properly with any other source resolution than the default
1920x1080.
Without this code, the driver will work with other resolutions (the ones
which are reported as supported by the connected sensors and lower than
1920x1080), but the image will be scaled down from 1920x1080. Scaling up
is not supported.
(cherry picked from commit a1a1244b1de00274586d1ea16048f8469966ff30)
(cherry picked from commit 16a4bd33e589b1f08c64a1b593d11921e62d6e72)
(cherry picked from commit f744198310d0849bd2fcb34bae4821317256b843)
(cherry picked from commit 8f67764a2fc758751a7de27973c4dd05a327244e)
|
|
The issue is that once the scaling was enabled, then the stream was
disabled and enabled again with a resolution that does not need scaling,
the actual scaling was never disabled in the ISI block. This made ISI
stream the scaled down with a large black padding.
(cherry picked from commit 148241e839644f6af83a3e677e1350ce50ce27e9)
(cherry picked from commit 13bef5c8fde55bf12be73ed05391427d393bb71c)
(cherry picked from commit 3ab199d9b1b3d0c94d89c2c1c5b2c5749d4bc476)
(cherry picked from commit edfbe38e61e6889afbbdf7a2608e5498619ef4ab)
|
|
Make the get_src_fmt callback treat all yuv formats equally. This is
needed to recognize the actual source format as yuv and enable yuv->rgb
conversion in the image processing unit of iMX8.
(cherry picked from commit 35711c32b6947d880f94bc5467acc842c0b3e96c)
Conflicts:
drivers/media/platform/imx8/mxc-isi-cap.c
Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
(cherry picked from commit 7f4707774bc1c4f737bfcfab82388c44b3b7bf68)
(cherry picked from commit 7fb7e36bfc525da2d3834e303db3230b395f35ba)
(cherry picked from commit 6be5a17562e2adf3d3dddee86c07cb6f3435e222)
|
|
Until now, the device searched for the subdev (sensor dev) using the
device name. That was a hack and required a hard-coded name of the
device in the common code.
This commit fixes it and makes it look for the proper subdevice using
the media pads layer.
(cherry picked from commit 9958f930c175cf8948278c85f4006870bebeebbb)
Conflicts:
drivers/media/platform/imx8/mxc-isi-cap.c
Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
(cherry picked from commit ce78564e48dca603c014786221b509bdc009e594)
(cherry picked from commit bfdbb433972d838171ed4a8b8c51e4fd3cc8d6cf)
(cherry picked from commit 839df9bc9ad0cf2aecc20302f767e9a7a938b8bb)
|
|
This driver is a copy of a driver by nVidia. It was improved by Antmicro
for the TK1 board.
Additionally there are some changes which were required to make it
compatible with iMX8.
(cherry picked from commit 8746c5c44e5405f09cf5f4568c2e71f402b11933)
(cherry picked from commit 3d1a424b1014f195525fc9e7cf6fe7a7e047ce56)
(cherry picked from commit 0b621d9cd8df6967fbfa659d9cf34f336f5afc98)
(cherry picked from commit 7fdb65b2a670f3bd62ad9ac484791c87a7c60e6e)
|
|
Add support to control HDMI levels using a GPIO. The driver simply
sets the GPIO high for HDMI and low for DisplayPort.
Signed-off-by: Stefan Agner <stefan.agner@toradex.com>
(cherry picked from commit d8868d38dc929cc5c4591f583489cdc57e93e9f2)
(cherry picked from commit b7d9e3c98e2d1681e2366f9011c599003e2179d3)
(cherry picked from commit 59004b52a9dcd08a1c1e3436851b2179f4ac7727)
(cherry picked from commit 060dd7a275260c26e0341dce9be59ec5c49722a4)
|
|
Add external reference clock via clock tree. This allows to model
the shared reference clock provided via PCIE_SATA_REFCLK100M_P/N
properly.
Signed-off-by: Stefan Agner <stefan.agner@toradex.com>
(cherry picked from commit db22e75903386929c76188978f28b3bf355322a0)
Conflicts:
drivers/pci/host/pci-imx6.c
Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
(cherry picked from commit 57364eca822fb2803b6aa93257e93e0d4242282d)
(cherry picked from commit f32040d9607bf3e7de57cf05733ae0b5d27b5640)
(cherry picked from commit 1c51d5cc8d041a5dfe3a1793bb3767450cab3c1a)
|
|
The keypad port (KPP) module is clocked by the IPG root clock
through clock gate CCM_CCGR170.
Signed-off-by: Stefan Agner <stefan.agner@toradex.com>
Acked-by: Marcel Ziswiler <marcel.ziswiler@toradex.com>
(cherry picked from commit 7b51b6365ebcf65b1054337a5bb0e1879397aae6)
(cherry picked from commit 09c36fb13aa73bac59709c5805f5f9f9e45acee9)
Conflicts:
include/dt-bindings/clock/imx7d-clock.h
Signed-off-by: Philippe Schenker <philippe.schenker@toradex.com>
|
|
Clear any interrupt that still is on the device on every channel
this driver is activated for in probe and specific channels in
the timeout handler.
Signed-off-by: Philippe Schenker <philippe.schenker@toradex.com>
Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
(cherry picked from commit ed1f310ee23d277d5386f532165911df69afe62f)
|
|
Use wait_for_completion_timeout instead of
wait_for_completion_interuptible_timeout.
The interruptible variant gets constantly interrupted if a user
program is compiled with the -pg option.
The killable variant was not used due to the fact that a second
program, reading on this device, that gets killed is then also killing
that wait.
Signed-off-by: Philippe Schenker <philippe.schenker@toradex.com>
Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
(cherry picked from commit e813dde6f83343012239a44e433eacc22de1079c)
|
|
This commit will enable the interrupts of all channels handled by this
driver only once in the probe function.
This will improve performance because one byte less has to be written over
i2c on each read out of the adc. On the fastest ADC mode this will improve
read out speed by 15%.
Signed-off-by: Philippe Schenker <philippe.schenker@toradex.com>
Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
(cherry picked from commit 4bd44bb2b470459d795c4bac328ed8edb7ebd132)
|
|
In some cases, the wait_completion got interrupted. This caused the
error-handling to mutex_unlock the function. The before turned on
interrupt then got called anyway. In the ISR then completion() was
called causing wrong adc-values returned in a following adc-readout.
Reinitialise completion struct to make sure the counter is zero
when beginning a new adc-conversion.
Signed-off-by: Philippe Schenker <philippe.schenker@toradex.com>
Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
(cherry picked from commit 263d21cd5e85eb4d96fd560eee814d98c5b89546)
|
|
Add the compatible name to the driver so it gets loaded when the proper
node in DT is detected.
Signed-off-by: Philippe Schenker <philippe.schenker@toradex.com>
Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
(cherry picked from commit 2abd293703ebafe8ae64876936ad345c6716cd9a)
|
|
Remove unnecessary assignment. This could potentially cause an issue, if
the wait function runs into a timeout. Furthermore is this assignment also
not there in stmpe_read_temp()
Signed-off-by: Philippe Schenker <philippe.schenker@toradex.com>
Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
(cherry picked from commit b1f4c9a3c78c70b05b2d844cc72c17d3620ba543)
|
|
This adds an ADC driver for the STMPE device using the industrial
input/output interface. The driver supports raw reading of values.
The driver depends on the MFD STMPE driver. If the touchscreen
block is enabled too, only four of the 8 ADC channels are available.
Signed-off-by: Stefan Agner <stefan@agner.ch>
Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
Signed-off-by: Philippe Schenker <philippe.schenker@toradex.com>
Reviewed-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Signed-off-by: Lee Jones <lee.jones@linaro.org>
(cherry picked from commit 9f3d084965a5544f096d4f769e274d4c2892079b)
|
|
This patch removes common ADC settings in favor to use
stmpe811_adc_common_init that is present in MFD. This is necessary in
preparation for the stmpe-adc driver, because those two drivers have
common settings for the ADC.
Signed-off-by: Philippe Schenker <philippe.schenker@toradex.com>
Acked-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Signed-off-by: Lee Jones <lee.jones@linaro.org>
(cherry picked from commit 88f29d0f2c8f0d8097dfca9fc3619dfe893e0b15)
|
|
This prepares the MFD for the STMPE ADC driver. This commit introduces
devicetree settings that are used by the ADC and adds an init function.
Common ADC settings that are shared with the touchscreen driver can now
reside in the overlying MFD.
Signed-off-by: Stefan Agner <stefan@agner.ch>
Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
Signed-off-by: Philippe Schenker <philippe.schenker@toradex.com>
Signed-off-by: Lee Jones <lee.jones@linaro.org>
(cherry picked from commit 6377cfa3b857ced301f2079ac97de6c19057ab65)
|
|
Move defines that are ADC related to the header of the overlying MFD,
so they can be used from multiple sub-devices.
Signed-off-by: Philippe Schenker <philippe.schenker@toradex.com>
Acked-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Signed-off-by: Lee Jones <lee.jones@linaro.org>
(cherry picked from commit 063755ab1d1c1127adc09703185967862584935b)
|
|
Due to the nature of CAN Tx/Rx pins have to be high when they are
idle. After boot, CAN is put into runtime_suspend state. When using
xceiver-supply in DT the power to the transceiver is turned off in this
state. The Tx/Rx pins are then causing backfeeding.
This patch adds selection of the sleep-state pins during
runtime_suspend, so someone is able to define another muxing
in this sate.
Signed-off-by: Philippe Schenker <philippe.schenker@toradex.com>
|
|
Use the max. junction temperature read from fusing for critical shutdown
temperature. Passive temperature is set 10C lower.
Signed-off-by: Philippe Schenker <philippe.schenker@toradex.com>
|
|
In kernel upgrade from 4.1 -> 4.9 trip point values have been changed
by NXP. These new values caused a lot of modules to critical shut-down
during validation and verification. This commit changes the new
imx_thermal.c code to use the old, well verified values.
Signed-off-by: Philippe Schenker <philippe.schenker@toradex.com>
Acked-by: Max Krummenacher <max.krummenacher@toradex.com>
(cherry picked from commit 308edefe57c5c96fad196b6e65fa159857e969f3)
|
|
Some Micrel KSZ8041NL PHY chips exhibit continous RX errors after
using the power down mode bit (0.11). If the PHY is taken out of
power down mode in a certain temperature range, the PHY enters a
weird state which leads to continously reporting RX errors. In that
state, the MAC is not able to receive or send any Ethernet frames
and the activity LED is constantly blinking. Since Linux is using
the suspend callback when the interface is taken down, ending up
in that state can easily happen during a normal startup.
Micrel confirmed the issue, caused by abnormal clock recovery when
using power down mode. Even the latest revision (A4, Revision ID
0x1513) seems to suffer that problem.
Remove the suspend/resume callback to avoid using the power down
mode completely.
Signed-off-by: Stefan Agner <stefan.agner@toradex.com>
Signed-off-by: Philippe Schenker <philippe.schenker@toradex.com>
Acked-by: Marcel Ziswiler <marcel.ziswiler@toradex.com>
(cherry picked from commit a76182f34d2963ee5dca3bc026cbddb44b19be7c)
|
|
Fix obvious typo that first return value is set but not checked.
Signed-off-by: Max Uvarov <muvarov@gmail.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
(cherry picked from commit a0da456bbf95d2a9294799bb05c61bfb24736bb7)
Signed-off-by: Philippe Schenker <philippe.schenker@toradex.com>
Acked-by: Marcel Ziswiler <marcel.ziswiler@toradex.com>
(cherry picked from commit 5f0a65495d895df2be2ddd681662f877f1a05b7f)
|
|
The current reset-gpio support triggers an interrupt storm on platforms
using the maxtouch with level based interrupt. The Motorola Droid 4,
which I used for some of the tests is not affected, since it uses a edge
based interrupt.
This change avoids the interrupt storm by enabling the device while its
interrupt is disabled. Afterwards we wait 100ms. This is important for
two reasons: The device is unresponsive for some time (~22ms for
mxt224E) and the CHG (interrupt) line is not working properly for 100ms.
We don't need to wait for any following interrupts, since the following
mxt_initialize() checks for bootloader mode anyways.
This fixes a boot issue on GE PPD (watchdog kills device due to
interrupt storm) and does not cause regression on Motorola Droid 4.
Fixes: f657b00df22e ("Input: atmel_mxt_ts - add support for reset line")
Signed-off-by: Sebastian Reichel <sebastian.reichel@collabora.co.uk>
Reviewed-by: Pavel Machek <pavel@ucw.cz>
Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
(cherry picked from commit ca1cd36cef00260db6b35b32d863e0c580c0488d)
(cherry picked from commit 6d7ffbea51c1f314a4435065147b36159169571f)
|
|
This reverts commit 6df9c073cb10a0f10d2fc2bea28f8133b5a89a66.
This fixes gpmi-nand being defunct on i.MX 6ULL and i.MX 7S/D just
hanging the ubifs background task during DMA.
Signed-off-by: Marcel Ziswiler <marcel.ziswiler@toradex.com>
Acked-by: Philippe Schenker <philippe.schenker@toradex.com>
|
|
from clks_init_on[]"
This reverts commit 04b647fe39e7b1f2ccbcde2e9eccc596b5f2b9da.
This fixes eMMC on sdhci3 being defunct just erroring out with -110.
Signed-off-by: Marcel Ziswiler <marcel.ziswiler@toradex.com>
Acked-by: Philippe Schenker <philippe.schenker@toradex.com>
|
|
Use the timing count from the parsed struct display_timings instead
of looping through the device tree again.
Signed-off-by: Stefan Agner <stefan.agner@toradex.com>
Acked-by: Max Krummenacher <max.krummenacher@toradex.com>
(cherry picked from commit 65be28e2a2b3761d088b20c43994be97d74c342f)
|
|
The PIXDATA flags of the display_flags enum are controller centric,
e.g. NEGEDGE means the controller shall drive the data signals on
pixelclocks negative edge. However, the drivers flag is display
centric: Sample the data on negative (falling) edge.
Therefore, change the if statement to check for the POSEDGE flag
(which is typically not set):
Drive on positive edge => sample on negative edge
Signed-off-by: Stefan Agner <stefan.agner@toradex.com>
Acked-by: Max Krummenacher <max.krummenacher@toradex.com>
(cherry picked from commit 5652dc1ad78303fb246f050ba23c563319d823cf)
|