linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: s.trumtrar@pengutronix.de (Steffen Trumtrar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 2/3] ARM: socfpga: Add driver for the L3 interconnect
Date: Tue, 16 Dec 2014 09:31:07 +0100	[thread overview]
Message-ID: <20141216083107.GB13070@pengutronix.de> (raw)
In-Reply-To: <20141215223440.GC27866@amd>

Hi!

On Mon, Dec 15, 2014 at 11:34:40PM +0100, Pavel Machek wrote:
> Hi!
> 
> > The L3 interconnect provides Global Programmer View (GPV) registers for every
> > AXI master and slave on the SoC.
> > Although this is just a bunch of bits, syscon is not the right approach for
> > this IP core.
> > The L3 interconnect is configured with a lot of reserved "holes" in its memory
> > space. Just mapping this with regmap, what syscon would do, would lead to the
> > system completely hanging, if one of those areas would be touched.
> > One example for when this might happen is the regmap registers dump in the
> > debugfs.
> 
> Could syscon be extended to take more than one range? Then, you could
> simply list all the ranges in device tree and use syscon...
>

Well it could. The question is, if it should. I don't think it would be a good
idea to abstract away every IP core with a syscon node, just because it works.

> > diff --git a/drivers/soc/Kconfig b/drivers/soc/Kconfig
> > index 76d6bd4da138..11db07da894f 100644
> > --- a/drivers/soc/Kconfig
> > +++ b/drivers/soc/Kconfig
> > @@ -1,6 +1,7 @@
> >  menu "SOC (System On Chip) specific Drivers"
> 
> SoC is usual spelling.
> 

Send patches :-)
This is already mainline and not added here.

> > @@ -0,0 +1,10 @@
> > +#
> > +# SoCFPGA Soc drivers
> 
> SoC.
> 

This however I will fix.

Thanks,
Steffen

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

  reply	other threads:[~2014-12-16  8:31 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-29 20:14 [PATCH v3 0/3] SoCFPGA: L3 NIC driver Steffen Trumtrar
2014-11-29 20:14 ` [PATCH v3 1/3] Documentation: dt: add Altera L3 NIC bindings Steffen Trumtrar
2014-12-02 16:44   ` Dinh Nguyen
2014-11-29 20:14 ` [PATCH v3 2/3] ARM: socfpga: Add driver for the L3 interconnect Steffen Trumtrar
2014-12-02 16:45   ` Dinh Nguyen
2014-12-05 19:51     ` atull
2014-12-05 20:19       ` Steffen Trumtrar
2014-12-15 22:34   ` Pavel Machek
2014-12-16  8:31     ` Steffen Trumtrar [this message]
2014-11-29 20:14 ` [PATCH v3 3/3] ARM: dts: socfpga: Add l3nic node Steffen Trumtrar
2014-12-02 16:46   ` Dinh Nguyen
2014-11-30 11:51 ` [PATCH v3 0/3] SoCFPGA: L3 NIC driver Arnd Bergmann
2014-11-30 20:53   ` Robert Schwebel
2014-12-04 16:30     ` Arnd Bergmann
2014-12-04 18:37       ` Mark Rutland
2014-12-05 11:30         ` Robin Murphy
2014-12-05 22:18           ` Rob Herring
2014-12-01 10:08 ` Mark Rutland
2014-12-01 10:36   ` Steffen Trumtrar
2014-12-02 16:44 ` Dinh Nguyen

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=20141216083107.GB13070@pengutronix.de \
    --to=s.trumtrar@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.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).