From: Sinan Kaya <okaya@codeaurora.org>
To: Rob Herring <robh@kernel.org>
Cc: dmaengine@vger.kernel.org, timur@codeaurora.org,
devicetree@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Vinod Koul <vinod.koul@intel.com>,
Mark Rutland <mark.rutland@arm.com>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH V5 1/7] Documentation: DT: qcom_hidma: Bump HW revision for the bugfixed HW
Date: Tue, 5 Dec 2017 12:13:06 -0500 [thread overview]
Message-ID: <61d54e4c-5ec9-441e-07bf-598204d772c6@codeaurora.org> (raw)
In-Reply-To: <20171204221414.f5tphhn7gvlle3li@rob-hp-laptop>
On 12/4/2017 5:14 PM, Rob Herring wrote:
> Hopefully 1.2 corresponds to some actual version numbering and not just
> something you made up. I'd really rather have SoC based compatible
> strings unless you have dozens of SoCs for each version. I'll probably
> just say the same thing again when 1.3 or 2.0 gets added...
>
No, these are coming from the HW. They are user visible.
[ 107.167207] hidma-mgmt QCOM8060:00: HW rev: 1.2 @ 0x0000ffff8b800000 with 6 physical channels
> Reviewed-by: Rob Herring <robh@kernel.org>
Thanks
--
Sinan Kaya
Qualcomm Datacenter Technologies, Inc. as an affiliate of Qualcomm Technologies, Inc.
Qualcomm Technologies, Inc. is a member of the Code Aurora Forum, a Linux Foundation Collaborative Project.
next prev parent reply other threads:[~2017-12-05 17:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1512188864-773-1-git-send-email-okaya@codeaurora.org>
2017-12-02 4:27 ` Sinan Kaya
2017-12-04 22:14 ` Rob Herring
2017-12-05 17:13 ` Sinan Kaya [this message]
2017-12-02 4:27 ` [PATCH V5 2/7] ACPI / bus: Introduce acpi_get_match_data() function Sinan Kaya
2017-12-04 21:59 ` Rafael J. Wysocki
2017-12-04 22:01 ` Sinan Kaya
2017-12-02 4:27 ` [PATCH V5 3/7] device property: Introduce a common API to fetch device match data Sinan Kaya
2017-12-02 4:27 ` [PATCH V5 4/7] OF: properties: Implement get_match_data() callback Sinan Kaya
2017-12-04 16:23 ` Rob Herring
2017-12-04 18:05 ` Sinan Kaya
2017-12-04 22:25 ` Rob Herring
2017-12-02 4:27 ` [PATCH V5 5/7] ACPI: " Sinan Kaya
2017-12-02 4:27 ` [PATCH V5 6/7] dmaengine: qcom_hidma: Add support for the new revision Sinan Kaya
2017-12-02 4:27 ` [PATCH V5 7/7] dmaengine: qcom_hidma: Add identity register support Sinan Kaya
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=61d54e4c-5ec9-441e-07bf-598204d772c6@codeaurora.org \
--to=okaya@codeaurora.org \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh@kernel.org \
--cc=timur@codeaurora.org \
--cc=vinod.koul@intel.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
Powered by JetHome