From: Sudeep Holla <sudeep.holla@arm.com>
To: "Christian Marangi (Ansuel)" <ansuelsmth@gmail.com>
Cc: Ulf Hansson <ulf.hansson@linaro.org>,
kernel test robot <lkp@intel.com>,
Sudeep Holla <sudeep.holla@arm.com>,
llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: Re: [linux-next:master 9185/10024] drivers/pmdomain/mediatek/airoha-cpu-pmdomain.c:59:2: error: write to reserved register 'R7'
Date: Mon, 20 Jan 2025 15:35:37 +0000 [thread overview]
Message-ID: <Z45tSadT6TxsuD_h@bogus> (raw)
In-Reply-To: <CA+_ehUyVH5r5LK5B2tKZgH_dR69OVaV-ES7+GPShNuJCWEXHVA@mail.gmail.com>
On Mon, Jan 20, 2025 at 04:28:08PM +0100, Christian Marangi (Ansuel) wrote:
>
> Honestly I will revert back and use the basic arm_smccc_smc. I don't really like
> the fix in the makefile and I think it should be handled in a more
> generic way for any user of arm_smccc_1_1_invoke.
You can use arm_smccc_smc() or arm_smccc_hvc() if that works for you.
If the system supports SMCCC v1.1+, then arm_smccc_1_1_invoke() helper
provides a generic and portable way(switch between the conduits if
running within a VM for example)
--
Regards,
Sudeep
next prev parent reply other threads:[~2025-01-20 15:35 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-20 10:32 [linux-next:master 9185/10024] drivers/pmdomain/mediatek/airoha-cpu-pmdomain.c:59:2: error: write to reserved register 'R7' kernel test robot
2025-01-20 10:36 ` Christian Marangi (Ansuel)
2025-01-20 13:01 ` Ulf Hansson
2025-01-20 13:34 ` Sudeep Holla
2025-01-20 13:37 ` Christian Marangi (Ansuel)
2025-01-20 13:44 ` Sudeep Holla
2025-01-20 14:52 ` Christian Marangi (Ansuel)
2025-01-20 15:05 ` Sudeep Holla
2025-01-20 15:20 ` Christian Marangi (Ansuel)
2025-01-20 15:28 ` Christian Marangi (Ansuel)
2025-01-20 15:31 ` Christian Marangi (Ansuel)
2025-01-20 15:33 ` Sudeep Holla
2025-01-20 15:35 ` Sudeep Holla [this message]
2025-01-20 17:28 ` Nathan Chancellor
2025-01-20 17:39 ` Christian Marangi (Ansuel)
2025-01-20 18:02 ` Nathan Chancellor
2025-01-22 1:33 ` Philip Li
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=Z45tSadT6TxsuD_h@bogus \
--to=sudeep.holla@arm.com \
--cc=ansuelsmth@gmail.com \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=ulf.hansson@linaro.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