From: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Olof Johansson <olof@lixom.net>, arm-soc <arm@kernel.org>,
SoC Team <soc@kernel.org>,
Sam Protsenko <semen.protsenko@linaro.org>,
Chanho Park <chanho61.park@samsung.com>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
"moderated list:ARM/SAMSUNG EXYNOS ARM ARCHITECTURES"
<linux-samsung-soc@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Krzysztof Kozlowski <krzk@kernel.org>
Subject: Re: [GIT PULL 1/6] samsung: soc: drivers: for v5.17
Date: Mon, 20 Dec 2021 17:48:52 +0100 [thread overview]
Message-ID: <81b39068-a06f-a4c9-bca7-6fb296d4b05d@canonical.com> (raw)
In-Reply-To: <CAK8P3a1A+6f1OsJ-8-8kbmXXbbsrQZTQywOAy59tJoUmdDN49g@mail.gmail.com>
On 20/12/2021 17:26, Arnd Bergmann wrote:
> On Mon, Dec 20, 2021 at 12:54 PM Krzysztof Kozlowski
> <krzysztof.kozlowski@canonical.com> wrote:
>> ----------------------------------------------------------------
>> Samsung SoC drivers changes for v5.17
>>
>> 1. Exynos ChipID: add Exynos7885 support.
>> 2. Exynos PMU: add Exynos850 support.
>> 3. Minor bindings cleanup.
>> 4. Add Exynos USIv2 (Universal Serial Interface) driver. The USI block is
>> a shared IP block between I2C, UART/serial and SPI. Basically one has
>> to choose which feature the USI block will support and later the
>> regular I2C/serial/SPI driver will bind and work.
>> This merges also one commit with dt-binding headers from my dts64
>> pull request.
>>
>> Together with a future serial driver change, this will break the ABI.
>>
>> Affected: Serial on ExynosAutov9 SADK and out-of-tree ExynosAutov9 boards
>>
>> Why: To properly and efficiently support the USI with new hierarchy
>> of USI-{serial,SPI,I2C} devicetree nodes.
>>
>> Rationale:
>> Recently added serial and USI support was short-sighted and did not
>> allow to smooth support of other features (SPI and I2C). Adding
>> support for USI-SPI and USI-I2C would effect in code duplication.
>> Adding support for different USI versions (currently supported is
>> USIv2 but support for v1 is planned) would cause even more code
>> duplication and create a solution difficult to maintain.
>> Since USI-serial and ExynosAutov9 have been added recently, are
>> considered fresh development features and there are no supported
>> products using them, the code/solution is being refactored in
>> non-backwards compatible way. The compatibility is not broken yet.
>> It will be when serial driver changes are accepted.
>> The ABI break was discussed with only known users of ExynosAutov9 and
>> received their permission.
>
> Thanks a lot for the detailed description, very helpful!
>
> I've applied pull requests 1 through 4, though it seems that once more
> the automated emails did not go out.
>
> I can't find the two defconfig patches you mentioned in the introductory
> mail, neither in patchwork nor in my inbox, I assume these were
> numbered 5/6 and 6/6?
>
Yes, these were patches 5/6 and 6/6 but maybe I made mistakes in address
list. Let me resend them now.
Best regards,
Krzysztof
next prev parent reply other threads:[~2021-12-20 16:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-20 11:53 [GIT PULL 0/6] Samsung " Krzysztof Kozlowski
2021-12-20 11:54 ` [GIT PULL 1/6] samsung: soc: drivers: " Krzysztof Kozlowski
2021-12-20 16:26 ` Arnd Bergmann
2021-12-20 16:48 ` Krzysztof Kozlowski [this message]
2021-12-20 11:55 ` [GIT PULL 2/6] ARM: dts: samsung: " Krzysztof Kozlowski
2021-12-20 11:55 ` [GIT PULL 3/6] arm64: " Krzysztof Kozlowski
2021-12-20 11:55 ` [GIT PULL 4/6] ARM: " Krzysztof Kozlowski
2021-12-20 17:21 ` Krzysztof Kozlowski
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=81b39068-a06f-a4c9-bca7-6fb296d4b05d@canonical.com \
--to=krzysztof.kozlowski@canonical.com \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=chanho61.park@samsung.com \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=olof@lixom.net \
--cc=semen.protsenko@linaro.org \
--cc=soc@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®