devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Florian Fainelli <f.fainelli@gmail.com>
To: Mark Brown <broonie@kernel.org>,
	Linux SPI List <linux-spi@vger.kernel.org>,
	Broadcom Kernel List <bcm-kernel-feedback-list@broadcom.com>,
	William Zhang <william.zhang@broadcom.com>
Cc: kursad.oney@broadcom.com, anand.gore@broadcom.com,
	dan.beygelman@broadcom.com, dregan@mail.com,
	joel.peshkin@broadcom.com, jonas.gorski@gmail.com,
	tomer.yacoby@broadcom.com,
	"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
	"Rafał Miłecki" <rafal@milecki.pl>,
	"Rob Herring" <robh+dt@kernel.org>,
	devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 00/15] spi: bcm63xx-hsspi: driver and doc updates
Date: Thu, 9 Feb 2023 10:34:34 -0800	[thread overview]
Message-ID: <ac6591f3-0420-3cd0-28b5-8b2ea333d723@gmail.com> (raw)
In-Reply-To: <167596308461.673456.2324521897149973878.b4-ty@kernel.org>

On 2/9/23 09:18, Mark Brown wrote:
> On Mon, 06 Feb 2023 22:58:11 -0800, William Zhang wrote:
>> This patch series include the accumulative updates and fixes for the
>> driver from Broadcom. It also added a new driver for the updated SPI
>> controller found in the new BCMBCA SoC. The device tree document is
>> converted to yaml format and updated accordingly.
>>
>> Changes in v3:
>> - Clean up spi-controller.yaml and update the example
>> - Drop the generic compatible string brcm,bcmbca-hsspi from the document
>>    and dts files
>> - Port the cs_change and cs_off logic from SPI core
>>    spi_transfer_one_message function to both controller drivers.
>> - Factor dummy cs workaround into a function, adjust the logic for
>>    different xfer modes and fine tune message level in bcm63xx-hsspi
>>    controller driver
>> - Replace hard-coded opcode with SPINOR_OP definition
>> - Add a new patch to export export spi_transfer_cs_change_delay_exec
>>    function in the spi core
>> - Add a new patch to include compatible string brcm,bcmbca-hsspi-v1.0 in
>>    bcm63xx-hsspi controller driver
>> - Minor coding style fix in bcmbca-hsspi controller driver
>> - Add Acked-by and Reviewed-by tag
>>
>> [...]
> 
> Applied to
> 
>     https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next
> 
> Thanks!
> 
> [01/15] dt-bindings: spi: Convert bcm63xx-hsspi bindings to json-schema
>          commit: fff948a44b44a628c81294af5498226cb66a2594
> [02/15] dt-bindings: spi: Add bcmbca-hsspi controller support
>          commit: 0ba979f995324417fd773881bc5a39910a9f2362
> [03/15] ARM: dts: broadcom: bcmbca: Add spi controller node
>          (no commit info)
> [04/15] arm64: dts: broadcom: bcmbca: Add spi controller node
>          (no commit info)

Usually we have SoC maintainers pick up the DTS patches affecting the 
platforms they cover to avoid conflicts... I suppose that is fine.
-- 
Florian


  reply	other threads:[~2023-02-09 18:34 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-07  6:58 [PATCH v3 00/15] spi: bcm63xx-hsspi: driver and doc updates William Zhang
2023-02-07  6:58 ` [PATCH v3 01/15] dt-bindings: spi: Convert bcm63xx-hsspi bindings to json-schema William Zhang
2023-02-07  6:58 ` [PATCH v3 02/15] dt-bindings: spi: Add bcmbca-hsspi controller support William Zhang
2023-02-07  8:03   ` Krzysztof Kozlowski
2023-02-07  6:58 ` [PATCH v3 03/15] ARM: dts: broadcom: bcmbca: Add spi controller node William Zhang
2023-02-09 18:38   ` Florian Fainelli
2023-02-07  6:58 ` [PATCH v3 04/15] arm64: " William Zhang
2023-02-09 18:39   ` Florian Fainelli
2023-02-09 17:18 ` [PATCH v3 00/15] spi: bcm63xx-hsspi: driver and doc updates Mark Brown
2023-02-09 18:34   ` Florian Fainelli [this message]
2023-02-09 18:36     ` Mark Brown
2023-02-09 18:38       ` Florian Fainelli

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=ac6591f3-0420-3cd0-28b5-8b2ea333d723@gmail.com \
    --to=f.fainelli@gmail.com \
    --cc=anand.gore@broadcom.com \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=broonie@kernel.org \
    --cc=dan.beygelman@broadcom.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dregan@mail.com \
    --cc=joel.peshkin@broadcom.com \
    --cc=jonas.gorski@gmail.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=kursad.oney@broadcom.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=rafal@milecki.pl \
    --cc=robh+dt@kernel.org \
    --cc=tomer.yacoby@broadcom.com \
    --cc=william.zhang@broadcom.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).