From: Petr Kulhavy <petr-Qh/3xLP0EvwAvxtiuMwx3w@public.gmane.org>
To: Mark Brown <broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Cc: cernekee-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org,
lgirdwood-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
alsa-devel-K7yf7f+aM1XWsZ/bQMPhNw@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH v3 2/5] ASoC: tas571x: chip type detection via I2C name
Date: Thu, 31 Mar 2016 18:32:25 +0200 [thread overview]
Message-ID: <56FD5119.9000000@barix.com> (raw)
In-Reply-To: <20160331153626.GB2350-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
On 31.03.2016 17:36, Mark Brown wrote:
> On Thu, Mar 31, 2016 at 01:53:58PM +0200, Petr Kulhavy wrote:
>> The chip selection was relying only on DT. It was not possible to use the
>> driver without DT.
>> This adds the chip type detection from the I2C name, which
>> allows to use the driver from the platform driver without DT.
>>
>> Signed-off-by: Petr Kulhavy <petr-Qh/3xLP0EvwAvxtiuMwx3w@public.gmane.org>
>> Reviewed-by: Kevin Cernekee <cernekee-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
>> Signed-off-by: Mark Brown <broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
> Don't resubmit already applied patches, as covered in SubmittingPatches
> you should submit against the latest development tree. Please resend
> with just the new stuff, if any changes are needed in already applied
> patches send incremental fixes.
Thanks for the remainder, I'm sorry, didn't know that.
I will resubmit them right now.
Petr
--
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 prev parent reply other threads:[~2016-03-31 16:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-31 11:53 [PATCH v3 1/5] ASoC: tas571x: added missing register literals Petr Kulhavy
[not found] ` <1459425241-21941-1-git-send-email-petr-Qh/3xLP0EvwAvxtiuMwx3w@public.gmane.org>
2016-03-31 11:53 ` [PATCH v3 2/5] ASoC: tas571x: chip type detection via I2C name Petr Kulhavy
[not found] ` <1459425241-21941-2-git-send-email-petr-Qh/3xLP0EvwAvxtiuMwx3w@public.gmane.org>
2016-03-31 15:36 ` Mark Brown
[not found] ` <20160331153626.GB2350-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2016-03-31 16:32 ` Petr Kulhavy [this message]
2016-03-31 11:53 ` [PATCH v3 3/5] ASoC: tas571x: implemented digital mute Petr Kulhavy
2016-03-31 11:54 ` [PATCH v3 4/5] ASoC: tas571x: added support for TAS5721 Petr Kulhavy
2016-03-31 17:33 ` Applied "ASoC: tas571x: added support for TAS5721" to the asoc tree Mark Brown
2016-03-31 11:54 ` [PATCH v3 5/5] dt/bindings: sound: new chip added into TAS571x binding Petr Kulhavy
[not found] ` <1459425241-21941-5-git-send-email-petr-Qh/3xLP0EvwAvxtiuMwx3w@public.gmane.org>
2016-04-01 18:33 ` Rob Herring
2016-03-31 17:33 ` Applied "ASoC: tas571x: added missing register literals" to the asoc tree 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=56FD5119.9000000@barix.com \
--to=petr-qh/3xlp0evwavxtiumwx3w@public.gmane.org \
--cc=alsa-devel-K7yf7f+aM1XWsZ/bQMPhNw@public.gmane.org \
--cc=broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=cernekee-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=lgirdwood-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=robh+dt-DgEjT+Ai2ygdnm+yROfE0A@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 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.