From: Mateusz Kulikowski <mateusz.kulikowski@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 16/18] arm: Add support for Qualcomm Snapdragon family
Date: Sat, 20 Feb 2016 10:32:24 +0100 [thread overview]
Message-ID: <56C832A8.7050000@gmail.com> (raw)
In-Reply-To: <CAD6G_RRW2-+2BLCRBXP=vKXFQpMsJVNpT3mYnEOXagDyaWN7ow@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On 09.02.2016 22:51, Jagan Teki wrote:
> On 8 February 2016 at 02:27, Mateusz Kulikowski
> <mateusz.kulikowski@gmail.com> wrote:
[..]
>> 8 files changed, 352 insertions(+)
>> create mode 100644 arch/arm/mach-snapdragon/Kconfig
>> create mode 100644 arch/arm/mach-snapdragon/Makefile
>> create mode 100644 arch/arm/mach-snapdragon/clock-apq8016.c
>> create mode 100644 arch/arm/mach-snapdragon/include/mach/gpio.h
>> create mode 100644 arch/arm/mach-snapdragon/include/mach/sysmap-apq8016.h
>> create mode 100644 arch/arm/mach-snapdragon/reset.c
>
> I think mach-qcom looks readable, I understand snapdragon is an soc
> name but why can't we place all qcom soc code to mach-qcom (I think
> Linux also doing the same)?
I know Linux has mach-qcom, also it was the first name I used, but IMO it's wrong.
This is Snapdragon-only code - it will not work with, say, wireless SoCs (previously Atheros)..
And it will be in-line with other mach-* in U-Boot:
We have mach-exynos, not mach-samsung; mach-at91 not mach-atmel etc.
Regards,
Mateusz
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQEcBAEBCAAGBQJWyDKlAAoJELvtohmVtQzB8UQH/jF/DWJSRiWvdBtvXDf0AGLy
6/2MMjhhDJDyz2C8zlwv5FlpVVggrNyX3NJoFoIuO7JAwECTnmYAiOj41AyRAYEW
vVeoK+rX4nlD3flYv4UevW+Np0HxYVPyjRX2ONsqWj1u0798Wu5sF4m7H1QC24Pi
iEFSTEdyNCVLaAqK2ELxL72OTiA3Xc+BQq9rvcHe8Q2wIEiAvP5F9LaWCl0z3dK8
ossNUA76d/YYfkczCgDeeY6xR6pdSizaxW7CsKdDaWFLgDQhZUzhJSgCWIGfgdgJ
nY+lVVV3FbJy1Xwe6pgs6vyIqzhb0/9m9d4DTIVZFF+voLzKzE8dREseNzpx+TQ=
=hT5h
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2016-02-20 9:32 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-07 20:57 [U-Boot] [PATCH v2 00/18] Add support for 96boards Dragonboard410C board Mateusz Kulikowski
2016-02-07 20:57 ` [U-Boot] [PATCH v2 01/18] serial: Add support for Qualcomm serial port Mateusz Kulikowski
2016-02-07 20:57 ` [U-Boot] [PATCH v2 02/18] gpio: Add support for Qualcomm gpio controller Mateusz Kulikowski
2016-02-09 21:25 ` Jagan Teki
2016-02-16 15:59 ` Simon Glass
2016-02-19 13:33 ` Mateusz Kulikowski
2016-02-07 20:57 ` [U-Boot] [PATCH v2 03/18] mmc: Add support for Qualcomm SDHCI controller Mateusz Kulikowski
2016-02-09 21:33 ` Jagan Teki
2016-02-24 22:44 ` Mateusz Kulikowski
2016-02-07 20:57 ` [U-Boot] [PATCH v2 04/18] ehci-hcd: Add init_after_reset Mateusz Kulikowski
2016-02-07 20:57 ` [U-Boot] [PATCH v2 05/18] usb: ulpi: Add Kconfig options for ULPI Mateusz Kulikowski
2016-02-08 15:16 ` Marek Vasut
2016-02-07 20:57 ` [U-Boot] [PATCH v2 06/18] Migrate CONFIG_ULPI* to Kconfig Mateusz Kulikowski
2016-02-08 15:16 ` Marek Vasut
2016-02-07 20:57 ` [U-Boot] [PATCH v2 07/18] usb: Rename ehci-fsl.h to ehci-ci.h Mateusz Kulikowski
2016-02-25 15:23 ` [U-Boot] [U-Boot,v2,07/18] " Tom Rini
2016-02-07 20:57 ` [U-Boot] [PATCH v2 08/18] usb: ehci-ci: Add missing registers Mateusz Kulikowski
2016-02-07 20:57 ` [U-Boot] [PATCH v2 09/18] ehci-ci.h: drop generic USBCMD fields Mateusz Kulikowski
2016-02-07 20:57 ` [U-Boot] [PATCH v2 10/18] ehci: Add support for Qualcomm EHCI Mateusz Kulikowski
2016-02-07 20:57 ` [U-Boot] [PATCH v2 11/18] drivers: Add SPMI bus uclass Mateusz Kulikowski
2016-02-07 20:57 ` [U-Boot] [PATCH v2 12/18] spmi: Add sandbox test driver Mateusz Kulikowski
2016-02-07 20:57 ` [U-Boot] [PATCH v2 13/18] drivers: spmi: Add support for Qualcomm SPMI bus driver Mateusz Kulikowski
2016-02-09 21:37 ` Jagan Teki
2016-02-19 21:02 ` Mateusz Kulikowski
2016-02-07 20:57 ` [U-Boot] [PATCH v2 14/18] pmic: Add support for Qualcomm PM8916 PMIC Mateusz Kulikowski
2016-02-07 20:57 ` [U-Boot] [PATCH v2 15/18] gpio: Add support for Qualcomm PM8916 gpios Mateusz Kulikowski
2016-02-09 21:44 ` Jagan Teki
2016-02-20 9:27 ` Mateusz Kulikowski
2016-02-07 20:57 ` [U-Boot] [PATCH v2 16/18] arm: Add support for Qualcomm Snapdragon family Mateusz Kulikowski
2016-02-09 21:51 ` Jagan Teki
2016-02-20 9:32 ` Mateusz Kulikowski [this message]
2016-02-07 20:57 ` [U-Boot] [PATCH v2 17/18] board: Add Qualcomm Dragonboard 410C support Mateusz Kulikowski
2016-03-11 23:58 ` Daniel Glöckner
2016-03-12 21:13 ` Mateusz Kulikowski
2016-03-13 21:08 ` Daniel Glöckner
2016-02-07 20:57 ` [U-Boot] [PATCH v2 18/18] Add myself as Snapdragon and SPMI maintainer Mateusz Kulikowski
2016-02-24 23:42 ` [U-Boot] [PATCH v2 00/18] Add support for 96boards Dragonboard410C board Tom Rini
2016-03-05 22:24 ` Mateusz Kulikowski
-- strict thread matches above, loose matches on Subject: below --
2016-01-24 20:52 Mateusz Kulikowski
2016-01-24 20:53 ` [U-Boot] [PATCH v2 16/18] arm: Add support for Qualcomm Snapdragon family Mateusz Kulikowski
2016-01-31 15:16 ` Simon Glass
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=56C832A8.7050000@gmail.com \
--to=mateusz.kulikowski@gmail.com \
--cc=u-boot@lists.denx.de \
/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