From: Charles Keepax <ckeepax-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org>
To: GIRISH K S <ks.giri-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
Cc: Mark Brown <broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
"devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: Re: [PATCH] spi/s3c64xx: Update DT binding documentation to match code
Date: Fri, 7 Mar 2014 11:12:02 +0000 [thread overview]
Message-ID: <20140307111202.GK8570@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <4F.EF.24278.5C999135-hl5l+cwj/UQ8ySZrqMDKH/pXobYPEAuW@public.gmane.org>
On Fri, Mar 07, 2014 at 10:04:53AM +0000, GIRISH K S wrote:
> Hello Charles, instead of the binding modification I shall
> handle it in the driver probe function by getting child
> node using the api of_get_child_by_name(child-node,
> "controller-data) and then use of_find_property to parse
> the cs-gpio.
>
> This looks like a better fix. Is that ok?
Sounds like a good solution to me.
Thanks,
Charles
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next parent reply other threads:[~2014-03-07 11:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4F.EF.24278.5C999135@epcpsbgx4.samsung.com>
[not found] ` <4F.EF.24278.5C999135-hl5l+cwj/UQ8ySZrqMDKH/pXobYPEAuW@public.gmane.org>
2014-03-07 11:12 ` Charles Keepax [this message]
[not found] <6F.EF.24278.6C999135@epcpsbgx4.samsung.com>
[not found] ` <6F.EF.24278.6C999135-hl5l+cwj/UQ8ySZrqMDKH/pXobYPEAuW@public.gmane.org>
2014-03-09 8:43 ` Re: [PATCH] spi/s3c64xx: Update DT binding documentation to match code Mark Brown
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=20140307111202.GK8570@opensource.wolfsonmicro.com \
--to=ckeepax-yzvpicuk2aatku/dhu1wvuem+bqzidxxqq4iyu8u01e@public.gmane.org \
--cc=broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=ks.giri-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.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: 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).