From: shawnguo@kernel.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v7 1/2] irqchip: imx-gpcv2: IMX GPCv2 driver for wakeup sources
Date: Tue, 28 Jul 2015 22:38:54 +0800 [thread overview]
Message-ID: <20150728143854.GH12927@tiger> (raw)
In-Reply-To: <CY1PR0301MB08438D52968A601F94DBB55C838D0@CY1PR0301MB0843.namprd03.prod.outlook.com>
On Tue, Jul 28, 2015 at 02:27:42PM +0000, Shenwei Wang wrote:
> > > +static int gpcv2_wakeup_source_save(void) {
> > > + struct imx_gpcv2_irq *cd;
> >
> > We generally name variables in an abbrev of the types to make them intuitive. I
> > tried hard to map "cd" to "imx_gpcv2_irq" and failed.
> > Can you help me on that?
>
> CD is the abbreviation of chip data which is a member of irq_data.
You are defining a variable of type imx_gpcv2_irq, neither chip_data nor
irq_data.
> > > +void ca7_cpu_resume(void);
> > > +void imx7_suspend(void __iomem *ocram_vbase);
> >
> > Why do these declarations need to be in this header?
>
> Just to resolve the compile errors.
Wrong solution. They belong to some header in arch/arm/mach-imx not
include/soc/imx, as there is no code outside arch/arm/mach-imx needs
these declaration.
Shawn
next prev parent reply other threads:[~2015-07-28 14:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-27 19:29 [PATCH v7 0/2] IMX GPCv2 drivers for wakeup source and suspend Shenwei Wang
2015-07-27 19:29 ` [PATCH v7 1/2] irqchip: imx-gpcv2: IMX GPCv2 driver for wakeup sources Shenwei Wang
2015-07-28 1:24 ` Shawn Guo
2015-07-28 14:27 ` Shenwei Wang
2015-07-28 14:38 ` Shawn Guo [this message]
2015-07-28 14:46 ` Shenwei Wang
2015-07-27 19:30 ` [PATCH v7 2/2] ARM: imx: Add suspend codes for imx7D Shenwei Wang
2015-07-30 22:44 ` Stefan Agner
2015-07-31 15:26 ` Shenwei Wang
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=20150728143854.GH12927@tiger \
--to=shawnguo@kernel.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).