From: Robin Murphy <robin.murphy@arm.com>
To: Johan Jonker <jbx6244@gmail.com>, Rob Herring <robh@kernel.org>
Cc: linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
heiko@sntech.de, linux-arm-kernel@lists.infradead.org,
devicetree@vger.kernel.org
Subject: Re: [RFC PATCH v1 1/2] dt-bindings: arm: rockchip: add A95X Z2 description
Date: Thu, 16 Jul 2020 14:34:08 +0100 [thread overview]
Message-ID: <56b1447d-6c62-9e73-a7ce-08fb70096a97@arm.com> (raw)
In-Reply-To: <14b39efe-f38b-b471-560d-1ecaeafc5dd5@gmail.com>
On 2020-07-16 13:05, Johan Jonker wrote:
> Hi Rob,
>
> The A95X Z2 boxes are sold by various vendors/manufacturers/web shops.
> The box it self only shows a label with a model name.
> Determining the true vendor is a kind of tricky for a outsider of the
> business.
> Could you advise what would be a save choice to the rather rigid vendor
> requirements.
> Is for example this a option:
>
> "^a95x,.*":
> description: A95X
>
> Is there someone who can give more info on this subject?
FWIW we already have some "A95X" branded things attributed to Nexbox in
upstream DTs, however, the evidence from scraping around the internet
suggests that the closest thing to an original vendor for the "A95X Z2"
model is probably these folks:
https://zkmagic.en.alibaba.com/
Robin.
>
> Kind regards,
>
> Johan Jonker
>
> On 7/15/20 9:29 PM, Rob Herring wrote:
>> On Sat, Jun 20, 2020 at 03:46:58PM +0200, Johan Jonker wrote:
>>> Add A95X Z2 description for a board with rk3318 processor.
>>>
>>> Signed-off-by: Johan Jonker <jbx6244@gmail.com>
>>> ---
>>> Documentation/devicetree/bindings/arm/rockchip.yaml | 5 +++++
>>> 1 file changed, 5 insertions(+)
>>>
>>> diff --git a/Documentation/devicetree/bindings/arm/rockchip.yaml b/Documentation/devicetree/bindings/arm/rockchip.yaml
>>> index d4a404509..3d44b3cf0 100644
>>> --- a/Documentation/devicetree/bindings/arm/rockchip.yaml
>>> +++ b/Documentation/devicetree/bindings/arm/rockchip.yaml
>>> @@ -25,6 +25,11 @@ properties:
>>> - const: vamrs,rock960
>>> - const: rockchip,rk3399
>>>
>>> + - description: A95X Z2
>>> + items:
>>> + - const: a95x,z2
>>
>> Need to document vendor prefix.
>>
>>> + - const: rockchip,rk3318
>>> +
>>> - description: Amarula Vyasa RK3288
>>> items:
>>> - const: amarula,vyasa-rk3288
>>> --
>>> 2.11.0
>>>
>
>
> _______________________________________________
> Linux-rockchip mailing list
> Linux-rockchip@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-rockchip
>
next prev parent reply other threads:[~2020-07-16 13:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-20 13:46 [RFC PATCH v1 0/2] rk3318 A95X Z2 board Johan Jonker
2020-06-20 13:46 ` [RFC PATCH v1 1/2] dt-bindings: arm: rockchip: add A95X Z2 description Johan Jonker
2020-07-15 19:29 ` Rob Herring
2020-07-16 12:05 ` Johan Jonker
2020-07-16 13:34 ` Robin Murphy [this message]
2020-07-16 16:11 ` Johan Jonker
2020-07-16 19:18 ` Robin Murphy
2020-06-20 13:46 ` [RFC PATCH v1 2/2] arm64: dts: rockchip: add rk3318 A95X Z2 board Johan Jonker
2020-06-22 8:01 ` [RFC PATCH v1 0/2] " Johan Jonker
2020-06-25 8:38 ` Johan Jonker
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=56b1447d-6c62-9e73-a7ce-08fb70096a97@arm.com \
--to=robin.murphy@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=jbx6244@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=robh@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®