From: Rob Herring <robh@kernel.org>
To: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Vineet.Gupta1@synopsys.com" <Vineet.Gupta1@synopsys.com>,
"Eugeniy.Paltsev@synopsys.com" <Eugeniy.Paltsev@synopsys.com>,
"linux-snps-arc@lists.infradead.org"
<linux-snps-arc@lists.infradead.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [PATCH 3/3 v7] ARC: hsdk: initial port for HSDK board
Date: Tue, 11 Jul 2017 14:07:02 -0500 [thread overview]
Message-ID: <CAL_JsqJkCjs-f6m-47--yX5XY9VawBFfSn0JMkJSJ7q2wa1kKQ@mail.gmail.com> (raw)
In-Reply-To: <1499693547.6394.17.camel@synopsys.com>
On Mon, Jul 10, 2017 at 8:32 AM, Alexey Brodkin <Alexey.Brodkin@synopsys.com> wrote:
> Hi Rob,
>
> On Sun, 2017-07-09 at 19:41 -0500, Rob Herring wrote:
>> On Mon, Jul 03, 2017 at 07:51:09PM +0300, Eugeniy Paltsev wrote:
>> >
>> > From: Alexey Brodkin <abrodkin@synopsys.com>
>
> [snip]
>
>> > + ohci@60000 {
>> > + compatible = "generic-ohci";
>>
>> Still, these need to be more specific.
>
> But I guess for that we first need to add your compatible values to
> drivers/usb/host/{o|e}hci-platform.c, right?
Not necessarily. You can leave this one for the driver to match on, but the dts needs a more specific one to ensure any quirks can be handled in the future.
Rob
prev parent reply other threads:[~2017-07-11 19:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-03 16:51 [PATCH 0/3 v7] hsdk: initial port for HSDK board Eugeniy Paltsev
2017-07-03 16:51 ` [PATCH 1/3 v7] ARC: Set IO-coherency aperture base to LINUX_LINK_BASE Eugeniy Paltsev
2017-07-03 16:51 ` [PATCH 2/3 v7] ARC: Decouple linux kernel memory address and link address Eugeniy Paltsev
2017-07-03 16:51 ` [PATCH 3/3 v7] ARC: hsdk: initial port for HSDK board Eugeniy Paltsev
[not found] ` <20170703165109.31535-4-Eugeniy.Paltsev-HKixBCOQz3hWk0Htik3J/w@public.gmane.org>
2017-07-10 0:41 ` Rob Herring
2017-07-10 13:32 ` Alexey Brodkin
2017-07-11 19:07 ` Rob Herring [this message]
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=CAL_JsqJkCjs-f6m-47--yX5XY9VawBFfSn0JMkJSJ7q2wa1kKQ@mail.gmail.com \
--to=robh@kernel.org \
--cc=Alexey.Brodkin@synopsys.com \
--cc=Eugeniy.Paltsev@synopsys.com \
--cc=Vineet.Gupta1@synopsys.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-snps-arc@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;
as well as URLs for NNTP newsgroup(s).