aboutsummaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2019-09-17arm64: dts: lx2160a: misc fixeshoneycomb/vendor-rebase-v4.19Rabeeh Khoury
those are misc fixes that will be removed in some point. the first is build amc6821 support the second is setting default amc6821 default poalirty to be active high; this modification will not be needed in REV 1.4 of the COM express module since the inversion will be on the module. Signed-off-by: Rabeeh Khoury <rabeeh@solid-run.com>
2019-09-17arm64: dts: lx2160a: add lx2160acex7 device treeRabeeh Khoury
The device tree enables the following features - 1. dpmac17 RGMII MAC connected to Atheros AR8035 phy 2. 2x MDIO busses 3. 2x USB 3.0 controllers 4. 4x SATA ports 5. MT35X 512Mb SPI flash 6. Temperature sensor on i2c0 channel 3 7. AMC6821 temperature and PWM fan controller The module supports AMC6821 and EMC2301 PWM controllers where either can be assembled, but not both together since the PWM and TACH signals are shared between them. Signed-off-by: Rabeeh Khoury <rabeeh@solid-run.com>
2019-09-17arm64: dts: lx2160a: add lx2160acex7 device tree buildRabeeh Khoury
Signed-off-by: Rabeeh Khoury <rabeeh@solid-run.com>
2019-09-17tcp: enforce tcp_min_snd_mss in tcp_mtu_probing()Eric Dumazet
commit 967c05aee439e6e5d7d805e195b3a20ef5c433d6 upstream. If mtu probing is enabled tcp_mtu_probing() could very well end up with a too small MSS. Use the new sysctl tcp_min_snd_mss to make sure MSS search is performed in an acceptable range. CVE-2019-11479 -- tcp mss hardcoded to 48 Signed-off-by: Eric Dumazet <edumazet@google.com> Reported-by: Jonathan Lemon <jonathan.lemon@gmail.com> Cc: Jonathan Looney <jtl@netflix.com> Acked-by: Neal Cardwell <ncardwell@google.com> Cc: Yuchung Cheng <ycheng@google.com> Cc: Tyler Hicks <tyhicks@canonical.com> Cc: Bruce Curtis <brucec@netflix.com> Signed-off-by: David S. Miller <davem@davemloft.net> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2019-09-17tcp: add tcp_min_snd_mss sysctlEric Dumazet
commit 5f3e2bf008c2221478101ee72f5cb4654b9fc363 upstream. Some TCP peers announce a very small MSS option in their SYN and/or SYN/ACK messages. This forces the stack to send packets with a very high network/cpu overhead. Linux has enforced a minimal value of 48. Since this value includes the size of TCP options, and that the options can consume up to 40 bytes, this means that each segment can include only 8 bytes of payload. In some cases, it can be useful to increase the minimal value to a saner value. We still let the default to 48 (TCP_MIN_SND_MSS), for compatibility reasons. Note that TCP_MAXSEG socket option enforces a minimal value of (TCP_MIN_MSS). David Miller increased this minimal value in commit c39508d6f118 ("tcp: Make TCP_MAXSEG minimum more correct.") from 64 to 88. We might in the future merge TCP_MIN_SND_MSS and TCP_MIN_MSS. CVE-2019-11479 -- tcp mss hardcoded to 48 Signed-off-by: Eric Dumazet <edumazet@google.com> Suggested-by: Jonathan Looney <jtl@netflix.com> Acked-by: Neal Cardwell <ncardwell@google.com> Cc: Yuchung Cheng <ycheng@google.com> Cc: Tyler Hicks <tyhicks@canonical.com> Cc: Bruce Curtis <brucec@netflix.com> Cc: Jonathan Lemon <jonathan.lemon@gmail.com> Signed-off-by: David S. Miller <davem@davemloft.net> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2019-09-17tcp: tcp_fragment() should apply sane memory limitsEric Dumazet
commit f070ef2ac66716357066b683fb0baf55f8191a2e upstream. Jonathan Looney reported that a malicious peer can force a sender to fragment its retransmit queue into tiny skbs, inflating memory usage and/or overflow 32bit counters. TCP allows an application to queue up to sk_sndbuf bytes, so we need to give some allowance for non malicious splitting of retransmit queue. A new SNMP counter is added to monitor how many times TCP did not allow to split an skb if the allowance was exceeded. Note that this counter might increase in the case applications use SO_SNDBUF socket option to lower sk_sndbuf. CVE-2019-11478 : tcp_fragment, prevent fragmenting a packet when the socket is already using more than half the allowed space Signed-off-by: Eric Dumazet <edumazet@google.com> Reported-by: Jonathan Looney <jtl@netflix.com> Acked-by: Neal Cardwell <ncardwell@google.com> Acked-by: Yuchung Cheng <ycheng@google.com> Reviewed-by: Tyler Hicks <tyhicks@canonical.com> Cc: Bruce Curtis <brucec@netflix.com> Cc: Jonathan Lemon <jonathan.lemon@gmail.com> Signed-off-by: David S. Miller <davem@davemloft.net> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2019-09-17tcp: limit payload size of sacked skbsEric Dumazet
commit 3b4929f65b0d8249f19a50245cd88ed1a2f78cff upstream. Jonathan Looney reported that TCP can trigger the following crash in tcp_shifted_skb() : BUG_ON(tcp_skb_pcount(skb) < pcount); This can happen if the remote peer has advertized the smallest MSS that linux TCP accepts : 48 An skb can hold 17 fragments, and each fragment can hold 32KB on x86, or 64KB on PowerPC. This means that the 16bit witdh of TCP_SKB_CB(skb)->tcp_gso_segs can overflow. Note that tcp_sendmsg() builds skbs with less than 64KB of payload, so this problem needs SACK to be enabled. SACK blocks allow TCP to coalesce multiple skbs in the retransmit queue, thus filling the 17 fragments to maximal capacity. CVE-2019-11477 -- u16 overflow of TCP_SKB_CB(skb)->tcp_gso_segs Fixes: 832d11c5cd07 ("tcp: Try to restore large SKBs while SACK processing") Signed-off-by: Eric Dumazet <edumazet@google.com> Reported-by: Jonathan Looney <jtl@netflix.com> Acked-by: Neal Cardwell <ncardwell@google.com> Reviewed-by: Tyler Hicks <tyhicks@canonical.com> Cc: Yuchung Cheng <ycheng@google.com> Cc: Bruce Curtis <brucec@netflix.com> Cc: Jonathan Lemon <jonathan.lemon@gmail.com> Signed-off-by: David S. Miller <davem@davemloft.net> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2019-09-17Revert "crypto: caam - fix concurrency issue in givencrypt descriptor"Valentin Ciocoi Radulescu
This reverts commit c9411038a43d32258785e8cd0e2c18b76c4c82e4, because it introduced a regression. Signed-off-by: Valentin Ciocoi Radulescu <valentin.ciocoi@nxp.com>
2019-09-17ahci_qoriq: bug fix for ecc_addrUdit Kumar
Original driver expect a register node with name "sata-ecc" this node is of 64 bit wide. In ACPI such nodes can be provided with QWordMemory, but QWordMemory can not hold DescriptorName more than 4 characters. Therefore this patch changes platform property retrival based upon index instead of named. Signed-off-by: Udit Kumar <udit.kumar@nxp.com>
2019-09-17arm64: dts: ls1028a: add gpu nodeYuantian Tang
Add GPU dts node to enable GPU feature. Signed-off-by: Yuantian Tang <andy.tang@nxp.com>
2019-09-17sdk_qbman: Avoid variable length array in USDPAARoy Pledge
As of Linux 5.0 variable length arrays on the stack are no longer allowed. Change to a dynamic array and create a common exit point in the function for cleanup. Signed-off-by: Roy Pledge <roy.pledge@nxp.com>
2019-09-17net: dev: introduce support for sch BYPASS for lockless qdiscPaolo Abeni
With commit c5ad119fb6c0 ("net: sched: pfifo_fast use skb_array") pfifo_fast no longer benefit from the TCQ_F_CAN_BYPASS optimization. Due to retpolines the cost of the enqueue()/dequeue() pair has become relevant and we observe measurable regression for the uncontended scenario when the packet-rate is below line rate. After commit 46b1c18f9deb ("net: sched: put back q.qlen into a single location") we can check for empty qdisc with a reasonably fast operation even for nolock qdiscs. This change extends TCQ_F_CAN_BYPASS support to nolock qdisc. The new chunk of code mirrors closely the existing one for traditional qdisc, leveraging a newly introduced helper to read atomically the qdisc length. Tested with pktgen in queue xmit mode, with pfifo_fast, a MQ device, and MQ root qdisc: threads vanilla patched kpps kpps 1 2465 2889 2 4304 5188 4 7898 9589 Same as above, but with a single queue device: threads vanilla patched kpps kpps 1 2556 2827 2 2900 2900 4 5000 5000 8 4700 4700 No mesaurable changes in the contended scenarios, and more 10% improvement in the uncontended ones. v1 -> v2: - rebased after flag name change Signed-off-by: Paolo Abeni <pabeni@redhat.com> Tested-by: Ivan Vecera <ivecera@redhat.com> Reviewed-by: Eric Dumazet <edumazet@google.com> Reviewed-by: Ivan Vecera <ivecera@redhat.com> Signed-off-by: David S. Miller <davem@davemloft.net>
2019-09-17net: sched: add empty status flag for NOLOCK qdiscPaolo Abeni
The queue is marked not empty after acquiring the seqlock, and it's up to the NOLOCK qdisc clearing such flag on dequeue. Since the empty status lays on the same cache-line of the seqlock, it's always hot on cache during the updates. This makes the empty flag update a little bit loosy. Given the lack of synchronization between enqueue and dequeue, this is unavoidable. v2 -> v3: - qdisc_is_empty() has a const argument (Eric) v1 -> v2: - use really an 'empty' flag instead of 'not_empty', as suggested by Eric Signed-off-by: Paolo Abeni <pabeni@redhat.com> Reviewed-by: Eric Dumazet <edumazet@google.com> Reviewed-by: Ivan Vecera <ivecera@redhat.com> Signed-off-by: David S. Miller <davem@davemloft.net>
2019-09-17dpaa2-eth: add irq for the dpmac connect/disconnect eventFlorin Chiculita
Add IRQ for the DPNI endpoint change event, resolving the issue when a dynamically created DPNI gets a randomly generated hw address when the endpoint is a DPMAC object. Signed-off-by: Florin Chiculita <florinlaurentiu.chiculita@nxp.com>
2019-09-17dpaa2-eth: Fix incorrect version checkIoana Radulescu
The code checking whether the new autoneg API is supported had a bug, fix it. Signed-off-by: Catalin Neacsu <valentin-catalin.neacsu@nxp.com>
2019-09-17dpaa2-eth: Fix FQ-based enqueueIoana Radulescu
Consider traffic class (prio) value when selecting Tx FQ to enqueue to. Signed-off-by: Ioana Radulescu <ruxandra.radulescu@nxp.com>
2019-09-17crypto: caam - fix pkcs1pad(rsa-caam, sha256) failure because of invalid inputIuliana Prodan
The problem is with the input data size sent to CAAM for encrypt/decrypt. Pkcs1pad is failing due to pkcs1 padding done in SW starting with0x01 instead of 0x00 0x01. CAAM expects an input of modulus size. For this we strip the leading zeros in case the size is more than modulus or pad the input with zeros until the modulus size is reached. Signed-off-by: Iuliana Prodan <iuliana.prodan@nxp.com> Reviewed-by: Horia Geantă <horia.geanta@nxp.com> Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au> (cherry picked from commit c3725f7ccc8cae1fb71e97768f03bfbd846f7827) Backported to dash-linux. Signed-off-by: Horia Geantă <horia.geanta@nxp.com>
2019-09-17crypto: caam - fix concurrency issue in givencrypt descriptorHoria Geantă
IV transfer from ofifo to class2 (set up at [29][30]) is not guaranteed to be scheduled before the data transfer from ofifo to external memory (set up at [38]: [29] 10FA0004 ld: ind-nfifo (len=4) imm [30] 81F00010 <nfifo_entry: ofifo->class2 type=msg len=16> [31] 14820004 ld: ccb2-datasz len=4 offs=0 imm [32] 00000010 data:0x00000010 [33] 8210010D operation: cls1-op aes cbc init-final enc [34] A8080B04 math: (seqin + math0)->vseqout len=4 [35] 28000010 seqfifold: skip len=16 [36] A8080A04 math: (seqin + math0)->vseqin len=4 [37] 2F1E0000 seqfifold: both msg1->2-last2-last1 len=vseqinsz [38] 69300000 seqfifostr: msg len=vseqoutsz [39] 5C20000C seqstr: ccb2 ctx len=12 offs=0 If ofifo -> external memory transfer happens first, DECO will hang (issuing a Watchdog Timeout error, if WDOG is enabled) waiting for data availability in ofifo for the ofifo -> c2 ififo transfer. Make sure IV transfer happens first by waiting for all CAAM internal transfers to end before running [38]. New descriptor with jump command inserted at [38]: [..] [37] 2F1E0000 seqfifold: both msg1->2-last2-last1 len=vseqinsz [38] A1000401 jump: jsl1 all-match[!nfifopend] offset=[01] local->[39] [39] 69300000 seqfifostr: msg len=vseqoutsz [40] 5C20000C seqstr: ccb2 ctx len=12 offs=0 Signed-off-by: Horia Geantă <horia.geanta@nxp.com>
2019-09-17arm64: dts: ls1028a: Add temperature sensor nodeYuantian Tang
Add nxp sa56004 chip node for temperature monitor. Signed-off-by: Yuantian Tang <andy.tang@nxp.com>
2019-09-17staging: fsl-dpaa2: Remove duplicate config optionsG.h. Gao
Remove dpaa2-eth config options left over from when the driver was located in staging. Signed-off-by: Ioana Radulescu <ruxandra.radulescu@nxp.com>
2019-09-17arm64: dts: ls1028a: Fix CPU idle fail.Ran Wang
PSCI spec define 1st parameter's bit 16 of function CPU_SUSPEND to indicate CPU State Type: 0 for standby, 1 for power down. In this case, we want to select standby for CPU idle feature. But current setting wrongly select power down and cause CPU SUSPEND fail every time. Need this fix. Signed-off-by: Ran Wang <ran.wang_1@nxp.com>
2019-09-17spi: nxp-fspi: add "get_name" functionZhao Qiang
Signed-off-by: Zhao Qiang <qiang.zhao@nxp.com>
2019-09-17dmaengine: fsl-edma: support little endian for edma driverPeng Ma
improve edma driver to support little endian. Signed-off-by: Peng Ma <peng.ma@nxp.com>
2019-09-17arm64: dts: fsl: ls1028a: Add qDMA nodePeng Ma
Add the qDMA device tree nodes for LS1028A devices. Signed-off-by: Peng Ma <peng.ma@nxp.com>
2019-09-17arm64: dts: lx2160a: update interrupt property for Aquantia phyFlorin Chiculita
Update Aquantia AQR107 nodes interrupt property. Signed-off-by: Florin Chiculita <florinlaurentiu.chiculita@nxp.com>
2019-09-17can: flexcan: Handle bit timings overflowPankaj Bansal
The can_calc_bittiming tries to divide the tseg1 equally between phase_seg1 and prop_seg, which may not fit in CBT/FDCBT registers. Therefore, if phase_seg1 is more than possible value, increase prop_seg and decrease phase_seg1 Signed-off-by: Pankaj Bansal <pankaj.bansal@nxp.com>
2019-09-17can: flexcan: enable flexcan for all architecturesPankaj Bansal
flexcan is an IP module independent of the SOC architecture. Therefore, enable it for all architectures. Signed-off-by: Pankaj Bansal <pankaj.bansal@nxp.com> Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>
2019-09-17can: flexcan: modify the interrupt register handlingPankaj Bansal
in flexcan there are two interrupt mask registers and two interrupt flag register. all these registers are u32 registers imask1 and imask2 together provide the interrupt mast for maximum possible 64 Message Buffers (MBs). like (u64)imask = (u64)imask2 << 32) | imask1; same is true for iflag1 and iflag2. Now when the MBs are 64 and we operate flexcan in timestamp mode, the Tx MB is 63 and Rx MBs are 1-62. Tx MB always lies in imask2/iflag2.Which is why at present in irq handling for Tx irq, only iflag2 is checked. However when the MB size grows (for flexcan FD mode) the total MB count decreases to 14 and Tx MB becomes 13. in this case only checking iflag2 would cause irq handler to loose Tx interrupt, which causes flexcan device to stop. Therefore, modify the imask and iflag handling such that we always check/set complete 64 bit iflag and imask in timestamp mode. As FD mode is not supported when FIFO mode is selected, leave the iflag and imask handling in FIFO mode unchanged. Signed-off-by: Pankaj Bansal <pankaj.bansal@nxp.com>
2019-09-17net: can: flexcan: can FD Format (FDF) changesPankaj Bansal
Signed-off-by: Pankaj Bansal <pankaj.bansal@nxp.com>
2019-09-17net: can: flexcan: use CAN FD frames for Tx/RxPankaj Bansal
Use can FD frames for Tx/Rx operations. This would be needed in upcoming SOC LX2160A, which supports CAN FD protocol Signed-off-by: Pankaj Bansal <pankaj.bansal@nxp.com>
2019-09-17can: flexcan: split the Message Buffer RAM areaPankaj Bansal
The message buffer RAM area is not a contiguous 1KB area but 2 partitions of 512 bytes each. Till now, we used Message buffers with payload size 8 bytes, which translates to 32 MBs per partition and no spare space is left in any partition. However, in upcoming SOC LX2160A the message buffers can have payload size 64 bytes. This results in less than 32 MBs per partition and some empty area is left at the end of each partition.This empty area should not be accessed. Therefore, split the Message Buffer RAM area into two partitions. Signed-off-by: Pankaj Bansal <pankaj.bansal@nxp.com> Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>
2019-09-17can: flexcan: Add provision for variable payload sizePankaj Bansal
Till now the flexcan module supported 8 byte payload size as per CAN 2.0 specifications. But now upcoming flexcan module in NXP LX2160A SOC supports CAN FD protocol too. The Message buffers need to be configured to have payload size 64 bytes. Therefore, added provision in the driver for payload size to be 64 bytes. Signed-off-by: Pankaj Bansal <pankaj.bansal@nxp.com> Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>
2019-09-17can: flexcan: move rx_offload_add() from flexcan_probe() to flexcan_open()Pankaj Bansal
rx offload depends on number of message buffers, which in turn depends on messgae buffer size. with the upcoming LX2160A SOC the message buffer size can be configured to 72 bytes if it were to be used in CAN FD mode. The current mode in which the flexcan is being operated is known at the time of flexcan_open() but not at the time of flexcan_probe(). Therefore, move the rx_offload_add() from flexcan_probe() to flexcan_open(). correspondingly, move rx_offload_delete() from flexcan_remove() to flexcan_close(). Signed-off-by: Pankaj Bansal <pankaj.bansal@nxp.com> Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>
2019-09-17can: flexcan: flexcan_chip_start(): enable loopback mode in flexcanPankaj Bansal
Self reception disable bit needs to be cleared for loopback mode to work in flexcan. Signed-off-by: Pankaj Bansal <pankaj.bansal@nxp.com> Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>
2019-09-17can: flexcan: add self wakeup supportAisheng Dong
If wakeup is enabled, enter stop mode, else enter disabled mode. Self wake can only work on stop mode. Starting from IMX6, the flexcan stop mode control bits is SoC specific, move it out of IP driver and parse it from devicetree. Signed-off-by: Aisheng Dong <aisheng.dong@nxp.com> Signed-off-by: Joakim Zhang <qiangqing.zhang@nxp.com> Reviewed-by: Dong Aisheng <aisheng.dong@nxp.com> Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>
2019-09-17arm64: dts: fsl: layerscape: fix warnings when compiling dts filesPankaj Bansal
when compiling dts file using DTC_FLAG='-@', the device tree compiler reports these warnings: Warning (alias_paths): /aliases: aliases property name must include only lowercase and '-' Fixed the node aliases to silence these warnings. Signed-off-by: Pankaj Bansal <pankaj.bansal@nxp.com>
2019-09-17arm64: dts: fsl: layerscape: fix warnings when compiling dts filesPankaj Bansal
when compiling dts file using DTC_FLAG='-@', the device tree compiler reports these warnings: Warning (simple_bus_reg): /soc/mdio@0x8c0b000: simple-bus unit address format error, expected "8c0b000" Warning (unit_address_format): /pfe@04000000: unit name should not have leading 0s Fixed the node names to silence these warnings. Signed-off-by: Pankaj Bansal <pankaj.bansal@nxp.com>
2019-09-17arm64: dts: fsl: remove backplane supportFlorinel Iordache
Remove entire backplane support from device tree for all supported platforms Signed-off-by: Florinel Iordache <florinel.iordache@nxp.com>
2019-09-17arm64: dts: fsl: ls1028a: add flexcan nodePankaj Bansal
Add flexcan node in LS1028A SOC file as well as in QDS and RDB files. The device tree bindings used can be referred from Documentation/devicetree/bindings/net/can/fsl-flexcan.txt Signed-off-by: Pankaj Bansal <pankaj.bansal@nxp.com>
2019-09-17arm64: dts: fsl: lx2160a: add flexcan nodePankaj Bansal
Add flexcan node in LX2160A SOC file as well as in QDS and RDB files. The device tree bindings used can be referred from Documentation/devicetree/bindings/net/can/fsl-flexcan.txt Signed-off-by: Pankaj Bansal <pankaj.bansal@nxp.com>
2019-09-17Documentation: can: flexcan: Add flexcan clocks' informationPankaj Bansal
The clocking information is missing from flexcan device tree bindings. This information is needed to be able to use flexcan. Document the same. Signed-off-by: Pankaj Bansal <pankaj.bansal@nxp.com>
2019-09-17arm64: defconfig: enable NXP FlexCAN driverPankaj Bansal
Enable driver support of NXP FlexCAN controller. Signed-off-by: Pankaj Bansal <pankaj.bansal@nxp.com>
2019-09-17driver: phy: remove Freescale backplane phy driverZhao Qiang
Signed-off-by: Zhao Qiang <qiang.zhao@nxp.com>
2019-09-17arm64: dts: lx2160: update sata nodePeng Ma
Fix the sata ecc register address error. Signed-off-by: Peng Ma <peng.ma@nxp.com>
2019-09-17sdk: dts: ls1046frwy move dma-coherent from soc to its child nodesRan Wang
Since SMMU is not supported for SDK version, USB function will down if still apply property 'dma-coherent' in scope of soc (USB driver is not ready to support it alone) in SDK device trees, decide to remove it. And add dma-coherent on other non-USB child nodes under soc. Signed-off-by: Ran Wang <ran.wang_1@nxp.com>
2019-09-17Changed VFIO_DEVICE_FLAGS_FSL_MC defineDiana Craciun
Newer versions of kernel have more devices. In order to use the same QEMU for all versions, we need to update the define. Signed-off-by: Diana Craciun <diana.craciun@nxp.com>
2019-09-17arm: multi_v7_defconfig: Update CONFIG_BLK_DEV_RAM_SIZERan Wang
Current ramdiskrfs is causing error of 'No space left on device' when merging kernel module into the ramdisk. Need change CONFIG_BLK_DEV_RAM_SIZE to 524288 to fix this issue. Signed-off-by: Ran Wang <ran.wang_1@nxp.com>
2019-09-17arm64: lsdk.config: Update CONFIG_BLK_DEV_RAM_SIZERan Wang
Current ramdiskrfs is causing error of 'No space left on device' when merging kernel module into the ramdisk. Need change CONFIG_BLK_DEV_RAM_SIZE to 524288 to fix this issue Signed-off-by: Ran Wang <ran.wang_1@nxp.com>
2019-09-17sdk: dts: ls1046: drop smmu from the frwy sdk dtsesLaurentiu Tudor
Drop the smmu from the frwy and frwy-usdpaa versions of the SDK device trees because SMMU is supported only for the upstream version of the dpaa ethernet drivers. Signed-off-by: Laurentiu Tudor <laurentiu.tudor@nxp.com>
2019-09-17soc/qman: add return value to interrupt coalesce changing APIsMadalin Bucur
Check that the values received by the portal interrupt coalesce change APIs are in range. Signed-off-by: Madalin Bucur <madalin.bucur@nxp.com> Signed-off-by: Roy Pledge <roy.pledge@nxp.com> Signed-off-by: David S. Miller <davem@davemloft.net>