From: Greg Ungerer <gerg@kernel.org>
To: Florian Fainelli <f.fainelli@gmail.com>,
sean.wang@mediatek.com, andrew@lunn.ch,
vivien.didelot@savoirfairelinux.com, netdev@vger.kernel.org
Cc: blogic@openwrt.org, neil@brown.name
Subject: Re: [PATCH 3/3] dt-bindings: net: dsa: add new bindings MT7530
Date: Mon, 3 Dec 2018 17:03:24 +1000 [thread overview]
Message-ID: <40200e23-7ec2-0109-3802-71237b948642@kernel.org> (raw)
In-Reply-To: <6d031e8f-17cd-cf64-9d05-a5b48bf448a7@gmail.com>
Hi Florian,
On 1/12/18 3:41 am, Florian Fainelli wrote:
> Hi Greg,
>
> On 11/29/2018 11:57 PM, gerg@kernel.org wrote:
>> From: Greg Ungerer <gerg@kernel.org>
>>
>> Add descriptive entries for the new bindings introduced to support the
>> MT7530 implementation in the MediaTek MT7621 SoC.
>>
>> New bindings added for:
>>
>> mediatek,no-clock-regulator
>> mediatek,mfc-has-cpuport
>
> I don't think any of these properties are necessary, if you can either
> use a compatible string, and/or infer the actual model at runtime in the
> driver's probe function, then you can assess based on that chip model as
There is an ID register in the 7530 - though I don't know if the lower
16 bits of it can tell us enough information about the device. For me on
the MT7621 they return "0001", I assume it is a revsion ID of some type.
Problem is we do not read that until after the regulators and some of
the clocking is setup.
A compatible string of some description would be simple enough.
Are you thinking something like "mediatek,mt7621" before
"mediatek,mt7530"?
> well as the properties being provided in Device Tree whether these
> resources must be grabbed and used. See mv88e6xxx and b53 for how these
> drivers deal with supporting several distinct models within the same
> code base.
I will have a close look at those, thanks.
> As far as the MFC programming goes, this is definitively something that
> must be done once you know the chip model you are dealing with.
Yep, certainly.
Thanks
Greg
next prev parent reply other threads:[~2018-12-03 7:03 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-30 7:57 [PATCH 0/3]: net: dsa: mt7530: support MT7530 in the MT7621 SoC gerg
2018-11-30 7:57 ` [PATCH 1/3] net: dsa: mt7530: make clock/regulator setup optional gerg
2018-11-30 7:57 ` [PATCH 2/3] net: dsa: mt7530: optional setting CPU field in MFC register gerg
2018-11-30 7:57 ` [PATCH 3/3] dt-bindings: net: dsa: add new bindings MT7530 gerg
2018-11-30 17:41 ` Florian Fainelli
2018-12-03 7:03 ` Greg Ungerer [this message]
2018-12-03 13:19 ` Andrew Lunn
2018-11-30 11:27 ` [PATCH 0/3]: net: dsa: mt7530: support MT7530 in the MT7621 SoC René van Dorst
2018-11-30 13:25 ` Greg Ungerer
2018-11-30 11:30 ` René van Dorst
2018-11-30 12:16 ` Bjørn Mork
2018-11-30 13:41 ` Greg Ungerer
2018-11-30 13:42 ` Andrew Lunn
2018-12-03 7:20 ` Greg Ungerer
2018-12-03 11:34 ` Bjørn Mork
2018-12-03 14:00 ` René van Dorst
2018-12-03 14:02 ` John Crispin
2018-12-07 7:12 ` Greg Ungerer
2018-12-04 7:23 ` Greg Ungerer
2018-12-11 5:02 ` NeilBrown
2018-12-11 8:28 ` Bjørn Mork
2018-12-16 22:08 ` NeilBrown
2018-12-16 22:14 ` David Miller
2018-12-16 23:19 ` NeilBrown
2018-12-17 0:00 ` Florian Fainelli
2018-12-17 7:11 ` NeilBrown
2018-11-30 13:33 ` Andrew Lunn
2018-12-03 6:47 ` Greg Ungerer
2018-11-30 13:37 ` Andrew Lunn
2018-11-30 13:45 ` Greg Ungerer
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=40200e23-7ec2-0109-3802-71237b948642@kernel.org \
--to=gerg@kernel.org \
--cc=andrew@lunn.ch \
--cc=blogic@openwrt.org \
--cc=f.fainelli@gmail.com \
--cc=neil@brown.name \
--cc=netdev@vger.kernel.org \
--cc=sean.wang@mediatek.com \
--cc=vivien.didelot@savoirfairelinux.com \
/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).