From: Stanimir Varbanov <svarbanov@mm-sol.com>
To: "Ivan T. Ivanov" <iivanov@mm-sol.com>
Cc: Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>,
Samuel Ortiz <sameo@linux.intel.com>,
Lee Jones <lee.jones@linaro.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH] mfd: qcom-spmi-pmic: Add support for more chips versions
Date: Tue, 04 Nov 2014 17:26:49 +0200 [thread overview]
Message-ID: <5458F039.3030809@mm-sol.com> (raw)
In-Reply-To: <1415114567.29957.14.camel@mm-sol.com>
On 11/04/2014 05:22 PM, Ivan T. Ivanov wrote:
>
> On Tue, 2014-11-04 at 17:06 +0200, Stanimir Varbanov wrote:
>> Hi Ivan,
>>
>>
> +
>>> + switch (subtype) {
>>> + case PM8941_SUBTYPE:
>>> + *name = "pm8941";
>>> + break;
>>
>> The XXX_SUBTYPE seems are continuous why not make it an const array and
>> get the name by index in this array?
>>
>
> Yep, it _seems_ to be continuous. But, yes. probably using array will
> more compact way to represent this.
>
> <snip>
>
>>> @@ -28,11 +144,27 @@ static int pmic_spmi_probe(struct spmi_device *sdev)
>>> {
>>> struct device_node *root = sdev->dev.of_node;
>>> struct regmap *regmap;
>>> + struct property *prop;
>>> + int major, minor, ret;
>>> + char *name, compatible[32];
>>>
>>> regmap = devm_regmap_init_spmi_ext(sdev, &spmi_regmap_config);
>>> if (IS_ERR(regmap))
>>> return PTR_ERR(regmap);
>>>
>>> + ret = pmic_spmi_read_revid(regmap, &name, &major, &minor);
>>> + if (!ret) {
>>
>> Are you sure that we want to continue if we can't read the revision id
>> and therefore will not be able to construct properly the compatible
>> property?
>>
>
> Yes. Driver is working fine even without exact chip version
> appended to compatible string.
>
>>> + snprintf(compatible, ARRAY_SIZE(compatible), "qcom,%s-v%d.%d",
>>> + name, major, minor);
>>> + prop = kzalloc(sizeof(*prop), GFP_KERNEL);
>>> + if (prop) {
>>> + prop->name = kstrdup("compatible", GFP_KERNEL);
>>> + prop->value = kstrdup(compatible, GFP_KERNEL);
>>> + prop->length = strlen(prop->value);
>>> + of_update_property(root, prop);
>>
>> of_update_property can fail, check the returned value.
>
> Same thing as above, but probably allocated memory at least can be freed.
might be better idea to use devm_kzalloc and devm_kstrdup?
--
regards,
Stan
next prev parent reply other threads:[~2014-11-04 15:26 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-04 13:33 [PATCH] mfd: qcom-spmi-pmic: Add support for more chips versions Ivan T. Ivanov
2014-11-04 14:56 ` Fabio Estevam
2014-11-04 15:17 ` Ivan T. Ivanov
2014-11-04 15:06 ` Stanimir Varbanov
2014-11-04 15:22 ` Ivan T. Ivanov
2014-11-04 15:26 ` Stanimir Varbanov [this message]
2014-11-04 15:49 ` Ivan T. Ivanov
2014-11-05 12:49 ` Andreas Färber
2014-11-05 13:50 ` Ivan T. Ivanov
2014-11-05 18:11 ` Bjorn Andersson
2014-11-05 18:31 ` Ivan T. Ivanov
2014-11-06 1:36 ` Bjorn Andersson
2014-11-06 7:54 ` Ivan T. Ivanov
2014-11-06 16:55 ` Bjorn Andersson
2014-11-07 15:33 ` Ivan T. Ivanov
2014-11-07 15:40 ` Ivan T. Ivanov
2014-11-11 20:27 ` Courtney Cavin
2014-11-12 9:12 ` Ivan T. Ivanov
2014-11-08 0:08 ` Gilad Avidov
2014-11-10 7:46 ` Ivan T. Ivanov
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=5458F039.3030809@mm-sol.com \
--to=svarbanov@mm-sol.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=iivanov@mm-sol.com \
--cc=ijc+devicetree@hellion.org.uk \
--cc=lee.jones@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--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