public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Sam Winchenbach <sam.winchenbach@framepointer.org>
Cc: linux-kernel@vger.kernel.org, lars@metafoo.de,
	Michael.Hennerich@analog.com, antoniu.miclaus@analog.com,
	jic23@kernel.org, robh@kernel.org, krzk+dt@kernel.org,
	conor+dt@kernel.org, linux-iio@vger.kernel.org,
	devicetree@vger.kernel.org
Subject: Re: [PATCH v4 2/2] dt-bindings: iio: filter: Add lpf/hpf freq margins
Date: Wed, 26 Feb 2025 22:22:03 +0100	[thread overview]
Message-ID: <05e56d15-059b-425b-9e55-66993d988f8d@kernel.org> (raw)
In-Reply-To: <Z79K8Ag4SJYtJTtM@65YTFL3.secure.tethers.com>

On 26/02/2025 18:10, Sam Winchenbach wrote:
> On Wed, Feb 26, 2025 at 09:03:13AM +0100, Krzysztof Kozlowski wrote:
>> On Tue, Feb 25, 2025 at 08:46:12AM -0500, Sam Winchenbach wrote:
>>> Adds two properties to add a margin when automatically finding the
>>> corner frequencies.
>>>
>>> Signed-off-by: Sam Winchenbach <sam.winchenbach@framepointer.org>
>>> ---
>>>  .../bindings/iio/filter/adi,admv8818.yaml          | 14 ++++++++++++++
>>>  1 file changed, 14 insertions(+)
>>
>> Bindings are before users (see DT submitting patches), so this should be
>> re-ordered.
>>
>>>
>>> diff --git a/Documentation/devicetree/bindings/iio/filter/adi,admv8818.yaml b/Documentation/devicetree/bindings/iio/filter/adi,admv8818.yaml
>>> index b77e855bd594..2acdbd8d84cb 100644
>>> --- a/Documentation/devicetree/bindings/iio/filter/adi,admv8818.yaml
>>> +++ b/Documentation/devicetree/bindings/iio/filter/adi,admv8818.yaml
>>> @@ -44,6 +44,18 @@ properties:
>>>    '#clock-cells':
>>>      const: 0
>>>  
>>> +  adi,lpf-margin-hz:
>>> +    description:
>>> +      Sets minimum low-pass corner frequency to the frequency of rf_in plus
>>> +      this value when in auto mode.
>>> +    default: 0
>>> +
>>> +  adi,hpf-margin-hz:
>>> +    description:
>>> +      Sets maximum high-pass corner frequency to the frequency of rf_in minus
>>> +      this value when in auto mode.
>>
>> IIUC, these are two bounds - lower and upper - in relation to something
>> else (like rf_in frequency)? If so, make it an array (naming to be
>> discuss, I assume you know better what's that):
> 
> It is true that these are both related to rf_in but both the low and high pass
> filters can operate independently. Logically, IMO, it makes more sense to have


You mean you can set only low or high pass and keep other as default?
But what is the default then - something from reset value or "0" means
disabled?

> them as separate controls but I am happy to put them into an array if that is
> the idiomatic approach to situations like this. That said, I am having a
> difficult time getting dt_binding_check to pass when I have an array of uint64.
> 
> When listing two items, as in your example below, I get the following:
> adi,admv8818.example.dtb: admv8818@0: adi,filter-margins-hz: [[0, 30000000], [0, 30000000]] is too long

Tricky to say without seeing your code. Magic crystal ball had
malfunction today.

Best regards,
Krzysztof

  reply	other threads:[~2025-02-26 21:22 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-25 13:46 [PATCH v4 1/2] iio: filter: admv8818: fix range calculation Sam Winchenbach
2025-02-25 13:46 ` [PATCH v4 2/2] dt-bindings: iio: filter: Add lpf/hpf freq margins Sam Winchenbach
2025-02-26  8:03   ` Krzysztof Kozlowski
2025-02-26 17:10     ` Sam Winchenbach
2025-02-26 21:22       ` Krzysztof Kozlowski [this message]
2025-02-26 22:16         ` Sam Winchenbach
2025-03-03  8:13           ` Krzysztof Kozlowski
2025-03-03 13:31             ` Sam Winchenbach
2025-03-03 14:16               ` Krzysztof Kozlowski
2025-03-03 14:48                 ` Sam Winchenbach
2025-02-27 20:23 ` [PATCH v4 1/2] iio: filter: admv8818: fix range calculation kernel test robot
2025-02-27 21:20   ` Sam Winchenbach
2025-03-04 23:55 ` Jonathan Cameron
2025-03-05 12:58   ` Sam Winchenbach
2025-03-08 17:25     ` Jonathan Cameron

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=05e56d15-059b-425b-9e55-66993d988f8d@kernel.org \
    --to=krzk@kernel.org \
    --cc=Michael.Hennerich@analog.com \
    --cc=antoniu.miclaus@analog.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jic23@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=sam.winchenbach@framepointer.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