linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bhaumik Bhatt <bbhatt@codeaurora.org>
To: manivannan.sadhasivam@linaro.org
Cc: linux-arm-msm@vger.kernel.org, hemantk@codeaurora.org,
	jhugo@codeaurora.org, linux-kernel@vger.kernel.org,
	carl.yin@quectel.com, naveen.kumar@quectel.com,
	loic.poulain@linaro.org, Bhaumik Bhatt <bbhatt@codeaurora.org>
Subject: [PATCH v1 0/4] MHI event ring priority updates
Date: Thu, 17 Jun 2021 14:30:31 -0700	[thread overview]
Message-ID: <1623965435-30224-1-git-send-email-bbhatt@codeaurora.org> (raw)

Event ring priorities have remained out of use and are set to 1 by default.
This series brings about an enum entry expanding use of the priority field by
adding high priority tasklet scheduling to the menu.

In some cases, tasklet scheduling delays can be a nuisance. An example would be
ath11k adding a610f3c65d3b ("bus: mhi: Wait for M2 state during system resume")
in response to it. This issue can be potentially avoided if the controller uses
a dedicated event ring for control packets with high priority tasklet scheduling
in place.

There are no functional changes added to the controller (pci_generic or ath11k)
drivers with this series and the only changes there are use of the enum in place
of a harcoded value of "1". In the future, controllers can opt in to have any
event ring scheduled in high priority.

Tested on: X86_64 architecture with SDX65 on Ubuntu 18.04 distribution.

Bhaumik Bhatt (3):
  bus: mhi: pci_generic: Use enum entry for event ring priority
  ath11k: Use enum entry for event ring priority
  bus: mhi: core: Enable support for event ring priorities

Hemant Kumar (1):
  bus: mhi: core: Add support for processing priority of event ring

 drivers/bus/mhi/core/init.c           |  3 +-
 drivers/bus/mhi/core/internal.h       |  2 +-
 drivers/bus/mhi/core/main.c           | 19 ++++++++--
 drivers/bus/mhi/pci_generic.c         | 66 +++++++++++++++++------------------
 drivers/net/wireless/ath/ath11k/mhi.c |  4 +--
 include/linux/mhi.h                   | 14 ++++++--
 6 files changed, 65 insertions(+), 43 deletions(-)

-- 
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project


             reply	other threads:[~2021-06-17 21:31 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-17 21:30 Bhaumik Bhatt [this message]
2021-06-17 21:30 ` [PATCH v1 1/4] bus: mhi: core: Add support for processing priority of event ring Bhaumik Bhatt
2021-06-18  7:03   ` Manivannan Sadhasivam
2021-06-18 17:17     ` Bhaumik Bhatt
2021-06-18 17:31       ` Manivannan Sadhasivam
2021-06-18 17:43         ` Bhaumik Bhatt
2021-06-17 21:30 ` [PATCH v1 2/4] bus: mhi: pci_generic: Use enum entry for event ring priority Bhaumik Bhatt
2021-06-17 22:21   ` Hemant Kumar
2021-06-17 21:30 ` [PATCH v1 3/4] ath11k: " Bhaumik Bhatt
2021-06-17 21:30 ` [PATCH v1 4/4] bus: mhi: core: Enable support for event ring priorities Bhaumik Bhatt
2021-06-17 22:20   ` Hemant Kumar

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1623965435-30224-1-git-send-email-bbhatt@codeaurora.org \
    --to=bbhatt@codeaurora.org \
    --cc=carl.yin@quectel.com \
    --cc=hemantk@codeaurora.org \
    --cc=jhugo@codeaurora.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=loic.poulain@linaro.org \
    --cc=manivannan.sadhasivam@linaro.org \
    --cc=naveen.kumar@quectel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).