From: "Jürg Billeter" <j@bitron.ch>
To: Peter Hurley <peter@hurleysoftware.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Gigi Joseph <gigi.joseph@gmail.com>,
Colin Ian King <colin.king@canonical.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] ti-st: st_kim: fix nshutdown_gpio in get_platform_data
Date: Wed, 24 Jun 2015 17:39:08 +0200 [thread overview]
Message-ID: <1435160348.12060.7.camel@bitron.ch> (raw)
In-Reply-To: <558ACD67.9050704@hurleysoftware.com>
On Wed, 2015-06-24 at 11:31 -0400, Peter Hurley wrote:
> On 06/24/2015 06:24 AM, Jürg Billeter wrote:
> > @@ -761,8 +762,14 @@ static struct ti_st_plat_data
> > *get_platform_data(struct device *dev)
> > dt_property = of_get_property(np, "dev_name", &len);
> > if (dt_property)
> > memcpy(&dt_pdata->dev_name, dt_property, len);
> > - of_property_read_u32(np, "nshutdown_gpio",
> > - &dt_pdata->nshutdown_gpio);
> > +
> > + gpio = of_get_named_gpio(np, "nshutdown_gpio", 0);
>
> NAK. This breaks existing dtbs, since the format is not the same.
Isn't the existing code completely broken as there is no predictable
GPIO numbering in general? There is also no documentation or use of
that device tree property in the kernel tree, as far as I can tell.
Do you have a suggestion how to fix this without breaking existing
dtbs? Do we need to introduce a second property and support both in the
driver?
Regards,
Jürg
next prev parent reply other threads:[~2015-06-24 15:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-24 10:24 [PATCH 1/3] ti-st: st_kim: use ERR_PTR(-ENOMEM) instead of NULL Jürg Billeter
2015-06-24 10:24 ` [PATCH 2/3] ti-st: st_kim: fix nshutdown_gpio in get_platform_data Jürg Billeter
2015-06-24 15:31 ` Peter Hurley
2015-06-24 15:39 ` Jürg Billeter [this message]
2015-06-24 15:49 ` Peter Hurley
2015-06-24 10:24 ` [PATCH 3/3] ti-st: st_kim: use gpio_set_value_cansleep to fix warning Jürg Billeter
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=1435160348.12060.7.camel@bitron.ch \
--to=j@bitron.ch \
--cc=colin.king@canonical.com \
--cc=gigi.joseph@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peter@hurleysoftware.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