From: maxime.ripard@free-electrons.com (Maxime Ripard)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/1] add mali r6p2 dt node
Date: Tue, 7 Nov 2017 14:02:13 +0100 [thread overview]
Message-ID: <20171107130213.g73f6oemzdkulgek@flea> (raw)
In-Reply-To: <1510059543-7064-1-git-send-email-giulio.benetti@micronovasrl.com>
On Tue, Nov 07, 2017 at 01:59:03PM +0100, Giulio Benetti wrote:
> It seems there is not mali node in sun7i-a20.dtsi
>
> Add mali node to sun7i-a20.dtsi
>
> This patch adds device tree mali node compatible with r6p2 utgard kernel driver
> provided by ARM and patched by maxime ripard on his github.
>
> It can be easily used in target.dts with:
>
> &mali {
> status = "okay";
> }
>
> then loading mali.ko in user space.
Can you please stop sending the same patch over and over again without
making any changes?
Thanks,
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20171107/69d494e8/attachment.sig>
next prev parent reply other threads:[~2017-11-07 13:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-07 12:59 [PATCH 1/1] add mali r6p2 dt node Giulio Benetti
2017-11-07 13:02 ` Maxime Ripard [this message]
[not found] ` <1b12fa21-bfe6-9ba7-ae1d-8131ac6f4668@micronovasrl.com>
[not found] ` <6fcdc0d9-d0f8-785a-bb00-b1b41c684e59@imkreisrum.de>
2017-11-16 10:37 ` [linux-sunxi] Cedrus driver Giulio Benetti
2017-11-16 11:02 ` Maxime Ripard
2017-11-16 19:59 ` Nicolas Dufresne
2017-11-17 8:01 ` Maxime Ripard
-- strict thread matches above, loose matches on Subject: below --
2017-11-07 10:03 [PATCH 1/1] add mali r6p2 dt node Giulio Benetti
2017-11-07 11:05 ` Maxime Ripard
2017-11-07 17:55 ` Giulio Benetti
2017-11-09 13:40 ` Maxime Ripard
2017-11-07 9:35 Giulio Benetti
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=20171107130213.g73f6oemzdkulgek@flea \
--to=maxime.ripard@free-electrons.com \
--cc=linux-arm-kernel@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