From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: "Paller, Kim Seer" <KimSeer.Paller@analog.com>
Cc: Jonathan Cameron <jic23@kernel.org>,
Lars-Peter Clausen <lars@metafoo.de>,
"Hennerich, Michael" <Michael.Hennerich@analog.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
kernel test robot <lkp@intel.com>
Subject: Re: [PATCH v3 1/2] dt-bindings: iio: frequency: add admfm2000
Date: Thu, 23 Nov 2023 09:32:27 +0100 [thread overview]
Message-ID: <7fb62b63-25d5-42f2-9803-61e813003fd5@linaro.org> (raw)
In-Reply-To: <PH0PR03MB7141957ABE612DB1275B1309F9B9A@PH0PR03MB7141.namprd03.prod.outlook.com>
On 23/11/2023 09:24, Paller, Kim Seer wrote:
>>>>> ---
>>>>> V2 -> V3: Adjusted indentation to resolve wrong indentation warning.
>>>>> Changed node name to converter. Updated the descriptions to clarify
>>>>> the properties.
>>>>
>>>>
>>>>> +title: ADMFM2000 Dual Microwave Down Converter
>>>>> +
>>>>> +maintainers:
>>>>> + - Kim Seer Paller <kimseer.paller@analog.com>
>>>>> +
>>>>> +description:
>>>>> + Dual microwave down converter module with input RF and LO frequency
>>>> ranges
>>>>> + from 0.5 to 32 GHz and an output IF frequency range from 0.1 to 8 GHz.
>>>>> + It consists of a LNA, mixer, IF filter, DSA, and IF amplifier for each down
>>>>> + conversion path.
>>>>> +
>>>>> +properties:
>>>>> + compatible:
>>>>> + enum:
>>>>> + - adi,admfm2000
>>>>> +
>>>>> + switch1-gpios:
>>>>> + items:
>>>>> + - description:
>>>>> + Setting B15 GPIO to high and B16 GPIO to low will result in channel
>> 1
>>>>> + being in Direct IF mode.
>>>>> + - description:
>>>>> + Setting B15 GPIO to low and B16 GPIO to high will result in channel
>> 1
>>>>> + being in Mixer mode.
>>>>
>>>> This still does not tell which one is B15 and which is B16. I am asking
>>>> this for third time.
>>>>
>>>> items:
>>>> - description: B15 GPIO, when high (and B16 low) channel 1 is in
>>>> Direct IF mode
>>>
>>> I understand now, thank you. I was also wondering if this applies to the
>>> attenuation-gpios, or if I should keep it as is?
>>
>> Yes, something like this applies to all your properties with multiple
>> entries. You need to define the order.
>
> Before I send a new patch/commit, could you please check this one if it is
> properly defined?
>
> attenuation1-gpios:
> items:
> - description: C14 GPIO, when low (and C15, C16, D14, D15 high)
> channel 1 attenuation is 1 dB.
> - description: C15 GPIO, when low (and C14, C16, D14, D15 high)
> channel 1 attenuation is 2 dB.
> - description: C16 GPIO, when low (and C14, C15, D14, D15 high)
> channel 1 attenuation is 4 dB.
> - description: D14 GPIO, when low (and C14, C15, C16, D15 high)
> channel 1 attenuation is 8 dB.
> - description: D15 GPIO, when low (and C14, C15, C16, D14 high)
> channel 1 attenuation is 16 dB.
This actually could be written in easier way like:
attenuation1-gpios:
description: |
Choice of attenuation:
C14 C15 ......
1 0 0 0 - 1 dB
0 1 0 0 - 2 dB
...
items:
- description: C14 GPIO
- description: C15 GPIO
- description: C16 GPIO
- description: D14 GPIO
- description: D15 GPIO
or whatever is easy to understand. The point is that you must define the
order of GPIOs and explain their meaning.
Best regards,
Krzysztof
prev parent reply other threads:[~2023-11-23 8:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-22 10:58 [PATCH v3 1/2] dt-bindings: iio: frequency: add admfm2000 Kim Seer Paller
2023-11-22 10:58 ` [PATCH v3 2/2] iio: frequency: admfm2000: New driver Kim Seer Paller
2023-11-22 18:21 ` [PATCH v3 1/2] dt-bindings: iio: frequency: add admfm2000 Krzysztof Kozlowski
2023-11-23 6:13 ` Paller, Kim Seer
2023-11-23 7:20 ` Krzysztof Kozlowski
2023-11-23 8:24 ` Paller, Kim Seer
2023-11-23 8:32 ` Krzysztof Kozlowski [this message]
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=7fb62b63-25d5-42f2-9803-61e813003fd5@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=KimSeer.Paller@analog.com \
--cc=Michael.Hennerich@analog.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jic23@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=robh+dt@kernel.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).