From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 9/9] ARM: ux500: always select ABX500_CORE
Date: Fri, 03 May 2013 21:38:07 +0200 [thread overview]
Message-ID: <1448676.shCqS631GB@wuerfel> (raw)
In-Reply-To: <CACRpkdaUKM1VzDhi3dMRh92XAYgg3KynvdmXKvCLfiCachP1EQ@mail.gmail.com>
On Friday 03 May 2013 20:43:42 Linus Walleij wrote:
>
> Sounds like a deal. The AB chips aren't on-chip though
> they sit on I2C or SPI actually. But they are still
> strongly coupled with the SoC.
>
> I just took a stroll around the premises and found this
> Aardvark I2C/SPI "embedded systems interface".
>
> This is a USB thing that makes it possible to connect
> any I2C or SPI peripheral to the desktop ... I don't know how
> such things should be used with Linux really, it seems like
> it's something that normally gets used from userspace by
> libusb but in theory we could have a kernel driver for this
> and plug in whatever SoC I2C/SPI device into a desktop.
>
> Whatever use it would be ... but could be useful for
> developing drivers for a chip outside of the target
> system I believe.
I would argue that the AB8500 is close enough to a
'system-on-a-chip' to make it depend on CONFIG_SOC, even
though it is technically one half of a 'system-on-two-chips'.
I would also allow x86 and all other architectures to enable
CONFIG_SOC, since there are lots of SoCs these days that combine
an x86 core with the same kind of peripherals we have on ARM
systems. It's just not what you you find in a regualar PC or
Laptop, and anyone building their own kernel can ignore those.
Arnd
next prev parent reply other threads:[~2013-05-03 19:38 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-02 21:02 [PATCH 0/9] arm-soc: randconfig fixes Arnd Bergmann
2013-05-02 21:02 ` [PATCH 1/9] ARM: tegra: Tegra114 needs CPU_FREQ_TABLE Arnd Bergmann
2013-05-03 4:57 ` Viresh Kumar
2013-05-03 11:20 ` Arnd Bergmann
2013-05-03 12:06 ` Viresh Kumar
2013-05-02 21:02 ` [PATCH 2/9] ARM: OMAP: build SMP code only for OMAP4/5 Arnd Bergmann
2013-05-02 23:30 ` Tony Lindgren
2013-05-02 21:02 ` [PATCH 3/9] ARM: imx: build CPU suspend code only when needed Arnd Bergmann
2013-05-02 21:02 ` [PATCH 4/9] ARM: SPEAr: conditionalize l2x0 support Arnd Bergmann
2013-05-02 21:02 ` [PATCH 5/9] ARM: imx: reset_controller may be disabled Arnd Bergmann
2013-05-02 21:02 ` [PATCH 6/9] ARM: SPEAr: conditionalize SMP code Arnd Bergmann
2013-05-02 21:02 ` [PATCH 7/9] ARM: OMAP: don't select SERIAL_OMAP unconditionally Arnd Bergmann
2013-05-02 23:32 ` Tony Lindgren
2013-05-03 20:34 ` Arnd Bergmann
2013-05-03 21:04 ` Tony Lindgren
2013-05-02 21:02 ` [PATCH 8/9] ARM: SIRF: select SMP_ON_UP only on SMP builds Arnd Bergmann
2013-05-02 21:02 ` [PATCH 9/9] ARM: ux500: always select ABX500_CORE Arnd Bergmann
2013-05-03 8:14 ` Linus Walleij
2013-05-03 11:28 ` Arnd Bergmann
2013-05-03 12:13 ` Linus Walleij
2013-05-03 12:48 ` Arnd Bergmann
2013-05-03 13:33 ` Linus Walleij
2013-05-03 13:56 ` Arnd Bergmann
2013-05-03 14:06 ` Linus Walleij
2013-05-03 14:20 ` Arnd Bergmann
2013-05-03 18:43 ` Linus Walleij
2013-05-03 19:38 ` Arnd Bergmann [this message]
2013-05-03 4:55 ` [PATCH 0/9] arm-soc: randconfig fixes Viresh Kumar
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=1448676.shCqS631GB@wuerfel \
--to=arnd@arndb.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