From: Carsten Haitzler <carsten.haitzler@foss.arm.com>
To: Sudeep Holla <sudeep.holla@arm.com>, Mark Brown <broonie@kernel.org>
Cc: carsten.haitzler@arm.com, soc@kernel.org,
linux-arm-kernel@lists.infradead.org,
Liviu Dudau <liviu.dudau@arm.com>,
Robin Murphy <robin.murphy@arm.com>
Subject: Re: [PATCH] arm64: defconfig: Enable modules for arm displays
Date: Tue, 10 May 2022 13:34:00 +0100 [thread overview]
Message-ID: <dd43b159-0510-dc78-8ec0-7a52fc3d404a@foss.arm.com> (raw)
In-Reply-To: <20220510120756.gcosdydmccbytmrn@bogus>
On 5/10/22 13:07, Sudeep Holla wrote:
> On Tue, May 10, 2022 at 12:27:50PM +0100, Mark Brown wrote:
>> On Tue, May 10, 2022 at 12:15:45PM +0100, Sudeep Holla wrote:
>>
>>> While at it, can we get these too enabled which are needed on JUNO IIUC.
>>> CONFIG_DRM_I2C_NXP_TDA998X
>>> CONFIG_DRM_I2C_NXP_TDA9950
>>
>>> Liviu/Robin who use HDLCD more than me on Juno can confirm if these are
>>> needed or not. I seem to have these for some HDLCD clock testing using SCMI.
>>
>> Those two, especially TDA998x, are very widely used so should probably
>> just be enabled anyway regardless of what's on Juno.
>
> Indeed, Robin mentioned the same. I am just adding it blindly every time
> I need to test HDLCD without noticing any warnings.
>
Yup - those were already there. I was just adding these for our new
Morello board - all it needed was I2C Cadence enabled as a module and
presto... it "just works". As it's just a module it's not really a bad
"cost" so defconfig additions seemed the right thing to do. Just chasing
up this patch as I sent it earlier this year and it was not merged or
denied... :)
WARNING: multiple messages have this Message-ID (diff)
From: Carsten Haitzler <carsten.haitzler@foss.arm.com>
To: Sudeep Holla <sudeep.holla@arm.com>, Mark Brown <broonie@kernel.org>
Cc: carsten.haitzler@arm.com, soc@kernel.org,
linux-arm-kernel@lists.infradead.org,
Liviu Dudau <liviu.dudau@arm.com>,
Robin Murphy <robin.murphy@arm.com>
Subject: Re: [PATCH] arm64: defconfig: Enable modules for arm displays
Date: Tue, 10 May 2022 13:34:00 +0100 [thread overview]
Message-ID: <dd43b159-0510-dc78-8ec0-7a52fc3d404a@foss.arm.com> (raw)
In-Reply-To: <20220510120756.gcosdydmccbytmrn@bogus>
On 5/10/22 13:07, Sudeep Holla wrote:
> On Tue, May 10, 2022 at 12:27:50PM +0100, Mark Brown wrote:
>> On Tue, May 10, 2022 at 12:15:45PM +0100, Sudeep Holla wrote:
>>
>>> While at it, can we get these too enabled which are needed on JUNO IIUC.
>>> CONFIG_DRM_I2C_NXP_TDA998X
>>> CONFIG_DRM_I2C_NXP_TDA9950
>>
>>> Liviu/Robin who use HDLCD more than me on Juno can confirm if these are
>>> needed or not. I seem to have these for some HDLCD clock testing using SCMI.
>>
>> Those two, especially TDA998x, are very widely used so should probably
>> just be enabled anyway regardless of what's on Juno.
>
> Indeed, Robin mentioned the same. I am just adding it blindly every time
> I need to test HDLCD without noticing any warnings.
>
Yup - those were already there. I was just adding these for our new
Morello board - all it needed was I2C Cadence enabled as a module and
presto... it "just works". As it's just a module it's not really a bad
"cost" so defconfig additions seemed the right thing to do. Just chasing
up this patch as I sent it earlier this year and it was not merged or
denied... :)
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-05-10 12:34 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-09 12:55 [PATCH] arm64: defconfig: Enable modules for arm displays carsten.haitzler
2022-05-09 12:55 ` carsten.haitzler
2022-05-10 11:15 ` Sudeep Holla
2022-05-10 11:15 ` Sudeep Holla
2022-05-10 11:27 ` Mark Brown
2022-05-10 11:27 ` Mark Brown
2022-05-10 11:56 ` Robin Murphy
2022-05-10 11:56 ` Robin Murphy
2022-05-10 12:01 ` Sudeep Holla
2022-05-10 12:01 ` Sudeep Holla
2022-05-10 12:07 ` Sudeep Holla
2022-05-10 12:07 ` Sudeep Holla
2022-05-10 12:34 ` Carsten Haitzler [this message]
2022-05-10 12:34 ` Carsten Haitzler
2022-05-10 14:51 ` Sudeep Holla
2022-05-10 14:51 ` Sudeep Holla
2022-05-10 14:53 ` Carsten Haitzler
2022-05-10 14:53 ` Carsten Haitzler
2022-05-10 12:55 ` Liviu Dudau
2022-05-10 12:55 ` Liviu Dudau
2022-05-10 13:05 ` Mark Brown
2022-05-10 13:05 ` Mark Brown
2022-05-10 14:05 ` Carsten Haitzler
2022-05-10 14:05 ` Carsten Haitzler
2022-05-10 16:19 ` Liviu Dudau
2022-05-10 16:19 ` Liviu Dudau
2022-05-10 16:31 ` Mark Brown
2022-05-10 16:31 ` Mark Brown
2022-05-10 20:06 ` Liviu Dudau
2022-05-10 20:06 ` Liviu Dudau
2022-05-11 13:13 ` Mark Brown
2022-05-11 13:13 ` Mark Brown
2022-05-11 13:15 ` Carsten Haitzler
2022-05-11 13:15 ` Carsten Haitzler
2022-05-11 11:00 ` Carsten Haitzler
2022-05-11 11:00 ` Carsten Haitzler
-- strict thread matches above, loose matches on Subject: below --
2022-04-27 11:42 carsten.haitzler
2022-04-27 11:42 ` carsten.haitzler
2022-05-09 14:34 ` Arnd Bergmann
2022-05-09 14:34 ` Arnd Bergmann
2022-05-10 12:42 ` Carsten Haitzler
2022-05-10 12:42 ` Carsten Haitzler
2022-01-28 10:07 carsten.haitzler
2022-01-28 10:07 ` carsten.haitzler
2022-04-21 12:09 ` Carsten Haitzler
2022-04-21 12:09 ` Carsten Haitzler
2022-04-21 12:18 ` Krzysztof Kozlowski
2022-04-21 12:18 ` 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=dd43b159-0510-dc78-8ec0-7a52fc3d404a@foss.arm.com \
--to=carsten.haitzler@foss.arm.com \
--cc=broonie@kernel.org \
--cc=carsten.haitzler@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=liviu.dudau@arm.com \
--cc=robin.murphy@arm.com \
--cc=soc@kernel.org \
--cc=sudeep.holla@arm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.