From: Jonathan Cameron <jic23@kernel.org>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Antoniu Miclaus <antoniu.miclaus@analog.com>,
robh@kernel.org, conor+dt@kernel.org, linux-iio@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-pwm@vger.kernel.org
Subject: Re: [PATCH v12 5/9] dt-bindings: iio: adc: add ad485x axi variant
Date: Tue, 11 Feb 2025 19:53:51 +0000 [thread overview]
Message-ID: <20250211195351.5331b2e6@jic23-huawei> (raw)
In-Reply-To: <20250211-industrious-rugged-gecko-9b5c02@krzk-bin>
On Tue, 11 Feb 2025 09:16:31 +0100
Krzysztof Kozlowski <krzk@kernel.org> wrote:
> On Sat, Feb 08, 2025 at 04:20:58PM +0000, Jonathan Cameron wrote:
> > On Fri, 7 Feb 2025 16:09:14 +0200
> > Antoniu Miclaus <antoniu.miclaus@analog.com> wrote:
> >
> > > Add a new compatible and related bindings for the fpga-based
> > > AD485x AXI IP core, a variant of the generic AXI ADC IP.
> > >
> > > The AXI AD485x IP is a very similar HDL (fpga) variant of the
> > > generic AXI ADC IP, intended to control ad485x familiy.
> >
> > Hmm. Should we name this after a specific part? Very unlikely
> > the wildcard will go wrong here because of how specific this
> > binding is anyway but we should perhaps stick to normal rules
> > of no wild cards.
>
> I am pretty sure we had this discussion about this or other block
> already and we reached some sort of concensus... which is undocumented
> in commit msg, so we are doomed to repeat the discussion.
>
Having just seen similar the axi-ad7606x support. I think the key bit
I was missing here is that ADI has published the firmware under the
name with wild card. If they shoot themselves in the foot in future
then fair enough. I'm fine with the wild card though a statement
in the commit to make me notice that detail would have been great!
Jonathan
> Best regards,
> Krzysztof
>
next prev parent reply other threads:[~2025-02-11 19:53 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-07 14:09 [PATCH v12 0/9] Add support for AD485x DAS Family Antoniu Miclaus
2025-02-07 14:09 ` [PATCH v12 1/9] iio: backend: add API for interface get Antoniu Miclaus
2025-02-07 14:09 ` [PATCH v12 2/9] iio: backend: add support for data size set Antoniu Miclaus
2025-02-07 14:09 ` [PATCH v12 3/9] iio: backend: add API for oversampling Antoniu Miclaus
2025-02-07 14:09 ` [PATCH v12 4/9] iio: adc: adi-axi-adc: add interface type Antoniu Miclaus
2025-02-07 14:09 ` [PATCH v12 5/9] dt-bindings: iio: adc: add ad485x axi variant Antoniu Miclaus
2025-02-08 16:20 ` Jonathan Cameron
2025-02-11 8:16 ` Krzysztof Kozlowski
2025-02-11 19:53 ` Jonathan Cameron [this message]
2025-02-07 14:09 ` [PATCH v12 6/9] iio: adc: adi-axi-adc: set data format Antoniu Miclaus
2025-02-07 20:51 ` David Lechner
2025-02-08 16:22 ` Jonathan Cameron
2025-02-11 19:55 ` Jonathan Cameron
2025-02-07 14:09 ` [PATCH v12 7/9] iio: adc: adi-axi-adc: add oversampling Antoniu Miclaus
2025-02-08 16:23 ` Jonathan Cameron
2025-02-07 14:09 ` [PATCH v12 8/9] dt-bindings: iio: adc: add ad4851 Antoniu Miclaus
2025-02-07 14:09 ` [PATCH v12 9/9] iio: adc: ad4851: add ad485x driver Antoniu Miclaus
2025-02-07 20:51 ` David Lechner
2025-02-08 16:28 ` 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=20250211195351.5331b2e6@jic23-huawei \
--to=jic23@kernel.org \
--cc=antoniu.miclaus@analog.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=robh@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