linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Philipp Zabel <p.zabel@pengutronix.de>
To: "Heiko Stübner" <heiko@sntech.de>
Cc: Samuel Ortiz <sameo@linux.intel.com>,
	Arnd Bergmann <arnd@arndb.de>,
	Pankaj Dubey <pankaj.dubey@samsung.com>,
	Tomasz Figa <tomasz.figa@gmail.com>,
	linux-kernel@vger.kernel.org,
	Vivek Gautam <gautam.vivek@samsung.com>,
	kernel@pengutronix.de, Lee Jones <lee.jones@linaro.org>,
	Javier Martinez Canillas <javier.martinez@collabora.co.uk>
Subject: Re: [PATCH] mfd: syscon: fix syscon probing from dt
Date: Wed, 07 Jan 2015 10:58:19 +0100	[thread overview]
Message-ID: <1420624699.3191.19.camel@pengutronix.de> (raw)
In-Reply-To: <3852443.x4DN8HDuzc@phil>

Hi Heiko,

Am Dienstag, den 06.01.2015, 20:05 +0100 schrieb Heiko Stübner:
> Hi Philipp,
> 
> Am Dienstag, 6. Januar 2015, 16:30:36 schrieb Philipp Zabel:
> > Patch bdb0066df96e ("mfd: syscon: Decouple syscon interface from platform
> > devices") breaks probing pure syscon devices from device tree, such as
> > anatop and iomuxc-gpr on i.MX. This patch adds back the dt id table to
> > match against "syscon" compatible device tree nodes.
> 
> could you elaborate a bit on the problem you're seeing without your patch?
>
> With bdb0066df96e the syscon should be registered by the first call to one of 
> the syscon_regmap_lookup_by_* functions. On my rockchip boards this works 
> without any hickups:

Oh, I didn't understand that is the way it's supposed to work now.

I noticed that after booting v3.19-rc on a nitrogen6x, the
/sys/kernel/debug/regmap/{20c8000.anatop,20e0000.iomuxc-gpr}
directories were missing. The syscon regmap is indeed registered,
but since regmap_init_mmio is called with dev = NULL, regmap_attach_dev,
and thus regmap_debugfs_init, is never called from regmap_init.

Also I want to add child devices to the syscon device since a while ago:
https://lkml.org/lkml/2014/12/15/133
This doesn't work anymore if there is no syscon device.

regards
Philipp


  reply	other threads:[~2015-01-07  9:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-06 15:30 [PATCH] mfd: syscon: fix syscon probing from dt Philipp Zabel
2015-01-06 19:05 ` Heiko Stübner
2015-01-07  9:58   ` Philipp Zabel [this message]
2015-01-06 19:36 ` Arnd Bergmann
2015-01-07 10:57   ` Philipp Zabel
2015-01-07 11:17     ` Pankaj Dubey
2015-01-07 11:55       ` Philipp Zabel
2015-01-08 11:07         ` Pankaj Dubey
2015-01-08 11:47           ` Philipp Zabel

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=1420624699.3191.19.camel@pengutronix.de \
    --to=p.zabel@pengutronix.de \
    --cc=arnd@arndb.de \
    --cc=gautam.vivek@samsung.com \
    --cc=heiko@sntech.de \
    --cc=javier.martinez@collabora.co.uk \
    --cc=kernel@pengutronix.de \
    --cc=lee.jones@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pankaj.dubey@samsung.com \
    --cc=sameo@linux.intel.com \
    --cc=tomasz.figa@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 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).