From: Mark Brown <broonie@kernel.org> To: Jianqun <jay.xu@rock-chips.com> Cc: robh+dt@kernel.org, pawel.moll@arm.com, mark.rutland@arm.com, ijc+devicetree@hellion.org.uk, galak@codeaurora.org, heiko@sntech.de, lgirdwood@gmail.com, perex@perex.cz, tiwai@suse.de, grant.likely@linaro.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, huangtao@rock-chips.com, cf@rock-chips.com Subject: Re: [PATCH 1/2] ASoC: rockchip-max98090: add documentation for rockchip-max98090 driver Date: Fri, 12 Sep 2014 14:44:46 +0100 [thread overview] Message-ID: <20140912134446.GT7960@sirena.org.uk> (raw) In-Reply-To: <1410507036-15442-1-git-send-email-jay.xu@rock-chips.com> [-- Attachment #1: Type: text/plain, Size: 892 bytes --] On Fri, Sep 12, 2014 at 03:30:36PM +0800, Jianqun wrote: > Add documentation for rockchip-max98090 driver, which is need by rockchip > board using a max98090. Can this use simple-card (perhaps after a bit of extension)? > +- rockchip,audio-codec : The phandle of the MAX98090 audio codec. Is the driver really specific to this CODEC? > + > +Optional properties: > +- rockchip,hp-det-gpios : The GPIO that detect headphones are plugged in > +- rockchip,mic-det-gpios : The GPIO that detect micphones are plugged in > + > +Example: > + > +sound { > + compatible = "rockchip,rockchip-audio-max98090"; > + rockchip,model = "ROCKCHIP-I2S"; > + rockchip,i2s-controller = <&i2s>; > + rockchip,audio-codec = <&max98090>; > + rockchip,hp-det-gpios = <&gpio6 5 GPIO_ACTIVE_HIGH>; > + rockchip,mic-det-gpios = <&gpio6 11 GPIO_ACTIVE_HIGH>; > +}; > -- > 1.9.1 > > > [-- Attachment #2: Digital signature --] [-- Type: application/pgp-signature, Size: 473 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: broonie@kernel.org (Mark Brown) To: linux-arm-kernel@lists.infradead.org Subject: [PATCH 1/2] ASoC: rockchip-max98090: add documentation for rockchip-max98090 driver Date: Fri, 12 Sep 2014 14:44:46 +0100 [thread overview] Message-ID: <20140912134446.GT7960@sirena.org.uk> (raw) In-Reply-To: <1410507036-15442-1-git-send-email-jay.xu@rock-chips.com> On Fri, Sep 12, 2014 at 03:30:36PM +0800, Jianqun wrote: > Add documentation for rockchip-max98090 driver, which is need by rockchip > board using a max98090. Can this use simple-card (perhaps after a bit of extension)? > +- rockchip,audio-codec : The phandle of the MAX98090 audio codec. Is the driver really specific to this CODEC? > + > +Optional properties: > +- rockchip,hp-det-gpios : The GPIO that detect headphones are plugged in > +- rockchip,mic-det-gpios : The GPIO that detect micphones are plugged in > + > +Example: > + > +sound { > + compatible = "rockchip,rockchip-audio-max98090"; > + rockchip,model = "ROCKCHIP-I2S"; > + rockchip,i2s-controller = <&i2s>; > + rockchip,audio-codec = <&max98090>; > + rockchip,hp-det-gpios = <&gpio6 5 GPIO_ACTIVE_HIGH>; > + rockchip,mic-det-gpios = <&gpio6 11 GPIO_ACTIVE_HIGH>; > +}; > -- > 1.9.1 > > > -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 473 bytes Desc: Digital signature URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20140912/b931caf2/attachment-0001.sig>
next prev parent reply other threads:[~2014-09-13 15:39 UTC|newest] Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-09-12 7:26 [PATCH 0/2] rockchip-max98090: add driver for rockchip board with max98090 Jianqun 2014-09-12 7:26 ` Jianqun 2014-09-12 7:30 ` [PATCH 1/2] ASoC: rockchip-max98090: add documentation for rockchip-max98090 driver Jianqun 2014-09-12 7:30 ` Jianqun 2014-09-12 7:30 ` Jianqun 2014-09-12 9:10 ` Jianqun 2014-09-12 9:10 ` Jianqun 2014-09-12 10:04 ` Heiko Stübner 2014-09-12 10:04 ` Heiko Stübner 2014-09-12 10:04 ` Heiko Stübner 2014-09-12 10:12 ` Jianqun 2014-09-12 10:12 ` Jianqun 2014-09-12 13:44 ` Mark Brown [this message] 2014-09-12 13:44 ` Mark Brown 2014-09-28 0:54 ` Jianqun 2014-09-28 0:54 ` Jianqun 2014-09-28 10:48 ` Mark Brown 2014-09-28 10:48 ` Mark Brown 2014-09-28 10:48 ` Mark Brown 2014-09-28 11:05 ` Jianqun 2014-09-28 11:05 ` Jianqun 2014-09-12 7:32 ` [PATCH 2/2] ASoC: rockchip-max98090: add driver for rockchip board using a max98090 Jianqun 2014-09-12 7:32 ` Jianqun 2014-09-12 7:39 ` [PATCH] " Jianqun 2014-09-12 7:39 ` Jianqun 2014-09-12 7:39 ` Jianqun 2014-09-12 13:52 ` Mark Brown 2014-09-12 13:52 ` Mark Brown 2014-10-02 8:06 ` Jianqun 2014-10-02 8:06 ` Jianqun 2014-10-02 8:06 ` Jianqun 2014-09-12 7:43 ` [PATCH 2/2] " Jianqun 2014-09-12 7:43 ` Jianqun 2014-09-12 7:43 ` Jianqun 2014-10-02 8:36 ` [PATCH v2 " Jianqun 2014-10-02 8:36 ` Jianqun 2014-10-02 8:36 ` Jianqun 2014-10-02 10:22 ` Mark Brown 2014-10-02 10:22 ` Mark Brown 2014-10-02 10:22 ` Mark Brown 2014-09-12 13:42 ` [PATCH 0/2] rockchip-max98090: add driver for rockchip board with max98090 Mark Brown 2014-09-12 13:42 ` Mark Brown 2014-09-14 3:00 ` Jianqun 2014-09-14 3:00 ` Jianqun
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=20140912134446.GT7960@sirena.org.uk \ --to=broonie@kernel.org \ --cc=cf@rock-chips.com \ --cc=devicetree@vger.kernel.org \ --cc=galak@codeaurora.org \ --cc=grant.likely@linaro.org \ --cc=heiko@sntech.de \ --cc=huangtao@rock-chips.com \ --cc=ijc+devicetree@hellion.org.uk \ --cc=jay.xu@rock-chips.com \ --cc=lgirdwood@gmail.com \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=mark.rutland@arm.com \ --cc=pawel.moll@arm.com \ --cc=perex@perex.cz \ --cc=robh+dt@kernel.org \ --cc=tiwai@suse.de \ /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: linkBe 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.