linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: marex@denx.de (Marek Vasut)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] iio: mxs: Add MX23 support into the IIO driver
Date: Mon, 21 Jan 2013 22:00:36 +0100	[thread overview]
Message-ID: <201301212200.36917.marex@denx.de> (raw)
In-Reply-To: <CAHXqBFLQUY6g6p988MVkk=sRu44B5tEzDMH2UbU2n2UDda0Q-A@mail.gmail.com>

Dear Micha? Miros?aw,

> 2013/1/21 Marek Vasut <marex@denx.de>:
> > This patch adds support for i.MX23 into the LRADC driver. The LRADC
> > block on MX23 is not much different from the one on MX28, thus this
> > is only a few changes fixing the parts that are specific to MX23.
> 
> [...]
> 
> > +struct mxs_lradc_of_config {
> > +       const int               irq_count;
> > +       const char * const      *irq_name;
> > +};
> > +
> > +static const struct mxs_lradc_of_config const mxs_lradc_of_config[] = {
> > +       [IMX23_LRADC] = {
> > +               .irq_count      = ARRAY_SIZE(mx23_lradc_irq_names),
> > +               .irq_name       = mx23_lradc_irq_names,
> > +       },
> > +       [IMX28_LRADC] = {
> > +               .irq_count      = ARRAY_SIZE(mx28_lradc_irq_names),
> > +               .irq_name       = mx28_lradc_irq_names,
> > +       },
> > +};
> > +
> > 
> >  enum mxs_lradc_ts {
> >  
> >         MXS_LRADC_TOUCHSCREEN_NONE = 0,
> >         MXS_LRADC_TOUCHSCREEN_4WIRE,
> > 
> > @@ -857,8 +890,19 @@ static void mxs_lradc_hw_stop(struct mxs_lradc
> > *lradc)
> > 
> >                 writel(0, lradc->base + LRADC_DELAY(i));
> >  
> >  }
> > 
> > +static const struct of_device_id mxs_lradc_dt_ids[] = {
> > +       { .compatible = "fsl,imx23-lradc", .data = (void *)IMX23_LRADC,
> > }, +       { .compatible = "fsl,imx28-lradc", .data = (void
> > *)IMX28_LRADC, }, +       { /* sentinel */ }
> > +};
> > +MODULE_DEVICE_TABLE(of, mxs_lradc_dt_ids);
> > +
> 
> Why not s/(void \*)\(IMX.._LRADC\)/\&mxs_lradc_of_config[\1]/ ?

Check the register layout, it differs between MX23 and MX28, that's one reason, 
since were we to access differently placed registers, we can do it easily as in 
the SSP/I2C drivers.

Moreover, there are some features on the MX28 that are not on the MX23 (like 
voltage treshold triggers and touchbuttons), with this setup, we can easily 
check what we're running at at runtime and determine to disallow these.

>From my point of view, using the number (IMX23_LRADC / IMX28_LRADC) is much more 
convenient in the long run.

Best regards,
Marek Vasut

  reply	other threads:[~2013-01-21 21:00 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-21 20:05 [PATCH 1/2] iio: mxs: Add MX23 support into the IIO driver Marek Vasut
2013-01-21 20:05 ` [PATCH 2/2] ARM: mxs: Add OF props for MX23 LRADC Marek Vasut
2013-01-22 12:06   ` Jonathan Cameron
2013-01-22 12:41     ` Shawn Guo
2013-01-22 13:02       ` Jonathan Cameron
2013-01-21 20:36 ` [PATCH 1/2] iio: mxs: Add MX23 support into the IIO driver Michał Mirosław
2013-01-21 21:00   ` Marek Vasut [this message]
2013-01-21 21:19     ` Michał Mirosław
2013-01-21 21:32       ` Marek Vasut
2013-01-21 21:37         ` Lars-Peter Clausen
2013-01-21 21:49           ` Marek Vasut
2013-01-22 12:09             ` Jonathan Cameron
2013-01-21 21:48         ` Michał Mirosław
2013-01-21 21:53           ` Marek Vasut

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=201301212200.36917.marex@denx.de \
    --to=marex@denx.de \
    --cc=linux-arm-kernel@lists.infradead.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).