From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Cc: jagath jogj <jagathjog1996@gmail.com>,
jic23@kernel.org, lars@metafoo.de, aardelean@deviqon.com,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: IIO Device Driver for Maxim DS3502 potentiometer
Date: Fri, 28 Jan 2022 16:42:59 +0200 [thread overview]
Message-ID: <YfQA8wRpauq058WK@smile.fi.intel.com> (raw)
In-Reply-To: <20220128103554.000028ff@Huawei.com>
On Fri, Jan 28, 2022 at 10:35:54AM +0000, Jonathan Cameron wrote:
> On Fri, 28 Jan 2022 09:11:28 +0530
> jagath jogj <jagathjog1996@gmail.com> wrote:
>
> > Hello,
> >
> > I have a Maxim DS3502 potentiometer breakout and I have written an IIO
> > driver for learning purposes and tested with Raspberry pi and wanted
> > to send patches of the driver for the IIO sub-system.
> >
> > Can I send the patches for DS3502 POT for review?
> >
> > The setup used to write driver
> > Raspberry pi 3b
> > DS3502 breakout board
> > Raspberry pi latest kernel branch - https://github.com/raspberrypi/linux
> Welcome to IIO.
>
> Absolutely on sending the patches for review.
> You'll need to rebase them on latest mainline from kernel.org
> (pick a tagged version which would currently be 5.17-rc1_
>
> and then follow the documentation for how to submit a patch in
> https://www.kernel.org/doc/html/latest/process/submitting-patches.html
>
> Feel free to ask if you have any questions about the process.
>
> Looking forwards to seeing your code.
Agree with Jonathan.
One remark though, can you double check that drivers/iio/potentiometer
doesn't have any similar driver that can be expanded (usually it can be
done by analyzing a register file of the devices, like register offsets
and their meanings or bit fields)?
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2022-01-28 14:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-28 3:41 jagath jogj
2022-01-28 10:35 ` Jonathan Cameron
2022-01-28 14:42 ` Andy Shevchenko [this message]
2022-01-29 4:54 ` jagath jogj
2022-01-30 13:07 ` Jonathan Cameron
2022-01-31 7:29 ` jagath jogj
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=YfQA8wRpauq058WK@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=aardelean@deviqon.com \
--cc=jagathjog1996@gmail.com \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®