From: Roman Volkov <v1ron@mail.ru>
To: Mark Rutland <mark.rutland@arm.com>
Cc: Roman Volkov <v1ron@v1ros.org>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Rob Herring <robh+dt@kernel.org>, Pawel Moll <Pawel.Moll@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>,
"grant.likely@linaro.org" <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-input@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Tony Prisk <linux@prisktech.co.nz>
Subject: Re: [PATCH 5/5] i8042: Add i8042_dt.h glue for DT support
Date: Tue, 3 Feb 2015 22:14:32 +0300 [thread overview]
Message-ID: <20150203221432.662461d8@v1ron-s7> (raw)
In-Reply-To: <20150203115249.GB30866@leverpostej>
В Tue, 3 Feb 2015 11:52:50 +0000
Mark Rutland <mark.rutland@arm.com> пишет:
> On Mon, Feb 02, 2015 at 09:48:50PM +0000, Roman Volkov wrote:
> > This header file designed to be similar to other glue layers found
> > for i8042. The difference is that interrupt numbers, device address,
> > and other information should be retrieved from the device tree.
> >
> > Signed-off-by: Tony Prisk <linux@prisktech.co.nz>
> > Signed-off-by: Roman Volkov <v1ron@v1ros.org>
> > ---
> > drivers/input/serio/i8042-dt.h | 112
> > +++++++++++++++++++++++++++++++++++++++++ 1 file changed, 112
> > insertions(+) create mode 100644 drivers/input/serio/i8042-dt.h
> >
> > diff --git a/drivers/input/serio/i8042-dt.h
> > b/drivers/input/serio/i8042-dt.h new file mode 100644
> > index 0000000..0d1a344
> > --- /dev/null
> > +++ b/drivers/input/serio/i8042-dt.h
> > @@ -0,0 +1,112 @@
> > +#ifndef _I8042_DT_H
> > +#define _I8042_DT_H
> > +
> > +#include <linux/of.h>
> > +#include <linux/of_address.h>
> > +#include <linux/of_irq.h>
> > +
> > +/*
> > + * This program is free software; you can redistribute it and/or
> > modify it
> > + * under the terms of the GNU General Public License version 2 as
> > published by
> > + * the Free Software Foundation.
> > + */
> > +
> > +static void __iomem *i8042_base;
> > +static unsigned int i8042_command_reg;
> > +static unsigned int i8042_status_reg;
> > +static unsigned int i8042_data_reg;
> > +#define I8042_COMMAND_REG i8042_command_reg
> > +#define I8042_STATUS_REG i8042_status_reg
> > +#define I8042_DATA_REG i8042_data_reg
> > +
> > +/*
> > + * Names.
> > + */
> > +
> > +static const char *i8042_kbd_phys_desc;
> > +static const char *i8042_aux_phys_desc;
> > +static const char *i8042_mux_phys_desc;
> > +#define I8042_KBD_PHYS_DESC i8042_kbd_phys_desc
> > +#define I8042_AUX_PHYS_DESC i8042_aux_phys_desc
> > +#define I8042_MUX_PHYS_DESC i8042_mux_phys_desc
> > +
> > +/*
> > + * IRQs.
> > + */
> > +static int i8042_kbd_irq;
> > +static int i8042_aux_irq;
> > +#define I8042_KBD_IRQ i8042_kbd_irq
> > +#define I8042_AUX_IRQ i8042_aux_irq
>
> That's a lot of static values. Surely nothing physically prevents the
> use of multiple i8042 chips?
>
> > +
> > +static inline int i8042_read_data(void)
> > +{
> > + return readb(i8042_base + i8042_data_reg);
> > +}
> > +
> > +static inline int i8042_read_status(void)
> > +{
> > + return readb(i8042_base + i8042_status_reg);
> > +}
> > +
> > +static inline void i8042_write_data(int val)
> > +{
> > + writeb(val, i8042_base + i8042_data_reg);
> > +}
> > +
> > +static inline void i8042_write_command(int val)
> > +{
> > + writeb(val, i8042_base + i8042_command_reg);
> > +}
> > +
> > +static inline int i8042_platform_init(struct platform_device *pdev)
> > +{
> > + struct device_node *np = pdev->dev.of_node;
> > + int status;
> > +
> > + i8042_base = of_iomap(np, 0);
> > + if (!i8042_base)
> > + return -ENOMEM;
> > +
> > + status = of_property_read_u32(np, "command-reg",
> > &i8042_command_reg);
> > + if (status)
> > + return status;
> > +
> > + status = of_property_read_u32(np, "status-reg",
> > &i8042_status_reg);
> > + if (status)
> > + return status;
> > +
> > + status = of_property_read_u32(np, "data-reg",
> > &i8042_data_reg);
> > + if (status)
> > + return status;
>
> You should probably validate that these are within the range provided
> in the reg property.
>
> You also need to clean up if you fail. It looks like here and below we
> leak the i8042_base mapping if we decide to fail.
>
> > +
> > + i8042_kbd_irq = irq_of_parse_and_map(np, 0);
> > + i8042_aux_irq = irq_of_parse_and_map(np, 1);
>
> You can use platform_get_irq(pdev, N) here, the IRQ will already have
> been parsed by the core.
>
> > + status = of_property_read_string(np, "linux,kbd_phys_desc",
> > +
> > &i8042_kbd_phys_desc);
> > + if (status)
> > + i8042_kbd_phys_desc = "i8042/serio0";
> > +
> > + status = of_property_read_string(np, "linux,aux_phys_desc",
> > +
> > &i8042_aux_phys_desc);
> > + if (status)
> > + i8042_aux_phys_desc = "i8042/serio1";
> > +
> > + status = of_property_read_string(np, "linux,mux_phys_desc",
> > +
> > &i8042_mux_phys_desc);
> > + if (status)
> > + i8042_mux_phys_desc = "i8042/serio%d";
>
> User-provided values as format strings? Not a good idea.
>
> What exactly are these used for?
>
> > +
> > + if (of_get_property(np, "init-reset", NULL))
> > + i8042_reset = true;
>
> Use of_property_read_bool.
>
> Thanks,
> Mark.
Mark, thanks for the good review. The current i8042 driver likely does
not support multiple controllers. Maybe Dmitry will comment something
regarding this and overall idea.
I will check the case when DTS contains multiple i8042-compatible
nodes. Expected behavior is that only the first node will be parsed and
next nodes are silently ignored.
Regards,
Roman.
Regards,
Roman.
next prev parent reply other threads:[~2015-02-03 19:14 UTC|newest]
Thread overview: 28+ 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
[not found] ` <1422913730-12663-5-git-send-email-v1ron-oLhuKTjYqW/YtjvyW6yDsg@public.gmane.org>
2015-02-03 11:52 ` Mark Rutland
2015-02-03 19:14 ` Roman Volkov [this message]
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
[not found] ` <1423857173-16432-1-git-send-email-v1ron-oLhuKTjYqW/YtjvyW6yDsg@public.gmane.org>
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
[not found] ` <1424034707-15723-2-git-send-email-v1ron-oLhuKTjYqW/YtjvyW6yDsg@public.gmane.org>
2015-03-15 3:20 ` Dmitry Torokhov
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
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=20150203221432.662461d8@v1ron-s7 \
--to=v1ron@mail.ru \
--cc=Pawel.Moll@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--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=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;
as well as URLs for NNTP newsgroup(s).