From: khilman@baylibre•com (Kevin Hilman)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH v2 0/4] ARM: amlogic: Add spifc support to Amlogic's GXBB family
Date: Tue, 13 Sep 2016 07:19:53 -0700 [thread overview]
Message-ID: <7h4m5jq3ue.fsf@baylibre.com> (raw)
In-Reply-To: <1473753807.2662.12.camel@baylibre.com> (jbrunet@baylibre.com's message of "Tue, 13 Sep 2016 10:03:27 +0200")
jbrunet <jbrunet@baylibre•com> writes:
> On Mon, 2016-09-12 at 13:38 -0700, Kevin Hilman wrote:
>> Jerome Brunet <jbrunet@baylibre•com> writes:
>>
>> >
>> > This patch series adds the necessary pins, clocks and device tree
>> > nodes to
>> > enable the spifc controller on the GXBB family. I had to add the
>> > nand pins
>> > in pintctrl as the pinmux setting left by u-boot was conflicting
>> > with the
>> > spifc pinmux during my test on the P200.
>>
>> This series seems to be missing a patch which enables the SPIfc on
>> the
>> P200 board for use with the on-board NOR flash.
>>
>
> Indeed, I did not provide this patch, on purpose.
> The SPI-NOR at 4U2 on the P200 schematics was not present on the board
> I have. I assumed this was the case for all other P200 as well.
>
> In addition, to enable the SPI-NOR, you would also need to solder
> something at 4R3 (SPI_CS signal disconnected by default)
OK, that makes seense. I thought the NOR was on the board by default.
> Finally, all the SPIfc lines are shared with the NAND controller which,
> like the SPI-NOR, appears on the schematics (4CCN1) but is not soldered
> on the actual hardware.
>
> Of course, I can share such patch for testing purposes if you would
> like me to.
Yeah, having a testing patch in the list archives would be useful.
Thanks,
Kevin
next prev parent reply other threads:[~2016-09-13 14:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-09 8:28 [PATCH v2 0/4] ARM: amlogic: Add spifc support to Amlogic's GXBB family Jerome Brunet
2016-09-09 8:28 ` [PATCH v2 1/4] pinctrl: amlogic: gxbb: add spi nor pins Jerome Brunet
2016-09-12 17:51 ` Kevin Hilman
2016-09-13 11:36 ` Linus Walleij
2016-09-09 8:28 ` [PATCH v2 2/4] pinctrl: amlogic: gxbb: add nand pins Jerome Brunet
2016-09-09 8:28 ` [PATCH v2 3/4] ARM64: dts: amlogic: add spi nor pins Jerome Brunet
2016-09-12 17:51 ` Kevin Hilman
2016-09-09 8:28 ` [PATCH v2 4/4] ARM64: dts: meson-gxbb: Add SPIFC node Jerome Brunet
2016-09-12 17:51 ` Kevin Hilman
2016-09-12 20:38 ` [PATCH v2 0/4] ARM: amlogic: Add spifc support to Amlogic's GXBB family Kevin Hilman
2016-09-13 8:03 ` jbrunet
2016-09-13 14:19 ` Kevin Hilman [this message]
2016-09-13 15:12 ` [RESEND PATCH v2 1/4] pinctrl: amlogic: gxbb: add spi nor pins Jerome Brunet
2016-09-13 15:12 ` [RESEND PATCH v2 2/4] pinctrl: amlogic: gxbb: add nand pins Jerome Brunet
2016-09-15 12:15 ` Linus Walleij
2016-09-15 12:06 ` [RESEND PATCH v2 1/4] pinctrl: amlogic: gxbb: add spi nor pins Linus Walleij
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=7h4m5jq3ue.fsf@baylibre.com \
--to=khilman@baylibre$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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