All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Cc: linux-iio@vger.kernel.org, Hartmut Knaack <knaack.h@gmx.de>,
	Stefan Roese <sr@denx.de>
Subject: Re: spear_adc driver help needed ?
Date: Sun, 21 May 2017 15:33:31 +0100	[thread overview]
Message-ID: <73991880-8585-95a3-3d67-6544717c1264@kernel.org> (raw)
In-Reply-To: <20170518094146.6504821a@free-electrons.com>

On 18/05/17 08:41, Thomas Petazzoni wrote:
> Hello Jonathan,
> 
> I've been working on a SPEAr600 platform recently, which uses the
> spear_adc driver, and was about to start working on moving the driver
> out of staging... only to discover in 4.12-rc1 that you already moved
> it out of staging.
Yeah, this one hit the question of:
Is it is good enough to move it or should we bin it as no improvements are
really happening and no one seems to have one?

I went with the it's good enough option being an optimist.
> 
> In the commit log that moves it out of staging, you're saying:
> 
>      There are some unanswered questions due to disagreements between the code
>      and various datasheets (including between different datasheets for the same
>      part).
>      
>      I don't think that is necessarily a reason to keep it in staging however.
>      I'm partly posting this patch inorder to reignite debate and with a bit
>      of luck find someone who has one of these to test!
> 
> What are the unanswered questions you are talking about?
These all came up in the previous attempt to move the driver out of staging
back in 2014

http://www.spinics.net/lists/linux-iio/msg12443.html
In particular the results of Harmut tracking down a datahsheet and going
through some elements of it in detail.
> 
> Also, I am currently using the driver on a SPEAr600 device, so I can do
> some testing.
Cool.
> 
> The driver has support for the SPEAr3xx, but it isn't used anywhere:
> there is no compatible string for it, and nowhere is old-style probing
> used for "spear-adc".
Stefan (cc'd) might know who is likely to be using it...

However after a bit of digging in the history, his original patch said
that it was untested and proper support might eventually be added.
> 
> So I'm thinking of:
> 
>   - Dropping SPEAr3xx support, because it's unused. This will also
>     remove the ugly checks done on the compatible string all over the
>     place.
I agree.
> 
>   - Moving to a "base + offset" style of register accesses, rather than
>     the struct-based accesses.
Yeah, with the 3xx stuff gone that would tidy things up further.

Only exception would be if someone rapidly jumps up and down and says
they use the 3xx support as is or have working patches they were aiming to
submit to make it work.

Thanks for working on this.  I'd forgotten that stuff was even in there!
> 
> What do you think ?
Would be great to tidy this up, particularly as it sounds like there
are actually users.   Sometimes I wonder on some of the stuff I've
lifted out of staging over the years ;)

Jonathan
> 
> Best regards,
> 
> Thomas
> 


  reply	other threads:[~2017-05-21 14:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-18  7:41 spear_adc driver help needed ? Thomas Petazzoni
2017-05-21 14:33 ` Jonathan Cameron [this message]
2017-05-22  5:37   ` Stefan Roese

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=73991880-8585-95a3-3d67-6544717c1264@kernel.org \
    --to=jic23@kernel.org \
    --cc=knaack.h@gmx.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=sr@denx.de \
    --cc=thomas.petazzoni@free-electrons.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.