From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Mark Brown <broonie@kernel.org>
Cc: linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org,
Andy Shevchenko <andy.shevchenko@gmail.com>
Subject: [PATCH v3 0/2] Allow specifying properties with spi_register_board_info
Date: Tue, 28 Feb 2017 14:25:17 -0800 [thread overview]
Message-ID: <20170228222519.38217-1-dmitry.torokhov@gmail.com> (raw)
I am trying to convert some input drivers to use only generic device
properties, and get rid of legacy platform data. For that I need to be
able to attach property lists to devices before they are registered, and
quite a few boards use spi_register_board_info() to create their devices.
v3: dropped former patch #2 (spi: allocate spi_board_info entries one by
one), changed patch #1 to not copy empty property sets and also to
remove added properties when spi_add_device() fails (when it is
successful driver core will free properties upon device removal).
v2: change patch #2 from kmemdup to kmalloc + copy as they are different
data types.
v1: initial posting
Dmitry Torokhov (2):
spi: allow attaching device properties to SPI board info
spi: allow registering empty spi_board_info lists
drivers/spi/spi.c | 34 +++++++++++++++++++++++++++++-----
include/linux/spi/spi.h | 4 ++++
2 files changed, 33 insertions(+), 5 deletions(-)
--
Dmitry
next reply other threads:[~2017-02-28 22:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-28 22:25 Dmitry Torokhov [this message]
2017-02-28 22:25 ` [PATCH v3 1/2] spi: allow attaching device properties to SPI board info Dmitry Torokhov
2017-02-28 22:25 ` [PATCH v3 2/2] spi: allow registering empty spi_board_info lists Dmitry Torokhov
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=20170228222519.38217-1-dmitry.torokhov@gmail.com \
--to=dmitry.torokhov@gmail.com \
--cc=andy.shevchenko@gmail.com \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.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).