From: Rajendra Nayak <rnayak@codeaurora.org>
To: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
sboyd@codeaurora.org, mturquette@linaro.org
Cc: linux-arm-msm@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, georgi.djakov@linaro.org,
svarbanov@mm-sol.com
Subject: Re: [PATCH v3 1/6] clk: qcom: Add support for GDSCs
Date: Fri, 20 Mar 2015 15:31:04 +0530 [thread overview]
Message-ID: <550BEFE0.1020004@codeaurora.org> (raw)
In-Reply-To: <550BED93.3000305@codeaurora.org>
[]...
>>> @@ -0,0 +1,46 @@
>>> +/*
>>> + * Copyright (c) 2015, The Linux Foundation. All rights reserved.
>>> + *
>>> + * This program is free software; you can redistribute it and/or modify
>>> + * it under the terms of the GNU General Public License version 2 and
>>> + * only version 2 as published by the Free Software Foundation.
>>> + *
>>> + * This program is distributed in the hope that it will be useful,
>>> + * but WITHOUT ANY WARRANTY; without even the implied warranty of
>>> + * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
>>> + * GNU General Public License for more details.
>>> + */
>>> +
>>> +#ifndef __QCOM_GDSC_H__
>>> +#define __QCOM_GDSC_H__
>>> +
>>> +#include <linux/pm_domain.h>
>>> +
>>> +struct regmap;
I realized, after Srini pointed out on irc that this fwd declaration
is a complete waste. I'll remove it when I do a repost.
>>> +
>>> +/**
>>> + * struct gdsc - Globally Distributed Switch Controller
>>> + * @pd: generic power domain
>>> + * @regmap: regmap for MMIO accesses
>>> + * @gdscr: gsdc control register
>>> + */
>>> +struct gdsc {
>>> + struct generic_pm_domain pd;
>>> + struct regmap *regmap;
>>> + unsigned int gdscr;
>>> +};
>>> +
>>> +#define domain_to_gdsc(domain) container_of(domain, struct gdsc, pd)
>>> +
>>> +#ifdef CONFIG_QCOM_GDSC
>>> +int gdsc_register(struct device *, struct gdsc **, size_t n, struct
>>> regmap *);
>>> +void gdsc_unregister(struct device *);
>>> +#else
>>> +int gdsc_register(struct device *d, struct gdsc **g, size_t n, struct
>>> regmap *r)
next prev parent reply other threads:[~2015-03-20 10:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-20 6:21 [PATCH v3 0/6] Add support for QCOM GDSCs Rajendra Nayak
2015-03-20 6:21 ` [PATCH v3 1/6] clk: qcom: Add support for GDSCs Rajendra Nayak
2015-03-20 7:38 ` Srinivas Kandagatla
2015-03-20 9:51 ` Rajendra Nayak
2015-03-20 10:01 ` Rajendra Nayak [this message]
2015-03-23 23:23 ` Stephen Boyd
2015-03-24 3:10 ` Rajendra Nayak
2015-03-20 6:21 ` [PATCH v3 2/6] clk: qcom: gdsc: Prepare common clk probe to register gdscs Rajendra Nayak
2015-03-20 6:21 ` [PATCH v3 3/6] clk: qcom: gdsc: Add GDSCs in msm8916 GCC Rajendra Nayak
2015-03-20 6:21 ` [PATCH v3 4/6] clk: qcom: gdsc: Add GDSCs in msm8974 GCC Rajendra Nayak
2015-03-20 6:21 ` [PATCH v3 5/6] clk: qcom: gdsc: Add GDSCs in msm8974 MMCC Rajendra Nayak
2015-03-20 6:21 ` [PATCH v3 6/6] clk: qcom: gdsc: Add GDSCs in apq8084 GCC Rajendra Nayak
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=550BEFE0.1020004@codeaurora.org \
--to=rnayak@codeaurora.org \
--cc=georgi.djakov@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=mturquette@linaro.org \
--cc=sboyd@codeaurora.org \
--cc=srinivas.kandagatla@linaro.org \
--cc=svarbanov@mm-sol.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).