From: Giuliano Belinassi <giuliano.belinassi@gmail.com>
To: lars@metafoo.de, Michael.Hennerich@analog.com, jic23@kernel.org,
knaack.h@gmx.de, pmeerw@pmeerw.net, gregkh@linuxfoundation.org,
renatogeh@gmail.com
Cc: linux-iio@vger.kernel.org, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org, kernel-usp@googlegroups.com
Subject: [PATCH v2 0/2] pattern generation and gain update
Date: Thu, 8 Nov 2018 11:03:02 -0200 [thread overview]
Message-ID: <cover.1541681371.git.giuliano.belinassi@usp.br> (raw)
This series of patches fixes a bug in ad717x chips where the PAT2 bit
was wrongly read as a GAIN bit. It also refactors the pattern_mask
generation with the PAT bits.
Changelog:
* v2
- Squashed is_add778x flag commit with the gain update fix
- Changed u8 is_add778x to bool is_add778x
- Set pattern and pattern_mask as macros
- Aligned identation of macros
Giuliano Belinassi (2):
staging: iio: ad7780: check if ad778x before gain update
staging: iio: ad7780: generates pattern_mask from PAT bits
drivers/staging/iio/adc/ad7780.c | 55 ++++++++++++++++++++------------
1 file changed, 35 insertions(+), 20 deletions(-)
--
2.19.1
next reply other threads:[~2018-11-08 22:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-08 13:03 Giuliano Belinassi [this message]
2018-11-08 13:03 ` [PATCH v2 1/2] staging: iio: ad7780: check if ad778x before gain update Giuliano Belinassi
2018-11-08 13:44 ` Ardelean, Alexandru
2018-11-08 13:44 ` Ardelean, Alexandru
2018-11-11 12:58 ` Jonathan Cameron
2018-11-12 7:57 ` Ardelean, Alexandru
2018-11-12 7:57 ` Ardelean, Alexandru
2018-11-16 18:32 ` Jonathan Cameron
2018-11-08 18:26 ` Tomasz Duszynski
2018-11-09 22:15 ` Giuliano Augusto Faulin Belinassi
2018-11-11 13:00 ` Jonathan Cameron
2018-11-08 13:03 ` [PATCH v2 2/2] staging: iio: ad7780: generates pattern_mask from PAT bits Giuliano Belinassi
2018-11-08 13:51 ` Ardelean, Alexandru
2018-11-08 13:51 ` Ardelean, Alexandru
2018-11-09 22:18 ` Giuliano Augusto Faulin Belinassi
2018-11-11 13:04 ` 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=cover.1541681371.git.giuliano.belinassi@usp.br \
--to=giuliano.belinassi@gmail.com \
--cc=Michael.Hennerich@analog.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=jic23@kernel.org \
--cc=kernel-usp@googlegroups.com \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pmeerw@pmeerw.net \
--cc=renatogeh@gmail.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 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.