From: bjorn.andersson@linaro.org (Bjorn Andersson)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] drivers: remoteproc: constify rproc_ops structures
Date: Sat, 31 Dec 2016 09:54:16 -0800 [thread overview]
Message-ID: <20161231175416.GA21596@minitux> (raw)
In-Reply-To: <CAOH+1jH=Y+1Nxe2L4d6OaC95dc-ORsuqsOYSNP5_8NYJVz-A4Q@mail.gmail.com>
On Sat 31 Dec 02:43 PST 2016, Bhumika Goyal wrote:
> On Fri, Dec 30, 2016 at 5:36 PM, Bjorn Andersson
> <bjorn.andersson@linaro.org> wrote:
> > On Sat 17 Dec 03:29 PST 2016, Bhumika Goyal wrote:
> >
> >> Declare rproc_ops structures as const as they are only passed as an
> >> argument to the function rproc_alloc. This argument is of type const, so
> >> rproc_ops structures having this property can be declared const too.
> >> Done using Coccinelle:
> >>
> >> @r1 disable optional_qualifier @
> >> identifier i;
> >> position p;
> >> @@
> >> static struct rproc_ops i at p = {...};
> >>
> >> @ok1@
> >> identifier r1.i;
> >> position p;
> >> @@
> >> rproc_alloc(...,&i at p,...)
> >>
> >> @bad@
> >> position p!={r1.p,ok1.p};
> >> identifier r1.i;
> >> @@
> >> i at p
> >>
> >> @depends on !bad disable optional_qualifier@
> >> identifier r1.i;
> >> @@
> >> +const
> >> struct rproc_ops i;
> >>
> >> File sizes before:
> >> text data bss dec hex filename
> >> 1258 416 0 1674 68a remoteproc/omap_remoteproc.o
> >> 2402 240 0 2642 a52 remoteproc/st_remoteproc.o
> >> 2064 272 0 2336 920 remoteproc/st_slim_rproc.o
> >> 2160 240 0 2400 960 remoteproc/wkup_m3_rproc.o
> >>
> >> File sizes after:
> >> text data bss dec hex filename
> >> 1297 368 0 1665 681 remoteproc/omap_remoteproc.o
> >> 2434 192 0 2626 a42 remoteproc/st_remoteproc.o
> >> 2112 240 0 2352 930 remoteproc/st_slim_rproc.o
> >> 2200 192 0 2392 958 remoteproc/wkup_m3_rproc.o
> >>
> >> Signed-off-by: Bhumika Goyal <bhumirks@gmail.com>
> >
> > Thanks Bhumika, this looks good.
> >
> > But as Suman already asked. Is there any reason why da8xx_remoteproc.c
> > did not get updated? It looks like the same change would apply there.
> >
> >
>
> The reason I did not sent a patch for that driver is because the .o
> file is not obtained. This is output I get when I try to compile the
> da8xx_remoteproc.o file.
>
> drivers/remoteproc/da8xx_remoteproc.c:22:72: fatal error:
> mach/clock.h: No such file or directory
> #include <mach/clock.h> /* for davinci_clk_reset_assert/deassert() */
> ^
> compilation terminated.
> make[1]: *** [drivers/remoteproc/da8xx_remoteproc.o] Error 1
> make: *** [drivers/remoteproc/da8xx_remoteproc.o] Error 2
>
> I also tried running the commands make.cross ARCH=arm allyesconfig;
> make.cross ARCH=arm drivers/remoteproc/da8xx_remoteproc.o but still
> the error remains the same.
>
> Could you please suggest me what to do in this case?
>
By using davinci_all_defconfig and then selecting
CONFIG_DA8XX_REMOTEPROC I managed to compile it, not sure what differs.
If you can't get it working please include the da8xx_remoteproc change
as well and just note that you didn't manage to test it.
Regards,
Bjorn
next prev parent reply other threads:[~2016-12-31 17:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-17 11:29 [PATCH] drivers: remoteproc: constify rproc_ops structures Bhumika Goyal
2016-12-22 21:22 ` Suman Anna
2016-12-30 12:06 ` Bjorn Andersson
2016-12-31 10:43 ` Bhumika Goyal
2016-12-31 17:54 ` Bjorn Andersson [this message]
2017-01-01 6:23 ` Bhumika Goyal
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=20161231175416.GA21596@minitux \
--to=bjorn.andersson@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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).