All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vinod Koul <vkoul@kernel.org>
To: Bjorn Andersson <bjorn.andersson@linaro.org>
Cc: Andy Gross <agross@kernel.org>, Ohad Ben-Cohen <ohad@wizery.com>,
	Baolin Wang <baolin.wang7@gmail.com>,
	Rob Herring <robh+dt@kernel.org>,
	linux-arm-msm@vger.kernel.org, linux-remoteproc@vger.kernel.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/4] dt-bindings: hwlock: qcom: Allow device on mmio bus
Date: Thu, 14 May 2020 19:49:21 +0530	[thread overview]
Message-ID: <20200514141921.GY14092@vkoul-mobl> (raw)
In-Reply-To: <20200513005441.1102586-3-bjorn.andersson@linaro.org>

On 12-05-20, 17:54, Bjorn Andersson wrote:
> In all modern Qualcomm platforms the mutex region of the TCSR is forked
> off into its own block, all with a offset of 0 and stride of 4096.
> Update the binding to allow the hardware block to be described directly
> on the mmio bus, in addition to allowing the existing syscon based
> definition.

Reviewed-by: Vinod Koul <vkoul@kernel.org>

-- 
~Vinod

  reply	other threads:[~2020-05-14 14:19 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-13  0:54 [PATCH 0/4] hwspinlock: qcom: Allow dropping the intermediate TCSR mutex syscon Bjorn Andersson
2020-05-13  0:54 ` [PATCH 1/4] dt-bindings: hwlock: qcom: Migrate binding to YAML Bjorn Andersson
2020-05-14 14:19   ` Vinod Koul
2020-05-27 19:31   ` Rob Herring
2020-05-13  0:54 ` [PATCH 2/4] dt-bindings: hwlock: qcom: Allow device on mmio bus Bjorn Andersson
2020-05-14 14:19   ` Vinod Koul [this message]
2020-05-13  0:54 ` [PATCH 3/4] hwspinlock: qcom: Allow mmio usage in addition to syscon Bjorn Andersson
2020-05-13  3:57   ` Baolin Wang
2020-05-14 17:06     ` Bjorn Andersson
2020-05-14 14:15   ` Vinod Koul
2020-05-14 17:00     ` Bjorn Andersson
2020-05-14 17:32       ` Vinod Koul
2020-05-13  0:54 ` [PATCH 4/4] arm64: dts: qcom: sm8250: Drop tcsr_mutex syscon Bjorn Andersson
2020-05-14 14:19   ` Vinod Koul

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=20200514141921.GY14092@vkoul-mobl \
    --to=vkoul@kernel.org \
    --cc=agross@kernel.org \
    --cc=baolin.wang7@gmail.com \
    --cc=bjorn.andersson@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-remoteproc@vger.kernel.org \
    --cc=ohad@wizery.com \
    --cc=robh+dt@kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.