From: Tony Lindgren <tony@atomide.com>
To: "Andrew F. Davis" <afd@ti.com>
Cc: Rob Herring <robh@kernel.org>,
kbuild-all@lists.01.org, kbuild test robot <lkp@intel.com>,
Arnd Bergmann <arnd@arndb.de>,
Aaro Koskinen <aaro.koskinen@iki.fi>,
Marc Zyngier <maz@kernel.org>,
linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: omap-secure.c:undefined reference to `__arm_smccc_smc'
Date: Fri, 21 Feb 2020 09:26:31 -0800 [thread overview]
Message-ID: <20200221172631.GY37466@atomide.com> (raw)
In-Reply-To: <333dd36f-e760-64b3-9e0f-3a316df9ad10@ti.com>
* Andrew F. Davis <afd@ti.com> [200220 10:23]:
> On 2/20/20 1:11 PM, Tony Lindgren wrote:
> > * Tony Lindgren <tony@atomide.com> [200220 17:58]:
> >> * Andrew F. Davis <afd@ti.com> [200220 17:39]:
> >>> If the machine has SMCCC then it will also have the
> >>> CONFIG_HAVE_ARM_SMCCC set and so nothing would change.
> >>
> >> Hmm yeah good point.
> >
> > So the patch below seems like the way to go then. Anybody have issues
> > with the patch below?
> >
> > Regards,
> >
> > Tony
> >
> > 8< -------------------------
> > diff --git a/include/linux/arm-smccc.h b/include/linux/arm-smccc.h
> > --- a/include/linux/arm-smccc.h
> > +++ b/include/linux/arm-smccc.h
> > @@ -121,6 +121,7 @@ struct arm_smccc_quirk {
> > } state;
> > };
> >
> > +#ifdef CONFIG_HAVE_ARM_SMCCC
> > /**
> > * __arm_smccc_smc() - make SMC calls
> > * @a0-a7: arguments passed in registers 0 to 7
> > @@ -137,6 +138,14 @@ asmlinkage void __arm_smccc_smc(unsigned long a0, unsigned long a1,
> > unsigned long a2, unsigned long a3, unsigned long a4,
> > unsigned long a5, unsigned long a6, unsigned long a7,
> > struct arm_smccc_res *res, struct arm_smccc_quirk *quirk);
> > +#else
> > +static inline void __arm_smccc_smc(unsigned long a0, unsigned long a1,
> > + unsigned long a2, unsigned long a3, unsigned long a4,
> > + unsigned long a5, unsigned long a6, unsigned long a7,
> > + struct arm_smccc_res *res, struct arm_smccc_quirk *quirk)
> > +{
>
>
> Maybe a warning? If you do not have SMC on your platform but are still
> making SMC calls then something is broken and it looks like it would
> fail silently here.
OK I'll add that and send out a proper patch.
Thanks,
Tony
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-02-21 17:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <202002131856.VeW4PhBJ%lkp@intel.com>
[not found] ` <20200220155429.GH37466@atomide.com>
[not found] ` <55ddcd29-ed8b-529e-dd54-cbac5cf74e42@ti.com>
[not found] ` <20200220162012.GI37466@atomide.com>
[not found] ` <d7b685b6-16a2-3743-1786-a5240726ed9c@ti.com>
2020-02-20 16:37 ` omap-secure.c:undefined reference to `__arm_smccc_smc' Tony Lindgren
2020-02-20 17:13 ` Tony Lindgren
2020-02-20 17:39 ` Andrew F. Davis
2020-02-20 17:57 ` Tony Lindgren
2020-02-20 18:11 ` Tony Lindgren
2020-02-20 18:22 ` Andrew F. Davis
2020-02-21 17:26 ` Tony Lindgren [this message]
2020-02-21 17:54 ` Tony Lindgren
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=20200221172631.GY37466@atomide.com \
--to=tony@atomide.com \
--cc=aaro.koskinen@iki.fi \
--cc=afd@ti.com \
--cc=arnd@arndb.de \
--cc=kbuild-all@lists.01.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=lkp@intel.com \
--cc=maz@kernel.org \
--cc=robh@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 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).