From: Felipe Balbi <balbi@ti.com>
To: Olof Johansson <olof@lixom.net>
Cc: Felipe Balbi <balbi@ti.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Kees Cook <keescook@chromium.org>,
Benson Leung <bleung@chromium.org>
Subject: Re: [PATCH] platform/chrome: Add pstore platform_device
Date: Mon, 25 Nov 2013 14:03:44 -0600 [thread overview]
Message-ID: <20131125200344.GF18046@saruman.home> (raw)
In-Reply-To: <CAOesGMhd0r6h63Y+z-6CCuo2iHPCNA56Bg762K+G7XOHO8FRGg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 948 bytes --]
Hi,
On Mon, Nov 25, 2013 at 11:59:50AM -0800, Olof Johansson wrote:
> >> +static int __init chromeos_pstore_init(void)
> >> +{
> >> + if (dmi_check_system(chromeos_pstore_dmi_table))
> >
> > is this check really necessary ? I would assume that your probe would
> > only be called if the device matches the dmi MODULE_DEVICE_TABLE().
> >
> > Except that you don't have a probe function which is quite odd. Also,
> > there's nothing using chromeos_ramoops_data, how does this work ?
>
> This is just a module that registers the device. The driver side is
> handled by pstore. See Documentation/ramoops.txt.
>
> That's also why the DMI table is needed: The module init is generic,
> and if built-in instead of loaded based on DMI table contents, it will
> always run. There's no specific device to bind against, since there's
> none in the tables passed in from firmware in this case.
I see now, thanks :-)
--
balbi
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-11-25 20:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-25 19:37 [PATCH] platform/chrome: Add pstore platform_device Olof Johansson
2013-11-25 19:52 ` Felipe Balbi
2013-11-25 19:59 ` Olof Johansson
2013-11-25 20:03 ` Felipe Balbi [this message]
2013-11-25 20:04 ` Randy Dunlap
2013-11-25 20:49 ` Olof Johansson
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=20131125200344.GF18046@saruman.home \
--to=balbi@ti.com \
--cc=bleung@chromium.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olof@lixom.net \
/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