From: Jonathan Cameron <jic23@kernel.org>
To: Prince Kumar <855princekumar@gmail.com>
Cc: linux-iio@vger.kernel.org
Subject: Re: Proposal Discussion: ADE9113 IIO Driver Development for Linux Kernel
Date: Mon, 10 Mar 2025 19:32:15 +0000 [thread overview]
Message-ID: <20250310193215.0f091dc0@jic23-huawei> (raw)
In-Reply-To: <CAMmuoAJy_GPL-7tfbrgH9U4T4UvUiDoHozw67BqadoV_nAJXog@mail.gmail.com>
On Mon, 10 Mar 2025 10:33:44 +0530
Prince Kumar <855princekumar@gmail.com> wrote:
> Hi Jonathan,
>
> Thanks for your valuable feedback! Your insights are really helpful in
> refining my approach and ensuring alignment with best practices.
>
> 1. DT Binding Flexibility:
> I initially considered making the DT binding adaptable for similar
> SPI-based ADCs to potentially support minor hardware variations with
> minimal changes. However, your point about maintainability makes
> sense, and I see that most existing bindings tend to be more specific.
> I’ll revisit this and reconsider whether a part-specific approach
> would be more appropriate. If there are examples of flexible but
> maintainable bindings worth looking into, I’d appreciate any pointers.
The problem with increasing flexibility is that in usually means
more complex matching rules (see allOf/oneOf statements in existing
bindings) to ensure we require what is needed for a given specific
device. Those are a lot harder to read than separate files but do
make sense if there are only one or two minor differences between
a small number of devices.
>
> 2. MCU-Assisted vs. Direct SPI:
> This was more of an exploratory idea rather than a fully defined
> plan. My initial thought was to assess whether offloading certain
> operations to an MCU (e.g., pre-processing or buffering) could offer
> benefits over direct SPI communication with the Linux system. Given
> that this isn’t a typical approach, I’ll take a step back and ensure I
> properly evaluate the feasibility and trade-offs before including it
> in the proposal. If there are existing implementations that explore
> similar optimizations, I’d be keen to study them.
There is SPI offload logic in the kernel that will merge this cycle.
(it's in the IIO tree on git.kernel.org togreg branch
Expanding that to MCU based handling (all implementations are currently
FPGA based) would be an interesting project. May be too complex to fit
in the timescale of a GSOC. Perhaps a valid stretch goal though if the
rest falls in place quickly.
Jonathan
next prev parent reply other threads:[~2025-03-10 19:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-03 16:45 Proposal Discussion: ADE9113 IIO Driver Development for Linux Kernel Prince Kumar
2025-03-09 16:26 ` Jonathan Cameron
2025-03-10 5:03 ` Prince Kumar
2025-03-10 19:32 ` Jonathan Cameron [this message]
2025-03-13 13:35 ` Prince Kumar
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=20250310193215.0f091dc0@jic23-huawei \
--to=jic23@kernel.org \
--cc=855princekumar@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox