From: Dan Carpenter <dan.carpenter@oracle.com>
To: Marcelo Schmitt <marcelo.schmitt1@gmail.com>
Cc: michael.hennerich@analog.com, stefan.popa@analog.com,
alexandru.Ardelean@analog.com, dragos.bogdan@analog.com,
jic23@kernel.org, linux-iio@vger.kernel.org,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
kernel-usp@googlegroups.com
Subject: Re: Help on testing ad5933 driver
Date: Fri, 22 Mar 2019 13:05:02 +0300 [thread overview]
Message-ID: <20190322100502.GM2202@kadam> (raw)
In-Reply-To: <20190321193913.q46gq3h7h63ltpgp@smtp.gmail.com>
On Thu, Mar 21, 2019 at 04:39:13PM -0300, Marcelo Schmitt wrote:
> Hello, would anyone mind helping me test ad5933 driver on actual
> hardware? I went through this
> (https://oslongjourney.github.io/linux-kernel/experiment-one-iio-dummy/)
> tutorial so I was able to load iio_simple_dummy driver, create and
> inspect some dummy devices. Now, as Jonathan has asked me, I would like
> to test ad5933 driver on an EVAL-AD5933 board which was donated to FLUSP
> (https://flusp.ime.usp.br/).
>
> So far I've been hesitating to plug this device on my Debian distro
> since this
> (https://www.analog.com/media/en/technical-documentation/user-guides/UG-364.pdf)
> user guide for Windows says not to connect it before driver
> installation. Is there something that could harm the board if plugged
> on a computer without a proper driver?
The kernel shouldn't be bricking hardware... Hardware used to be easier
to brick in olden times...
regards,
dan carpenter
next prev parent reply other threads:[~2019-03-22 10:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-21 19:39 Help on testing ad5933 driver Marcelo Schmitt
2019-03-22 10:05 ` Dan Carpenter [this message]
2019-03-22 20:34 ` Alexandru Ardelean
2019-03-24 16:31 ` 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=20190322100502.GM2202@kadam \
--to=dan.carpenter@oracle.com \
--cc=alexandru.Ardelean@analog.com \
--cc=devel@driverdev.osuosl.org \
--cc=dragos.bogdan@analog.com \
--cc=jic23@kernel.org \
--cc=kernel-usp@googlegroups.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.schmitt1@gmail.com \
--cc=michael.hennerich@analog.com \
--cc=stefan.popa@analog.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.