devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lukas Wunner <lukas@wunner.de>
To: Stefan Wahren <stefan.wahren@i2se.com>
Cc: "Loic Poulain" <loic.poulain@gmail.com>,
	"Frédéric Danis" <frederic.danis.oss@gmail.com>,
	"Marcel Holtmann" <marcel@holtmann.org>,
	"Johan Hedberg" <johan.hedberg@gmail.com>,
	"Eric Anholt" <eric@anholt.net>,
	"Rob Herring" <robh+dt@kernel.org>,
	"Mark Rutland" <mark.rutland@arm.com>,
	"Phil Elwell" <phil@raspberrypi.org>,
	"Florian Fainelli" <f.fainelli@gmail.com>,
	linux-bluetooth@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-rpi-kernel@lists.infradead.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 1/4] Bluetooth: hci_bcm: Make shutdown and device wake GPIO optional
Date: Sun, 25 Feb 2018 16:15:05 +0100	[thread overview]
Message-ID: <20180225151505.GA17726@wunner.de> (raw)
In-Reply-To: <1519567855-26105-2-git-send-email-stefan.wahren@i2se.com>

On Sun, Feb 25, 2018 at 03:10:52PM +0100, Stefan Wahren wrote:
> According to the devicetree binding the shutdown and device wake
> GPIOs are optional. Since commit 3e81a4ca51a1 ("Bluetooth: hci_bcm:
> Mandate presence of shutdown and device wake GPIO") this driver
> won't probe anymore on Raspberry Pi 3 and Zero W (no device wake GPIO
> connected). So fix this regression by reverting this commit partially.

Okay when submitting 3e81a4ca51a1 I missed that gpiod_set_value()
becomes a no-op if the gpio_desc is NULL, I thought it would oops.


> -	dev->device_wakeup = devm_gpiod_get(dev->dev, "device-wakeup",
> -					    GPIOD_OUT_LOW);
> +	dev->device_wakeup = devm_gpiod_get_optional(dev->dev,
> +						     "device-wakeup",
> +						     GPIOD_OUT_LOW);

The "device-wakeup" would still fit within 80 chars on the preceding line.
Otherwise this is

Reviewed-by: Lukas Wunner <lukas@wunner.de>

Thanks,

Lukas

>  	if (IS_ERR(dev->device_wakeup))
>  		return PTR_ERR(dev->device_wakeup);
>  
> -	dev->shutdown = devm_gpiod_get(dev->dev, "shutdown", GPIOD_OUT_LOW);
> +	dev->shutdown = devm_gpiod_get_optional(dev->dev, "shutdown",
> +						GPIOD_OUT_LOW);
>  	if (IS_ERR(dev->shutdown))
>  		return PTR_ERR(dev->shutdown);
>  

  reply	other threads:[~2018-02-25 15:15 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-25 14:10 [PATCH 0/4] ARM: bcm2835-rpi-zero-w: Enable Bluetooth support Stefan Wahren
2018-02-25 14:10 ` [PATCH 1/4] Bluetooth: hci_bcm: Make shutdown and device wake GPIO optional Stefan Wahren
2018-02-25 15:15   ` Lukas Wunner [this message]
2018-02-25 20:17   ` Marcel Holtmann
2018-02-25 14:10 ` [PATCH 2/4] ARM: dts: bcm283x: Apply pull settings to Zero W relevant groups Stefan Wahren
2018-02-25 14:10 ` [PATCH 3/4] ARM: dts: bcm2835-rpi-zero-w: Add bcm43438 serial slave Stefan Wahren
2018-02-25 20:17   ` Marcel Holtmann
2018-02-25 21:16     ` Stefan Wahren
2018-02-25 21:38       ` Marcel Holtmann
2018-02-27 18:51         ` Stefan Wahren
2018-03-04 21:58         ` Stefan Wahren
2018-03-05  5:19           ` Marcel Holtmann
2018-03-05  6:28             ` Stefan Wahren
2018-03-05  7:06               ` Marcel Holtmann
2018-03-05  7:55                 ` Loic Poulain
2018-03-05 10:04                   ` Marcel Holtmann
2018-03-07 11:28         ` Stefan Wahren
2018-03-07 12:08           ` Loic Poulain
2018-03-07 12:12           ` Marcel Holtmann
2018-03-07 12:42             ` Stefan Wahren
2018-03-07 13:35               ` Marcel Holtmann
2018-03-07 19:08               ` Eric Anholt
2018-03-07 19:35                 ` Marcel Holtmann
2018-03-07 22:36                   ` Eric Anholt
2018-03-08  0:02                     ` Stefan Wahren
2018-03-08  9:14                       ` Loic Poulain
2018-03-08 10:41                         ` Marcel Holtmann
2018-03-08 10:56                       ` Lukas Wunner
2018-03-08 12:08                         ` Marcel Holtmann
2018-03-08 12:06                       ` Marcel Holtmann
2018-02-25 14:10 ` [PATCH 4/4] ARM: bcm2385_defconfig: Enable BT support for BCM43438 Stefan Wahren
2018-02-26 23:31   ` Eric Anholt

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=20180225151505.GA17726@wunner.de \
    --to=lukas@wunner.de \
    --cc=devicetree@vger.kernel.org \
    --cc=eric@anholt.net \
    --cc=f.fainelli@gmail.com \
    --cc=frederic.danis.oss@gmail.com \
    --cc=johan.hedberg@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-rpi-kernel@lists.infradead.org \
    --cc=loic.poulain@gmail.com \
    --cc=marcel@holtmann.org \
    --cc=mark.rutland@arm.com \
    --cc=phil@raspberrypi.org \
    --cc=robh+dt@kernel.org \
    --cc=stefan.wahren@i2se.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).