From: Julien Grall <julien.grall@arm.com>
To: Ian Jackson <ian.jackson@citrix.com>, Stephen Boyd <swboyd@chromium.org>
Cc: Andy Gross <agross@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-msm@vger.kernel.org" <linux-arm-msm@vger.kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Avaneesh Kumar Dwivedi <akdwived@codeaurora.org>
Subject: Re: [PATCH 1/3] firmware: qcom_scm: Use proper types for dma mappings
Date: Mon, 20 May 2019 14:20:06 +0100 [thread overview]
Message-ID: <c78c372a-4cf4-9721-38f2-d173eecee27e@arm.com> (raw)
In-Reply-To: <23778.30265.117488.781364@mariner.uk.xensource.com>
Hi Ian,
On 20/05/2019 10:41, Ian Jackson wrote:
> Stephen Boyd writes ("[PATCH 1/3] firmware: qcom_scm: Use proper types for dma mappings"):
>> We need to use the proper types and convert between physical addresses
>> and dma addresses here to avoid mismatch warnings. This is especially
>> important on systems with a different size for dma addresses and
>> physical addresses. Otherwise, we get the following warning:
>
> Thanks. Do you expect this to be a backport candidate and if so how
> far back do you think it will go ? To be honest, I am not really
> convinced that backporting this would be a service to users. The
> situation I have, where I changed the compiler but kept the old kernel
> code and old configuration, is going to be fairly rare.
I will leave the maintainers answering to that.
>
> I think I should probably therefore disable this driver in the config
> on stable branches of Linux, at least.
If we decide to disable the driver, then we would need to add in our .config,
then we would need to disable completely the support for Qualcomm (i.e
CONFIG_ARCH_QCOM=n) on Arm32.
This should not be an issue in osstest as we don't test any qualcomm board so far.
Cheers,
--
Julien Grall
next prev parent reply other threads:[~2019-05-20 13:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <osstest-135420-mainreport@xen.org>
[not found] ` <23752.17186.527512.614163@mariner.uk.xensource.com>
2019-04-30 14:06 ` qcom_scm: Incompatible pointer type build failure Julien Grall
2019-04-30 14:06 ` Julien Grall
2019-05-17 16:10 ` Ian Jackson
2019-05-17 21:09 ` [PATCH 0/3] qcom_scm: Fix some dma mapping things Stephen Boyd
2019-05-17 21:09 ` [PATCH 1/3] firmware: qcom_scm: Use proper types for dma mappings Stephen Boyd
2019-05-20 9:41 ` Ian Jackson
2019-05-20 13:20 ` Julien Grall [this message]
2019-05-30 16:51 ` [OSSTEST PATCH] ts-kernel-build: Disable CONFIG_ARCH_QCOM in Xen Project CI Ian Jackson
2019-05-31 15:52 ` Julien Grall
2019-05-17 21:09 ` [PATCH 2/3] firmware: qcom_scm: Cleanup code in qcom_scm_assign_mem() Stephen Boyd
2019-07-22 23:27 ` Bjorn Andersson
2019-07-23 0:04 ` Stephen Boyd
2019-07-23 0:21 ` Bjorn Andersson
2019-05-17 21:09 ` [PATCH 3/3] firmware: qcom_scm: Fix some typos in docs and printks Stephen Boyd
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=c78c372a-4cf4-9721-38f2-d173eecee27e@arm.com \
--to=julien.grall@arm.com \
--cc=agross@kernel.org \
--cc=akdwived@codeaurora.org \
--cc=bjorn.andersson@linaro.org \
--cc=ian.jackson@citrix.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=swboyd@chromium.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 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).