From: shawnguo@kernel.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v6 1/2] irqchip: imx-gpcv2: IMX GPCv2 driver for wakeup sources
Date: Mon, 27 Jul 2015 22:35:15 +0800 [thread overview]
Message-ID: <20150727143515.GQ12927@tiger> (raw)
In-Reply-To: <CY1PR0301MB084352861E63DA2DE286CC77838E0@CY1PR0301MB0843.namprd03.prod.outlook.com>
On Mon, Jul 27, 2015 at 02:13:37PM +0000, Shenwei Wang wrote:
> > -----Original Message-----
> > From: Shawn Guo [mailto:shawnguo at kernel.org]
> > Sent: 2015?7?27? 8:41
> > To: Wang Shenwei-B38339
> > Cc: shawn.guo at linaro.org; tglx at linutronix.de; jason at lakedaemon.net; Huang
> > Yongcai-B20788; linux-kernel at vger.kernel.org;
> > linux-arm-kernel at lists.infradead.org
> > Subject: Re: [PATCH v6 1/2] irqchip: imx-gpcv2: IMX GPCv2 driver for wakeup
> > sources
> >
> > On Wed, Jul 22, 2015 at 12:07:38PM -0500, Shenwei Wang wrote:
> > > diff --git a/include/soc/imx/gpcv2.h b/include/soc/imx/gpcv2.h new
> > > file mode 100644 index 0000000..73d6e75
> > > --- /dev/null
> > > +++ b/include/soc/imx/gpcv2.h
> >
> > I do not like this header, which couples imx7d irqchip and pm driver so
> > much. Can you please elaborate why we have to have this header?
>
> PM driver does depend on the irqchip driver. It needs some input like enabled irqs and
> wakeup irqs to decide which module to be powered off in low power states. I am also
> considering if the header file could be removed or not. So far it seems a common place
> to define a structure which is used in both drivers is still required.
Please be more specific. Trimming the header down to the macros and
structures/fields that are necessary to be in the header might be a good
idea. And then we can go through them one by one to see if there is a
way to avoid them being in the header.
Shawn
WARNING: multiple messages have this Message-ID (diff)
From: Shawn Guo <shawnguo@kernel.org>
To: Shenwei Wang <Shenwei.Wang@freescale.com>
Cc: "jason@lakedaemon.net" <jason@lakedaemon.net>,
Huang Anson <Anson.Huang@freescale.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"shawn.guo@linaro.org" <shawn.guo@linaro.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v6 1/2] irqchip: imx-gpcv2: IMX GPCv2 driver for wakeup sources
Date: Mon, 27 Jul 2015 22:35:15 +0800 [thread overview]
Message-ID: <20150727143515.GQ12927@tiger> (raw)
In-Reply-To: <CY1PR0301MB084352861E63DA2DE286CC77838E0@CY1PR0301MB0843.namprd03.prod.outlook.com>
On Mon, Jul 27, 2015 at 02:13:37PM +0000, Shenwei Wang wrote:
> > -----Original Message-----
> > From: Shawn Guo [mailto:shawnguo@kernel.org]
> > Sent: 2015年7月27日 8:41
> > To: Wang Shenwei-B38339
> > Cc: shawn.guo@linaro.org; tglx@linutronix.de; jason@lakedaemon.net; Huang
> > Yongcai-B20788; linux-kernel@vger.kernel.org;
> > linux-arm-kernel@lists.infradead.org
> > Subject: Re: [PATCH v6 1/2] irqchip: imx-gpcv2: IMX GPCv2 driver for wakeup
> > sources
> >
> > On Wed, Jul 22, 2015 at 12:07:38PM -0500, Shenwei Wang wrote:
> > > diff --git a/include/soc/imx/gpcv2.h b/include/soc/imx/gpcv2.h new
> > > file mode 100644 index 0000000..73d6e75
> > > --- /dev/null
> > > +++ b/include/soc/imx/gpcv2.h
> >
> > I do not like this header, which couples imx7d irqchip and pm driver so
> > much. Can you please elaborate why we have to have this header?
>
> PM driver does depend on the irqchip driver. It needs some input like enabled irqs and
> wakeup irqs to decide which module to be powered off in low power states. I am also
> considering if the header file could be removed or not. So far it seems a common place
> to define a structure which is used in both drivers is still required.
Please be more specific. Trimming the header down to the macros and
structures/fields that are necessary to be in the header might be a good
idea. And then we can go through them one by one to see if there is a
way to avoid them being in the header.
Shawn
next prev parent reply other threads:[~2015-07-27 14:35 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-22 17:07 [PATCH v6 0/2] IMX GPCv2 drivers for wakeup source and suspend Shenwei Wang
2015-07-22 17:07 ` Shenwei Wang
2015-07-22 17:07 ` [PATCH v6 1/2] irqchip: imx-gpcv2: IMX GPCv2 driver for wakeup sources Shenwei Wang
2015-07-22 17:07 ` Shenwei Wang
2015-07-26 11:48 ` Thomas Gleixner
2015-07-26 11:48 ` Thomas Gleixner
2015-07-27 13:58 ` Shenwei Wang
2015-07-27 13:58 ` Shenwei Wang
2015-07-27 13:40 ` Shawn Guo
2015-07-27 13:40 ` Shawn Guo
2015-07-27 14:13 ` Shenwei Wang
2015-07-27 14:13 ` Shenwei Wang
2015-07-27 14:35 ` Shawn Guo [this message]
2015-07-27 14:35 ` Shawn Guo
2015-07-27 14:50 ` Shenwei Wang
2015-07-27 14:50 ` Shenwei Wang
2015-07-28 0:47 ` Shawn Guo
2015-07-28 0:47 ` Shawn Guo
2015-07-28 14:24 ` Shenwei Wang
2015-07-28 14:24 ` Shenwei Wang
2015-07-22 17:07 ` [PATCH v6 2/2] ARM: imx: Add suspend codes for imx7D Shenwei Wang
2015-07-22 17:07 ` Shenwei Wang
2015-07-27 13:28 ` Shawn Guo
2015-07-27 13:28 ` Shawn Guo
2015-07-27 18:24 ` Shenwei Wang
2015-07-27 18:24 ` Shenwei Wang
2015-07-28 1:02 ` Shawn Guo
2015-07-28 1:02 ` Shawn Guo
2015-07-28 14:16 ` Shenwei Wang
2015-07-28 14:16 ` Shenwei Wang
2015-07-28 14:30 ` Shawn Guo
2015-07-28 14:30 ` Shawn Guo
2015-07-28 15:14 ` Shenwei Wang
2015-07-28 15:14 ` Shenwei Wang
2015-07-28 16:39 ` Zhi Li
2015-07-28 16:39 ` Zhi 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=20150727143515.GQ12927@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.