All of lore.kernel.org
 help / color / mirror / Atom feed
From: Charles Keepax <ckeepax@opensource.cirrus.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Lee Jones <lee.jones@linaro.org>,
	Michael Turquette <mturquette@baylibre.com>,
	Stephen Boyd <sboyd@kernel.org>, Mark Brown <broonie@kernel.org>,
	Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Liam Girdwood <lgirdwood@gmail.com>,
	"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" 
	<devicetree@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	<patches@opensource.cirrus.com>
Subject: Re: [PATCH 1/5] mfd: lochnagar: Add support for the Cirrus Logic Lochnagar
Date: Thu, 6 Sep 2018 15:48:34 +0100	[thread overview]
Message-ID: <20180906144834.GD1653@imbe.wolfsonmicro.main> (raw)
In-Reply-To: <CACRpkdakAAAFKfRFeB_8kUCyGts_7sojVwyexe4aL4QQo2CcGg@mail.gmail.com>

On Thu, Sep 06, 2018 at 03:46:12PM +0200, Linus Walleij wrote:
> On Wed, Sep 5, 2018 at 12:41 PM Charles Keepax
> <ckeepax@opensource.cirrus.com> wrote:
> 
> > From: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
> >
> > Lochnagar is an evaluation and development board for Cirrus
> > Logic Smart CODEC and Amp devices. It allows the connection of
> > most Cirrus Logic devices on mini-cards, as well as allowing
> > connection of various application processor systems to provide a
> > full evaluation platform.  Audio system topology, clocking and
> > power can all be controlled through the Lochnagar, allowing the
> > device under test to be used in a variety of possible use cases.
> >
> > As the Lochnagar is a fairly complex device this MFD driver
> > allows the drivers for the various features to be bound
> > in. Initially clocking, regulator and pinctrl will be added as
> > these are necessary to configure the system. But in time at least
> > audio and voltage/current monitoring will also be added.
> >
> > Signed-off-by: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
> 
> It's a bit confusing, maybe you can clear it up:
> it appears to be an I2C device, so when you say this is a
> "development board" is there something like a board
> controller that is accessed over I2C and this is what the
> driver really probes to, not the board per se?
> 
> I guess jamming this card into the I2C slot of any other
> system (would work fine with a 96Boards LS connector
> as it seems, actually)  also involves connecting some
> I2S or similar on the side for high-datarate traffic?
> 
> This driver seems to only concern itself with the I2C
> board controller per se, not the board is that right?
> 

Yeah I have poorly phrased that, these patches are very much
just dealing with the board controller chip.

You could connect just the I2C to something like the 96Boards LS
connector, and control all the functionality accessed by this
driver. Although if you want to send audio between your 96Boards
device and the Lochnagar you would need to connect up some I2S as
well.

Thanks,
Charles

WARNING: multiple messages have this Message-ID (diff)
From: Charles Keepax <ckeepax@opensource.cirrus.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Lee Jones <lee.jones@linaro.org>,
	Michael Turquette <mturquette@baylibre.com>,
	Stephen Boyd <sboyd@kernel.org>, Mark Brown <broonie@kernel.org>,
	Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Liam Girdwood <lgirdwood@gmail.com>,
	"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
	<devicetree@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	patches@opensource.cirrus.com
Subject: Re: [PATCH 1/5] mfd: lochnagar: Add support for the Cirrus Logic Lochnagar
Date: Thu, 6 Sep 2018 15:48:34 +0100	[thread overview]
Message-ID: <20180906144834.GD1653@imbe.wolfsonmicro.main> (raw)
In-Reply-To: <CACRpkdakAAAFKfRFeB_8kUCyGts_7sojVwyexe4aL4QQo2CcGg@mail.gmail.com>

On Thu, Sep 06, 2018 at 03:46:12PM +0200, Linus Walleij wrote:
> On Wed, Sep 5, 2018 at 12:41 PM Charles Keepax
> <ckeepax@opensource.cirrus.com> wrote:
> 
> > From: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
> >
> > Lochnagar is an evaluation and development board for Cirrus
> > Logic Smart CODEC and Amp devices. It allows the connection of
> > most Cirrus Logic devices on mini-cards, as well as allowing
> > connection of various application processor systems to provide a
> > full evaluation platform.  Audio system topology, clocking and
> > power can all be controlled through the Lochnagar, allowing the
> > device under test to be used in a variety of possible use cases.
> >
> > As the Lochnagar is a fairly complex device this MFD driver
> > allows the drivers for the various features to be bound
> > in. Initially clocking, regulator and pinctrl will be added as
> > these are necessary to configure the system. But in time at least
> > audio and voltage/current monitoring will also be added.
> >
> > Signed-off-by: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
> 
> It's a bit confusing, maybe you can clear it up:
> it appears to be an I2C device, so when you say this is a
> "development board" is there something like a board
> controller that is accessed over I2C and this is what the
> driver really probes to, not the board per se?
> 
> I guess jamming this card into the I2C slot of any other
> system (would work fine with a 96Boards LS connector
> as it seems, actually)  also involves connecting some
> I2S or similar on the side for high-datarate traffic?
> 
> This driver seems to only concern itself with the I2C
> board controller per se, not the board is that right?
> 

Yeah I have poorly phrased that, these patches are very much
just dealing with the board controller chip.

You could connect just the I2C to something like the 96Boards LS
connector, and control all the functionality accessed by this
driver. Although if you want to send audio between your 96Boards
device and the Lochnagar you would need to connect up some I2S as
well.

Thanks,
Charles

  reply	other threads:[~2018-09-06 14:48 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-05 10:41 [PATCH 1/5] mfd: lochnagar: Add support for the Cirrus Logic Lochnagar Charles Keepax
2018-09-05 10:41 ` Charles Keepax
2018-09-05 10:41 ` [PATCH 2/5] clk: " Charles Keepax
2018-09-05 10:41   ` Charles Keepax
2018-09-16 23:12   ` Rob Herring
2018-09-05 10:41 ` [PATCH 3/5] regulator: " Charles Keepax
2018-09-05 10:41   ` Charles Keepax
2018-09-05 10:41 ` [PATCH 4/5] pinctrl: " Charles Keepax
2018-09-05 10:41   ` Charles Keepax
2018-09-25 20:20   ` Rob Herring
2018-09-05 10:41 ` [PATCH 5/5] mfd: lochnagar: Add initial binding documentation Charles Keepax
2018-09-05 10:41   ` Charles Keepax
2018-09-05 11:01 ` [PATCH 1/5] mfd: lochnagar: Add support for the Cirrus Logic Lochnagar Mark Brown
2018-09-06 13:46 ` Linus Walleij
2018-09-06 13:46   ` Linus Walleij
2018-09-06 14:48   ` Charles Keepax [this message]
2018-09-06 14:48     ` Charles Keepax
2018-09-16 23:11     ` Rob Herring
2018-09-17 13:50       ` Charles Keepax
2018-09-17 13:50         ` Charles Keepax
2018-09-07  0:06 ` kbuild test robot
2018-09-07  8:44   ` Charles Keepax
2018-09-07  8:44     ` Charles Keepax

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=20180906144834.GD1653@imbe.wolfsonmicro.main \
    --to=ckeepax@opensource.cirrus.com \
    --cc=broonie@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=lee.jones@linaro.org \
    --cc=lgirdwood@gmail.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mturquette@baylibre.com \
    --cc=patches@opensource.cirrus.com \
    --cc=robh+dt@kernel.org \
    --cc=sboyd@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 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.