From: ben.hutchings@codethink.co.uk (Ben Hutchings)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] [RFC PATCH 7/7] ARM: shmobile: defconfig: Enable missing support based on DTSes
Date: Wed, 30 May 2018 19:04:55 +0100 [thread overview]
Message-ID: <1527703495.2289.27.camel@codethink.co.uk> (raw)
In-Reply-To: <1527177910-65275-8-git-send-email-biju.das@bp.renesas.com>
On Thu, 2018-05-24 at 17:05 +0100, Biju Das wrote:
> From: Geert Uytterhoeven <geert+renesas@glider.be>
>
> Enable all missing support, extracted from the various Renesas ARM DTSes
> using linux-config-from-dt.
>
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> Signed-off-by: Simon Horman <horms+renesas@verge.net.au>
> (cherry picked from commit 6161cc147277e7537d73a45d732a7112997c20f6)
> (enabled only USB-DMAC apart from previously enabled CAN and
> ?CAN_RCAR)
Why not apply the whole of the commit (that hasn't already been
applied)? I understand that we don't need all these things enabled for
the reference hardware, but this is meant to be a generic configuration
for all SH-Mobile and R-Car systems.
(I don't particularly care whether we take the whole commit or not. It
just seems like more work to edit out parts of it, and I want to
understand your reasons for doing so.)
Ben.
> Signed-off-by: Biju Das <biju.das@bp.renesas.com>
> ---
> ?arch/arm/configs/shmobile_defconfig | 1 +
> ?1 file changed, 1 insertion(+)
>
> diff --git a/arch/arm/configs/shmobile_defconfig b/arch/arm/configs/shmobile_defconfig
> index 31d7ccc..69b95f5 100644
> --- a/arch/arm/configs/shmobile_defconfig
> +++ b/arch/arm/configs/shmobile_defconfig
> @@ -189,6 +189,7 @@ CONFIG_RTC_DRV_RX8581=y
> ?CONFIG_DMADEVICES=y
> ?CONFIG_SH_DMAE=y
> ?CONFIG_RCAR_DMAC=y
> +CONFIG_RENESAS_USB_DMAC=y
> ?# CONFIG_IOMMU_SUPPORT is not set
> ?CONFIG_IIO=y
> ?CONFIG_AK8975=y
--
Ben Hutchings, Software Developer ? Codethink Ltd
https://www.codethink.co.uk/ Dale House, 35 Dale Street
Manchester, M1 2HF, United Kingdom
We respect your privacy.?? See https://www.codethink.co.uk/privacy.html
next prev parent reply other threads:[~2018-05-30 18:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-24 16:05 [cip-dev] [RFC PATCH 0/7] 'SKB reserve' quirk setup to u_ether Biju Das
2018-05-24 16:05 ` [cip-dev] [RFC PATCH 1/7] usb: gadget: add a new quirk to avoid skb_reserve in u_ether.c Biju Das
2018-05-24 16:05 ` [cip-dev] [RFC PATCH 2/7] usb: gadget: u_ether: add a flag to avoid skb_reserve() calling Biju Das
2018-05-24 16:05 ` [cip-dev] [RFC PATCH 3/7] usb: gadget: f_ncm: add support for no_skb_reserve Biju Das
2018-05-24 16:05 ` [cip-dev] [RFC PATCH 4/7] usb: renesas_usbhs: set quirk_avoids_skb_reserve if USB-DMAC is used Biju Das
2018-05-24 16:05 ` [cip-dev] [RFC PATCH 5/7] usb: gadget: f_ncm/u_ether: Move 'SKB reserve' quirk setup to u_ether Biju Das
2018-05-24 16:05 ` [cip-dev] [RFC PATCH 6/7] dmaengine: usb-dmac: fix endless loop in usb_dmac_chan_terminate_all() Biju Das
2018-05-24 16:05 ` [cip-dev] [RFC PATCH 7/7] ARM: shmobile: defconfig: Enable missing support based on DTSes Biju Das
2018-05-30 18:04 ` Ben Hutchings [this message]
2018-05-30 18:16 ` Biju Das
2018-05-30 18:22 ` Ben Hutchings
2018-05-30 18:26 ` Biju Das
2018-05-30 17:44 ` [cip-dev] [RFC PATCH 0/7] 'SKB reserve' quirk setup to u_ether Ben Hutchings
2018-06-26 9:13 ` Biju Das
2018-07-08 20:02 ` Ben Hutchings
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=1527703495.2289.27.camel@codethink.co.uk \
--to=ben.hutchings@codethink.co.uk \
--cc=cip-dev@lists.cip-project.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