Received: by 10.223.185.111 with SMTP id b44csp761676wrg; Fri, 9 Mar 2018 13:13:53 -0800 (PST) X-Google-Smtp-Source: AG47ELt5380L87QQ7XiqcoY+YtM1CZX9Wwlabe9lqAvHpsWRZD6c8B/w+c8awSPVePWy3oZsD6Sy X-Received: by 10.98.75.18 with SMTP id y18mr31539118pfa.124.1520630033510; Fri, 09 Mar 2018 13:13:53 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1520630033; cv=none; d=google.com; s=arc-20160816; b=S6PE7/MM95TQ042rCBuD6ESVBe3IMq9+/diD6A7yYuPwNc8KYN/Zk9DjpYJoxg1NrE ldRnWFo7mPlTt3m8T6UNVV43UjbEs18pGrva/Q/ktu+cj7ZX3pMnTvpY0LnXvkbFpgva LRWQNNA6gRynMV0C4lHqixcGElizrKa4WwQQ6eJmaaodpIjOgCTim03NDxyWRxRz8/Er Nk3HoKPMQ6D7nFCt8H23oJPdFk3U4WXiYWmudeHYULZveAIvmijiaS9s+SU8N0TQQgte m4LLIyoFtrpRoKc4L7D2qLnLXwBAsua/+x5reeEgLbXkE5XIVYYbQ98dXpqNHYB9YPxX 4KxQ== 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=c2tTM+18yJuLazLFw8tp9zidIdNr8+QuQ2lRk4Q3kMw=; b=GpYo/oXUFHrM6Va19fqLwRoYLICn6rJzIhJFmC7x99E1Rhf8RAJLOOAao1T5smv4yQ 4IyuHLeC9gDPlBZxibYwZvJZGBTUe5F2Gfs5O8vsDtKVrqXTzrI64GQQLfB6F+WxDlF4 of2FRs3nKk1ziM5mnOzby0flA4UMH8oEynSP+VEw4itCRT62vLNvx4wVrM7Y6/M5XWRg rvJL+vVybB8X24JvJjRQhw3o/Nmg+w7g3j2cmqlbCkLMeLNxIjBA+pLu8ODFh2+aZBNH 9m0bkRx/DVatS2J3xJxfYMwq/kPyRuNQmxf/r4JPyUReYJE0Anl4WPInF1k0UNyldwLv 5WFA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=ItiOOHGY; 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 t64si1248170pgd.620.2018.03.09.13.13.39; Fri, 09 Mar 2018 13:13:53 -0800 (PST) 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=ItiOOHGY; 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 S932556AbeCIVKF (ORCPT + 99 others); Fri, 9 Mar 2018 16:10:05 -0500 Received: from mail-wr0-f179.google.com ([209.85.128.179]:45107 "EHLO mail-wr0-f179.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932288AbeCIVKC (ORCPT ); Fri, 9 Mar 2018 16:10:02 -0500 Received: by mail-wr0-f179.google.com with SMTP id h2so2967137wre.12 for ; Fri, 09 Mar 2018 13:10:01 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=from:to:cc:subject:date:message-id; bh=c2tTM+18yJuLazLFw8tp9zidIdNr8+QuQ2lRk4Q3kMw=; b=ItiOOHGYxe/gk8vYu0eQdIKosGBCgC09TjVLOFYYqAQ0Hb/jPYoQp86meYh0xVwpcV uRjsthdQvoQtob43ai1TM4B/hVu5Nv8gOI56DkhgDEX4n3zfD83rr4bWM6MG0freTWfj e8nTLPVikfU1VbfHwHFyLJWu2/7bBssh7vzjk= 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=c2tTM+18yJuLazLFw8tp9zidIdNr8+QuQ2lRk4Q3kMw=; b=LRqOyDtpSNu/IgVrQWRhr/Zt8uracgkS+0XKUkPbqQvpWJWfUHUQ5P9bVmR7/pxtSt 0V9ME8z6TSkYsu+9CEr0vNtW4oZyL75c6RRDaF7qH/MbLdeEEyKcSllTI/Z/IXKNMby6 5MbyEiEk534KQB5gU4fh+989dkhs1ElW6jjeIbZmWJ0FGJpY3kReFhEXcFzNCNvwjmpp gJa61hlawnPhosngXWYOY5kRThddiEBvg8ShW5dZ5tWSmStxCrzz9YkSf9/aa8jrBaG8 i+yBI+epTetnH7pQ0iG5AZc1KnrvCNvUIiGjc87PkwPl4S4SsKMPKqTnsLgxhDhKoiR5 SD4Q== X-Gm-Message-State: APf1xPCmvFgcIODmxt4VrjzrXzFuPIcNTc56AAMFpGfY7OpmYJXPyGTM bjdbfOXiHuIelviiMP0esMiRtw== X-Received: by 10.223.175.44 with SMTP id z41mr25521217wrc.129.1520629800864; Fri, 09 Mar 2018 13:10:00 -0800 (PST) Received: from mms-0441.qualcomm.mm-sol.com ([212.45.67.2]) by smtp.googlemail.com with ESMTPSA id g7sm1853118wrb.78.2018.03.09.13.09.59 (version=TLS1_2 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Fri, 09 Mar 2018 13:10:00 -0800 (PST) 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, davidai@quicinc.com, mark.rutland@arm.com, lorenzo.pieralisi@arm.com, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-arm-msm@vger.kernel.org, georgi.djakov@linaro.org Subject: [PATCH v4 0/7] Introduce on-chip interconnect API Date: Fri, 9 Mar 2018 23:09:51 +0200 Message-Id: <20180309210958.16672-1-georgi.djakov@linaro.org> X-Mailer: git-send-email 2.16.2 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 term 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 identifiers. * 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 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 (7): interconnect: Add generic on-chip interconnect API dt-bindings: Introduce interconnect provider bindings interconnect: Add debugfs support interconnect: qcom: Add RPM communication interconnect: qcom: Add msm8916 interconnect provider driver dt-bindings: Introduce interconnect consumers bindings interconnect: Allow endpoints translation via DT .../bindings/interconnect/interconnect.txt | 70 +++ .../devicetree/bindings/interconnect/qcom-smd.txt | 31 ++ Documentation/interconnect/interconnect.rst | 96 ++++ drivers/Kconfig | 2 + drivers/Makefile | 1 + drivers/interconnect/Kconfig | 15 + drivers/interconnect/Makefile | 2 + drivers/interconnect/core.c | 597 +++++++++++++++++++++ drivers/interconnect/qcom/Kconfig | 11 + drivers/interconnect/qcom/Makefile | 3 + drivers/interconnect/qcom/msm8916.c | 482 +++++++++++++++++ drivers/interconnect/qcom/smd-rpm.c | 90 ++++ drivers/interconnect/qcom/smd-rpm.h | 15 + include/linux/interconnect-provider.h | 109 ++++ include/linux/interconnect.h | 46 ++ include/linux/interconnect/qcom.h | 350 ++++++++++++ 16 files changed, 1920 insertions(+) create mode 100644 Documentation/devicetree/bindings/interconnect/interconnect.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/linux/interconnect-provider.h create mode 100644 include/linux/interconnect.h create mode 100644 include/linux/interconnect/qcom.h