| Message ID | 20201117013349.2458416-1-robh@kernel.org |
|---|---|
| Headers | show |
| Series | ASoC: graph card schema rework | expand |
On Mon, Nov 16, 2020 at 7:33 PM Rob Herring <robh@kernel.org> wrote: > > Now that we have an OF graph schema, let's use it for the > audio-graph-port schema. > > There's no need to define 'ports' nodes as specific bindings must define > that and port numbering of the child 'port' nodes. > > Signed-off-by: Rob Herring <robh@kernel.org> > --- > Note that graph.yaml is part of dtschema now intead of the kernel tree. > --- > .../bindings/sound/audio-graph-port.yaml | 16 ++-------------- > 1 file changed, 2 insertions(+), 14 deletions(-) Hold off on applying this. I think graph.yaml is going to need some more refinement. The rest should be able to be applied without this patch. Rob
On Mon, 16 Nov 2020 19:33:45 -0600, Rob Herring wrote: > This series updates Sameer's patch to repartition the graph card binding > schema and incorporate the OF graph schema. The schema was also mixing > card node and DAI node properties, so I've split the DAI part (the > 'port' node) into a separate schema. > > There's another problem that 'frame-master' and 'bitclock-master' have > inconsistent types of boolean and phandle. Having the properties just > point to the local or remote endpoint within an endpoint node is kind of > pointless. We should have gone with just boolean, but looks like we > already have several users. MMP OLPC is the one platform using boolean, > but it happens to work because the properties are effectively ignored > and CPU DAI as the master is the default. > > [...] Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next Thanks! [1/3] ASoC: audio-graph-card: Refactor schema commit: e52f3f291152042f1759b2b8838e7ca24556997e [2/3] ASoC: dt-bindings: marvell, mmp-sspa: Use audio-graph-port schema commit: fd97ee45ec63759593b06be010a8ed395b299cce [3/3] ASoC: dt-bindings: Refine 'frame-master' and 'bitclock-master' type commit: 251bf658558f9feff8a92ddcde402ffa220d13b8 All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to Linus during the next merge window (or sooner if it is a bug fix), however if problems are discovered then the patch may be dropped or reverted. You may get further e-mails resulting from automated or manual testing and review of the tree, please engage with people reporting problems and send followup patches addressing any issues that are reported if needed. If any updates are required or you are submitting further changes they should be sent as incremental updates against current git, existing patches will not be replaced. Please add any relevant lists and maintainers to the CCs when replying to this mail. Thanks, Mark
Hi Rob, >> Now that we have an OF graph schema, let's use it for the >> audio-graph-port schema. >> >> There's no need to define 'ports' nodes as specific bindings must define >> that and port numbering of the child 'port' nodes. >> >> Signed-off-by: Rob Herring <robh@kernel.org> >> --- >> Note that graph.yaml is part of dtschema now intead of the kernel tree. >> --- >> .../bindings/sound/audio-graph-port.yaml | 16 ++-------------- >> 1 file changed, 2 insertions(+), 14 deletions(-) > Hold off on applying this. I think graph.yaml is going to need some > more refinement. Would this be OK if below part of the patch is submitted separately in case above is not immediately planned? - required: - - remote-endpoint - Currently I have dependency on this for series https://patchwork.kernel.org/project/alsa-devel/list/?series=391735&state=*. > > The rest should be able to be applied without this patch. > > Rob