From: Tomasz Figa <t.figa@samsung.com>
To: Vaibhav Bedia <vaibhav.bedia@gmail.com>
Cc: Abhilash Kesavan <a.kesavan@samsung.com>,
kgene.kim@samsung.com, tomasz.figa@gmail.com,
Linux ARM Kernel List <linux-arm-kernel@lists.infradead.org>,
linux-samsung-soc@vger.kernel.org, olof@lixom.net,
dianders@chromium.org
Subject: Re: [PATCH 1/2] ARM: EXYNOS: Support Suspend-to-RAM on EXYNOS5420
Date: Mon, 16 Dec 2013 17:15:08 +0100 [thread overview]
Message-ID: <1470279.CK35gJZeX3@amdc1227> (raw)
In-Reply-To: <CANacCWx7YV45mVK=7BJjc95cSgm6ck1qSMRsfW3oeGxLC1LC5w@mail.gmail.com>
Hi,
On Monday 16 of December 2013 08:27:17 Vaibhav Bedia wrote:
> Hi,
>
> On Mon, Dec 16, 2013 at 7:01 AM, Abhilash Kesavan <a.kesavan@samsung.com> wrote:
[snip]
> > + { EXYNOS5_CMU_RESET_GSCL_SYS_PWR_REG, { 0x0, 0x0, 0x0} },
> > + { EXYNOS5_CMU_RESET_ISP_SYS_PWR_REG, { 0x0, 0x0, 0x0} },
> > + { EXYNOS5_CMU_RESET_MFC_SYS_PWR_REG, { 0x0, 0x0, 0x0} },
> > + { EXYNOS5_CMU_RESET_G3D_SYS_PWR_REG, { 0x0, 0x0, 0x0} },
> > + { EXYNOS5420_CMU_RESET_DISP1_SYS_PWR_REG, { 0x0, 0x0, 0x0} },
> > + { EXYNOS5420_CMU_RESET_MAU_SYS_PWR_REG, { 0x0, 0x0, 0x0} },
> > + { EXYNOS5420_CMU_RESET_G2D_SYS_PWR_REG, { 0x0, 0x0, 0x0} },
> > + { EXYNOS5420_CMU_RESET_MSC_SYS_PWR_REG, { 0x0, 0x0, 0x0} },
> > + { EXYNOS5420_CMU_RESET_FSYS_SYS_PWR_REG, { 0x0, 0x0, 0x0} },
> > + { PMU_TABLE_END,},
> > +};
> > +
>
> Looking at a rather long list of register defines and soc_is_* checks here
> makes me wonder how this is any different from the static data that the
> other SoC vendors (TI) are trying very hard to move out of arch/arm...
Well, this data will eventually get moved to a PMU driver once
drivers/syslib (as discussed on KS in Edinburgh) infrastructure shows up.
We can't get rid of these data from kernel sources, since there is no
other place where they would fit. (No, DT is not such place.)
Best regards,
Tomasz
WARNING: multiple messages have this Message-ID (diff)
From: t.figa@samsung.com (Tomasz Figa)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] ARM: EXYNOS: Support Suspend-to-RAM on EXYNOS5420
Date: Mon, 16 Dec 2013 17:15:08 +0100 [thread overview]
Message-ID: <1470279.CK35gJZeX3@amdc1227> (raw)
In-Reply-To: <CANacCWx7YV45mVK=7BJjc95cSgm6ck1qSMRsfW3oeGxLC1LC5w@mail.gmail.com>
Hi,
On Monday 16 of December 2013 08:27:17 Vaibhav Bedia wrote:
> Hi,
>
> On Mon, Dec 16, 2013 at 7:01 AM, Abhilash Kesavan <a.kesavan@samsung.com> wrote:
[snip]
> > + { EXYNOS5_CMU_RESET_GSCL_SYS_PWR_REG, { 0x0, 0x0, 0x0} },
> > + { EXYNOS5_CMU_RESET_ISP_SYS_PWR_REG, { 0x0, 0x0, 0x0} },
> > + { EXYNOS5_CMU_RESET_MFC_SYS_PWR_REG, { 0x0, 0x0, 0x0} },
> > + { EXYNOS5_CMU_RESET_G3D_SYS_PWR_REG, { 0x0, 0x0, 0x0} },
> > + { EXYNOS5420_CMU_RESET_DISP1_SYS_PWR_REG, { 0x0, 0x0, 0x0} },
> > + { EXYNOS5420_CMU_RESET_MAU_SYS_PWR_REG, { 0x0, 0x0, 0x0} },
> > + { EXYNOS5420_CMU_RESET_G2D_SYS_PWR_REG, { 0x0, 0x0, 0x0} },
> > + { EXYNOS5420_CMU_RESET_MSC_SYS_PWR_REG, { 0x0, 0x0, 0x0} },
> > + { EXYNOS5420_CMU_RESET_FSYS_SYS_PWR_REG, { 0x0, 0x0, 0x0} },
> > + { PMU_TABLE_END,},
> > +};
> > +
>
> Looking at a rather long list of register defines and soc_is_* checks here
> makes me wonder how this is any different from the static data that the
> other SoC vendors (TI) are trying very hard to move out of arch/arm...
Well, this data will eventually get moved to a PMU driver once
drivers/syslib (as discussed on KS in Edinburgh) infrastructure shows up.
We can't get rid of these data from kernel sources, since there is no
other place where they would fit. (No, DT is not such place.)
Best regards,
Tomasz
next prev parent reply other threads:[~2013-12-16 16:15 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-16 12:01 [PATCH 1/2] ARM: EXYNOS: Support Suspend-to-RAM on EXYNOS5420 Abhilash Kesavan
2013-12-16 12:01 ` Abhilash Kesavan
2013-12-16 12:01 ` [PATCH 2/2] ARM: dts: Add node for GPIO keys on SMDK5420 Abhilash Kesavan
2013-12-16 12:01 ` Abhilash Kesavan
2013-12-16 12:48 ` [PATCH 1/2] ARM: EXYNOS: Support Suspend-to-RAM on EXYNOS5420 Bartlomiej Zolnierkiewicz
2013-12-16 12:48 ` Bartlomiej Zolnierkiewicz
2013-12-17 3:10 ` Abhilash Kesavan
2013-12-17 3:10 ` Abhilash Kesavan
2013-12-20 10:26 ` sunil joshi
2013-12-20 10:26 ` sunil joshi
2013-12-20 11:38 ` Abhilash Kesavan
2013-12-20 11:38 ` Abhilash Kesavan
2013-12-20 11:53 ` sunil joshi
2013-12-20 11:53 ` sunil joshi
2013-12-20 21:22 ` Olof Johansson
2013-12-20 21:22 ` Olof Johansson
2013-12-20 21:23 ` Tomasz Figa
2013-12-20 21:23 ` Tomasz Figa
2013-12-20 21:25 ` Olof Johansson
2013-12-20 21:25 ` Olof Johansson
2013-12-20 21:25 ` Tomasz Figa
2013-12-20 21:25 ` Tomasz Figa
2013-12-21 7:06 ` Abhilash Kesavan
2013-12-21 7:06 ` Abhilash Kesavan
2013-12-20 21:19 ` Tomasz Figa
2013-12-20 21:19 ` Tomasz Figa
2013-12-20 21:37 ` Olof Johansson
2013-12-20 21:37 ` Olof Johansson
2013-12-20 21:53 ` Tomasz Figa
2013-12-20 21:53 ` Tomasz Figa
2013-12-21 7:40 ` Abhilash Kesavan
2013-12-21 7:40 ` Abhilash Kesavan
2013-12-21 1:15 ` Doug Anderson
2013-12-21 1:15 ` Doug Anderson
[not found] ` <CAPQV+nO=Xe=z669QxCJSerrm-xP0b=WtyPveyh2uTcM2B3i5KQ@mail.gmail.com>
2014-01-18 2:44 ` Abhilash Kesavan
2014-01-18 2:44 ` Abhilash Kesavan
2013-12-16 13:27 ` Vaibhav Bedia
2013-12-16 13:27 ` Vaibhav Bedia
2013-12-16 16:15 ` Tomasz Figa [this message]
2013-12-16 16:15 ` Tomasz Figa
2013-12-20 21:37 ` Tomasz Figa
2013-12-20 21:37 ` Tomasz Figa
2013-12-21 7:18 ` Abhilash Kesavan
2013-12-21 7:18 ` Abhilash Kesavan
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=1470279.CK35gJZeX3@amdc1227 \
--to=t.figa@samsung.com \
--cc=a.kesavan@samsung.com \
--cc=dianders@chromium.org \
--cc=kgene.kim@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=olof@lixom.net \
--cc=tomasz.figa@gmail.com \
--cc=vaibhav.bedia@gmail.com \
/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.