| Age | Commit message (Collapse) | Author |
|---|
|
integration-linux-qcomlt
|
|
integration-linux-qcomlt
|
|
integration-linux-qcomlt
|
|
'qcs404-defconfig/tracking-qcomlt-qcs404-defconfig' into integration-linux-qcomlt
# Conflicts:
# arch/arm64/configs/defconfig
|
|
into integration-linux-qcomlt
|
|
integration-linux-qcomlt
# Conflicts:
# drivers/clk/qcom/Kconfig
# drivers/clk/qcom/clk-krait.c
|
|
integration-linux-qcomlt
# Conflicts:
# drivers/regulator/Kconfig
# drivers/regulator/Makefile
|
|
into integration-linux-qcomlt
|
|
integration-linux-qcomlt
# Conflicts:
# arch/arm64/boot/dts/qcom/msm8916.dtsi
# arch/arm64/boot/dts/qcom/msm8996.dtsi
|
|
integration-linux-qcomlt
|
|
|
|
integration-linux-qcomlt
# Conflicts:
# arch/arm64/boot/dts/qcom/apq8096-db820c.dtsi
# arch/arm64/boot/dts/qcom/msm8996.dtsi
# arch/arm64/boot/dts/qcom/sdm845.dtsi
|
|
integration-linux-qcomlt
|
|
'distro.config/tracking-qcomlt-config-fragments' into integration-linux-qcomlt
|
|
'arm64-defconfig/tracking-qcomlt-arm64-defconfig' into integration-linux-qcomlt
|
|
integration-linux-qcomlt
|
|
integration-linux-qcomlt
|
|
'fixes/tracking-qcomlt-fixes-without-devfreq-reverts' into integration-linux-qcomlt
|
|
integration-linux-qcomlt
|
|
integration-linux-qcomlt
# Conflicts:
# arch/arm64/boot/dts/qcom/msm8996.dtsi
|
|
integration-linux-qcomlt
|
|
integration-linux-qcomlt
|
|
Add support for wake and sleep commands by using a tag to indicate
whether or not the aggregate and set requests are active only or
dual context for a particular path.
Signed-off-by: David Dai <daidavid1@codeaurora.org>
Signed-off-by: Georgi Djakov <georgi.djakov@linaro.org>
|
|
Consumers may have use cases with different bandwidth requirements based on
the system or driver state. The consumer driver can append a specific tag to
the path and pass this information to the interconnect platform driver to do
the aggregation based on this state.
Introduce set_path_tag() function that will allow the consumers to optionally
append tag to each path. The aggregation of these tagged paths is platoform
specific.
Signed-off-by: Georgi Djakov <georgi.djakov@linaro.org>
|
|
Signed-off-by: Georgi Djakov <georgi.djakov@linaro.org>
|
|
Signed-off-by: Georgi Djakov <georgi.djakov@linaro.org>
|
|
Signed-off-by: Georgi Djakov <georgi.djakov@linaro.org>
|
|
Add driver for the Qualcomm interconnect buses found in msm8916
based platforms.
Signed-off-by: Georgi Djakov <georgi.djakov@linaro.org>
|
|
Add the network-on-chip interconnect buses found on msm8916/apq8016-based
platforms as interconnect providers.
Signed-off-by: Georgi Djakov <georgi.djakov@linaro.org>
|
|
Signed-off-by: Georgi Djakov <georgi.djakov@linaro.org>
|
|
Add driver for the Qualcomm interconnect buses found in msm8916 based
platforms.
Signed-off-by: Georgi Djakov <georgi.djakov@linaro.org>
|
|
On some Qualcomm SoCs, there is a remote processor, which controls some of
the Network-On-Chip interconnect resources. Other CPUs express their needs
by communicating with this processor. Add a driver to handle communication
with this remote processor.
Signed-off-by: Georgi Djakov <georgi.djakov@linaro.org>
|
|
Add myself as the maintainer of the interconnect API.
Signed-off-by: Georgi Djakov <georgi.djakov@linaro.org>
|
|
Add RSC (Resource State Coordinator) provider
dictating network-on-chip interconnect bus performance
found on SDM845-based platforms.
Signed-off-by: David Dai <daidavid1@codeaurora.org>
Signed-off-by: Georgi Djakov <georgi.djakov@linaro.org>
|
|
Introduce Qualcomm SDM845 specific provider driver using the
interconnect framework.
Signed-off-by: David Dai <daidavid1@codeaurora.org>
Signed-off-by: Georgi Djakov <georgi.djakov@linaro.org>
|
|
Add a functionality to provide information about the current constraints
per each node and provider.
Signed-off-by: Georgi Djakov <georgi.djakov@linaro.org>
|
|
Currently we support only platform data for specifying the interconnect
endpoints. As now the endpoints are hard-coded into the consumer driver
this may lead to complications when a single driver is used by multiple
SoCs, which may have different interconnect topology.
To avoid cluttering the consumer drivers, introduce a translation function
to help us get the board specific interconnect data from device-tree.
Signed-off-by: Georgi Djakov <georgi.djakov@linaro.org>
|
|
This binding is intended to represent the relations between the interconnect
controllers (providers) and consumer device nodes. It will allow creating links
between consumers and interconnect paths (exposed by interconnect providers).
Signed-off-by: Georgi Djakov <georgi.djakov@linaro.org>
|
|
This patch introduces a new API to get requirements and configure the
interconnect buses across the entire chipset to fit with the current
demand.
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) between endpoints and
set the desired constraints on this data flow path. The providers receive
requests from consumers and aggregate these requests for all master-slave
pairs on that path. Then the providers configure each node along the path
to support a bandwidth that satisfies all bandwidth requests that cross
through that node. The topology could be complicated and multi-tiered and
is SoC specific.
Signed-off-by: Georgi Djakov <georgi.djakov@linaro.org>
|
|
Signed-off-by: Georgi Djakov <georgi.djakov@linaro.org>
|
|
Signed-off-by: Georgi Djakov <georgi.djakov@linaro.org>
|
|
The interconnect API provides an interface for consumer drivers to express
their bandwidth needs in the SoC. This data is aggregated and the on-chip
interconnect hardware is configured to the most appropriate power/performance
profile.
Use the interconnect API to get() the path between the endpoints used for
data transfers by the SD host controller and report the needed bandwidth based
on the clock rate, bus width and mode.
Signed-off-by: Georgi Djakov <georgi.djakov@linaro.org>
|
|
Signed-off-by: Georgi Djakov <georgi.djakov@linaro.org>
|
|
Signed-off-by: Georgi Djakov <georgi.djakov@linaro.org>
|
|
The interconnect API provides an interface for consumer drivers to express
their bandwidth needs. This data is then aggregated and the interconnect
hardware is configured to the most appropriate power/performance profile.
Use the interconnect API to get() the path between the endpoints used for
data transfers by the I2C QUP and report the needed bandwidth.
Signed-off-by: Georgi Djakov <georgi.djakov@linaro.org>
|
|
Signed-off-by: Georgi Djakov <georgi.djakov@linaro.org>
|
|
Signed-off-by: Georgi Djakov <georgi.djakov@linaro.org>
|
|
Signed-off-by: Georgi Djakov <georgi.djakov@linaro.org>
|
|
Signed-off-by: Georgi Djakov <georgi.djakov@linaro.org>
|
|
Signed-off-by: Georgi Djakov <georgi.djakov@linaro.org>
|
