Received: by 2002:ac0:a5a7:0:0:0:0:0 with SMTP id m36-v6csp5336768imm; Tue, 31 Jul 2018 09:15:00 -0700 (PDT) X-Google-Smtp-Source: AAOMgpcriRjLE9elOpdzFZzB/AMv+uBOC5h7sH44+WebRvqq7JA3hzMnJhqjKh+13yZPbXplFakv X-Received: by 2002:a17:902:e18d:: with SMTP id cd13-v6mr20601618plb.305.1533053700168; Tue, 31 Jul 2018 09:15:00 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1533053700; cv=none; d=google.com; s=arc-20160816; b=DAmVTJv9sTWhxYkkAVkdaerRsVMXv0WfqI33Znn+njc0PGo5gOZ1mQFKzF+iqOf+RT 8b4xw7J/Hx3H6wqGT3lc3Zi1FPrAM5QPuRTiOUKRt3kB/iXoicemmXzEdd4SbMO5JzIL rXcPHTM8+gAvwmYH2d/w915YHlo7lipvevAR3YGBZO+68W8H2vpjmPtVQKvR5Ezmw3Cg qTuH4HICodGXj7/04fpm5koujCDRIb5QkF8lXpsjmhHzJhmgGNp4QlSk60riFjx6Tsek 5mbWwy2QyaX65pPBi1NWMi/wCTOAm7Y94uIoJXHvyWt63mv9q0InBk12WLmxqVd+aGQr wCEQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:message-id:date:subject:cc:to:from :dkim-signature:arc-authentication-results; bh=Bz3G3p5Hkg4TXYwqTjT6qNuoVx3+KMbVy7giaEmfv+I=; b=t2wZW0+A5OS9P9aWIpGQPalAi3KTRcXxce65y73F6FzoFmbVnXGwZ+YLg8XpgR4f2F 3jUa5r9Ar2DsMXHwxx2liPSWspXfnvG7Z4GStKfgMK3VAhgh/5X2/TB0ZFgNveHFZemd qcX1J9jz3ci7jfti3CiI0/VrZwvSSgqZC2iWBRdlqgrz6swGklsaweqi63eALOYc4T/b j3unWtP0aZzh1qRAyB8fpwUFHr/oi65+Y4Q1GNf8KccSn+EMQeRGW/Z3tXHuTTJ9b76+ FFBkgH4HNjx7H4I/iQCEi1rquNCaVFRSEtDgJdXJiPAJeOMtB8IwTE0Vf/ecB+ZxPY3r ec/A== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=YjLERdFg; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linaro.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id e17-v6si12108842pgv.615.2018.07.31.09.14.45; Tue, 31 Jul 2018 09:15:00 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=YjLERdFg; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linaro.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1732495AbeGaRyq (ORCPT + 99 others); Tue, 31 Jul 2018 13:54:46 -0400 Received: from mail-wr1-f66.google.com ([209.85.221.66]:40760 "EHLO mail-wr1-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728052AbeGaRyq (ORCPT ); Tue, 31 Jul 2018 13:54:46 -0400 Received: by mail-wr1-f66.google.com with SMTP id h15-v6so17260322wrs.7 for ; Tue, 31 Jul 2018 09:13:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=from:to:cc:subject:date:message-id; bh=Bz3G3p5Hkg4TXYwqTjT6qNuoVx3+KMbVy7giaEmfv+I=; b=YjLERdFg541lODcMb7d3wqMEHXKRAGnGCLH0SiVxax45nssG4BTtZzNdzJ/eIAWyk+ Yqhx3IVJBW2yJG3E7MRNWhdLMKuAWoa7KdLFdL6XitPfbc9Ls+6WSixJ/WZvQS6/0gfx QrSXXEs5+TS76RfmoBO/qN7Kf6/2eXC7ZTHlQ= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id; bh=Bz3G3p5Hkg4TXYwqTjT6qNuoVx3+KMbVy7giaEmfv+I=; b=uRBurbb/LbJzaYczYoGmjrJts8St1BX2As6GMAc+8NDnb0eFFyvoR+s0yKrD6e6Xnq OUr+tULSqEJo8mjoMO3+ed54BR/hOclee4ZdnL55FdO3rvQX/4EgmZZVd6iMeuBJPb1I RrlPWyNi7IJeb7myki0I5pkkCBWr14gKlptp/eXQPhrVpj1KIdWERILmCJa3nxLk2iuY y6RKujmBXdbszBp4QZPL568Y0X90DldHqG3Jpdm1J1ChW+c3RoA4tQUbw9uQjev+NxBj weaFeYmVZo1noRywlpJnif6vsiEjcG/TbGo+C3TE5ljEK4/qlDkyYf8asmDUAEJHjm8u qN/Q== X-Gm-Message-State: AOUpUlGDOmeRWegCWsoV9aZVQvz7g5Y2OeKfZuVsX4sLg2kgxP7FjRRd lzA6ymDNXSBInq8SxmP3ATxLsw== X-Received: by 2002:a5d:41c1:: with SMTP id e1-v6mr21218627wrq.25.1533053622395; Tue, 31 Jul 2018 09:13:42 -0700 (PDT) Received: from localhost.localdomain ([212.45.67.2]) by smtp.googlemail.com with ESMTPSA id t186-v6sm3643457wmf.14.2018.07.31.09.13.40 (version=TLS1_2 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Tue, 31 Jul 2018 09:13:41 -0700 (PDT) From: Georgi Djakov To: linux-pm@vger.kernel.org, gregkh@linuxfoundation.org Cc: rjw@rjwysocki.net, robh+dt@kernel.org, mturquette@baylibre.com, khilman@baylibre.com, vincent.guittot@linaro.org, skannan@codeaurora.org, bjorn.andersson@linaro.org, amit.kucheria@linaro.org, seansw@qti.qualcomm.com, daidavid1@codeaurora.org, evgreen@chromium.org, mark.rutland@arm.com, lorenzo.pieralisi@arm.com, abailon@baylibre.com, arnd@arndb.de, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-arm-msm@vger.kernel.org, georgi.djakov@linaro.org Subject: [PATCH v7 0/8] Introduce on-chip interconnect API Date: Tue, 31 Jul 2018 19:13:32 +0300 Message-Id: <20180731161340.13000-1-georgi.djakov@linaro.org> X-Mailer: git-send-email 2.18.0 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Modern SoCs have multiple processors and various dedicated cores (video, gpu, graphics, modem). These cores are talking to each other and can generate a lot of data flowing through the on-chip interconnects. These interconnect buses could form different topologies such as crossbar, point to point buses, hierarchical buses or use the network-on-chip concept. These buses have been sized usually to handle use cases with high data throughput but it is not necessary all the time and consume a lot of power. Furthermore, the priority between masters can vary depending on the running use case like video playback or CPU intensive tasks. Having an API to control the requirement of the system in terms of bandwidth and QoS, so we can adapt the interconnect configuration to match those by scaling the frequencies, setting link priority and tuning QoS parameters. This configuration can be a static, one-time operation done at boot for some platforms or a dynamic set of operations that happen at run-time. This patchset introduce a new API to get the requirement and configure the interconnect buses across the entire chipset to fit with the current demand. The API is NOT for changing the performance of the endpoint devices, but only the interconnect path in between them. The API is using a consumer/provider-based model, where the providers are the interconnect buses and the consumers could be various drivers. The consumers request interconnect resources (path) to an endpoint and set the desired constraints on this data flow path. The provider(s) receive requests from consumers and aggregate these requests for all master-slave pairs on that path. Then the providers configure each participating in the topology node according to the requested data flow path, physical links and constraints. The topology could be complicated and multi-tiered and is SoC specific. Below is a simplified diagram of a real-world SoC topology. The interconnect providers are the NoCs. +----------------+ +----------------+ | HW Accelerator |--->| M NoC |<---------------+ +----------------+ +----------------+ | | | +------------+ +-----+ +-------------+ V +------+ | | | DDR | | +--------+ | PCIe | | | +-----+ | | Slaves | +------+ | | ^ ^ | +--------+ | | C NoC | | | V V | | +------------------+ +------------------------+ | | +-----+ | |-->| |-->| |-->| CPU | | |-->| |<--| | +-----+ | Mem NoC | | S NoC | +------------+ | |<--| |---------+ | | |<--| |<------+ | | +--------+ +------------------+ +------------------------+ | | +-->| Slaves | ^ ^ ^ ^ ^ | | +--------+ | | | | | | V +------+ | +-----+ +-----+ +---------+ +----------------+ +--------+ | CPUs | | | GPU | | DSP | | Masters |-->| P NoC |-->| Slaves | +------+ | +-----+ +-----+ +---------+ +----------------+ +--------+ | +-------+ | Modem | +-------+ TODO: * Create icc_set_extended() to handle parameters such as latency and other QoS values. * Convert from using global node identifiers to local per provider ids. * Cache the path between the nodes instead of walking the graph on each get(). * Sync interconnect requests with the idle state of the device. Changes since patchset v6 (https://lkml.org/lkml/2018/7/9/698) * [patches 1,6]: Move the aggregation within the provider from the framework to the platform driver's set() callback, as the aggregation point could be SoC specific. * [patch 1]: Include missing header, reset state only of the traversed nodes, move more code into path_init(), add more asserts, move misplaced mutex, simplify icc_link_destroy() (Evan) * [patch 1]: Fix the order of requests to go from source to destination. (Alex) * [patch 7]: Use better wording in the documentation. (Evan) * [patch 6]: Reorder struct members, sort nodes alphabetically, improve naming of variables , add missing clk_disable_unprepare() in error paths. (Matthias) * [patch 6]: Remove redundant NULL pointer check in msm8916 driver. (Alex) * [patch 6]: Add missing depend on QCOM_SMD_RPM in Kconfig. (Evan) * [patch 3]: Don't check for errors on debugfs calls, remove debugfs directory when module is unloaded (Greg) Changes since patchset v5 (https://lkml.org/lkml/2018/6/20/453) * Fix the modular build, make rpm-smd driver a module. * Optimize locking and move to higher level. (Evan) * Code cleanups. Fix typos. (Evan, Matthias) * Add the source node to the path. (Evan) * Rename path_allocate() to path_init() with minor refactoring. (Evan) * Rename *_remove() functions to *_destroy(). * Return fixed errors in icc_link_destroy(). (Evan) * Fix krealloc() usage in icc_link_destroy(). (Evan) * Add missing kfree() in icc_node_create(). (Matthias) * Make icc_node_add() return void. (Matthias) * Change mutex_init to mutex_lock in icc_provider_add(). (Matthias) * Add new icc_node_del() function to delete nodes from provider. * Fix the header guard to reflect the path in smd-rpm.h. (Evan) * Check for errors returned by qcom_icc_rpm_smd_send(). (Evan) * Propagate the error of icc_provider_del(). (Evan) Changes since patchset v4 (https://lkml.org/lkml/2018/3/9/856) * Simplified locking by using a single global mutex. (Evan) * Changed the aggregation function interface. * Implemented functions for node, link, provider removal. (Evan) * Naming changes on variables and functions, removed redundant code. (Evan) * Fixes and clarifications in the docs. (Matthias, Evan, Amit, Alexandre) * Removed mandatory reg DT property, made interconnect-names optional. (Bjorn) * Made interconnect-cells property required to align with other bindings. (Neil) * Moved msm8916 specific bindings into a separate file and patch. (Bjorn) * Use the names, instead of the hardcoded ids for topology. (Matthias) * Init the node before creating the links. (Evan) * Added icc_units_to_bps macro. (Amit) Changes since patchset v3 (https://lkml.org/lkml/2017/9/8/544) * Refactored the constraints aggregation. * Use the IDR API. * Split the provider and consumer bindings into separate patches and propose new bindings for consumers, which allows to specify the local source port. * Adopted the icc_ prefix for API functions. * Introduced separate API functions for creating interconnect nodes and links. * Added DT lookup support in addition to platform data. * Dropped the event tracing patch for now. * Added a patch to provide summary via debugfs. * Use macro for the list of topology definitions in the platform driver. * Various minor changes. Changes since patchset v2 (https://lkml.org/lkml/2017/7/20/825) * Split the aggregation into per node and per provider. Cache the aggregated values. * Various small refactorings and cleanups in the framework. * Added a patch introducing basic tracepoint support for monitoring the time required to update the interconnect nodes. Changes since patchset v1 (https://lkml.org/lkml/2017/6/27/890) * Updates in the documentation. * Changes in request aggregation, locking. * Dropped the aggregate() callback and use the default as it currently sufficient for the single vendor driver. Will add it later when needed. * Dropped the dt-bindings draft patch for now. Changes since RFC v2 (https://lkml.org/lkml/2017/6/12/316) * Converted documentation to rst format. * Fixed an incorrect call to mutex_lock. Renamed max_bw to peak_bw. Changes since RFC v1 (https://lkml.org/lkml/2017/5/15/605) * Refactored code into shorter functions. * Added a new aggregate() API function. * Rearranged some structs to reduce padding bytes. Changes since RFC v0 (https://lkml.org/lkml/2017/3/1/599) * Removed DT support and added optional Patch 3 with new bindings proposal. * Converted the topology into internal driver data. * Made the framework modular. * interconnect_get() now takes (src and dst ports as arguments). * Removed public declarations of some structs. * Now passing prev/next nodes to the vendor driver. * Properly remove requests on _put(). * Added refcounting. * Updated documentation. * Changed struct interconnect_path to use array instead of linked list. Georgi Djakov (8): interconnect: Add generic on-chip interconnect API dt-bindings: Introduce interconnect provider bindings interconnect: Add debugfs support interconnect: qcom: Add RPM communication dt-bindings: interconnect: Document qcom,msm8916 NoC bindings interconnect: qcom: Add msm8916 interconnect provider driver dt-bindings: Introduce interconnect consumers bindings interconnect: Allow endpoints translation via DT .../bindings/interconnect/interconnect.txt | 60 ++ .../bindings/interconnect/qcom-msm8916.txt | 39 + .../bindings/interconnect/qcom-smd.txt | 32 + Documentation/interconnect/interconnect.rst | 96 +++ drivers/Kconfig | 2 + drivers/Makefile | 1 + drivers/interconnect/Kconfig | 15 + drivers/interconnect/Makefile | 3 + drivers/interconnect/core.c | 709 ++++++++++++++++++ drivers/interconnect/qcom/Kconfig | 23 + drivers/interconnect/qcom/Makefile | 4 + drivers/interconnect/qcom/msm8916.c | 510 +++++++++++++ drivers/interconnect/qcom/smd-rpm.c | 91 +++ drivers/interconnect/qcom/smd-rpm.h | 16 + include/dt-bindings/interconnect/qcom.h | 187 +++++ include/linux/interconnect-provider.h | 125 +++ include/linux/interconnect.h | 49 ++ 17 files changed, 1962 insertions(+) create mode 100644 Documentation/devicetree/bindings/interconnect/interconnect.txt create mode 100644 Documentation/devicetree/bindings/interconnect/qcom-msm8916.txt create mode 100644 Documentation/devicetree/bindings/interconnect/qcom-smd.txt create mode 100644 Documentation/interconnect/interconnect.rst create mode 100644 drivers/interconnect/Kconfig create mode 100644 drivers/interconnect/Makefile create mode 100644 drivers/interconnect/core.c create mode 100644 drivers/interconnect/qcom/Kconfig create mode 100644 drivers/interconnect/qcom/Makefile create mode 100644 drivers/interconnect/qcom/msm8916.c create mode 100644 drivers/interconnect/qcom/smd-rpm.c create mode 100644 drivers/interconnect/qcom/smd-rpm.h create mode 100644 include/dt-bindings/interconnect/qcom.h create mode 100644 include/linux/interconnect-provider.h create mode 100644 include/linux/interconnect.h