From: brgl@bgdev.pl (Bartosz Golaszewski)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] memory: aemif: add support for machine code
Date: Wed, 18 Apr 2018 17:35:50 +0200 [thread overview]
Message-ID: <20180418153552.14632-1-brgl@bgdev.pl> (raw)
From: Bartosz Golaszewski <bgolaszewski@baylibre.com>
This is a follow-up to the series that contained both changes to the
aemif driver and platform code. It contains only the driver changes.
As the first step in removing duplicate support for aemif from the
kernel we need to add support for board files to the aemif memory
driver.
First patch just uses a static string for the ti-aemif driver name.
The second adds support for board files to the aemif driver.
This series includes changes requested by Sekhar in his code review:
- made aemif the parent of each sub-device before registering it
- documented the new members in aemif_platform_data
Bartosz Golaszewski (2):
memory: aemif: don't rely on kbuild for driver's name
memory: aemif: add support for board files
drivers/memory/ti-aemif.c | 60 +++++++++++++++++---------
include/linux/platform_data/ti-aemif.h | 25 +++++++++++
2 files changed, 64 insertions(+), 21 deletions(-)
--
2.17.0
next reply other threads:[~2018-04-18 15:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-18 15:35 Bartosz Golaszewski [this message]
2018-04-18 15:35 ` [PATCH 1/2] memory: aemif: don't rely on kbuild for driver's name Bartosz Golaszewski
2018-04-18 15:35 ` [PATCH 2/2] memory: aemif: add support for board files Bartosz Golaszewski
2018-04-19 12:09 ` Sekhar Nori
2018-04-19 12:42 ` Bartosz Golaszewski
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=20180418153552.14632-1-brgl@bgdev.pl \
--to=brgl@bgdev.pl \
--cc=linux-arm-kernel@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;
as well as URLs for NNTP newsgroup(s).