From: AngeloGioacchino Del Regno <angelogioacchino.delregno@somainline.org>
To: Mark Brown <broonie@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, agross@kernel.org,
bjorn.andersson@linaro.org, lgirdwood@gmail.com,
robh+dt@kernel.org, sumit.semwal@linaro.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
phone-devel@vger.kernel.org, konrad.dybcio@somainline.org,
marijn.suijten@somainline.org, martin.botka@somainline.org
Subject: Re: [PATCH 5/7] regulator: qcom-labibb: Implement short-circuit and over-current IRQs
Date: Tue, 12 Jan 2021 18:49:53 +0100 [thread overview]
Message-ID: <e872bc39-a941-d552-5145-49f40d6fa657@somainline.org> (raw)
In-Reply-To: <20210112172919.GD4646@sirena.org.uk>
Il 12/01/21 18:29, Mark Brown ha scritto:
> On Mon, Jan 11, 2021 at 10:06:18PM +0100, AngeloGioacchino Del Regno wrote:
>
>> ...which was already a requirement before I touched it.
>> Now, this leaves two options here:
>> 1. Keep the of_get_irq way, or
>> 2. Move the interrupts, change the documentation (currently, only
>> pmi8998.dtsi) and also fix pmi8998.dtsi to reflect the new changes.
>
>> I am asking before proceeding because I know that changing a schema that is
>> already set sometimes gets "negated".
>
> Well, if the binding isn't actually used changing it is a possibility.
> If we keep the current binding you can still continue to use
> of_get_irq() even from within the probe function, you know the name of
> the node it's supposed to be in so you don't need to iterate or anything
> to get it so not really any reason to use the callback.
>
I had understood that you didn't want to see of_* functions used in the
driver, that's why I was hesitant about the first one.
I would be more for keeping the binding (that, by the way, is not really
used, the interrupts weren't implemented at all in the driver before me
doing that) for just one reason, which I'm going to explain with "sort
of" pseudocode (just to be shorter):
EXAMPLE 1:
labibb {
interrupts = <0 0>, <1 0>, <2 0>, <3 0>;
interrupt-names = "lab-sc", "lab-ocp", "ibb-sc", "ibb-ocp";
lab { };
ibb { };
};
for (i = 0; i < max_vregs; i++) {
short_circuit = platform_get_irq(pdev, i * 2);
overcurrent = platform_get_irq(pdev, ((i * 2) + 1));
}
EXAMPLE 2:
snprintf strings for {lab,ibb}_{shortcircuit,overcurrent}, use
platform_get_irq_byname
(pdev, blah);
EXAMPLE 3:
labibb {
lab {
interrupts = <0 0>, <1 0>;
interrupt-names = "sc", "ocp";
};
ibb {
interrupts = <2 0>, <3 0>;
interrupt-names = "sc", "ocp";
};
};
for (i = 0; i < max_vregs; i++) {
short_circuit = of_irq_get_byname(node, "sc");
overcurrent = of_irq_get_byname(node, "ocp");
}
First of all, in the *EXAMPLE 1*, we may be declaring interrupts for
both LAB and IBB, but actually disabling one of the two regulators: in
this specific case (I have no idea why anyone would want to do that, but
evaluating all the cases anyway) the human readability would be way
lower, in my opinion, as that'd add a possible layer of confusion.
Also, I don't really like having to preallocate an array of chars and
snprintf names here and there (EXAMPLE 2) on the fly: in my eyes, it
looks a bit of a mess, but that's a highly personal opinion, many may
disagree.
In *EXAMPLE 3* everything looks more human readable and, in some way,
less error-prone, as we can just use two fixed strings and that's it,
without multiplying this and adding that.
I would go for keeping the current binding for the aforementioned
reasons. Before I go on sending a V2, I would like to know your opinion.
Do you agree?
Thanks,
-- Angelo
next prev parent reply other threads:[~2021-01-12 17:51 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-09 13:29 [PATCH 0/7] Really implement Qualcomm LAB/IBB regulators AngeloGioacchino Del Regno
2021-01-09 13:29 ` [PATCH 1/7] regulator: qcom-labibb: Implement voltage selector ops AngeloGioacchino Del Regno
2021-01-11 13:16 ` Mark Brown
2021-01-11 18:43 ` AngeloGioacchino Del Regno
2021-01-09 13:29 ` [PATCH 2/7] regulator: qcom-labibb: Implement current limiting AngeloGioacchino Del Regno
2021-01-09 13:29 ` [PATCH 3/7] regulator: qcom-labibb: Implement pull-down, softstart, active discharge AngeloGioacchino Del Regno
2021-01-09 13:29 ` [PATCH 4/7] dt-bindings: regulator: qcom-labibb: Document soft start properties AngeloGioacchino Del Regno
2021-01-10 17:18 ` Rob Herring
2021-01-10 18:01 ` AngeloGioacchino Del Regno
2021-01-09 13:29 ` [PATCH 5/7] regulator: qcom-labibb: Implement short-circuit and over-current IRQs AngeloGioacchino Del Regno
2021-01-11 13:57 ` Mark Brown
2021-01-11 19:14 ` AngeloGioacchino Del Regno
2021-01-11 19:23 ` AngeloGioacchino Del Regno
2021-01-11 21:06 ` AngeloGioacchino Del Regno
2021-01-12 17:29 ` Mark Brown
2021-01-12 17:49 ` AngeloGioacchino Del Regno [this message]
2021-01-13 17:40 ` Mark Brown
2021-01-09 13:29 ` [PATCH 6/7] dt-bindings: regulator: qcom-labibb: Document SCP/OCP interrupts AngeloGioacchino Del Regno
2021-01-09 13:29 ` [PATCH 7/7] arm64: dts: pmi8998: Add the right interrupts for LAB/IBB SCP and OCP AngeloGioacchino Del Regno
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=e872bc39-a941-d552-5145-49f40d6fa657@somainline.org \
--to=angelogioacchino.delregno@somainline.org \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@somainline.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marijn.suijten@somainline.org \
--cc=martin.botka@somainline.org \
--cc=phone-devel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=sumit.semwal@linaro.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;
as well as URLs for NNTP newsgroup(s).