linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jerome Brunet <jbrunet@baylibre.com>
To: Kevin Hilman <khilman@baylibre.com>,
	Neil Armstrong <narmstrong@baylibre.com>
Cc: devicetree <devicetree@vger.kernel.org>,
	linux-amlogic <linux-amlogic@lists.infradead.org>,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
	lkml <linux-kernel@vger.kernel.org>,
	patchwork-bot+notify@kernel.org
Subject: Re: [PATCH 0/7] arm64: meson: g12a: add audio devices
Date: Wed, 17 Apr 2019 09:07:13 +0200	[thread overview]
Message-ID: <3eec8b122aa4912dfa67aeb37ad2c941c34c0a38.camel@baylibre.com> (raw)
In-Reply-To: <CAOi56cU0dHoyRzTXeKGoiFwTms4WuJ7LV2EXTJLoEmOsC8OyrA@mail.gmail.com>

On Tue, 2019-04-16 at 12:22 -0700, Kevin Hilman wrote:
> On Tue, Apr 16, 2019 at 11:52 AM Kevin Hilman <khilman@baylibre.com> wrote:
> > Jerome Brunet <jbrunet@baylibre.com> writes:
> > 
> > > This patchset adds most the audio devices of the g12a SoCs.
> > > 
> > > Kevin, couple of things worth noting:
> > >  * This patch depends of the new audio clocks binding recently applied
> > >    by Neil [0].
> > 
> > Was this supposed to be part of the clk-headers dependency PR I
> > received?  /me looks... It looks like it's applied right after the tag I
> > pulled, so I doesn't look like it.
> > 
> > If I should queue $SUBJECT series up for 5.2, I'll need another stable
> > tag.
> 
> Also, this doesn't apply cleanly anymore to my v5.2/dt64 branch.  When
> the stable tag is ready, do you mind doing a rebase? (or telling me
> what it currently applies to, and I will do the rebase.)

Hi Kevin,

Until we have a solution for the drive strength in pinctrl, I won't be able to
submit the audio pins. I doubt it will happen in this cycle.

Without the pins, audio won't work anyway ... so no rush

If it is ok with you, I'll resend at the beginning of the next cycle. Clk and
ASoC deps will be merged by then, so things should be more straight forward.

> 
> Thanks,
> 
> Kevin



  reply	other threads:[~2019-04-17  7:07 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-12 12:51 [PATCH 0/7] arm64: meson: g12a: add audio devices Jerome Brunet
2019-04-12 12:51 ` [PATCH 1/7] arm64: dts: meson: g12a: add audio clock controller Jerome Brunet
2019-04-12 12:51 ` [PATCH 2/7] arm64: dts: meson: g12a: add audio memory arbitrer Jerome Brunet
2019-04-12 12:51 ` [PATCH 3/7] arm64: dts: meson: g12a: add audio fifos Jerome Brunet
2019-04-12 12:51 ` [PATCH 4/7] arm64: dts: meson: g12a: add tdm devices Jerome Brunet
2019-04-12 12:51 ` [PATCH 5/7] arm64: dts: meson: g12a: add spdifouts Jerome Brunet
2019-04-12 12:51 ` [PATCH 6/7] arm64: dts: meson: g12a: add pdm Jerome Brunet
2019-04-12 12:51 ` [PATCH 7/7] arm64: dts: meson: g12a: add spdifin Jerome Brunet
2019-04-16 18:52 ` [PATCH 0/7] arm64: meson: g12a: add audio devices Kevin Hilman
2019-04-16 19:22   ` Kevin Hilman
2019-04-17  7:07     ` Jerome Brunet [this message]
2019-04-17 14:58       ` Kevin Hilman

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=3eec8b122aa4912dfa67aeb37ad2c941c34c0a38.camel@baylibre.com \
    --to=jbrunet@baylibre.com \
    --cc=devicetree@vger.kernel.org \
    --cc=khilman@baylibre.com \
    --cc=linux-amlogic@lists.infradead.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=narmstrong@baylibre.com \
    --cc=patchwork-bot+notify@kernel.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).