- 08 Jan, 2021 1 commit
-
-
Bart Vissers authored
This fixes a clock drift issue that is measurable with clocktest. The change was suggested by Jan a while ago [0], I tested it again on 4.19.89. [0] https://www.xenomai.org/pipermail/xenomai/2019-May/040929.htmlSigned-off-by:
Bart Vissers <bvissers@e2mtechnologies.eu> Signed-off-by:
Jan Kiszka <jan.kiszka@siemens.com>
-
- 11 Dec, 2020 1 commit
-
-
Fino Meng authored
Some GPIO or pinmux drivers referencing ipipe_handle_demuxed_irq() may compile as modules, which requires __ipipe_dispatch_irq() exported. Signed-off-by:
Fino Meng <fino.meng@linux.intel.com> [Jan: fine-tune commit message] Signed-off-by:
-
- 04 Nov, 2020 3 commits
-
-
Jan Kiszka authored
Signed-off-by: -
Jan Kiszka authored
This is the v4.19.152-cip37 CIP release
-
Jan Kiszka authored
This is not needed, in fact, and it is in conflict with upcoming stable changes. Philippe writes: "IIRC, the reason was to ensure that any mapping duplicated from a parent process which has pinned its memory via an earlier call to __ipipe_disable_ondemand_mappings() would be immediately un-COWed upon fork() in the child process. On second thoughts, this is useless since the child process either: - if it has to, explicitly attaches to the real-time core, which ends up calling mlock(), therefore causing these mappings to be un-COWed if need be. IOW, there is no inheritance of the Cobalt context at fork. Maybe at some point in time there was the assumption that such context might be shared between both processes somehow, which has been ruled out later on. - the child process does not attach to the real-time core, in which case COW is a non-issue." Signed-off-by:
-
- 25 Oct, 2020 1 commit
-
-
Nobuhiro Iwamatsu authored
Signed-off-by:Nobuhiro Iwamatsu <nobuhiro1.iwamatsu@toshiba.co.jp>
-
- 23 Oct, 2020 7 commits
-
-
Nobuhiro Iwamatsu authored
This is the 4.19.152 stable release
-
Lad Prabhakar authored
commit b03025c57396b23fe2423384c25aa580000e9883 upstream. Add Renesas R8A774C0 in pci_device_id table so that pci-epf-test can be used for testing PCIe EP on RZ/G2E. Signed-off-by:
Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com> Reviewed-by:
Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com> Link: https://lore.kernel.org/r/1589493809-2602-1-git-send-email-prabhakar.mahadev-lad.rj@bp.renesas.comSigned-off-by:
Greg Kroah-Hartman <gregkh@linuxfoundation.org> Signed-off-by:
Pavel Machek <pavel@denx.de> -
Lad Prabhakar authored
commit cd8bc7d4eb6608afe78ac51422ef94b7824f1646 upstream. Enable R-Car PCIe endpoint driver on RZ/G2E board, including enabling endpoint configurations CONFIG_PCI_ENDPOINT, CONFIG_PCI_ENDPOINT_CONFIGFS, CONFIG_PCI_EPF_TEST and CONFIG_PCI_ENDPOINT_TEST required to use and test the driver. Signed-off-by:
Geert Uytterhoeven <geert+renesas@glider.be> [PL: Manually applied changes to defconfig file] Signed-off-by:
Pavel Machek <pavel@denx.de> -
Lad Prabhakar authored
commit 2a6d0d63d99956a66f6605832f11755d74a41951 upstream. Add support for R-Car PCIe controller to work in endpoint mode. Link: https://lore.kernel.org/r/1588854799-13710-8-git-send-email-prabhakar.mahadev-lad.rj@bp.renesas.comSigned-off-by:
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com> Reviewed-by:
Pavel Machek <pavel@denx.de> -
Lad Prabhakar authored
commit 4c0f80920923f1033e9fe048f44b6e1ffe18c58d upstream. This patch adds the bindings for the R-Car PCIe endpoint driver. Link: https://lore.kernel.org/r/1588854799-13710-7-git-send-email-prabhakar.mahadev-lad.rj@bp.renesas.comSigned-off-by:
Rob Herring <robh@kernel.org> Reviewed-by:
Pavel Machek <pavel@denx.de> -
Lad Prabhakar authored
commit 328263687148bebf0d5daf5d06bcc2a46f3d7b0a upstream. The mask value was calculated incorrectly for PCIEPAMR register if the size was less than 128 bytes. Fix this issue by adding a check on size. Link: https://lore.kernel.org/r/1588854799-13710-4-git-send-email-prabhakar.mahadev-lad.rj@bp.renesas.comSigned-off-by:
Pavel Machek <pavel@denx.de> -
Lad Prabhakar authored
commit 78a0d7f2f5a31357bce68012d886507b4cf33598 upstream. Move shareable code to common file pcie-rcar.c and the #defines to pcie-rcar.h so that the common code can be reused with endpoint driver. There are no functional changes with this patch for the host controller driver. Link: https://lore.kernel.org/r/1588854799-13710-3-git-send-email-prabhakar.mahadev-lad.rj@bp.renesas.comSigned-off-by:
Pavel Machek <pavel@denx.de>
-
- 22 Oct, 2020 13 commits
-
-
Lad Prabhakar authored
commit fecc5cfcd55f7aacc483726c405a951bd6aaaf2e upstream. config option PCIE_RCAR internally selects PCIE_RCAR_HOST which builds the same driver. So this patch renames CONFIG_PCIE_RCAR to CONFIG_PCIE_RCAR_HOST so that PCIE_RCAR can be safely dropped from Kconfig file. Signed-off-by:
Pavel Machek <pavel@denx.de> -
Lad Prabhakar authored
commit a18f4b6ea50b81e28bd05381883a531ab345f753 upstream. This commit renames pcie-rcar.c to pcie-rcar-host.c in preparation for adding support for endpoint mode. CONFIG_PCIE_RCAR is kept so that arm64 defconfig change can be a separate patch. With this patch both config options PCIE_RCAR and PCIE_RCAR_HOST will be available but PCIE_RCAR internally selects PCIE_RCAR_HOST so that bisect builds wont be affected. Link: https://lore.kernel.org/r/1588854799-13710-2-git-send-email-prabhakar.mahadev-lad.rj@bp.renesas.comSigned-off-by:
Pavel Machek <pavel@denx.de> -
Kishon Vijay Abraham I authored
commit 5893c2e5353bb9a723d862d8b6ba8028a8f6a6eb upstream. Print throughput information in KB/s after every completed transfer, including information on whether DMA is used or not. Signed-off-by:
Kishon Vijay Abraham I <kishon@ti.com> Signed-off-by:
Alan Mikhak <alan.mikhak@sifive.com> [PL: Applied changes to pci-epf-test.c manually, always pass dma variable to pci_epf_test_print_rate() function as false since streaming DMA support is missing in EPF] Signed-off-by:
Pavel Machek <pavel@denx.de> -
Lad Prabhakar authored
commit d45e3c1a5979efd40dbbac9a5c3586f4fa41f734 upstream. R-Car PCIe controller has support to map multiple memory regions for mapping the outbound memory in local system also the controller limits single allocation for each region (that is, once a chunk is used from the region it cannot be used to allocate a new one). This features inspires to add support for handling multiple memory bases in endpoint framework. With this patch pci_epc_mem_init() initializes address space for endpoint controller which support single window and pci_epc_multi_mem_init() initializes multiple windows supported by endpoint controller. Link: https://lore.kernel.org/r/1588854799-13710-6-git-send-email-prabhakar.mahadev-lad.rj@bp.renesas.comSigned-off-by:
Pavel Machek <pavel@denx.de> -
Lad Prabhakar authored
commit 975cf23e3aa89588cbfc9ad6f2b23bd32af4edc7 upstream. pci_epc_mem_init() internally used page size equal to *PAGE_SIZE* to manage the address space so instead just pass the page size as a argument to pci_epc_mem_init(). Also make pci_epc_mem_init() as a C function instead of a macro function in preparation for adding support for pci-epc-mem core to handle multiple windows. Link: https://lore.kernel.org/r/1588854799-13710-5-git-send-email-prabhakar.mahadev-lad.rj@bp.renesas.comSigned-off-by:
Pavel Machek <pavel@denx.de> -
Kishon Vijay Abraham I authored
commit 83153d9f36e24978c6211d246cb6f532bf54e5dc upstream. commit 8963106e ("PCI: endpoint: Add MSI-X interfaces") while adding support to raise MSI-X interrupts from endpoint didn't include BAR Indicator register (BIR) configuration and MSI-X table offset as arguments in pci_epc_set_msix(). This would result in endpoint controller register using random BAR indicator register, the memory for which might not be allocated by the endpoint function driver. Add BAR indicator register and MSI-X table offset as arguments in pci_epc_set_msix() and allocate space for MSI-X table and pending bit array (PBA) in pci-epf-test endpoint function driver. Fixes: 8963106e ("PCI: endpoint: Add MSI-X interfaces") Signed-off-by:
Pavel Machek <pavel@denx.de> -
Vidya Sagar authored
commit 5e50ee27d4a52a817ab152128c48690ec7c5cdf1 upstream. Add support to defer core initialization for the endpoint mode of operation. This would enable support for implementations where the core initialization needs to be deferred until the PCIe reference clock is available from the host system. Signed-off-by:
Vidya Sagar <vidyas@nvidia.com> [lorenzo.pieralisi@arm.com: commit log] Signed-off-by:
Pavel Machek <pavel@denx.de> -
Vidya Sagar authored
commit 0ef22dcf0c1871888c4c0ee46a9d9c494f2fe997 upstream. Add support to send notifications to EPF from EPC once the core registers initialization is complete. Signed-off-by:
Pavel Machek <pavel@denx.de> -
Vidya Sagar authored
commit 3d5f7d9f6a38ddcc105ebfb23b640630bbabba65 upstream. Add a new feature core_init_notifier for cores that can notify about their availability for initialization. Signed-off-by:
Pavel Machek <pavel@denx.de> -
Kishon Vijay Abraham I authored
commit 2499ee84e02774a8573b7b4c76c8f2ea38669313 upstream. The PCIe endpoint core relies on the drivers that invoke the pci_epc_add_epf() API to allocate and assign a function number to each physical function (PF). Since endpoint function device can be created by multiple mechanisms (configfs, devicetree, etc..), allowing each of these mechanisms to assign a function number would result in mutliple endpoint function devices having the same function number. In order to avoid this, let EPC core assign a function number to the endpoint device. Signed-off-by:
Pavel Machek <pavel@denx.de> -
Kishon Vijay Abraham I authored
commit 07301c982643a432212840a4b648b5d3f5a061fa upstream. Protect concurrent access to pci_epf_ops with a mutex. Signed-off-by:
Pavel Machek <pavel@denx.de> -
Kishon Vijay Abraham I authored
commit 3d3248dbd018502f654064c78efcd2e165ab3486 upstream. The pci_epc_ops is not intended to be invoked from interrupt context. Hence replace spin_lock_irqsave and spin_unlock_irqrestore with mutex_lock and mutex_unlock respectively. Signed-off-by:
Pavel Machek <pavel@denx.de> -
Kishon Vijay Abraham I authored
commit 5779dd0a7dbd71e82478fb0bf125cc6cd3c43266 upstream. Use atomic_notifier_call_chain() to notify EPC events like linkup to EPF driver instead of using linkup ops in EPF driver. This is in preparation for adding proper locking mechanism to EPF ops. This will also enable to add more events (in addition to linkup) in the future. Signed-off-by:
Pavel Machek <pavel@denx.de>
-
- 20 Oct, 2020 14 commits
-
-
Hewenliang authored
commit 3c379a59b4795d7279d38c623e74b9790345a32b upstream. We should close fd before the return of run_test. Fixes: 3f2ed813 ("tools: PCI: Add a userspace tool to test PCI endpoint") Signed-off-by:
Hewenliang <hewenliang4@huawei.com> Signed-off-by:
Pavel Machek <pavel@denx.de> -
Jean-Jacques Hiblot authored
commit b71f0a0b upstream. This makes it easier to use pcitest in automated setups. Signed-off-by:
Jean-Jacques Hiblot <jjhiblot@ti.com> Signed-off-by:
Pavel Machek <pavel@denx.de> -
Kishon Vijay Abraham I authored
commit 6f5e193bfb55963ce5f4f68cc927f371ddb0913b upstream. commit beb4641a ("PCI: dwc: Add MSI-X callbacks handler"), in order to raise MSI-X interrupt, obtained MSIX table address from Base Address Register (BAR). However BAR only holds PCI address programmed by the host whereas the MSI-X table should be in the local memory. Store the MSI-X table address (virtual address) as part of ->set_bar() callback and use that to get the message address and message data here. Fixes: beb4641a ("PCI: dwc: Add MSI-X callbacks handler") Signed-off-by:
Pavel Machek <pavel@denx.de> -
Kunihiko Hayashi authored
commit f58d5f53c89479c12ad719c1960176442add5aaa upstream. After an endpoint is started through configfs, if 0 is written to the configfs entry 'start', the controller stops but the epc_group->start value remains 1. A subsequent unlinking of the function from the controller would trigger a spurious WARN_ON_ONCE() in pci_epc_epf_unlink() despite right behavior. Fix it by setting epc_group->start = 0 when a controller is stopped using configfs. Fixes: d7467991 ("PCI: endpoint: Introduce configfs entry for configuring EP functions") Signed-off-by:
Kunihiko Hayashi <hayashi.kunihiko@socionext.com> Signed-off-by:
Pavel Machek <pavel@denx.de> -
Alan Mikhak authored
commit daee4f4e42c792997f4fee47dcdfa65dd720ec02 upstream. Modify pci_epc_mem_alloc_addr() to cast the variable 'pageno' from type 'int' to 'phys_addr_t' before shifting left. This cast is needed to avoid treating bit 31 of 'pageno' as the sign bit which would otherwise get sign-extended to produce a negative value. When added to the base address of PCI memory space, the negative value would produce an invalid physical address which falls before the start of the PCI memory space. Signed-off-by:
Pavel Machek <pavel@denx.de> -
Alan Mikhak authored
commit dbb7bbcc upstream. Associated pci_epf_bar structure is needed in pci_epc_clear_bar() to clear a BAR correctly but it is reset in pci_epf_free_space() (that is called first) which results in pci_epc_clear_bar() failure. Reorder the pci_epc_clear_bar()/pci_epf_free_space() calls execution to fix the issue. Signed-off-by:
Pavel Machek <pavel@denx.de> -
Alan Mikhak authored
commit 3041a643 upstream. Always skip odd BAR when skipping 64bit BARs in pci_epf_test_set_bar() and pci_epf_test_alloc_space() otherwise pci_epf_test_set_bar() will call pci_epc_set_bar() on an odd loop index when skipping reserved 64bit BAR. Moreover, pci_epf_test_alloc_space() will call pci_epf_alloc_space() on bind for an odd loop index when BAR is 64bit but leaks on subsequent unbind by not calling pci_epf_free_space(). Signed-off-by:
Paul Walmsley <paul.walmsley@sifive.com> Signed-off-by:
Pavel Machek <pavel@denx.de> -
Alan Mikhak authored
commit f16fb16e upstream. PCI endpoint test function code should honor the .bar_fixed_size parameter from underlying endpoint controller drivers or results may be unexpected. In pci_epf_test_alloc_space(), check if BAR being used for test register space is a fixed size BAR. If so, allocate the required fixed size. Signed-off-by:
Pavel Machek <pavel@denx.de> -
Alan Mikhak authored
commit db7a6248 upstream. Set endpoint controller pointer to NULL in pci_epc_remove_epf() to avoid -EBUSY on subsequent call to pci_epc_add_epf(). Add a check for NULL endpoint function pointer. Signed-off-by:
Pavel Machek <pavel@denx.de> -
Kishon Vijay Abraham I authored
commit 2a9a8016 upstream. The address that is allocated using pci_epf_alloc_space() is directly written to the target address of the Inbound Address Translation unit (ie the HW component implementing inbound address decoding) on endpoint controllers. Designware IP [1] has a configuration parameter (CX_ATU_MIN_REGION_SIZE [2]) which has 64KB as default value and the lower 16 bits of the Base, Limit and Target registers of the Inbound ATU are fixed to zero. If the programmed memory address is not aligned to 64 KB boundary this causes memory corruption. Modify pci_epf_alloc_space() API to take alignment size as argument in order to allocate buffers to be mapped to BARs with an alignment that suits the platform where they are used. Add an 'align' parameter to epc_features which can be used by platform drivers to specify the BAR allocation alignment requirements and use this while invoking pci_epf_alloc_space(). [1] "I/O and MEM Match Modes" section in DesignWare Cores PCI Express Controller Databook version 4.90a [2] http://www.ti.com/lit/ug/spruid7c/spruid7c.pdfSigned-off-by:
Pavel Machek <pavel@denx.de> -
Kangjie Lu authored
commit 507b8200 upstream. In case alloc_workqueue() fails, return -ENOMEM to avoid potential NULL pointer dereferences. Signed-off-by:
Kangjie Lu <kjlu@umn.edu> [lorenzo.pieralisi@arm.com: commit log and code update] Signed-off-by:
Pavel Machek <pavel@denx.de> -
Kishon Vijay Abraham I authored
commit 35ce0d79 upstream. Since EPC features are now implemented using pci_epc_features and all the EPC drivers are moved to using pci_epc_features, remove features member in struct pci_epc and all the helper macros for configuring the features. Tested-by:
Gustavo Pimentel <gustavo.pimentel@synopsys.com> Signed-off-by:
Pavel Machek <pavel@denx.de> -
Kishon Vijay Abraham I authored
commit 92f2b028 upstream. Now that pci-epf-test uses get_features callback and dw_plat_pcie_epc_features in Designware plat EP driver already indicates it doesn't support linkup notification and is MSIX capable, remove setting epc->features which is not used anymore by the endpoint function driver. Tested-by:
Pavel Machek <pavel@denx.de> -
Kishon Vijay Abraham I authored
commit f1267978 upstream. pci_epf_linkup() is intended to be invoked if the EPC supports linkup notification. Now that pci-epf-test uses get_features callback, which indicates Rockchip EP driver doesn't support linkup notification, remove pci_epf_linkup() from Rockchip EP driver. Tested-by:
Shawn Lin <shawn.lin@rock-chips.com> Signed-off-by:
Pavel Machek <pavel@denx.de>
-
