All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
To: Chris Ruehl <chris.ruehl@gtsys.com.hk>
Cc: <linux-iio@vger.kernel.org>
Subject: Re: inquiry: where to place iio/ bandpass filter driver
Date: Wed, 22 Apr 2020 18:25:40 +0100	[thread overview]
Message-ID: <20200422182540.0000410f@huawei.com> (raw)
In-Reply-To: <a67b5e24-94df-cc84-73ae-004c0a27a26a@gtsys.com.hk>

On Tue, 21 Apr 2020 08:37:13 +0800
Chris Ruehl <chris.ruehl@gtsys.com.hk> wrote:

> Jonathan,
> 
> On 17/4/2020 5:23 pm, Jonathan Cameron wrote:
> > On Thu, 16 Apr 2020 11:48:31 +0800
> > Chris Ruehl <chris.ruehl@gtsys.com.hk> wrote:
> >  
> >> Hi,
> >>
> >> I'm working on implementation for ltc6602 dual match bandpass
> >> filter spi driver.
> >> The driver tree has a iio/frequency which has PLLs at time beeing
> >> and I wondering to drop my driver there or have a new directory
> >> freqfilter or bpf ?
> >>
> >> This isn't urgent, but would be nice to know.
> >>  
> > Perhaps iio/afe?  It's a type of analog front end (or might be used
> > as such). Is the intent to wrap these up as a consumer of an ADC?
> > So they ultimately provide a unified device presentation to
> > userspace of the ADC + filters. Or are we looking at simply
> > controlling a filter which doesn't connect to an ADC or DAC visible
> > to us?
> >
> > I'm not against a new directory for filters though.  Don't be
> > specific on the type unless we need to be :)
> >
> > Jonathan  
> I place the driver into afe, makes totally sense to me, but have to
> create a directory
> linux/iio/afe which is not existing while I write this.

curious.  It was introduced in 4.18.

What tree are you working on top of?

> 
> will be then:
> drivers/iio/afe/ltc6602.c
> include/linux/iio/afe/ltc6602.h

possibly on the header, but most IIO drivers don't have their own
header. For kernel code it is preferred to put as much as possible
directly in the c file.  The exceptions are drivers needing multiple
files or where the header is used in conjunction with a DT binding.

> add entry to drivers/iio/afe/Kconfig + Makefile.
> 
> If i have the driver ready and checked I send my patches

Great.

Jonathan
> 
> Cheers
> Chris
> 
> >> Regards
> >> Chris  
> >  
> 


  reply	other threads:[~2020-04-22 17:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-16  3:48 inquiry: where to place iio/ bandpass filter driver Chris Ruehl
2020-04-17  9:23 ` Jonathan Cameron
2020-04-21  0:37   ` Chris Ruehl
2020-04-22 17:25     ` Jonathan Cameron [this message]
2020-04-23  4:52       ` Chris Ruehl

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=20200422182540.0000410f@huawei.com \
    --to=jonathan.cameron@huawei.com \
    --cc=chris.ruehl@gtsys.com.hk \
    --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.