From: Howard Mitchell <hm@hmbedded.co.uk>
To: Peter Rosin <peda@axentia.se>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"broonie@kernel.org" <broonie@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ASoC: pcm512x: Remove hardcoding of pll-lock to GPIO4
Date: Tue, 24 Mar 2015 10:10:35 +0000 [thread overview]
Message-ID: <5511381B.8030709@hmbedded.co.uk> (raw)
In-Reply-To: <80347e73030a4e31b9765defd4f6ff5a@EMAIL.axentia.se>
On 24/03/15 07:52, Peter Rosin wrote:
> Howard Mitchell wrote:
>> Currently GPIO4 is hardcoded to output the pll-lock signal.
>> Unfortunately this is after the pll-out GPIO is configured which
>> is selectable in the device tree. Therefore it is not possible to
>> use GPIO4 for pll-out. Therefore this patch removes the
>> configuration of GPIO4.
> Howard, thanks for picking up my laundry!
No problem. It was pretty quick and easy to redo from my previous patch
anyway.
> Is master mode working for you otherwise? Have you seen any sign
> of bad dividers for the various clocks, or anything like that?
Not so far. I've run though all the sampling rates from 44.1KHz to
192KHz with a 24.576MHz input clock and they all sounded ok. I haven't
done the maths and checked every single divider setting but I think I
would have heard if something wasn't quite right.
> Regarding the pin configuration, I suppose the cleanest approach
> would be to implement it as a pin control driver? Then you could
> also expose the pins as gpios and select the pin functions in a more
> standard way, right? I wouldn't know where to start with that
> though. I have the feeling that it would also mean that there would
> have to be a mfd driver for the chip???
Yes that would allow userspace access as well. I guess a good place to
start would be one of the I2C gpio expanders:
.../drivers_/_gpio_/_gpio-pca953x.c for instance.
> However, there is the issue that we don't need anything more from
> the chip, so we're happy with the driver as is (assuming the overclocking
> patch goes in as planned for 4.1).
On our board the additional gpios are not even tracked out so the driver
is fine as is for now. For the future we have discussed the possibility
of providing two master clock oscillators to avoid using the pll
altogether. In this case one of the gpios could be used for switching.
- Howard
prev parent reply other threads:[~2015-03-24 10:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-23 21:17 [PATCH] ASoC: pcm512x: Remove hardcoding of pll-lock to GPIO4 Howard Mitchell
[not found] ` <1427145421-5544-1-git-send-email-hm-n6SlHCM0l+K9FHfhHBbuYA@public.gmane.org>
2015-03-23 21:38 ` Mark Brown
2015-03-24 7:52 ` Peter Rosin
2015-03-24 10:10 ` Howard Mitchell [this message]
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=5511381B.8030709@hmbedded.co.uk \
--to=hm@hmbedded.co.uk \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peda@axentia.se \
/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