From: Randy Dunlap <randy.dunlap@oracle.com>
To: tapio.vihuri@nokia.com
Cc: dmitry.torokhov@gmail.com, linux-kernel@vger.kernel.org,
alsa-devel@alsa-project.org, ilkka.koskinen@nokia.com,
samu.p.onkalo@nokia.com
Subject: Re: [PATCH 2/3] ECI: introducing ECI bus driver
Date: Wed, 22 Dec 2010 09:17:51 -0800 [thread overview]
Message-ID: <20101222091751.10009e90.randy.dunlap@oracle.com> (raw)
In-Reply-To: <1293020435-5680-3-git-send-email-tapio.vihuri@nokia.com>
On Wed, 22 Dec 2010 14:20:34 +0200 tapio.vihuri@nokia.com wrote:
> From: Tapio Vihuri <tapio.vihuri@nokia.com>
>
> ECI bus controller is kind of bridge between host CPU I2C and ECI accessory
> ECI communication.
>
> Signed-off-by: Tapio Vihuri <tapio.vihuri@nokia.com>
> ---
> drivers/Kconfig | 2 +
> drivers/Makefile | 1 +
> drivers/ecibus/Kconfig | 46 ++++
> drivers/ecibus/Makefile | 10 +
> drivers/ecibus/ecibus.c | 583 +++++++++++++++++++++++++++++++++++++++++++++
> include/linux/input/eci.h | 8 +
> 6 files changed, 650 insertions(+), 0 deletions(-)
> create mode 100644 drivers/ecibus/Kconfig
> create mode 100644 drivers/ecibus/Makefile
> create mode 100644 drivers/ecibus/ecibus.c
ERROR: "intel_scu_ipc_iowrite8" [drivers/ecibus/ecibus.ko] undefined!
You must have had some kernel config enabled that I don't have enabled
when you built this. Please fix Kconfig files so that this won't happen.
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
desserts: http://www.xenotime.net/linux/recipes/
prev parent reply other threads:[~2010-12-22 17:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-22 12:20 [PATCH 0/3] input: Add support for ECI (multimedia) accessories tapio.vihuri
2010-12-22 12:20 ` [PATCH 1/3] ECI: input: introduce ECI accessory input driver tapio.vihuri
2010-12-22 12:20 ` [PATCH 2/3] ECI: introducing ECI bus driver tapio.vihuri
2010-12-22 12:20 ` [PATCH 3/3] ECI: adding platform data for ECI driver tapio.vihuri
2010-12-22 17:11 ` [PATCH 2/3] ECI: introducing ECI bus driver Randy Dunlap
2010-12-22 17:17 ` Randy Dunlap [this message]
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=20101222091751.10009e90.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=alsa-devel@alsa-project.org \
--cc=dmitry.torokhov@gmail.com \
--cc=ilkka.koskinen@nokia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=samu.p.onkalo@nokia.com \
--cc=tapio.vihuri@nokia.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
all inboxes | Powered by JetHome®