linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: pavel@ucw.cz (Pavel Machek)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] sound/tlv320dac33: Add device tree support
Date: Tue, 30 Jan 2018 13:28:29 +0100	[thread overview]
Message-ID: <20180130122829.GA10373@amd> (raw)
In-Reply-To: <20180130113238.GA10525@sirena.org.uk>

On Tue 2018-01-30 11:32:38, Mark Brown wrote:
> On Tue, Jan 30, 2018 at 09:53:14AM +0100, Pavel Machek wrote:
> 
> > Well, notice I'm converting existing driver to device tree. And that
> > one already has GPIO dependency. It is possible that more work needs
> > to be done there, but that should not be a reason to delay this. Feel
> > free to help.
> 
> No, it's a very good reason to delay merging something.  A DT binding is
> an ABI so we need to sort out interface issues and describe things as
> well as we can, with board files it's not an ABI so we can just do any
> old thing that happens to work and while it might not be ideal it
> doesn't really matter since we can change it later if we need to.

Whatever.

Turns out this was GPIO after all.

I believe power-gpio and reset-gpio are equiavalent, with different
polarity. (After all, devices in reset consume less power).

If you prefer one solution over another, let me know...

									Pavel


-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20180130/df26b399/attachment.sig>

  reply	other threads:[~2018-01-30 12:28 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-29 23:05 [PATCH] sound/tlv320dac33: Add device tree support Pavel Machek
2018-01-29 23:20 ` Ladislav Michl
2018-01-29 23:33   ` Pavel Machek
2018-01-30  8:34     ` Ladislav Michl
2018-01-30  8:53       ` Pavel Machek
2018-01-30  9:11         ` Filip Matijević
2018-01-30  9:38           ` Ladislav Michl
2018-01-30 10:00             ` Pavel Machek
2018-01-30 10:10               ` Ladislav Michl
2018-01-30 10:35                 ` Pavel Machek
2018-01-30 11:38                   ` Ladislav Michl
2018-01-31  9:24                     ` [alsa-devel] " Peter Ujfalusi
2018-01-30 11:32         ` Mark Brown
2018-01-30 12:28           ` Pavel Machek [this message]
2018-01-31  9:12   ` [alsa-devel] " Peter Ujfalusi
2018-01-31 19:01 ` [PATCHv2] tlv320dac33: Add device tree bindings Pavel Machek
2018-02-01  7:39   ` Peter Ujfalusi
2018-02-05  8:24     ` [PATCHv3] " Pavel Machek
2018-02-06 12:11       ` Mark Brown
2018-02-06 13:49         ` Pavel Machek
2018-02-06 15:27           ` Mark Brown
2018-02-24 20:57             ` Pavel Machek
2018-03-05 12:52               ` Peter Ujfalusi
2018-02-09  2:25       ` Rob Herring
2018-02-05  6:08   ` [PATCHv2] " Rob Herring

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=20180130122829.GA10373@amd \
    --to=pavel@ucw.cz \
    --cc=linux-arm-kernel@lists.infradead.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).