From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Hans de Goede <hdegoede@redhat.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Lee Jones <lee@kernel.org>, Mark Brown <broonie@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] Backlight for v6.1
Date: Thu, 20 Oct 2022 16:48:49 +0300 [thread overview]
Message-ID: <Y1FRwfeX+ynmHxPm@smile.fi.intel.com> (raw)
In-Reply-To: <e0fb158f-81af-8f3d-5d8b-c4c423feec6c@infradead.org>
On Wed, Oct 19, 2022 at 08:31:33PM -0700, Randy Dunlap wrote:
> On 10/9/22 05:58, Hans de Goede wrote:
> > On 10/9/22 01:23, Linus Torvalds wrote:
> >> On Sat, Oct 8, 2022 at 12:59 PM Hans de Goede <hdegoede@redhat.com> wrote:
...
> >> Because if it depends on some symbols from I2C_DESIGNWARE_PLATFORM,
> >> and that one can be a module, then the Intel PMIC driver also needs to
> >> be built as a module to just get the build coverage, at least.
>
> I don't see intel_soc_pmic_crc.c using any direct calls into
> i2c-designware-platform code. If it calls into it, it must be thru some
> indirect pointers (?).
It's on hardware level, the PMIC is connected to the I²C host controller,
which is Synopsys DesignWare and being services by the respective driver.
Any access to the PMIC's registers requires the I²C to be involved.
What we talked above is even bigger loop, that takes AML code in
the chain.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2022-10-20 13:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-05 12:44 Lee Jones
2022-10-05 17:59 ` Linus Torvalds
2022-10-07 13:16 ` Lee Jones
2022-10-07 18:45 ` Linus Torvalds
2022-10-08 18:30 ` Andy Shevchenko
2022-10-08 19:02 ` Linus Torvalds
2022-10-08 19:59 ` Hans de Goede
2022-10-08 23:23 ` Linus Torvalds
2022-10-09 12:58 ` Hans de Goede
2022-10-20 3:31 ` Randy Dunlap
2022-10-20 13:48 ` Andy Shevchenko [this message]
2022-10-20 13:53 ` Hans de Goede
2022-10-10 7:42 ` Lee Jones
2022-10-05 18:40 ` pr-tracker-bot
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=Y1FRwfeX+ynmHxPm@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=broonie@kernel.org \
--cc=hdegoede@redhat.com \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=torvalds@linux-foundation.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
Powered by JetHome