From: Neil Armstrong <narmstrong@baylibre.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH u-boot v3 0/3] Add Amlogic Meson SPI Flash Controller driver
Date: Thu, 22 Nov 2018 09:21:22 +0100 [thread overview]
Message-ID: <0f324d94-c851-caec-eb77-c23418e5264f@baylibre.com> (raw)
In-Reply-To: <CAMty3ZAQOdxjTttfCFA4hnZzgEX9cgijZrmdcxHXnkka+uNusQ@mail.gmail.com>
On 22/11/2018 07:40, Jagan Teki wrote:
> On Wed, Nov 14, 2018 at 3:55 PM Neil Armstrong <narmstrong@baylibre.com> wrote:
>>
>> The Amlogic Meson SoCs embeds a Flash oriented SPI Controller name SPIFC.
>>
>> This patchset add the driver ported from linux, but also import the regmap
>> regmap_read_poll_timeout() to implify the register polling in the driver.
>>
>> Neil Armstrong (3):
>> regmap: add regmap_read_poll_timeout() helper
>> test: regmap: add regmap_read_poll_timeout test
>> spi: Add Amlogic Meson SPI Flash Controller driver
>
> There are few regmap patches upstreamed recently, can you rebase and
> the send the series again. take care of direct poll_timeout w/o any
> function on driver.
>
Sure,
Neil
next prev parent reply other threads:[~2018-11-22 8:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-14 10:25 [U-Boot] [PATCH u-boot v3 0/3] Add Amlogic Meson SPI Flash Controller driver Neil Armstrong
2018-11-14 10:25 ` [U-Boot] [PATCH u-boot v3 1/3] regmap: add regmap_read_poll_timeout() helper Neil Armstrong
2018-11-14 13:09 ` Jagan Teki
2018-11-14 10:25 ` [U-Boot] [PATCH u-boot v3 2/3] test: regmap: add regmap_read_poll_timeout test Neil Armstrong
2018-11-14 13:09 ` Jagan Teki
2018-11-14 10:25 ` [U-Boot] [PATCH u-boot v3 3/3] spi: Add Amlogic Meson SPI Flash Controller driver Neil Armstrong
2018-11-14 13:11 ` Jagan Teki
2018-11-14 13:12 ` Neil Armstrong
2018-11-15 15:41 ` [U-Boot] [PATCH u-boot v3 0/3] " Jerome Brunet
2018-11-22 6:40 ` Jagan Teki
2018-11-22 8:21 ` Neil Armstrong [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-11-22 10:01 Neil Armstrong
2018-11-23 5:39 ` Jagan Teki
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=0f324d94-c851-caec-eb77-c23418e5264f@baylibre.com \
--to=narmstrong@baylibre.com \
--cc=u-boot@lists.denx.de \
/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