From: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Please pull ARC changes
Date: Fri, 24 Nov 2017 16:39:15 +0000 [thread overview]
Message-ID: <1511541554.3497.86.camel@synopsys.com> (raw)
Hi Tom,
Could you please pull a couple of fixes and improvements for ARC?
Among them 2 trivial fixes and addition of GPIO controller for ARC HSDK board.
The following changes since commit d9d76023ea0d567b0630e85d1bef67b5b1a788d3:
Merge git://git.denx.de/u-boot-rockchip (2017-11-22 07:28:58 -0500)
are available in the git repository at:
git://git.denx.de/u-boot-arc.git
for you to fetch changes up to f2a226780fa0e4055bec636b8108bf7e80951174:
arc: cache: Add required NOPs after invalidation of instruction cache (2017-11-24 19:38:23 +0300)
----------------------------------------------------------------
Alexey Brodkin (2):
arc: bootm: Move slave cores kick-starting under !fake
arc: cache: Add required NOPs after invalidation of instruction cache
Eugeniy Paltsev (1):
ARC: HSDK: introduce CREG GPIO driver
MAINTAINERS | 6 ++++++
arch/arc/lib/bootm.c | 8 ++++----
arch/arc/lib/cache.c | 7 +++++++
drivers/gpio/Kconfig | 7 +++++++
drivers/gpio/Makefile | 1 +
drivers/gpio/hsdk-creg-gpio.c | 110 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
6 files changed, 135 insertions(+), 4 deletions(-)
create mode 100644 drivers/gpio/hsdk-creg-gpio.c
-Alexey
next reply other threads:[~2017-11-24 16:39 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-24 16:39 Alexey Brodkin [this message]
2017-11-24 21:33 ` [U-Boot] Please pull ARC changes Tom Rini
-- strict thread matches above, loose matches on Subject: below --
2019-01-25 5:52 Alexey Brodkin
2019-01-27 3:50 ` Tom Rini
2018-12-03 11:32 Alexey Brodkin
2018-12-03 15:32 ` Tom Rini
2018-11-01 20:41 Alexey Brodkin
2018-11-02 20:30 ` Tom Rini
2018-10-15 10:22 Alexey Brodkin
2018-10-12 12:38 Alexey Brodkin
2018-10-05 14:10 Alexey Brodkin
2018-10-06 1:16 ` Tom Rini
2018-06-21 11:59 Alexey Brodkin
2018-06-21 18:21 ` Tom Rini
2018-06-18 9:29 Alexey Brodkin
2018-06-15 13:14 Alexey Brodkin
2018-06-16 2:34 ` Tom Rini
2018-05-24 13:09 Alexey Brodkin
2018-05-24 23:41 ` Tom Rini
2018-03-23 13:23 Alexey Brodkin
2018-03-23 13:33 ` Tom Rini
2018-03-23 13:38 ` Alexey Brodkin
2018-03-23 13:51 ` Tom Rini
2018-02-15 12:53 Alexey Brodkin
2018-02-15 19:07 ` Tom Rini
2018-01-19 15:08 Alexey Brodkin
2018-01-19 21:11 ` Tom Rini
2017-12-12 15:52 Alexey Brodkin
2017-12-12 15:58 ` Tom Rini
2017-12-11 8:43 Alexey Brodkin
2017-12-12 1:55 ` Tom Rini
2017-06-29 16:39 Alexey Brodkin
2017-06-30 1:26 ` Tom Rini
2017-04-11 14:56 Alexey Brodkin
2017-04-11 15:55 ` Tom Rini
2017-03-31 19:12 Alexey Brodkin
2017-04-04 20:00 ` Tom Rini
2017-03-24 11:53 Alexey Brodkin
2017-03-24 17:37 ` Tom Rini
2016-09-16 11:30 Alexey Brodkin
2016-09-19 0:31 ` Tom Rini
2016-08-05 10:09 Alexey Brodkin
2016-08-06 2:09 ` Tom Rini
2016-07-04 8:49 Alexey Brodkin
2016-07-05 2:44 ` Tom Rini
2016-06-13 12:43 Alexey Brodkin
2016-06-19 14:08 ` Tom Rini
2016-04-21 17:11 Alexey Brodkin
2016-04-22 14:26 ` Tom Rini
2016-04-11 17:23 Alexey Brodkin
2016-04-12 2:27 ` Tom Rini
2016-02-20 8:22 Alexey Brodkin
2016-02-20 14:23 ` Tom Rini
2015-12-08 14:33 Alexey Brodkin
2015-12-08 15:00 ` Tom Rini
2015-11-17 21:41 Alexey Brodkin
2015-11-18 0:50 ` Tom Rini
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=1511541554.3497.86.camel@synopsys.com \
--to=alexey.brodkin@synopsys.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