public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: MyungJoo Ham <myungjoo.ham@samsung.com>
To: Abhilash Kesavan <kesavan.abhilash@gmail.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
	김국진 <kgene.kim@samsung.com>, 박경민 <kyungmin.park@samsung.com>,
	"rjw@sisk.pl" <rjw@sisk.pl>, 최종환 <jhbird.choi@samsung.com>
Subject: Re: Re: [PATCH v4 4/4] PM: Devfreq: Add Exynos5-bus devfreq driver for Exynos5250
Date: Mon, 04 Feb 2013 08:19:13 +0000 (GMT)	[thread overview]
Message-ID: <17352980.268481359965953092.JavaMail.weblogic@epml13> (raw)

> Hi,
> 
> > Sorry for being late.
> >
> > One concern is that I cannot apply Patch 1/4 directly as the .dts file isn't
> > available to me.
> > Do you intend to apply that patch to another tree and apply the other three
> > to devfreq tree?
> I have been merging the devfreq tree into Kgene's tree for my testing. I am not
> sure how this should get in, any suggestions ?

I'd suggest to send Patch 1/4 to Kgene and get it applied first if that patch is preliminary to the other patchset. If it is not, we can go seperated and independently.

> >
> > Another is the location of exynos_ppmu.h.
> > Who is going to refer exynos_ppmu.h?
> > If Exynos devfreq drivers are the only files to refer, wouldn't it be better
> > located at drivers/devfreq/exynos/ ?
> >
> > Or do you intend to let someone else (drivers located not in
> > drivers/devfreq) access exynos-ppmu?
> > (If so, who's going to be? and that means we are going to have
> > include/linux/devfreq/, I don't think it'd be appropriate to populate
> > include/linux with device driver specific headers)
> In an earlier comment on this patch Olof suggested I place it in
> include/linux/. It is going to be
> used only by Exynos and I will move it into drivers/devfreq/exynos as
> per your suggestion.

If it is to be used by Exynos non-devfreq drivers (e.g., Exynos ADC driver in drivers/iio/...), it should be stting on include/linux/devfreq/. If it is to be used by Exynos devfreq drivers only, it'd be better located at drivers/devfreq/exynos/. It appears to be still compatible with Olof's suggestion:

(quoting Olof) "Local defines that are used in just one C file can either go in that file, or in a header file that sits next to it instead of in the shared directory."



> >
> >
> >
> > And, there are errors (we do not have __devinit/__devexit anymore):
> >
> >   CC      drivers/devfreq/exynos/exynos5_bus.o
> > drivers/devfreq/exynos/exynos5_bus.c:315:18: error: expected =, ,, ;, asm or
> > __attribute__ before int
> > drivers/devfreq/exynos/exynos5_bus.c:430:18: error: expected =, ,, ;, asm or
> > __attribute__ before int
> > drivers/devfreq/exynos/exynos5_bus.c:462:11: error:
> > exynos5_busfreq_int_probe undeclared here (not in a function)
> > drivers/devfreq/exynos/exynos5_bus.c:463:2: error: implicit declaration of
> > function __devexit_p [-Werror=implicit-function-declaration]
> > drivers/devfreq/exynos/exynos5_bus.c:463:24: error:
> > exynos5_busfreq_int_remove undeclared here (not in a function)
> > drivers/devfreq/exynos/exynos5_bus.c:235:35: warning:
> > exynos5_devfreq_int_profile defined but not used [-Wunused-variable]
> > drivers/devfreq/exynos/exynos5_bus.c:243:12: warning:
> > exynos5250_init_int_tables defined but not used [-Wunused-function]
> > drivers/devfreq/exynos/exynos5_bus.c:259:12: warning:
> > exynos5_busfreq_int_pm_notifier_event defined but not used
> > [-Wunused-function]
> > cc1: some warnings being treated as errors
> I will fix these and re-post.
> >
> >
> >
> > Cheers,
> > MyungJoo.
> >
> Abhilash
> 

             reply	other threads:[~2013-02-04  8:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-04  8:19 MyungJoo Ham [this message]
2013-02-04  8:31 ` Re: [PATCH v4 4/4] PM: Devfreq: Add Exynos5-bus devfreq driver for Exynos5250 Abhilash Kesavan
2013-04-03  4:35   ` Kukjin Kim

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=17352980.268481359965953092.JavaMail.weblogic@epml13 \
    --to=myungjoo.ham@samsung.com \
    --cc=jhbird.choi@samsung.com \
    --cc=kesavan.abhilash@gmail.com \
    --cc=kgene.kim@samsung.com \
    --cc=kyungmin.park@samsung.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=rjw@sisk.pl \
    /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