From: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
To: Akash Borde <Akash.Borde@heilatech.com>
Cc: "linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
Emily Guthrie <Emily.Guthrie@heilatech.com>,
Erika Silva <Erika.Silva@heilatech.com>,
Bart Oegema <bart.oegema@heilatech.com>
Subject: Re: [ti-dac5571] Checking compatibility of TI DAC with kernel driver
Date: Wed, 24 Jul 2024 13:48:42 +0100 [thread overview]
Message-ID: <20240724134842.00001c29@Huawei.com> (raw)
In-Reply-To: <1261F7BA-D202-4BED-ADB4-87EB75E2C068@heilatech.com>
On Tue, 23 Jul 2024 23:07:19 +0000
Akash Borde <Akash.Borde@heilatech.com> wrote:
> Hi,
>
> I'd like to see if the TI DAC8563 is potentially compatible with this existing device driver in the main branch of the kernel.
>
> This is the part I'm evaluating for my board: https://www.ti.com/lit/ds/symlink/dac8563.pdf
> Here is the most similar kernel driver I could find: https://github.com/torvalds/linux/blob/master/drivers/iio/dac/ti-dac5571.c
>
> I see very similar DACs in the compatible list of this driver, but not the exact part number family that I'm looking for.
> Is there a way to verify a DAC or family of DACs' compatibility with existing drivers?
Sadly best bet is to open the datasheets side by side and verify if the
devices are compatible in all software visible ways.
It's a pain to do but only way to know if it will continue to be compatible
in the future if new driver features are added.
Jonathan
>
> Thanks!
>
> Akash Borde | Embedded Systems | Heila Technologies
> https://heilatech.com/
>
next prev parent reply other threads:[~2024-07-24 12:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-23 23:07 [ti-dac5571] Checking compatibility of TI DAC with kernel driver Akash Borde
2024-07-24 12:48 ` Jonathan Cameron [this message]
2024-07-24 17:48 ` [EXT]: " Akash Borde
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=20240724134842.00001c29@Huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=Akash.Borde@heilatech.com \
--cc=Emily.Guthrie@heilatech.com \
--cc=Erika.Silva@heilatech.com \
--cc=bart.oegema@heilatech.com \
--cc=linux-iio@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.