From: Mark Brown <broonie@kernel.org>
To: Michal Simek <monstr@monstr.eu>
Cc: Lee Jones <lee.jones@linaro.org>,
Michal Simek <michal.simek@xilinx.com>,
linux-kernel@vger.kernel.org, pankaj.dubey@samsung.com,
Samuel Ortiz <sameo@linux.intel.com>,
arnd@arndb.de
Subject: Re: [PATCH v3] mfd: syscon: Support early initialization
Date: Wed, 23 Apr 2014 16:19:32 +0100 [thread overview]
Message-ID: <20140423151932.GD12304@sirena.org.uk> (raw)
In-Reply-To: <5357BA5C.6000606@monstr.eu>
[-- Attachment #1: Type: text/plain, Size: 783 bytes --]
On Wed, Apr 23, 2014 at 03:04:28PM +0200, Michal Simek wrote:
> In early_syscon_probe np->data contains pointer to struct syscon which
> stores base, regmap and res - driver private data for system controller.
> (init in early_syscon_probe)
> This is the way I am aware of how to share driver private data without pdev.
> Maybe there is better way how to do it that's why please let me know
> if you are aware about it.
The main issue I'm seeing is that the fact that the pointer in the node
is being used without a reference being held; I'd expect something to
explicitly own the reference. Either hold the reference somewhere and
hand it off between the various stages or free the syscon object and
allocate a new one each time it's used prior to the device being
instantiated.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2014-04-23 15:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-08 15:00 Michal Simek
2014-04-10 6:20 ` Pankaj Dubey
2014-04-10 6:17 ` Michal Simek
2014-04-23 7:27 ` Michal Simek
2014-04-23 8:22 ` Pankaj Dubey
2014-04-23 8:27 ` Michal Simek
2014-04-25 13:26 ` Pankaj Dubey
2014-04-23 10:01 ` Lee Jones
2014-04-23 10:05 ` Lee Jones
2014-04-23 11:42 ` Mark Brown
2014-04-23 13:04 ` Michal Simek
2014-04-23 15:19 ` Mark Brown [this message]
2014-04-25 21:33 ` Tomasz Figa
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=20140423151932.GD12304@sirena.org.uk \
--to=broonie@kernel.org \
--cc=arnd@arndb.de \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.simek@xilinx.com \
--cc=monstr@monstr.eu \
--cc=pankaj.dubey@samsung.com \
--cc=sameo@linux.intel.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
all inboxes | Powered by JetHome®