All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa@the-dreams.de>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH/RFC 10/10] Local: Hack: arm64: dts: r8a7795: add ravb phy max-speed 100 for Salvator-X bo
Date: Thu, 27 Aug 2015 12:46:45 +0000	[thread overview]
Message-ID: <20150827124645.GC4326@katana> (raw)
In-Reply-To: <1440667450-3513-11-git-send-email-horms+renesas@verge.net.au>

[-- Attachment #1: Type: text/plain, Size: 775 bytes --]

On Thu, Aug 27, 2015 at 01:59:32PM +0200, Geert Uytterhoeven wrote:
> On Thu, Aug 27, 2015 at 1:57 PM, Wolfram Sang <wsa@the-dreams.de> wrote:
> > On Thu, Aug 27, 2015 at 06:24:10PM +0900, Simon Horman wrote:
> >> From: Kazuya Mizuguchi <kazuya.mizuguchi.ks@renesas.com>
> >>
> >> This is a work-around for limitations in the driver implementation.
> >
> > I know this is marked "local: hack:", still: If this is a driver
> > limitation, shouldn't it rather be in the dtsi then?
> 
> You mean, in the driver?
> 
> DT decribes the hardware, not driver limitations.

I wanted to ensure that this workaround goes into all dts files
including the r8a7795 dtsi, even custom ones for testing. This is rather
SoC than board specific, no? And yes, still a hack :)


[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  parent reply	other threads:[~2015-08-27 12:46 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-27  9:24 [PATCH/RFC 10/10] Local: Hack: arm64: dts: r8a7795: add ravb phy max-speed 100 for Salvator-X board Simon Horman
2015-08-27 11:57 ` [PATCH/RFC 10/10] Local: Hack: arm64: dts: r8a7795: add ravb phy max-speed 100 for Salvator-X bo Wolfram Sang
2015-08-27 11:59 ` Geert Uytterhoeven
2015-08-27 12:46 ` Wolfram Sang [this message]
2015-08-27 12:58 ` Sergei Shtylyov
2015-08-27 13:00 ` Sergei Shtylyov
2015-08-27 13:24 ` Wolfram Sang
2015-08-27 23:14 ` Simon Horman
2015-08-28  0:46 ` Magnus Damm
2015-08-28  5:23 ` Simon Horman
2015-08-28  8:29 ` Magnus Damm

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=20150827124645.GC4326@katana \
    --to=wsa@the-dreams.de \
    --cc=linux-sh@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.