linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Maxime Ripard <maxime.ripard@free-electrons.com>
To: Nicolas Ferre <nicolas.ferre@atmel.com>
Cc: Josh Wu <josh.wu@atmel.com>,
	plagnioj@jcrosoft.com, jic23@cam.ac.uk,
	linux-arm-kernel@lists.infradead.org, linux-iio@vger.kernel.org
Subject: Re: [PATCH 2/5] iio: at91: Use different prescal, startup mask in MR for different IP
Date: Tue, 16 Jul 2013 13:20:17 +0200	[thread overview]
Message-ID: <20130716112017.GC3125@lukather> (raw)
In-Reply-To: <51E50864.6020904@atmel.com>

[-- Attachment #1: Type: text/plain, Size: 1300 bytes --]

On Tue, Jul 16, 2013 at 10:46:28AM +0200, Nicolas Ferre wrote:
> >>capabilities from which compatible is declared.
> >>
> >>It seems safer.
> 
> I see it as handier in the sense that a different IP version can be
> compatible with an older IP version: so we do not need to modify the
> driver just to use another SoC.
> 
> On your side Maxime, what makes you say that it is "safer"?

Well, the register holding the IP version seem to be not programmed in
some cases (or, at least, the driver handles this case).

So, what would happen if one SoC was in such case? You wouldn't be able
to use the ADC/touchscreen, even though the IP in itself might very well
work, which doesn't sound very nice, while the DT will always be there,
and will always have a compatible property.

> >Ok, that make sense. I will use compatible names for the capabilities in
> >next version. Thanks.
> 
> Hold on a little bit Josh, I know that Jean-Christophe is not in
> favor of the use of multiple compatible strings. So, as the code is
> already there, let's wait and see if we find another argument...

And you know my feeling about this for quite some time already ;)

Maxime

-- 
Maxime Ripard, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2013-07-16 11:20 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-14  8:04 [PATCH 0/5] iio: at91: Add touch screen support in at91 adc Josh Wu
2013-07-14  8:04 ` [PATCH 1/5] iio: at91: use adc_clk_khz to make the calculation not easy to large than u32 Josh Wu
2013-07-15 12:52   ` Maxime Ripard
2013-07-16  7:54     ` Josh Wu
2013-07-14  8:04 ` [PATCH 2/5] iio: at91: Use different prescal, startup mask in MR for different IP Josh Wu
2013-07-15 12:58   ` Maxime Ripard
2013-07-16  8:35     ` Josh Wu
2013-07-16  8:46       ` Nicolas Ferre
2013-07-16 11:20         ` Maxime Ripard [this message]
2013-07-16 11:30         ` Thomas Petazzoni
2013-07-16 19:03           ` Jonathan Cameron
2013-07-16 19:17             ` Thomas Petazzoni
2013-07-17  8:23               ` Nicolas Ferre
2013-07-17  8:12     ` Nicolas Ferre
2013-07-17  9:07       ` Josh Wu
2013-07-17 15:40       ` Maxime Ripard
2013-07-17  7:58   ` Nicolas Ferre
2013-07-17 10:09     ` Josh Wu
2013-07-20  9:35       ` Jonathan Cameron
2013-07-14  8:04 ` [PATCH 3/5] iio: at91: ADC start-up time calculation changed since at91sam9x5 Josh Wu
2013-07-20  9:39   ` Jonathan Cameron
2013-07-25  7:35     ` Josh Wu
2013-07-14  8:04 ` [PATCH 4/5] iio: at91: add an optional dt property for for adc clock hz Josh Wu
2013-07-15 13:06   ` Maxime Ripard
2013-07-16  7:55     ` Josh Wu
2013-07-16 10:30       ` Maxime Ripard
2013-07-16 11:16         ` Lars-Peter Clausen
2013-07-25  7:29           ` Josh Wu
2013-07-25 12:01   ` boris brezillon
2013-07-25 12:11     ` boris brezillon
2013-07-14  8:04 ` [PATCH 5/5] iio: at91: introduce touch screen support in iio adc driver Josh Wu
2013-07-15 13:15   ` Maxime Ripard
2013-07-16  9:09     ` Josh Wu
2013-07-16 11:43       ` Maxime Ripard
2013-07-20  9:57   ` Jonathan Cameron
2013-07-22 13:17   ` Mark Rutland
2013-07-25  7:56     ` Josh Wu
2013-07-25 16:45       ` Mark Rutland
2013-08-06 10:24         ` Josh Wu
2013-08-08 13:40           ` Mark Rutland

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=20130716112017.GC3125@lukather \
    --to=maxime.ripard@free-electrons.com \
    --cc=jic23@cam.ac.uk \
    --cc=josh.wu@atmel.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=nicolas.ferre@atmel.com \
    --cc=plagnioj@jcrosoft.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 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).