From: Paul Bolle <pebolle@tiscali.nl>
To: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
Cc: tglx@linutronix.de, mingo@redhat.com, hpa@zytor.com,
x86@kernel.org, linux-kernel@vger.kernel.org,
Kumar P Mahesh <mahesh.kumar.p@intel.com>
Subject: Re: [PATCH] x86: punit_atom: punit device state debug driver
Date: Sat, 25 Apr 2015 11:43:19 +0200 [thread overview]
Message-ID: <1429954999.2927.117.camel@x220> (raw)
In-Reply-To: <1429911723-31095-1-git-send-email-srinivas.pandruvada@linux.intel.com>
On Fri, 2015-04-24 at 14:42 -0700, Srinivas Pandruvada wrote:
> --- a/arch/x86/Kconfig
> +++ b/arch/x86/Kconfig
>
> +config PUNIT_ATOM
> + bool "ATOM Punit debug driver"
> + def_bool n
The kconfig tools will do what you mean here. But just
default n
is neater. And, moreover, even that is probably not needed, as n is the
default anyway.
> + depends on DEBUG_FS
> + select IOSF_MBI
> + ---help---
> + This is a debug driver, which gets the power states
> + of all Punit North Complex devices.The power states of
> + each IP is exposed as part of the debugfs interface.
(This menu will show up in menuconfig's main menu. Shouldn't this be put
in some debug related menu?)
> --- a/arch/x86/kernel/Makefile
> +++ b/arch/x86/kernel/Makefile
> +obj-$(CONFIG_PUNIT_ATOM) += punit_atom.o
PUNIT_ATOM is a bool symbol, so punit_atom.o will never be part of a
module, correct?
> --- /dev/null
> +++ b/arch/x86/kernel/punit_atom.c
> +#include <linux/module.h>
Is this include needed (except for the stuff that will be preprocessed
away, see below)?
> +MODULE_DEVICE_TABLE(x86cpu, intel_punit_cpu_ids);
MODULE_DEVICE_TABLE will be preprocessed away for built-in code,
according to include/linux/module.h.
> +static void __exit punit_atom_exit(void)
> +{
> + punit_dbgfs_unregister();
> +}
> +
> +module_init(punit_atom_init);
According to include/linux/init.h this is equal to
device_initcall(punit_atom_init);
for built-in code.
> +module_exit(punit_atom_exit);
Built-in only code will never call that function.
> +MODULE_AUTHOR("Kumar P, Mahesh <mahesh.kumar.p.intel.com>");
(<mahesh.kumar.p@intel.com>?)
> +MODULE_DESCRIPTION("Driver for Punit devices states debugging");
> +MODULE_LICENSE("GPL v2");
And these three macros will be effectively preprocessed away for
built-in only code.
But, on the other hand, changing PUNIT_ATOM to tristate allows it to be
built as a module (I just did that). So perhaps that was your intention?
Paul Bolle
next prev parent reply other threads:[~2015-04-25 9:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-24 21:42 [PATCH] x86: punit_atom: punit device state debug driver Srinivas Pandruvada
2015-04-25 9:43 ` Paul Bolle [this message]
2015-04-29 23:33 ` Srinivas Pandruvada
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=1429954999.2927.117.camel@x220 \
--to=pebolle@tiscali.nl \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mahesh.kumar.p@intel.com \
--cc=mingo@redhat.com \
--cc=srinivas.pandruvada@linux.intel.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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