From: Thierry Reding <thierry.reding@gmail.com> To: "Lothar Waßmann" <LW@KARO-electronics.de> Cc: "Denis Carikli" <denis@eukrea.com>, "Rob Herring" <rob.herring@calxeda.com>, "Shawn Guo" <shawn.guo@linaro.org>, "Eric Bénard" <eric@eukrea.com>, "Sascha Hauer" <kernel@pengutronix.de>, linux-arm-kernel@lists.infradead.org, "Grant Likely" <grant.likely@secretlab.ca>, "Pawel Moll" <pawel.moll@arm.com>, "Mark Rutland" <mark.rutland@arm.com>, "Stephen Warren" <swarren@wwwdotorg.org>, "Ian Campbell" <ijc+devicetree@hellion.org.uk>, devicetree@vger.kernel.org, "Dmitry Torokhov" <dmitry.torokhov@gmail.com>, linux-input@vger.kernel.org, "Linus Walleij" <linus.walleij@linaro.org> Subject: Re: [PATCHv7][ 1/4] Input: tsc2007: Add device tree support. Date: Fri, 25 Oct 2013 10:33:06 +0200 [thread overview] Message-ID: <20131025083305.GE19622@ulmo.nvidia.com> (raw) In-Reply-To: <20131025083951.18675574@ipc1.ka-ro> [-- Attachment #1: Type: text/plain, Size: 3967 bytes --] On Fri, Oct 25, 2013 at 08:39:51AM +0200, Lothar Waßmann wrote: > Hi, > > Thierry Reding wrote: > > On Thu, Oct 24, 2013 at 02:42:13PM +0200, Denis Carikli wrote: > > > Cc: Rob Herring <rob.herring@calxeda.com> > > > Cc: Pawel Moll <pawel.moll@arm.com> > > > Cc: Mark Rutland <mark.rutland@arm.com> > > > Cc: Stephen Warren <swarren@wwwdotorg.org> > > > Cc: Ian Campbell <ijc+devicetree@hellion.org.uk> > > > Cc: devicetree@vger.kernel.org > > > Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com> > > > Cc: linux-input@vger.kernel.org > > > Cc: Sascha Hauer <kernel@pengutronix.de> > > > Cc: linux-arm-kernel@lists.infradead.org > > > Cc: Lothar Waßmann <LW@KARO-electronics.de> > > > Cc: Eric Bénard <eric@eukrea.com> > > > Signed-off-by: Denis Carikli <denis@eukrea.com> > > > --- > > > ChangeLog v6->v7: > > > - One small whitespace cleanup. > > > - The properties specific to that driver are now prefixed with "ti,". > > > - The ti,fuzzy property has now better documentation. > > > --- > > > .../bindings/input/touchscreen/tsc2007.txt | 45 +++++ > > > drivers/input/touchscreen/tsc2007.c | 194 +++++++++++++++----- > > > 2 files changed, 198 insertions(+), 41 deletions(-) > > > create mode 100644 Documentation/devicetree/bindings/input/touchscreen/tsc2007.txt > > > > > > diff --git a/Documentation/devicetree/bindings/input/touchscreen/tsc2007.txt b/Documentation/devicetree/bindings/input/touchscreen/tsc2007.txt > > > new file mode 100644 > > > index 0000000..516b63b > > > --- /dev/null > > > +++ b/Documentation/devicetree/bindings/input/touchscreen/tsc2007.txt > > > @@ -0,0 +1,45 @@ > > > +* Texas Instruments tsc2007 touchscreen controller > > > + > > > +Required properties: > > > +- compatible: must be "ti,tsc2007". > > > +- reg: I2C address of the chip. > > > +- ti,x-plate-ohms: X-plate resistance in ohms. > > > + > > > +Optional properties: > > > +- gpios: the interrupt gpio the chip is connected to (trough the penirq pin) > > > + (see GPIO binding[2] for more details). > > > +- interrupt-parent: the phandle for the gpio controller > > > + (see interrupt binding[1]). > > > +- interrupts: (gpio) interrupt to which the chip is connected > > > + (see interrupt binding[1]). > > > +- pinctrl-0: Should specify pin control groups used for the gpio > > > + (see pinctrl bindings[0]). > > > +- pinctrl-names: Should contain only one value - "default" > > > + (see pinctrl bindings[0]). > > > > Also I haven't seen a response as to why this can't be handled by the > > GPIO driver. Adding Linus Walleij, perhaps he knows a more definitive > > answer. > > > > Linus, the issue here is that the pinctrl properties for this chip are > > supposed to pinmux the pendown GPIO for this chip. I was under the > > impression that this should be handled by the GPIO controller itself, so > > that when gpio_request() was called on a pin it would be the GPIO > > controller driver's responsibility to pinmux it appropriately. > > > When a GPIO is requested the GPIO layer cannot know what it is > requested for and how the pinmux for the pin function should be > configured (pullups, drive strength, ...). A pin may have multiple > functions depending on what modules are plugged into a baseboard. But GPIO is one specific function of a given pin, isn't it? > Thus the pinctrl binding needs to be with the driver that uses the pin. I wonder if this really needs to be dynamically configured depending on the driver. Properties like pullups and driver strength can potentially harm hardware when they're wrong, so relying on the driver's probe to configure them correctly doesn't sound very safe. It's always possible to disable the device (either via modifying the DTS or by having the bootloader patch it). That means the driver won't be probed at all, and therefore none of the pinctrl or pinmux settings will be applied. Thierry [-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: thierry.reding@gmail.com (Thierry Reding) To: linux-arm-kernel@lists.infradead.org Subject: [PATCHv7][ 1/4] Input: tsc2007: Add device tree support. Date: Fri, 25 Oct 2013 10:33:06 +0200 [thread overview] Message-ID: <20131025083305.GE19622@ulmo.nvidia.com> (raw) In-Reply-To: <20131025083951.18675574@ipc1.ka-ro> On Fri, Oct 25, 2013 at 08:39:51AM +0200, Lothar Wa?mann wrote: > Hi, > > Thierry Reding wrote: > > On Thu, Oct 24, 2013 at 02:42:13PM +0200, Denis Carikli wrote: > > > Cc: Rob Herring <rob.herring@calxeda.com> > > > Cc: Pawel Moll <pawel.moll@arm.com> > > > Cc: Mark Rutland <mark.rutland@arm.com> > > > Cc: Stephen Warren <swarren@wwwdotorg.org> > > > Cc: Ian Campbell <ijc+devicetree@hellion.org.uk> > > > Cc: devicetree at vger.kernel.org > > > Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com> > > > Cc: linux-input at vger.kernel.org > > > Cc: Sascha Hauer <kernel@pengutronix.de> > > > Cc: linux-arm-kernel at lists.infradead.org > > > Cc: Lothar Wa?mann <LW@KARO-electronics.de> > > > Cc: Eric B?nard <eric@eukrea.com> > > > Signed-off-by: Denis Carikli <denis@eukrea.com> > > > --- > > > ChangeLog v6->v7: > > > - One small whitespace cleanup. > > > - The properties specific to that driver are now prefixed with "ti,". > > > - The ti,fuzzy property has now better documentation. > > > --- > > > .../bindings/input/touchscreen/tsc2007.txt | 45 +++++ > > > drivers/input/touchscreen/tsc2007.c | 194 +++++++++++++++----- > > > 2 files changed, 198 insertions(+), 41 deletions(-) > > > create mode 100644 Documentation/devicetree/bindings/input/touchscreen/tsc2007.txt > > > > > > diff --git a/Documentation/devicetree/bindings/input/touchscreen/tsc2007.txt b/Documentation/devicetree/bindings/input/touchscreen/tsc2007.txt > > > new file mode 100644 > > > index 0000000..516b63b > > > --- /dev/null > > > +++ b/Documentation/devicetree/bindings/input/touchscreen/tsc2007.txt > > > @@ -0,0 +1,45 @@ > > > +* Texas Instruments tsc2007 touchscreen controller > > > + > > > +Required properties: > > > +- compatible: must be "ti,tsc2007". > > > +- reg: I2C address of the chip. > > > +- ti,x-plate-ohms: X-plate resistance in ohms. > > > + > > > +Optional properties: > > > +- gpios: the interrupt gpio the chip is connected to (trough the penirq pin) > > > + (see GPIO binding[2] for more details). > > > +- interrupt-parent: the phandle for the gpio controller > > > + (see interrupt binding[1]). > > > +- interrupts: (gpio) interrupt to which the chip is connected > > > + (see interrupt binding[1]). > > > +- pinctrl-0: Should specify pin control groups used for the gpio > > > + (see pinctrl bindings[0]). > > > +- pinctrl-names: Should contain only one value - "default" > > > + (see pinctrl bindings[0]). > > > > Also I haven't seen a response as to why this can't be handled by the > > GPIO driver. Adding Linus Walleij, perhaps he knows a more definitive > > answer. > > > > Linus, the issue here is that the pinctrl properties for this chip are > > supposed to pinmux the pendown GPIO for this chip. I was under the > > impression that this should be handled by the GPIO controller itself, so > > that when gpio_request() was called on a pin it would be the GPIO > > controller driver's responsibility to pinmux it appropriately. > > > When a GPIO is requested the GPIO layer cannot know what it is > requested for and how the pinmux for the pin function should be > configured (pullups, drive strength, ...). A pin may have multiple > functions depending on what modules are plugged into a baseboard. But GPIO is one specific function of a given pin, isn't it? > Thus the pinctrl binding needs to be with the driver that uses the pin. I wonder if this really needs to be dynamically configured depending on the driver. Properties like pullups and driver strength can potentially harm hardware when they're wrong, so relying on the driver's probe to configure them correctly doesn't sound very safe. It's always possible to disable the device (either via modifying the DTS or by having the bootloader patch it). That means the driver won't be probed at all, and therefore none of the pinctrl or pinmux settings will be applied. Thierry -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 836 bytes Desc: not available URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20131025/d64703ea/attachment-0001.sig>
next prev parent reply other threads:[~2013-10-25 8:33 UTC|newest] Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-10-24 12:42 [PATCHv7][ 1/4] Input: tsc2007: Add device tree support Denis Carikli 2013-10-24 12:42 ` Denis Carikli 2013-10-24 12:42 ` [PATCHv7][ 2/4] ARM: dts: cpuimx51 Add touchscreen support Denis Carikli 2013-10-24 12:42 ` Denis Carikli 2013-10-24 12:42 ` [PATCHv7][ 3/4] ARM: dts: cpuimx35 " Denis Carikli 2013-10-24 12:42 ` Denis Carikli 2013-10-24 12:42 ` [PATCHv7][ 4/4] ARM: imx_v6_v7_defconfig: Enable tsc2007 support Denis Carikli 2013-10-24 12:42 ` Denis Carikli 2013-10-24 15:17 ` [PATCHv7][ 1/4] Input: tsc2007: Add device tree support Thierry Reding 2013-10-24 15:17 ` Thierry Reding 2013-10-24 15:26 ` Eric Bénard 2013-10-24 15:26 ` Eric Bénard 2013-10-25 6:39 ` Lothar Waßmann 2013-10-25 6:39 ` Lothar Waßmann 2013-10-25 8:33 ` Thierry Reding [this message] 2013-10-25 8:33 ` Thierry Reding 2013-11-04 12:01 ` Linus Walleij 2013-11-04 12:01 ` Linus Walleij 2013-10-24 16:47 ` Grant Likely 2013-10-24 16:47 ` Grant Likely 2013-10-25 5:56 ` Lothar Waßmann 2013-10-25 5:56 ` Lothar Waßmann 2013-10-25 19:11 ` Grant Likely 2013-10-25 19:11 ` Grant Likely
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=20131025083305.GE19622@ulmo.nvidia.com \ --to=thierry.reding@gmail.com \ --cc=LW@KARO-electronics.de \ --cc=denis@eukrea.com \ --cc=devicetree@vger.kernel.org \ --cc=dmitry.torokhov@gmail.com \ --cc=eric@eukrea.com \ --cc=grant.likely@secretlab.ca \ --cc=ijc+devicetree@hellion.org.uk \ --cc=kernel@pengutronix.de \ --cc=linus.walleij@linaro.org \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-input@vger.kernel.org \ --cc=mark.rutland@arm.com \ --cc=pawel.moll@arm.com \ --cc=rob.herring@calxeda.com \ --cc=shawn.guo@linaro.org \ --cc=swarren@wwwdotorg.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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.