From: Sascha Hauer <s.hauer@pengutronix.de>
To: Kai Che <Kai.Che@mixed-mode.de>
Cc: "barebox@lists.infradead.org" <barebox@lists.infradead.org>
Subject: Re: issues communicating with SPI on Raspberry Pi 3
Date: Thu, 6 Dec 2018 09:03:36 +0100 [thread overview]
Message-ID: <20181206080336.cjf244h57y56wnvh@pengutronix.de> (raw)
In-Reply-To: <1544023361576.94285@mixed-mode.de>
On Wed, Dec 05, 2018 at 03:22:40PM +0000, Kai Che wrote:
> Hi all,
>
> I'm trying to communicate with a TPM 2.0 (infineon,slb9670) over SPI on a Raspberry Pi 3 in barebox.
>
> CONFIG_SPI=y
> CONFIG_DRIVER_SPI_GPIO=y
> CONFIG_CMD_SPI=y
>
> are set in the barebox configuration and
>
> dtparam=spi=on
>
> is set in the /boot/config.txt on the raspberry pi.
>
> But when checking /dev/ on barebox, there is nothing related to spi except cs0.
>
> I would have expected something similiar to /dev/spidev0.0 showing up.
I you want to communicate with a SPI device directly without the driver,
there's the 'spi' command. It directly uses internal functions without
the need of any file in /dev/.
We don't have any bcm283x SPI driver in barebox. You probably already
noticed that and enable the spi-gpio driver for this reason. However,
you'll need the appropriate device nodes (Compatible to "spi-gpio")
and the pinctrl setup to make this work.
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2018-12-06 8:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-05 15:22 Kai Che
2018-12-06 8:03 ` Sascha Hauer [this message]
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=20181206080336.cjf244h57y56wnvh@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=Kai.Che@mixed-mode.de \
--cc=barebox@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