public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@kernel.org>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-mediatek@lists.infradead.org,
	kernel@pengutronix.de, Matthias Brugger <matthias.bgg@gmail.com>
Subject: Re: [PATCH 1/5] soc: mediatek: Add infracfg misc driver support
Date: Tue, 26 May 2015 16:12:06 -0700	[thread overview]
Message-ID: <7hfv6jorw9.fsf@deeprootsystems.com> (raw)
In-Reply-To: <1431372206-1237-2-git-send-email-s.hauer@pengutronix.de> (Sascha Hauer's message of "Mon, 11 May 2015 21:23:22 +0200")

Sascha Hauer <s.hauer@pengutronix.de> writes:

> This adds support for some miscellaneous bits of the infracfg controller.
> The mtk_infracfg_set/clear_bus_protection functions are necessary for
> the scpsys power domain driver to handle the bus protection bits which
> are contained in the infacfg register space.
>
> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>

IMO, this feature still needs more documentation.  From an earlier
exchange with James Liao, he was able to get some more details from the
HW designer[1] which I think belong in comments somewhere in this
driver.

Kevin
 
[1] http://lists.infradead.org/pipermail/linux-mediatek/2015-March/000142.html


  parent reply	other threads:[~2015-05-26 23:12 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-11 19:23 [PATCH v2] Mediatek SCPSYS power domain support Sascha Hauer
2015-05-11 19:23 ` [PATCH 1/5] soc: mediatek: Add infracfg misc driver support Sascha Hauer
2015-05-12  7:12   ` Sascha Hauer
2015-05-12  9:24   ` Paul Bolle
2015-05-12 13:26     ` Sascha Hauer
2015-05-15 14:17   ` Daniel Kurtz
2015-05-18  8:16     ` Sascha Hauer
2015-05-19  6:54       ` Daniel Kurtz
2015-05-19  7:45         ` Sascha Hauer
2015-05-19 10:39           ` Daniel Kurtz
2015-05-26 23:12   ` Kevin Hilman [this message]
2015-05-27  7:33     ` Sascha Hauer
2015-05-11 19:23 ` [PATCH 2/5] dt-bindings: soc: Add documentation for the MediaTek SCPSYS unit Sascha Hauer
2015-05-11 19:23 ` [PATCH 3/5] soc: Mediatek: Add SCPSYS power domain driver Sascha Hauer
2015-05-12 11:52   ` Matthias Brugger
2015-05-12 13:47     ` Sascha Hauer
2015-05-15 14:17   ` Daniel Kurtz
2015-05-19 10:30     ` Sascha Hauer
2015-05-19 11:06       ` Matthias Brugger
2015-05-20 14:03         ` Sascha Hauer
2015-05-20 16:06           ` Matthias Brugger
2015-05-11 19:23 ` [PATCH 4/5] ARM64: MediaTek: Add generic pm domain support Sascha Hauer
2015-05-11 19:23 ` [PATCH 5/5] ARM64: MediaTek MT8173: Add SCPSYS device node Sascha Hauer
  -- strict thread matches above, loose matches on Subject: below --
2015-05-20 14:18 [PATCH v3] Mediatek SCPSYS power domain support Sascha Hauer
2015-05-20 14:18 ` [PATCH 1/5] soc: mediatek: Add infracfg misc driver support Sascha Hauer
2015-05-21  8:09   ` Paul Bolle
2015-06-09  8:46 [PATCH v4] Mediatek SCPSYS power domain support Sascha Hauer
2015-06-09  8:46 ` [PATCH 1/5] soc: mediatek: Add infracfg misc driver support Sascha Hauer

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=7hfv6jorw9.fsf@deeprootsystems.com \
    --to=khilman@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=kernel@pengutronix.de \
    --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 \
    /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