public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Roman Volkov <v1ron@v1ros.org>
Cc: Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
	Mark Rutland <mark.rutland@arm.com>,
	Ian Campbell <ijc+devicetree@hellion.org.uk>,
	Kumar Gala <galak@codeaurora.org>,
	Grant Likely <grant.likely@linaro.org>,
	Hans de Goede <hdegoede@redhat.com>,
	Jiri Kosina <jkosina@suse.cz>, Wolfram Sang <wsa@the-dreams.de>,
	linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
	devicetree@vger.kernel.org, Tony Prisk <linux@prisktech.co.nz>
Subject: Re: [PATCH v3 1/5] i8042: intel-8042 DT documentation
Date: Sat, 14 Mar 2015 20:20:38 -0700	[thread overview]
Message-ID: <20150315032038.GA13064@dtor-ws> (raw)
In-Reply-To: <1424034707-15723-2-git-send-email-v1ron@v1ros.org>

Hi Roman,

On Mon, Feb 16, 2015 at 12:11:43AM +0300, Roman Volkov wrote:
> Documentation for 'intel,8042' DT compatible node.
> 
> Signed-off-by: Tony Prisk <linux@prisktech.co.nz>
> Signed-off-by: Roman Volkov <v1ron@v1ros.org>
> ---
>  .../devicetree/bindings/input/intel-8042.txt       | 26 ++++++++++++++++++++++
>  1 file changed, 26 insertions(+)
>  create mode 100644 Documentation/devicetree/bindings/input/intel-8042.txt
> 
> diff --git a/Documentation/devicetree/bindings/input/intel-8042.txt b/Documentation/devicetree/bindings/input/intel-8042.txt
> new file mode 100644
> index 0000000..ab8a3e0
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/input/intel-8042.txt
> @@ -0,0 +1,26 @@
> +Intel 8042 Keyboard Controller
> +
> +Required properties:
> +- compatible: should be "intel,8042"
> +- regs: memory for keyboard controller
> +- interrupts: usually, two interrupts should be specified (keyboard and aux).
> +	However, only one interrupt is also allowed in case of absence of the
> +	physical port in the controller. The i8042 driver must be loaded with
> +	nokbd/noaux option in this case.
> +- interrupt-names: interrupt names corresponding to numbers in the list.
> +	"kbd" is the keyboard interrupt and "aux" is the auxiliary (mouse)
> +	interrupt.
> +- command-reg: offset in memory for command register
> +- status-reg: offset in memory for status register
> +- data-reg: offset in memory for data register
> +
> +Example:
> +	i8042@d8008800 {
> +		compatible = "intel,8042";
> +		regs = <0xd8008800 0x100>;
> +		interrupts = <23>, <4>;
> +		interrupt-names = "kbd", "aux";
> +		command-reg = <0x04>;
> +		status-reg = <0x04>;
> +		data-reg = <0x00>;
> +	};

No, we already have existing OF bindings for i8042 on sparc and powerpc,
I do not think we need to invent a brand new one.

Thanks.

-- 
Dmitry

  reply	other threads:[~2015-03-15  3:20 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-02 21:48 [PATCH 1/5] i8042: intel-8042 DT documentation Roman Volkov
2015-02-02 21:48 ` [PATCH 2/5] i8042: Kernel configuration handling for DT support Roman Volkov
2015-02-02 21:48 ` [PATCH 3/5] i8042: Add OF match table Roman Volkov
2015-02-02 21:48 ` [PATCH 4/5] i8042: Prepare i8042 driver for DT support Roman Volkov
2015-02-03 19:38   ` Dmitry Torokhov
2015-02-04  9:30     ` Roman Volkov
2015-02-02 21:48 ` [PATCH 5/5] i8042: Add i8042_dt.h glue " Roman Volkov
2015-02-03 11:52   ` Mark Rutland
2015-02-03 19:14     ` Roman Volkov
2015-02-03 19:26       ` Dmitry Torokhov
2015-02-02 22:10 ` [PATCH 1/5] i8042: intel-8042 DT documentation Roman Volkov
2015-02-13 19:52   ` [PATCH v2 0/5] Device Tree support for i8042 driver Roman Volkov
2015-02-13 19:52     ` [PATCH v2 1/5] i8042: intel-8042 DT documentation Roman Volkov
2015-02-13 19:52     ` [PATCH v2 2/5] i8042: Kernel configuration handling for DT support Roman Volkov
2015-02-13 19:52     ` [PATCH v2 3/5] i8042: Add OF match table Roman Volkov
2015-02-13 19:52     ` [PATCH v2 4/5] i8042: Prepare i8042 driver for DT support Roman Volkov
2015-02-13 19:52     ` [PATCH v2 5/5] i8042: Add i8042_dt.h glue " Roman Volkov
2015-02-15 21:11       ` [PATCH v3 0/5] Device Tree support for i8042 driver Roman Volkov
2015-02-15 21:11         ` [PATCH v3 1/5] i8042: intel-8042 DT documentation Roman Volkov
2015-03-15  3:20           ` Dmitry Torokhov [this message]
2015-02-15 21:11         ` [PATCH v3 2/5] i8042: Kernel configuration handling for DT support Roman Volkov
2015-02-15 21:11         ` [PATCH v3 3/5] i8042: Add OF match table Roman Volkov
2015-02-15 21:11         ` [PATCH v3 4/5] i8042: Prepare i8042 driver for DT support Roman Volkov
2015-02-15 21:11         ` [PATCH v3 5/5] i8042: Add i8042_dt.h glue " Roman Volkov
2015-06-13 17:57           ` Roman Volkov
2015-02-03 11:38 ` [PATCH 1/5] i8042: intel-8042 DT documentation Mark Rutland
2015-02-03 19:32   ` Dmitry Torokhov
2015-02-10 21:01     ` Roman Volkov
     [not found] <E1Yz4NQ-0000Cw-B5@feisty.vs19.net>
2015-05-31 15:37 ` Roman Volkov
2015-05-31 16:00   ` [PATCH v3 1/5] i8042: intel-8042 DT documentation Roman Volkov

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=20150315032038.GA13064@dtor-ws \
    --to=dmitry.torokhov@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=galak@codeaurora.org \
    --cc=grant.likely@linaro.org \
    --cc=hdegoede@redhat.com \
    --cc=ijc+devicetree@hellion.org.uk \
    --cc=jkosina@suse.cz \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@prisktech.co.nz \
    --cc=mark.rutland@arm.com \
    --cc=pawel.moll@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=v1ron@v1ros.org \
    --cc=wsa@the-dreams.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