devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Nuno Sá" <noname.nuno@gmail.com>
To: andy.shevchenko@gmail.com, Nuno Sa <nuno.sa@analog.com>
Cc: linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
	Lars-Peter Clausen <lars@metafoo.de>,
	Michael Hennerich <Michael.Hennerich@analog.com>,
	 Jonathan Cameron <jic23@kernel.org>,
	Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Conor Dooley <conor+dt@kernel.org>,
	 Frank Rowand <frowand.list@gmail.com>,
	Olivier Moysan <olivier.moysan@foss.st.com>
Subject: Re: [PATCH v8 5/7] iio: add the IIO backend framework
Date: Mon, 05 Feb 2024 11:02:20 +0100	[thread overview]
Message-ID: <50e29a95f5a620179f19056fd7948da5e093d980.camel@gmail.com> (raw)
In-Reply-To: <Zb-yr0u_a9-vE86t@surfacebook.localdomain>

On Sun, 2024-02-04 at 17:52 +0200, andy.shevchenko@gmail.com wrote:
> Fri, Feb 02, 2024 at 04:08:36PM +0100, Nuno Sa kirjoitti:
> > This is a Framework to handle complex IIO aggregate devices.
> > 
> > The typical architecture is to have one device as the frontend device which
> > can be "linked" against one or multiple backend devices. All the IIO and
> > userspace interface is expected to be registers/managed by the frontend
> > device which will callback into the backends when needed (to get/set
> > some configuration that it does not directly control).
> > 
> > The basic framework interface is pretty simple:
> >  - Backends should register themselves with @devm_iio_backend_register()
> >  - Frontend devices should get backends with @devm_iio_backend_get()
> 
> ...
> 
> > + * Copyright (C) 2023 Analog Devices Inc.
> 
> 2024 as well?
> 
> ...
> 
> > +#include <linux/cleanup.h>
> > +#include <linux/device.h>
> > +#include <linux/err.h>
> > +#include <linux/list.h>
> > +#include <linux/module.h>
> > +#include <linux/mutex.h>
> > +#include <linux/property.h>
> > +#include <linux/slab.h>
> 
> Missing types.h and maybe more. (E.g., IIRC linux/err.h doesn't cover
> linux/errno.h for Linux internal error codes, >= 512.)

Just sanity checking... EOPNOTSUPP is define in [1] but I don't really think we
should be including that directly (don't see anyone doing it at least)? I guess I
should include <linux/errno.h>, right?

[1]: https://elixir.bootlin.com/linux/v5.0.21/source/include/uapi/asm-generic/errno.h#L78


- Nuno Sá

  parent reply	other threads:[~2024-02-05 10:02 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-02 15:08 [PATCH v8 0/7] iio: add new backend framework Nuno Sa via B4 Relay
2024-02-02 15:08 ` [PATCH v8 1/7] dt-bindings: adc: ad9467: add new io-backend property Nuno Sa via B4 Relay
2024-02-02 15:08 ` [PATCH v8 2/7] dt-bindings: adc: axi-adc: update bindings for backend framework Nuno Sa via B4 Relay
2024-02-02 16:35   ` Rob Herring
2024-02-02 21:38   ` David Lechner
2024-02-04  7:30     ` Sa, Nuno
2024-02-04 14:51       ` Jonathan Cameron
2024-02-02 15:08 ` [PATCH v8 3/7] of: property: add device link support for io-backends Nuno Sa via B4 Relay
2024-02-04 14:55   ` Jonathan Cameron
2024-02-02 15:08 ` [PATCH v8 4/7] iio: buffer-dmaengine: export buffer alloc and free functions Nuno Sa via B4 Relay
2024-02-02 15:08 ` [PATCH v8 5/7] iio: add the IIO backend framework Nuno Sa via B4 Relay
2024-02-04 15:52   ` andy.shevchenko
2024-02-05  8:44     ` Nuno Sá
2024-02-05 10:02     ` Nuno Sá [this message]
2024-02-06  8:26       ` Nuno Sá
2024-02-02 15:08 ` [PATCH v8 6/7] iio: adc: ad9467: convert to " Nuno Sa via B4 Relay
2024-02-02 15:08 ` [PATCH v8 7/7] iio: adc: adi-axi-adc: move " Nuno Sa via B4 Relay
2024-02-04 14:59 ` [PATCH v8 0/7] iio: add new " Jonathan Cameron
2024-02-04 16:01   ` 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=50e29a95f5a620179f19056fd7948da5e093d980.camel@gmail.com \
    --to=noname.nuno@gmail.com \
    --cc=Michael.Hennerich@analog.com \
    --cc=andy.shevchenko@gmail.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=frowand.list@gmail.com \
    --cc=jic23@kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=nuno.sa@analog.com \
    --cc=olivier.moysan@foss.st.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).