Linux IIO development
 help / color / mirror / Atom feed
From: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
To: "Nuno Sá" <noname.nuno@gmail.com>
Cc: Nuno Sa <nuno.sa@analog.com>, <linux-iio@vger.kernel.org>,
	"Jonathan Cameron" <jic23@kernel.org>
Subject: Re: [RFC PATCH 0/3] Add converter framework
Date: Thu, 31 Aug 2023 10:28:06 +0100	[thread overview]
Message-ID: <20230831102806.000026cd@Huawei.com> (raw)
In-Reply-To: <d4eead3eedb99e252f7c022ce5572a3a307b9b1e.camel@gmail.com>

On Thu, 31 Aug 2023 10:20:20 +0200
Nuno Sá <noname.nuno@gmail.com> wrote:

> On Wed, 2023-08-30 at 17:29 +0100, Jonathan Cameron wrote:
> > On Fri, 4 Aug 2023 16:53:38 +0200
> > Nuno Sa <nuno.sa@analog.com> wrote:
> >   
> > > This is the initial RFC following the discussion in [1]. I'm aware this is
> > > by no means ready for inclusion and it's not even compilable since in
> > > the RFC I did not included the patch to add component_compare_fwnode()
> > > and component_release_fwnode().   
> > 
> > Whilst I haven't read this through yet, I suspect Olivier will be able to
> > offer some insight on some of this and likewise you may be able to
> > point out pitfalls etc in his series (I see you did some review already :)
> > 
> > https://lore.kernel.org/linux-iio/20230727150324.1157933-1-olivier.moysan@foss.st.com/
> > 
> > Both are about multiple interacting components of an overall datapath.
> > Whether there is commonality isn't yet clear to me.
> >   
> 
> I made a very general comment in that series but I need to look better at it. Not
> sure if we can merge them together but let's see...

Great. I wasn't sure either!  If nothing else more cross review is always
good even if we decide we need two frameworks.

My one takeaway from looking at this is I need to understand the component
framework better and do some messing around with simple cases before I'll
be confident on how this works.  Maybe we can get some input from developers
of that framework on future versions?

Jonathan

  reply	other threads:[~2023-08-31  9:28 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-04 14:53 [RFC PATCH 0/3] Add converter framework Nuno Sa
2023-08-04 14:53 ` [RFC PATCH 1/3] iio: addac: add new " Nuno Sa
2023-08-30 17:02   ` Jonathan Cameron
2023-08-31  9:32     ` Nuno Sá
2023-09-03 10:56       ` Jonathan Cameron
2023-09-04 14:14         ` Nuno Sá
2023-09-04 15:31           ` Jonathan Cameron
2023-11-13 17:20             ` Olivier MOYSAN
2023-11-14  9:03               ` Nuno Sá
2023-11-16 15:42                 ` Olivier MOYSAN
2023-08-04 14:53 ` [RFC PATCH 2/3] iio: adc: ad9647: add based on " Nuno Sa
2023-08-30 17:13   ` Jonathan Cameron
2023-08-04 14:53 ` [RFC PATCH 3/3] iio: adc: adi-axi-adc: add based on new " Nuno Sa
2023-08-30 17:15   ` Jonathan Cameron
2023-08-30 16:29 ` [RFC PATCH 0/3] Add " Jonathan Cameron
2023-08-30 16:30   ` Jonathan Cameron
2023-08-31  8:20   ` Nuno Sá
2023-08-31  9:28     ` Jonathan Cameron [this message]
2023-08-31 10:58       ` Nuno Sá

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=20230831102806.000026cd@Huawei.com \
    --to=jonathan.cameron@huawei.com \
    --cc=jic23@kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=noname.nuno@gmail.com \
    --cc=nuno.sa@analog.com \
    /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