From: ben.hutchings@codethink.co.uk (Ben Hutchings)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] [PATCH 6/7] ARM: dts: r8a7743: Add USB-DMAC device nodes
Date: Tue, 10 Apr 2018 17:51:33 +0100 [thread overview]
Message-ID: <1523379093.2654.186.camel@codethink.co.uk> (raw)
In-Reply-To: <TY1PR01MB17708DE86986BEB8D5702986C0D00@TY1PR01MB1770.jpnprd01.prod.outlook.com>
On Thu, 2018-03-15 at 16:07 +0000, Fabrizio Castro wrote:
> Hi Ben,
>
> > Subject: Re: [cip-dev][PATCH 6/7] ARM: dts: r8a7743: Add USB-DMAC device nodes
> >
> > [This sender failed our fraud detection checks and may not be who they appear to be. Learn about spoofing at
> > http://aka.ms/LearnAboutSpoofing]
> >
> > On Tue, 2018-03-06 at 11:34 +0000, Fabrizio Castro wrote:
> > > From: Biju Das <biju.das@bp.renesas.com>
> > >
> > > Signed-off-by: Biju Das <biju.das@bp.renesas.com>
> > > Signed-off-by: Chris Paterson <chris.paterson2@renesas.com>
> > > Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be>
> > > Signed-off-by: Simon Horman <horms+renesas@verge.net.au>
> > > (cherry picked from commit 310861003a0d59cb410538bcdf73a218157a111d)
> > > (modified clocks and power-domains properties, removed resets property)
> > > Signed-off-by: Fabrizio Castro <fabrizio.castro@bp.renesas.com>
> > > ---
> > > ?arch/arm/boot/dts/r8a7743.dtsi | 24 ++++++++++++++++++++++++
> > > ?1 file changed, 24 insertions(+)
> > >
> > > diff --git a/arch/arm/boot/dts/r8a7743.dtsi b/arch/arm/boot/dts/r8a7743.dtsi
> > > index 1237746..db00959 100644
> > > --- a/arch/arm/boot/dts/r8a7743.dtsi
> > > +++ b/arch/arm/boot/dts/r8a7743.dtsi
> > > @@ -309,6 +309,30 @@
> > > ??????????????????????dma-channels = <15>;
> > > ??????????????};
> > >
> > > +?????????????usb_dmac0: dma-controller at e65a0000 {
> > > +?????????????????????compatible = "renesas,usb-dmac";
> >
> > [...]
> >
> > Why no "renesas,r8a7743-usb-dmac" compatible string?
>
> It's down to the dt-bindings, commit 0b2eed49875ec3605b7a71bdf05adc8c1cbd49fc
> introduces SoC specific support, this would trigger changes to the corresponding SoC
> specific DT touched by such a change,
It adds documentation of the string. It wouldn't trigger anything.
> and as usual, where do we draw the line with
> the backporting? Would you rather I used "renesas,r8a7743-usb-dmac" instead?
In general we should make the minimum necessary changes to a backported
commit. Deleting one of the compatible strings does not appear to be
necessary.
Ben.
--
Ben Hutchings
Software Developer, Codethink Ltd.
next prev parent reply other threads:[~2018-04-10 16:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-06 11:34 [cip-dev] [PATCH 0/7] Add HSUSB to r8a7743 Fabrizio Castro
2018-03-06 11:34 ` [cip-dev] [PATCH 1/7] usb: renesas_usbhs: add SoC names to compatibility string documentation Fabrizio Castro
2018-03-06 11:34 ` [cip-dev] [PATCH 2/7] usb: renesas_usbhs: add fallback compatibility strings Fabrizio Castro
2018-03-06 11:34 ` [cip-dev] [PATCH 3/7] usb: renesas_usbhs: Add compatible string for r8a7743/5 Fabrizio Castro
2018-03-06 11:34 ` [cip-dev] [PATCH 4/7] ARM: dts: r8a7743: Add HS-USB device node Fabrizio Castro
2018-03-06 11:34 ` [cip-dev] [PATCH 5/7] ARM: dts: iwg20d-q7: Enable HS-USB Fabrizio Castro
2018-03-06 11:34 ` [cip-dev] [PATCH 6/7] ARM: dts: r8a7743: Add USB-DMAC device nodes Fabrizio Castro
2018-03-14 22:47 ` Ben Hutchings
2018-03-15 16:07 ` Fabrizio Castro
2018-04-10 16:51 ` Ben Hutchings [this message]
2018-03-06 11:34 ` [cip-dev] [PATCH 7/7] ARM: dts: r8a7743: Enable DMA for HSUSB Fabrizio Castro
2018-04-10 17:16 ` [cip-dev] [PATCH 0/7] Add HSUSB to r8a7743 Ben Hutchings
2018-04-10 17:45 ` Fabrizio Castro
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=1523379093.2654.186.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