From: Arnd Bergmann <arnd@arndb.de>
To: Karol Wrona <k.wrona@samsung.com>
Cc: Jonathan Cameron <jic23@kernel.org>,
Samuel Ortiz <sameo@linux.intel.com>,
Lee Jones <lee.jones@linaro.org>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
Kyungmin Park <kyungmin.park@samsung.com>
Subject: Re: [PATCH v2 1/5] misc: sensorhub: Add sensorhub driver
Date: Mon, 24 Nov 2014 13:35:55 +0100 [thread overview]
Message-ID: <5942877.97OQIAaJx7@wuerfel> (raw)
In-Reply-To: <547318E0.8070407@samsung.com>
On Monday 24 November 2014 12:39:12 Karol Wrona wrote:
> It is possible that it can serve as input device sth else. So you are
> right about MFD.
>
> The structure of mfd directory is flat. I wonder what can be better:
> just putting these sources inside mfd dir or to some new category inside mfd.
> Generally sensorhub will not differ than others mfd devs but in the near future
> it can be that we end up with different (sensor)hubs or in my case with one core
> driver with several interfaces, mcu's modes - sth like ssp-i2c.c etc.
> These drivers can grow in size as these devices will appear in different boards.
You should be able to abstract the interface differences using regmap for the
most part, so there would only be a small stub that is i2c or spi specific,
and a lot of mfd drivers have that.
> Also there is a question where firmware loader (stm32fwu) should be placed as it
> is a library?
Can you describe what this library does? Is this for loading firmware into
device RAM or into flash? Does it always use USB?
Arnd
next prev parent reply other threads:[~2014-11-24 12:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-21 18:19 [PATCH v2 0/5] misc: sensorhub: Add sensorhub driver Karol Wrona
2014-11-21 18:19 ` [PATCH v2 1/5] " Karol Wrona
2014-11-21 19:38 ` Arnd Bergmann
2014-11-22 12:17 ` Jonathan Cameron
2014-11-24 11:39 ` Karol Wrona
2014-11-24 12:35 ` Arnd Bergmann [this message]
2014-11-24 13:04 ` Karol Wrona
2014-12-03 23:12 ` Hartmut Knaack
2014-11-21 18:19 ` [PATCH v2 2/5] sensorhub: Add sensorhub bindings Karol Wrona
2014-12-03 23:14 ` Hartmut Knaack
2014-11-21 18:19 ` [PATCH v2 3/5] iio: sensorhub: Add sensorhub iio commons Karol Wrona
2014-12-03 23:19 ` Hartmut Knaack
2014-11-21 18:19 ` [PATCH v2 4/5] iio: sensorhub: Add sensorhub accelerometer sensor Karol Wrona
2014-12-03 23:29 ` Hartmut Knaack
2014-11-21 18:19 ` [PATCH v2 5/5] iio: sensorhub: Add sensorhub gyroscope sensor Karol Wrona
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=5942877.97OQIAaJx7@wuerfel \
--to=arnd@arndb.de \
--cc=b.zolnierkie@samsung.com \
--cc=jic23@kernel.org \
--cc=k.wrona@samsung.com \
--cc=kyungmin.park@samsung.com \
--cc=lee.jones@linaro.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sameo@linux.intel.com \
/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).