All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v3] sunxi: video: Add simplefb support
Date: Mon, 17 Nov 2014 15:41:49 +0100	[thread overview]
Message-ID: <546A092D.4050307@redhat.com> (raw)
In-Reply-To: <CACxGe6ttF-00aTsEDycJQ5YNiZ0jjAOs7zoHaWsND0wC0JyHDg@mail.gmail.com>

Hi,

On 11/17/2014 10:35 AM, Grant Likely wrote:
> On Sun, Nov 16, 2014 at 7:39 PM, Hans de Goede <hdegoede@redhat.com> wrote:
>> From: Luc Verhaegen <libv@skynet.be>
>>
>> Add simplefb support, note this depends on the kernel having support for
>> the clocks property which has recently been added to the simplefb devicetree
>> binding.
>>
>> Signed-off-by: Luc Verhaegen <libv@skynet.be>
>> [hdegoede at redhat.com: Use pre-populated simplefb node under /chosen as
>>  disussed on the devicetree list]
>> Signed-off-by: Hans de Goede <hdegoede@redhat.com>
> 
> I'm not a U-Boot maintainer, so take my comments with a grain of salt...
> 
> This patch seems quite short sighted. The code that calculates and
> updates the simple framebuffer node addresses is pretty much going to
> be identical for all platforms. Why is sunxi open coding it?
> Particularly when there could be fiddly bits around dealing with
> #address-cells/#size-cells.
> 
> I would think the code to update a simplefb node would be a common
> library function.

You're right I've spun it out into a generic helper function for the
next version of this patch-set.

Regards,

Hans

      reply	other threads:[~2014-11-17 14:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-16 19:39 [U-Boot] [PATCH v3 0/1] sunxi: video: Add simplefb support Hans de Goede
2014-11-16 19:39 ` [U-Boot] [PATCH v3] " Hans de Goede
2014-11-17  9:35   ` Grant Likely
2014-11-17 14:41     ` Hans de Goede [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=546A092D.4050307@redhat.com \
    --to=hdegoede@redhat.com \
    --cc=u-boot@lists.denx.de \
    /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.