From: "Ardelean, Alexandru" <alexandru.Ardelean-OyLXuOCK7orQT0dZR+AlfA@public.gmane.org>
To: "jic23-tko9wxEg+fIOOJlXag/Snyp2UmYkHbXO@public.gmane.org"
<jic23-tko9wxEg+fIOOJlXag/Snyp2UmYkHbXO@public.gmane.org>
Cc: "mark.rutland-5wv7dgnIgG8@public.gmane.org"
<mark.rutland-5wv7dgnIgG8@public.gmane.org>,
"linux-iio-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-iio-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"Hennerich,
Michael"
<Michael.Hennerich-OyLXuOCK7orQT0dZR+AlfA@public.gmane.org>,
"robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org"
<robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
"devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH 1/3] staging: iio: adc: ad7192: fix external frequency setting
Date: Wed, 17 Jan 2018 07:45:35 +0000 [thread overview]
Message-ID: <1516175133.4383.3.camel@analog.com> (raw)
In-Reply-To: <20180114123745.7a1180ca@archlinux>
On Sun, 2018-01-14 at 12:37 +0000, Jonathan Cameron wrote:
> On Wed, 10 Jan 2018 13:29:54 +0200
> <alexandru.ardelean@analog.com> wrote:
>
> > From: Alexandru Ardelean <alexandru.ardelean@analog.com>
> >
> > According to the datasheet:
> > * 0 - external crystal, connected from pin MCLK1 to MCLK2
>
> What frequency of crystal? My quick read of the datasheet
> implies this may be flexible. Possibly as flexible as
> the clock option...
I think you're right about this.
Will re-visit this.
Is it ok if I re-spin this as a standalone patch ?
Since I'm new around here, maybe it would probably be good to try to
send one patch at a time and resolve synchronization [between what I
deliver vs recommended ways of doing things].
>
>
> > * 1 - external clock, applied to MCLK2 pin
> > * 2 - internal 4.92 Mhz clock; pin MCLK2 is tristated
> > * 3 - internal 4.92 Mhz clock; internal clock is available on MCLK2
> >
> > Which means that the external clock value only has sense
> > for value 1 (AD7192_CLK_EXT_MCLK2).
> >
> > Also added range validation for the external frequency
> > setting, which the datasheet mentions that it's
> > between 2.4576 and 5.12 Mhz.
> >
> > Signed-off-by: Alexandru Ardelean <alexandru.ardelean@analog.com>
> > ---
> > drivers/staging/iio/adc/ad7192.c | 22 +++++++++++++++-------
> > 1 file changed, 15 insertions(+), 7 deletions(-)
> >
> > diff --git a/drivers/staging/iio/adc/ad7192.c
> > b/drivers/staging/iio/adc/ad7192.c
> > index 7f204013d6d4..7bc04101d133 100644
> > --- a/drivers/staging/iio/adc/ad7192.c
> > +++ b/drivers/staging/iio/adc/ad7192.c
> > @@ -141,6 +141,8 @@
> > #define AD7192_GPOCON_P1DAT BIT(1) /* P1 state */
> > #define AD7192_GPOCON_P0DAT BIT(0) /* P0 state */
> >
> > +#define AD7192_EXT_FREQ_MHZ_MIN 2457600
> > +#define AD7192_EXT_FREQ_MHZ_MAX 5120000
> > #define AD7192_INT_FREQ_MHZ 4915200
> >
> > /* NOTE:
> > @@ -217,6 +219,12 @@ static int ad7192_calibrate_all(struct
> > ad7192_state *st)
> > ARRAY_SIZE(ad7192_calib_arr));
> > }
> >
> > +static inline bool ad7192_valid_external_frequency(u32 freq)
> > +{
> > + return (freq >= AD7192_EXT_FREQ_MHZ_MIN &&
> > + freq <= AD7192_EXT_FREQ_MHZ_MAX);
> > +}
> > +
> > static int ad7192_setup(struct ad7192_state *st,
> > const struct ad7192_platform_data *pdata)
> > {
> > @@ -245,16 +253,16 @@ static int ad7192_setup(struct ad7192_state
> > *st,
> >
> > switch (pdata->clock_source_sel) {
> > case AD7192_CLK_EXT_MCLK1_2:
> > - case AD7192_CLK_EXT_MCLK2:
> > - st->mclk = AD7192_INT_FREQ_MHZ;
> > - break;
> > case AD7192_CLK_INT:
> > case AD7192_CLK_INT_CO:
> > - if (pdata->ext_clk_hz)
> > - st->mclk = pdata->ext_clk_hz;
> > - else
> > - st->mclk = AD7192_INT_FREQ_MHZ;
> > + st->mclk = AD7192_INT_FREQ_MHZ;
> > break;
> > + case AD7192_CLK_EXT_MCLK2:
> > + if (ad7192_valid_external_frequency(pdata-
> > >clock_source_sel)) {
> > + st->mclk = pdata->clock_source_sel;
> > + break;
> > + }
> > + /* FALLTHROUGH */
> > default:
> > ret = -EINVAL;
> > goto out;
>
>
next prev parent reply other threads:[~2018-01-17 7:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-10 11:29 [PATCH 1/3] staging: iio: adc: ad7192: fix external frequency setting alexandru.ardelean-OyLXuOCK7orQT0dZR+AlfA
[not found] ` <20180110112956.23931-1-alexandru.ardelean-OyLXuOCK7orQT0dZR+AlfA@public.gmane.org>
2018-01-10 11:29 ` [PATCH 2/3] staging: iio: adc: ad7192: add device-tree support to driver alexandru.ardelean-OyLXuOCK7orQT0dZR+AlfA
2018-01-10 11:29 ` [PATCH 3/3] staging: iio: docs: add ad7192 doc to detail dt usage alexandru.ardelean-OyLXuOCK7orQT0dZR+AlfA
[not found] ` <20180110112956.23931-3-alexandru.ardelean-OyLXuOCK7orQT0dZR+AlfA@public.gmane.org>
2018-01-14 12:56 ` Jonathan Cameron
2018-01-18 13:16 ` Ardelean, Alexandru
2018-01-14 12:37 ` [PATCH 1/3] staging: iio: adc: ad7192: fix external frequency setting Jonathan Cameron
2018-01-17 7:45 ` Ardelean, Alexandru [this message]
[not found] ` <1516175133.4383.3.camel-OyLXuOCK7orQT0dZR+AlfA@public.gmane.org>
2018-01-20 15:28 ` 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=1516175133.4383.3.camel@analog.com \
--to=alexandru.ardelean-oylxuock7orqt0dzr+alfa@public.gmane.org \
--cc=Michael.Hennerich-OyLXuOCK7orQT0dZR+AlfA@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=jic23-tko9wxEg+fIOOJlXag/Snyp2UmYkHbXO@public.gmane.org \
--cc=linux-iio-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mark.rutland-5wv7dgnIgG8@public.gmane.org \
--cc=robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.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).