From: Igor Prusov <ivprusov@salutedevices.com>
To: Simon Glass <sjg@google.com>
Cc: Neil Armstrong <neil.armstrong@linaro.org>,
Jagan Teki <jagan@amarulasolutions.com>, <prusovigor@gmail.com>,
<kernel@sberdevices.ru>, Igor Prusov <IVPrusov@sberdevices.ru>,
Martin Kurbanov <mmkurbanov@sberdevices.ru>,
<u-boot-amlogic@groups.io>, <u-boot@lists.denx.de>
Subject: Re: [RESEND PATCH v1 1/2] spi: add support for Amlogic A1 SPI Flash Controller
Date: Thu, 19 Oct 2023 23:45:53 +0300 [thread overview]
Message-ID: <20231019204553.sb2qij65h6qsszik@pc> (raw)
In-Reply-To: <CAPnjgZ06Le0qRukSRsCZ5CoKur6ciaCGGUnRpbfz7OQYzZaGBA@mail.gmail.com>
On Tue, Oct 17, 2023 at 09:33:02PM -0600, Simon Glass wrote:
> Hi Igor,
>
> On Tue, 17 Oct 2023 at 11:18, Igor Prusov <ivprusov@salutedevices.com> wrote:
> >
> > From: Igor Prusov <IVPrusov@sberdevices.ru>
> >
> > Add A1 SPIFC driver from Linux. Slightly modified to use u-boot driver
> > framework and accommodate to lack of ioread32_rep/iowrite32_rep.
>
> Well, you could bring them in!
>
I was thinking about it, but I'd prefer to make a separate series with
it, if you don't mind. Need some time to figure out best way to
integrate them into u-boot and I'd like to take a look at other drivers
that could use those while I'm at it.
[...]
--
Best Regards,
Igor Prusov
next prev parent reply other threads:[~2023-10-19 20:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-17 17:17 [RESEND PATCH v1 0/2] ARM: amlogic: Add A1 SPIFC support Igor Prusov
2023-10-17 17:17 ` [RESEND PATCH v1 1/2] spi: add support for Amlogic A1 SPI Flash Controller Igor Prusov
2023-10-18 3:33 ` Simon Glass
2023-10-19 15:33 ` Igor Prusov
2023-10-19 20:45 ` Igor Prusov [this message]
2023-10-17 17:17 ` [RESEND PATCH v1 2/2] ARM: amlogic: ad401: enable SPIFC Igor Prusov
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=20231019204553.sb2qij65h6qsszik@pc \
--to=ivprusov@salutedevices.com \
--cc=IVPrusov@sberdevices.ru \
--cc=jagan@amarulasolutions.com \
--cc=kernel@sberdevices.ru \
--cc=mmkurbanov@sberdevices.ru \
--cc=neil.armstrong@linaro.org \
--cc=prusovigor@gmail.com \
--cc=sjg@google.com \
--cc=u-boot-amlogic@groups.io \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).