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:22:44 +0100 [thread overview]
Message-ID: <1527704564.2289.29.camel@codethink.co.uk> (raw)
In-Reply-To: <OSBPR01MB21037C5E4BED34BDD0001814B86C0@OSBPR01MB2103.jpnprd01.prod.outlook.com>
On Wed, 2018-05-30 at 18:16 +0000, Biju Das wrote:
> Hi Ben,
>
> Thanks for the feedback.
>
> > -----Original Message-----
> > From: Ben Hutchings [mailto:ben.hutchings at codethink.co.uk]
> > Sent: 30 May 2018 19:05
> > To: Biju Das <biju.das@bp.renesas.com>
> > Cc: Chris Paterson <Chris.Paterson2@renesas.com>; Fabrizio Castro
> > <fabrizio.castro@bp.renesas.com>; cip-dev at lists.cip-project.org
> > Subject: Re: [RFC PATCH 7/7] ARM: shmobile: defconfig: Enable missing
> > support based on DTSes
> >
> > 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.
>
> We are enabling the config options which are??tested.
> Initially we have??tested CAN driver with this patch. At that point, we found that USB DMAC driver
> is broken with network gadget configuration. Now we found a patch series which fixes USB DMAC driver issue.
> So we can enable USB DMAC driver as well.
OK, that makes sense.
> But the following IP's are not present in RZ/G1M and RZ/G1E platform.
> So currently we don't know the impact, if we enable the same.
>
> CONFIG_I2C_EMEV2=y
> CONFIG_VIDEO_RENESAS_JPU=y
> CONFIG_RTC_DRV_DA9063=y
[...]
The impact should be none, for those platforms. :-)
I'm happy with this patch series. Patch 6 should go to 4.4-stable, but
I can also apply it to 4.4-cip without waiting for that.
Ben.
--
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:22 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
2018-05-30 18:16 ` Biju Das
2018-05-30 18:22 ` Ben Hutchings [this message]
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=1527704564.2289.29.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