summaryrefslogtreecommitdiff
path: root/Documentation
AgeCommit message (Collapse)Author
2019-08-07dt-bindings: lontium,lt8912: follow code changeMax Krummenacher
The driver got converted to a I2C device, DDC/EDID and HPD handling is added. Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
2019-06-21Input: colbri-vf50-ts: improve bindings documentationMax Krummenacher
Clarify properties. Drop unused pinctrl-2 state 'gpio'. Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
2019-06-21drm/bridge: Add support for Lontium LT8912Wyon Bi
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)
2019-06-21usb/misc/usb3503: add setting of 'non removable devices' registerMax Krummenacher
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)
2019-06-21usb: misc: usb3503: add the usb3803 variantMax Krummenacher
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)
2019-05-24iio: adc: add STMPE ADC devicetree bindingsStefan Agner
This adds the devicetree bindings for the STMPE ADC. This also corrects a typo in st,sample-time it is rather "6 -> 124 clocks" according to the datasheet and not 144. We need to use the naming stmpe_adc in devicetree because this is given by the mfd device. 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> Reviewed-by: Rob Herring <robh@kernel.org> Signed-off-by: Lee Jones <lee.jones@linaro.org> (cherry picked from commit 81cdab79818988d27d8aeb162b7988c9e6dde936)
2019-05-24dt-bindings: stmpe: Reformatting parameter list and use tabs onlyPhilippe Schenker
This patch reformats the parameter list for stmpe device in a table-style so it is more clear to read. Signed-off-by: Philippe Schenker <philippe.schenker@toradex.com> Reviewed-by: Rob Herring <robh@kernel.org> Signed-off-by: Lee Jones <lee.jones@linaro.org> (cherry picked from commit 270a60bcc8f23254d749987f3d2acb79ea5c599e)
2019-05-24Documentation: fix imx7d pinctrl dse config bitsMax Krummenacher
From the i.MX 7 reference manual the drive strenght field is defined as follows: 00 DSE_0_X1 01 DSE_1_X4 10 DSE_2_X2 11 DSE_3_X6 Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com> Acked-by: Marcel Ziswiler <marcel.ziswiler@toradex.com> (cherry picked from commit 38524d73583e8f7fc61c8acd57b77c0a29889616)
2019-05-13ENGR00305648-1 ASoC: imx-sgtl5000: Support non-ssi cpu-daiNicolin Chen
The current imx-sgtl5000 driver always attaches the cpu-dai to ssi while in fact it could be attached to other cpu-dais like SAI. Thus this patch use a general code to support another cpu-dai. And meanwhile update the devicetree for i.MX6 Series. Acked-by: Wang Shengjiu <b02247@freescale.com> Signed-off-by: Nicolin Chen <Guangyu.Chen@freescale.com> (cherry picked from commit f9302eb42ad8f597b46e681b5ad402af3fb7dd9d)
2019-05-08Merge branch 'linux-4.14.y_for_4.14-2.0.x-imx' into 4.14-2.0.x-imxPhilippe Schenker
2019-05-08USB: core: Fix bug caused by duplicate interface PM usage counterAlan Stern
commit c2b71462d294cf517a0bc6e4fd6424d7cee5596f upstream. The syzkaller fuzzer reported a bug in the USB hub driver which turned out to be caused by a negative runtime-PM usage counter. This allowed a hub to be runtime suspended at a time when the driver did not expect it. The symptom is a WARNING issued because the hub's status URB is submitted while it is already active: URB 0000000031fb463e submitted while active WARNING: CPU: 0 PID: 2917 at drivers/usb/core/urb.c:363 The negative runtime-PM usage count was caused by an unfortunate design decision made when runtime PM was first implemented for USB. At that time, USB class drivers were allowed to unbind from their interfaces without balancing the usage counter (i.e., leaving it with a positive count). The core code would take care of setting the counter back to 0 before allowing another driver to bind to the interface. Later on when runtime PM was implemented for the entire kernel, the opposite decision was made: Drivers were required to balance their runtime-PM get and put calls. In order to maintain backward compatibility, however, the USB subsystem adapted to the new implementation by keeping an independent usage counter for each interface and using it to automatically adjust the normal usage counter back to 0 whenever a driver was unbound. This approach involves duplicating information, but what is worse, it doesn't work properly in cases where a USB class driver delays decrementing the usage counter until after the driver's disconnect() routine has returned and the counter has been adjusted back to 0. Doing so would cause the usage counter to become negative. There's even a warning about this in the USB power management documentation! As it happens, this is exactly what the hub driver does. The kick_hub_wq() routine increments the runtime-PM usage counter, and the corresponding decrement is carried out by hub_event() in the context of the hub_wq work-queue thread. This work routine may sometimes run after the driver has been unbound from its interface, and when it does it causes the usage counter to go negative. It is not possible for hub_disconnect() to wait for a pending hub_event() call to finish, because hub_disconnect() is called with the device lock held and hub_event() acquires that lock. The only feasible fix is to reverse the original design decision: remove the duplicate interface-specific usage counter and require USB drivers to balance their runtime PM gets and puts. As far as I know, all existing drivers currently do this. Signed-off-by: Alan Stern <stern@rowland.harvard.edu> Reported-and-tested-by: syzbot+7634edaea4d0b341c625@syzkaller.appspotmail.com CC: <stable@vger.kernel.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2019-05-02Documentation: Add nospectre_v1 parameterDiana Craciun
commit 26cb1f36c43ee6e89d2a9f48a5a7500d5248f836 upstream. Currently only supported on powerpc. Signed-off-by: Diana Craciun <diana.craciun@nxp.com> Signed-off-by: Michael Ellerman <mpe@ellerman.id.au> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2019-05-02powerpc/fsl: Add FSL_PPC_BOOK3E as supported arch for nospectre_v2 boot argDiana Craciun
commit e59f5bd759b7dee57593c5b6c0441609bda5d530 upstream. Signed-off-by: Diana Craciun <diana.craciun@nxp.com> Signed-off-by: Michael Ellerman <mpe@ellerman.id.au> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2019-05-02ipv4: set the tcp_min_rtt_wlen range from 0 to one dayZhangXiaoxu
[ Upstream commit 19fad20d15a6494f47f85d869f00b11343ee5c78 ] There is a UBSAN report as below: UBSAN: Undefined behaviour in net/ipv4/tcp_input.c:2877:56 signed integer overflow: 2147483647 * 1000 cannot be represented in type 'int' CPU: 3 PID: 0 Comm: swapper/3 Not tainted 5.1.0-rc4-00058-g582549e #1 Call Trace: <IRQ> dump_stack+0x8c/0xba ubsan_epilogue+0x11/0x60 handle_overflow+0x12d/0x170 ? ttwu_do_wakeup+0x21/0x320 __ubsan_handle_mul_overflow+0x12/0x20 tcp_ack_update_rtt+0x76c/0x780 tcp_clean_rtx_queue+0x499/0x14d0 tcp_ack+0x69e/0x1240 ? __wake_up_sync_key+0x2c/0x50 ? update_group_capacity+0x50/0x680 tcp_rcv_established+0x4e2/0xe10 tcp_v4_do_rcv+0x22b/0x420 tcp_v4_rcv+0xfe8/0x1190 ip_protocol_deliver_rcu+0x36/0x180 ip_local_deliver+0x15b/0x1a0 ip_rcv+0xac/0xd0 __netif_receive_skb_one_core+0x7f/0xb0 __netif_receive_skb+0x33/0xc0 netif_receive_skb_internal+0x84/0x1c0 napi_gro_receive+0x2a0/0x300 receive_buf+0x3d4/0x2350 ? detach_buf_split+0x159/0x390 virtnet_poll+0x198/0x840 ? reweight_entity+0x243/0x4b0 net_rx_action+0x25c/0x770 __do_softirq+0x19b/0x66d irq_exit+0x1eb/0x230 do_IRQ+0x7a/0x150 common_interrupt+0xf/0xf </IRQ> It can be reproduced by: echo 2147483647 > /proc/sys/net/ipv4/tcp_min_rtt_wlen Fixes: f672258391b42 ("tcp: track min RTT using windowed min-filter") Signed-off-by: ZhangXiaoxu <zhangxiaoxu5@huawei.com> Signed-off-by: David S. Miller <davem@davemloft.net> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2019-04-05ARM: 8833/1: Ensure that NEON code always compiles with ClangNathan Chancellor
[ Upstream commit de9c0d49d85dc563549972edc5589d195cd5e859 ] While building arm32 allyesconfig, I ran into the following errors: arch/arm/lib/xor-neon.c:17:2: error: You should compile this file with '-mfloat-abi=softfp -mfpu=neon' In file included from lib/raid6/neon1.c:27: /home/nathan/cbl/prebuilt/lib/clang/8.0.0/include/arm_neon.h:28:2: error: "NEON support not enabled" Building V=1 showed NEON_FLAGS getting passed along to Clang but __ARM_NEON__ was not getting defined. Ultimately, it boils down to Clang only defining __ARM_NEON__ when targeting armv7, rather than armv6k, which is the '-march' value for allyesconfig. >From lib/Basic/Targets/ARM.cpp in the Clang source: // This only gets set when Neon instructions are actually available, unlike // the VFP define, hence the soft float and arch check. This is subtly // different from gcc, we follow the intent which was that it should be set // when Neon instructions are actually available. if ((FPU & NeonFPU) && !SoftFloat && ArchVersion >= 7) { Builder.defineMacro("__ARM_NEON", "1"); Builder.defineMacro("__ARM_NEON__"); // current AArch32 NEON implementations do not support double-precision // floating-point even when it is present in VFP. Builder.defineMacro("__ARM_NEON_FP", "0x" + Twine::utohexstr(HW_FP & ~HW_FP_DP)); } Ard Biesheuvel recommended explicitly adding '-march=armv7-a' at the beginning of the NEON_FLAGS definitions so that __ARM_NEON__ always gets definined by Clang. This doesn't functionally change anything because that code will only run where NEON is supported, which is implicitly armv7. Link: https://github.com/ClangBuiltLinux/linux/issues/287 Suggested-by: Ard Biesheuvel <ard.biesheuvel@linaro.org> Signed-off-by: Nathan Chancellor <natechancellor@gmail.com> Acked-by: Nicolas Pitre <nico@linaro.org> Reviewed-by: Nick Desaulniers <ndesaulniers@google.com> Reviewed-by: Stefan Agner <stefan@agner.ch> Signed-off-by: Russell King <rmk+kernel@armlinux.org.uk> Signed-off-by: Sasha Levin <sashal@kernel.org>
2019-04-03KVM: Reject device ioctls from processes other than the VM's creatorSean Christopherson
commit ddba91801aeb5c160b660caed1800eb3aef403f8 upstream. KVM's API requires thats ioctls must be issued from the same process that created the VM. In other words, userspace can play games with a VM's file descriptors, e.g. fork(), SCM_RIGHTS, etc..., but only the creator can do anything useful. Explicitly reject device ioctls that are issued by a process other than the VM's creator, and update KVM's API documentation to extend its requirements to device ioctls. Fixes: 852b6d57dc7f ("kvm: add device control API") Cc: <stable@vger.kernel.org> Signed-off-by: Sean Christopherson <sean.j.christopherson@intel.com> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2019-03-27MLK-21150-3 drm/bridge: sec-dsim: add a new property 'pref-rate'Fancy Fang
Add a new property 'pref-rate' support which can be used to assign a different clock frequency for the DPHY PLL reference clock in the dtb file. And if this property does not exist, the default clock frequency for the reference clock will be used. And according to the spec, the DPHY PLL reference clk frequency should be in [6MHz, 300MHz] range. Signed-off-by: Fancy Fang <chen.fang@nxp.com> (cherry picked from commit a9fafe8108505f8a1580af898ff5fa9c26d03680)
2019-02-22MLK-20940-1 i2c: busses: Add virtual i2c driver based on rpmsgClark Wang
Add virtual i2c driver to send SRTM i2c messages to M4. Each virtual I2C bus has a specal bus id, which is abstracted by M4. Each SRTM message include a bus id for the bus which the device is on. Virtual i2c rpmsg bus will bind rpbus nodes with compatible string "fsl,i2c-rpbus". And "rpmsg-i2c-channel" will probe only one rpmsg channel for all rpbuses. This virtual i2c driver depends on CONFIG_I2C and CONFIG_RPMSG. Signed-off-by: Clark Wang <xiaoning.wang@nxp.com>
2019-02-20dt-bindings: eeprom: at24: add "atmel,24c2048" compatible stringAdrian Bunk
commit 6c0c5dc33ff42af49243e94842d0ebdb153189ea upstream. Add new compatible to the device tree bindings. Signed-off-by: Adrian Bunk <bunk@kernel.org> Acked-by: Rob Herring <robh@kernel.org> Signed-off-by: Bartosz Golaszewski <brgl@bgdev.pl> Signed-off-by: Sasha Levin <sashal@kernel.org>
2019-02-12drm: content-type property for HDMI connectorStanislav Lisovskiy
Added content_type property to drm_connector_state in order to properly handle external HDMI TV content-type setting. v2: * Moved helper function which attaches content type property to the drm core, as was suggested. Removed redundant connector state initialization. v3: * Removed caps in drm_content_type_enum_list. After some discussion it turned out that HDMI Spec 1.4 was wrongly assuming that IT Content(itc) bit doesn't affect Content type states, however itc bit needs to be manupulated as well. In order to not expose additional property for itc, for sake of simplicity it was decided to bind those together in same "content type" property. v4: * Added it_content checking in intel_digital_connector_atomic_check. Fixed documentation for new content type enum. v5: * Moved patch revision's description to commit messages. v6: * Minor naming fix for the content type enumeration string. v7: * Fix parameter name for documentation and parameter alignment in order not to get warning. Added Content Type description to new HDMI connector properties section. v8: * Thrown away unneeded numbers from HDMI content-type property description. Switch to strings desription instead of plain definitions. v9: * Moved away hdmi specific content-type enum from drm_connector_state. Content type property should probably not be bound to any specific connector interface in drm_connector_state. Same probably should be done to hdmi_picture_aspect_ration enum which is also contained in drm_connector_state. Added special helper function to get derive hdmi specific relevant infoframe fields. v10: * Added usage description to HDMI properties kernel doc. v11: * Created centralized function for filling HDMI AVI infoframe, based on correspondent DRM property value. Acked-by: Hans Verkuil <hans.verkuil@cisco.com> Acked-by: Daniel Vetter <daniel.vetter@ffwll.ch> Signed-off-by: Stanislav Lisovskiy <stanislav.lisovskiy@intel.com> Link: https://patchwork.freedesktop.org/patch/msgid/20180515135928.31092-2-stanislav.lisovskiy@intel.com [vsyrjala: clean up checkpatch multiple blank lines warnings] Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
2019-02-12MLK-17537-8: drm/mxsfb: Add support for mode_validRobert Chiras
Implement mode_valid and check functions from drm_simple_display_pipe_funcs such that we can filter-out modes that cannot be driven by this controller. Add 3 new clocks: - video_pll: this is the PLL that provides the pixel clock; it's rate needs to be set such that the pixel clock can be achieved - osc_25: this is an oscillater that can be used as source clock for the video_pll; default freq is 25MHz - osc_27: same as above, but with freq of 27MHz Depending on the display mode used, the video_pll needs to have it's clock source a 25MHz or 27MHz oscillator. Also, the video_pll rate needs to be set to a rate that can be evenly divided to obtain the required pixel clock. All these settings (clock source and video_pll rate) are saved in mode_valid, then applied before mode needs to be set in the check function. Signed-off-by: Robert Chiras <robert.chiras@nxp.com> Reviewed-by: Laurentiu Palcu <laurentiu.palcu@nxp.com>
2019-02-12MLK-20691-1: rpmsg: imx_rpmsg: add new partition reset interruptRobin Gong
Add new partition reset interrupt group to know M4 reset and restore back at rpmsg level later. Signed-off-by: Robin Gong <yibin.gong@nxp.com> Acked-by: Richard Zhu <hongxing.zhu@nxp.com>
2019-02-12MLK-20351-2 Doc: fsl-imx-cspi: Add a description of dmas cellsClark Wang
The description of dmas pointed to the common description of dma, and the introduction of dmas was unclear. Add a doc link to sdma introduction. Signed-off-by: Clark Wang <xiaoning.wang@nxp.com>
2019-02-12MLK-20183-2: ASoC: imx-cdnhdmi: reconfigure the mclk for HDMI on imx8mqShengjiu Wang
In order to support 44kHz and 48kHz sample rate together, we need to reconfigure the parent clock of mclk. Signed-off-by: Shengjiu Wang <shengjiu.wang@nxp.com>
2019-02-12MLK-20177-1 doc: dts: ci-hdrc-usb2: add imx8mm compatible stringLi Jun
Add "fsl,imx8mm-usb" compatible string. Acked-by: Peter Chen <peter.chen@nxp.com> Signed-off-by: Li Jun <jun.li@nxp.com>
2019-02-12MLK-19850-6 usb: chipidea: introduce flag for enable USB PHY charger detectionPeter Chen
Some platforms may want to use USB PHY charger detection function when VBUS is there, add one flag for it. The user can enable it at firmware. Reviewed-by: Jun Li <jun.li@nxp.com> Signed-off-by: Peter Chen <peter.chen@nxp.com>
2019-02-12MLK-18789-2: drm/bridge: Add driver for legacy Freescale Seiko 43WVFIG adapterRobert Chiras
This is an adapter card made for the 4.3", 800x480, LCD panel Seiko 43WVFIG. The LCD panel is a 24bit DPI bus, while the adapter card has two ports: 18-bit and 24-bit data input. For the 18-bit data input, the adapter card is demuxing some of the data lines, in order to feed all of the 24 lines needed by the LCD. This driver handles both this use-cases. Signed-off-by: Robert Chiras <robert.chiras@nxp.com>
2019-02-12MLK-18789-1: drm/panel: Add driver for Seiko 43WVF1G panelMarco Franchi
Add driver for Seiko Instruments Inc. 4.3" WVGA (800 x RGB x 480) TFT with Touch-Panel. Datasheet available at: http://www.glyn.de/data/glyn/media/doc/43wvf1g-0.pdf Seiko 43WVF1G panel has two power supplies: avdd and dvdd and they require a specific power on/down sequence. For this reason the simple panel driver cannot be used to drive this panel, so create a new one heavily based on simple panel. Based on initial patch submission from Breno Lima. Signed-off-by: Marco Franchi <marco.franchi@nxp.com> Signed-off-by: Thierry Reding <treding@nvidia.com> Link: https://patchwork.freedesktop.org/patch/msgid/1500567179-6967-1-git-send-email-marco.franchi@nxp.com
2019-02-12MLK-19692-1 can: flexcan: add CAN wakeup function for MX8Joakim Zhang
This patch is to add CAN wakeup function on MX8 platforms and update the binding file fsl-flexcan.txt. For MX8, the function "flexcan_irq()" should not call "flexcan_exit_stop_mode()" due to firmware(SCU) cannot make SC IPC calls from an interrupt context. If not exit stop mode in ISR, it will continuously enter wakeup ISR for the reason that system will respond IRQ before call CAN system resume. To fix the issue, we can exit stop mode during noirq resume stage. For wakeup case, it should not set pinctrl to sleep state by pinctrl_pm_select_sleep_state. Reviewed-by: Dong Aisheng <aisheng.dong@nxp.com> Reviewed-by: Andy Duan <fugang.duan@nxp.com> Signed-off-by: Joakim Zhang <qiangqing.zhang@nxp.com>
2019-02-12MLK-19728-4 Documentation: bindings: i2c: add xen,i2cPeng Fan
Add xen,i2c bindings Signed-off-by: Peng Fan <peng.fan@nxp.com>
2019-02-12MLK-19557-2 can: flexcan: note for clock source selectJoakim Zhang
FLEXCAN has supported selecting the clock source to the CAN Protocol Engine (PE). It's SoC Implementation dependent. Refer to RM for detailed definition of each SoC. Signed-off-by: Joakim Zhang <qiangqing.zhang@nxp.com>
2019-02-12MLK-19351-5 can: flexcan: allow user to disable can fd mode from deviceDong AiSheng
tree Normally CAN FD capable device must work on FD mode as it has different statically claimed bittiming capability. This patch provides users to disable CAN FD capability if users want to only work at normal mode. Signed-off-by: Joakim Zhang <qiangqing.zhang@nxp.com>
2019-02-12MLK-19452-3 ARM: dts: Add spi slave support for imx7ulpXiaoning Wang
Add "spi-slave" attribute for recognizing slave mode. If it is not in slave mode, please delete this attribute. Usage can be found at spi-fsl-lpspi.txt. Modify "Makefile" to build "imx7ulp-evk-spi-slave.dtb". Signed-off-by: Xiaoning Wang <xiaoning.wang@nxp.com>
2019-02-12MLK-19565-1: ASoC: fsl_rpmsg_i2s: support rpmsg on imx8qmShengjiu Wang
On imx8qm mek, the cs42888 is connected with i2c in cm41 domain, but wm8960 is connected with i2c1, which is not in m4 domain. So we only need to eable rpmsg for cs42888. Signed-off-by: Shengjiu Wang <shengjiu.wang@nxp.com> (cherry picked from commit 9d2368aef40e4d107e4deee1a2c7e191c1afe644)
2019-02-12MLK-19432-1: ASoC: imx-ak5558: limit max rate as function of sample bitsViorel Suman
According to AK5558 MCLK frequence must not exceed 36.864 MHz. Limit maximum supported rate as function of max MCLK frequency, sample bits and number of slots. Signed-off-by: Viorel Suman <viorel.suman@nxp.com> Reviewed-by: Shengjiu Wang <shengjiu.wang@nxp.com> (cherry picked from commit 236796cad225daa39d5b77d763a1d964dd4de4c9)
2019-02-12MLK-19413-1 dt-bindings: display: imx-drm: Add pixel combiner descriptionsLiu Ying
Pixel combiner found in i.MX8 SoCs may combine two display streams(one master and the other slave) to drive a high pixel rate display. This patch adds DT property descriptions in imx-drm DT documentation for pixel combiner. Signed-off-by: Liu Ying <victor.liu@nxp.com>
2019-02-12MLK-19258-4 doc: dts: ci-hdrc-usb2: add property for picophyPeter Chen
Add two parameters which are used to tune USB signal for picophy, picophy is used at imx7d and imx845. Signed-off-by: Peter Chen <peter.chen@nxp.com>
2019-02-12MLK-18898-2: ASoC: imx-ak4458: refine mclk rate calculationViorel Suman
The existing implementation calculates mclk rate as function of audio sample rate multiplied to multiplier taken from Table 5. However this is not accurate for Manual Setting Mode - tables 3 & 4 from AK4458 RM defines rate (LRCK/FS) and frame width (MCLK/16fs..1152fs) ranges as parameters to calculate mclk frequency. Aside of this - adjust bclk:mclk ratio from machine driver as function of "compatible" id. Signed-off-by: Viorel Suman <viorel.suman@nxp.com> (cherry picked from commit 527b8b7032dcb75c14bb2790330ab96743d83b16)
2019-02-12MLK-19251-01 gpio: max732x: add output IO default voltage setAndy Duan
Add output IOs defalut voltage set in device tree by add property like: out-default = /bits/ 16 <mask val>; Reviewed-by: Haibo Chen <haibo.chen@nxp.com> Signed-off-by: Fugang Duan <fugang.duan@nxp.com>
2019-02-12MLK-19168-4: ASoC: fsl_rpmsg_i2s: support more codecShengjiu Wang
support more codecs, codec is specified by compatible string Signed-off-by: Shengjiu Wang <shengjiu.wang@nxp.com> (cherry picked from commit 7c92a75fcf83ec0aa3fe6773e4cb5f5e88a1ff09)
2019-02-12MLK-19042-1: ASoC: fsl_rpmsg_i2s: support low power audioShengjiu Wang
Add two new message command I2S_TX_POINTER and I2S_RX_POINTER, which are used to get the hw pointer in m4 side. For in low power audio mode, m4 won't send notification every period, the notification only be sent when hw pointer reach end of buffer, so we need these command to get the position of hw pointer, user can use it to calculate the timestamp. Restructure send message and recv message together for i2s_rpmsg, that every send message has a recv message. so the i2s_send_message can store the recv message indepedently. one reason is that the receive message is async withe send message. The low power audio is disabled in default, user need to enabled it by add "fsl,enable-lpa" in dts. Signed-off-by: Shengjiu Wang <shengjiu.wang@nxp.com> Reviewed-by: Viorel Suman <viorel.suman@nxp.com> (cherry picked from commit 753e7b819609ad4791e32069a124d4411c720947)
2019-02-12MLK-19192 dt-bindings: imx8qm/imx8qxp: update pad definitionAnson Huang
i.MX8QM/i.MX8QXP has pad type/definition change on B0, update binding doc accordingly. Signed-off-by: Anson Huang <Anson.Huang@nxp.com> Reviewed-by: Robin Gong <yibin.gong@nxp.com> (cherry picked from commit fd1e1f035e7cd2b0fd74549ba16172b5a10779cf)
2019-02-12MLK-19153-1 ARM: dts: update new "fsl,tx-d-cal" propertyPeter Chen
Using new "fsl,tx-d-cal" for dts, and update document accordingly. Acked-by: Jun Li <jun.li@nxp.com> Signed-off-by: Peter Chen <peter.chen@nxp.com>
2019-02-12MLK-18605-15 dt-bindings: display: panel: add 'video-mode' prop for rm67191Fancy Fang
Add a new property 'video-mode' binding for panel rm67191 which is used to specify a video data transfer mode. Signed-off-by: Fancy Fang <chen.fang@nxp.com> (cherry picked from commit 9dba8643d7b9c73a2b20ef517c79bb799f5ade3d)
2019-02-12MLK-18082: ARM: dts: imx: Change size of caam-sm to correct sizeFranck LENORMAND
The resources retrieved by CAAM driver was wrong as the size was not correct hence future uses might have issues. before: [ 3.010744] caam 30900000.caam: sm res: [start: 0000000000100000, end: 0000000000107ffe, name: /caam-sm@00100000, flags:0x200 desc:0x0] -> size: 0x7fff modif to actual size: [ 3.012495] caam 30900000.caam: sm res: [start: 0000000000100000, end: 0000000000107fff, name: /caam-sm@00100000, flags:0x200 desc:0x0] -> size: 0x8000 Signed-off-by: Franck LENORMAND <franck.lenormand@nxp.com>
2019-02-12MLK-18082: crypto: caam: Doc replace tab with spacesFranck LENORMAND
Signed-off-by: Franck LENORMAND <franck.lenormand@nxp.com>
2019-02-12MLK-18082: boot: dtsi: Align DTSIFranck LENORMAND
Signed-off-by: Franck LENORMAND <franck.lenormand@nxp.com>
2019-02-12MLK-15473-1: crypto: caam: Add CAAM driver support for iMX8 soc familyFranck LENORMAND
Enable CAAM driver for i.MX8 family: - Use a Job ring for RNG instantiation rather than DECO, even for i.MX6/7 families. - Use of aliased CAAM registers instead of original registers in page 0 since page 0 is no more accessible in i.MX8 family except mScale. Signed-off-by: Aymen Sghaier <aymen.sghaier@nxp.com>
2019-02-12MLK-18082: defconfig: Add caam to 7ulp confFranck LENORMAND
Signed-off-by: Franck LENORMAND <franck.lenormand@nxp.com>
2019-02-12MLK-18428-02: doc: binding: Add binding doc for imx8mm tmuBai Ping
Add dts binding doc for i.MX8MM TMU. Signed-off-by: Bai Ping <ping.bai@nxp.com> Reviewed-by: Anson Huang <Anson.Huang@nxp.com>
generated by cgit v1.2.3 (git 2.0.4) at 2024-06-01 15:30:41 +0000