LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: James Liao <jamesjj.liao@mediatek.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: Kevin Hilman <khilman@kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
<linux-mediatek@lists.infradead.org>, <kernel@pengutronix.de>
Subject: Re: [PATCH 2/4] soc: Mediatek: Add SCPSYS power domain driver
Date: Wed, 11 Mar 2015 11:16:31 +0800 [thread overview]
Message-ID: <1426043791.24243.9.camel@mtksdaap41> (raw)
In-Reply-To: <20150310094142.GD24885@pengutronix.de>
Hi,
On Tue, 2015-03-10 at 10:41 +0100, Sascha Hauer wrote:
> On Mon, Mar 09, 2015 at 02:35:03PM -0700, Kevin Hilman wrote:
> > Sascha Hauer <s.hauer@pengutronix.de> writes:
> >
> > > Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
> >
> > A bit of a changelog here would be useful describing this driver, that
> > it's only covering part of the device (e.g. power controller) with more
> > to come, dependency on the syscon driver, etc.
> >
> > > +/*
> > > + * The Infracfg unit has bus protection bits. We enable the bus protection
> > > + * for disabled power domains so that the system does not hang when some unit
> > > + * accesses the bus while in power down.
> > > + */
> >
> > Hmm, why don't you want to know if some device is accessing another
> > device which is in a domain that is powered down? Seems like this is a
> > good way to hide real bugs.
>
> How I understand it the system just hangs on erroneous accesses without
> these protection bits enabled, so enabling them at least makes sure we
> can output something.
> I must admit though that my understanding of these bits is quite limited
> and the only user of this driver I have available here (audio) doesn't
> make use of these protection bits, so I can't test here.
>
> James, could you shed some light on this issue?
I asked our designer about the bus protection feature, here is his
response:
"
It's for unexpected signal glitch in Power switch process.
During Power switch process, we have clock switch, reset, isolation
enable/disable and power switch involved where the transition of
asynchronous reset and isolation is the most critical one, which have
risk to introduce a unexpected short period signal transition from
MTCMOS’s interface to other alive HW .
"
That means it protects unexpected bus accessing from HW, not from SW. So
it will not hide bugs from wrong SW access.
Best regards,
James
************* Email Confidentiality Notice ********************
The information contained in this e-mail message (including any
attachments) may be confidential, proprietary, privileged, or otherwise
exempt from disclosure under applicable laws. It is intended to be
conveyed only to the designated recipient(s). Any use, dissemination,
distribution, printing, retaining or copying of this e-mail (including its
attachments) by unintended recipient(s) is strictly prohibited and may
be unlawful. If you are not an intended recipient of this e-mail, or believe
that you have received this e-mail in error, please notify the sender
immediately (by replying to this e-mail), delete any and all copies of
this e-mail (including any attachments) from your system, and do not
disclose the content of this e-mail to any other person. Thank you!
next prev parent reply other threads:[~2015-03-11 3:16 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-09 8:09 [RFC] Mediatek SCPSYS power domain support Sascha Hauer
2015-03-09 8:10 ` [PATCH 1/4] dt-bindings: soc: Add documentation for the MediaTek SCPSYS unit Sascha Hauer
2015-03-09 20:46 ` Kevin Hilman
2015-03-10 8:02 ` Sascha Hauer
2015-03-09 8:10 ` [PATCH 2/4] soc: Mediatek: Add SCPSYS power domain driver Sascha Hauer
2015-03-09 21:35 ` Kevin Hilman
2015-03-10 9:41 ` Sascha Hauer
2015-03-10 14:40 ` Sascha Hauer
2015-03-10 16:00 ` Kevin Hilman
2015-03-11 3:16 ` James Liao [this message]
2015-03-11 9:03 ` Sascha Hauer
2015-03-11 17:14 ` Kevin Hilman
2015-03-12 7:21 ` Sascha Hauer
2015-03-09 8:10 ` [PATCH 3/4] ARM64: MediaTek: Add generic pm domain support Sascha Hauer
2015-03-09 8:10 ` [PATCH 4/4] ARM64: MediaTek MT8173: Add SCPSYS device node Sascha Hauer
2015-03-09 20:43 ` [RFC] Mediatek SCPSYS power domain support Kevin Hilman
2015-03-10 15:40 [PATCH v1] " Sascha Hauer
2015-03-10 15:41 ` [PATCH 2/4] soc: Mediatek: Add SCPSYS power domain driver Sascha Hauer
2015-03-11 11:10 ` Paul Bolle
2015-03-31 16:27 ` Kevin Hilman
2015-04-13 10:55 ` Sascha Hauer
2015-05-08 12:16 ` Matthias Brugger
2015-05-08 12:19 ` Sascha Hauer
2015-05-08 12:28 ` Matthias Brugger
2015-05-08 12:51 ` Sascha Hauer
2015-05-08 15:51 ` Matthias Brugger
2015-05-11 13:11 [PATCH v2] Mediatek SCPSYS power domain support Sascha Hauer
2015-05-11 13:11 ` [PATCH 2/4] soc: Mediatek: Add SCPSYS power domain driver Sascha Hauer
2015-05-26 22:35 ` Kevin Hilman
2015-05-27 6:24 ` Sascha Hauer
2015-05-28 17:22 ` Kevin Hilman
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=1426043791.24243.9.camel@mtksdaap41 \
--to=jamesjj.liao@mediatek.com \
--cc=devicetree@vger.kernel.org \
--cc=kernel@pengutronix.de \
--cc=khilman@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=s.hauer@pengutronix.de \
--subject='Re: [PATCH 2/4] soc: Mediatek: Add SCPSYS power domain driver' \
/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
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).